linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ted Ts'o <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: Eric Sandeen <esandeen@redhat.com>,
	Phillip Susi <psusi@ubuntu.com>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: E2fsprogs 1.42.1 release
Date: Mon, 20 Feb 2012 14:18:20 -0500	[thread overview]
Message-ID: <20120220191820.GB6541@thunk.org> (raw)
In-Reply-To: <4F4298A0.1000900@redhat.com>

On Mon, Feb 20, 2012 at 01:01:52PM -0600, Eric Sandeen wrote:
> > The tarball is a little messed up:
> > 
> > [esandeen@neon e2fsprogs]$ tar xvzf e2fsprogs-1.42.1.tar.gz
> > e2fsprogs-libs-1.42.1/
> > e2fsprogs-libs-1.42.1/.gitignore
> > e2fsprogs-libs-1.42.1/.release-checklist
> > e2fsprogs-libs-1.42.1/lib/
> > 
> > why does it unpack into e2fsprogs-libs-1.42.1?
> >                                   ^^^^
> > 
> > I could work around that but it's unexpected.
> 
> Oh actually I can't work around it, it really is just the libs.

Whoops, kup screwup.  I uploaded e2fsprogs-1.42.tar.gz and
e2fsprogs-libs-1.42.tar.gz.... into the same destination file.  I just
fixed it on master.kernel.org; it should propagate over in 15 minutes
or so.

Or you can grab the files from sourceforge.  (Note that the
sourceforge tarballs are actually signed by me.  In contrast the
kernel.org tarballs are signed by the ftp.kernel.org machine key, and
the signature covers the uncompressed tar file.  That way they can use
the same signature file for the tar.gz and tar.bz2 tarball.)

    	 	   	    	       	   	   - Ted

      reply	other threads:[~2012-02-20 19:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-18  3:00 e2fsck and backup superblocks Phillip Susi
2012-02-18  3:05 ` Eric Sandeen
2012-02-18 22:31   ` Ted Ts'o
2012-02-20  3:11     ` Eric Sandeen
2012-02-20  3:19       ` E2fsprogs 1.42.1 release Ted Ts'o
2012-02-20 18:59         ` Eric Sandeen
2012-02-20 19:01           ` Eric Sandeen
2012-02-20 19:18             ` Ted Ts'o [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120220191820.GB6541@thunk.org \
    --to=tytso@mit.edu \
    --cc=esandeen@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=psusi@ubuntu.com \
    --cc=sandeen@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).