From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: "Holger Hoffstätte" <holger@applied-asynchrony.com>,
linux-xfs@vger.kernel.org
Subject: Re: New package locations of xfsprogs vs. xfsdump
Date: Tue, 29 Nov 2016 08:37:09 +1100 [thread overview]
Message-ID: <20161128213709.GC28177@dastard> (raw)
In-Reply-To: <a588c917-945f-30ab-59f6-946a31b96e19@sandeen.net>
On Mon, Nov 28, 2016 at 12:00:12PM -0600, Eric Sandeen wrote:
> On 11/28/16 10:35 AM, Holger Hoffstätte wrote:
> > Hi,
> >
> > I just bumped my xfsprogs on Gentoo to 4.8.0 to use the new download location
> > at kernel.org and noticed that xfsdump is still at sgi.com, even though it has
> > an empty directory at https://www.kernel.org/pub/linux/utils/fs/xfs/xfsdump/.
> >
> > Is xfsdump supposed to be there as well or has that migration just not
> > happened yet? Just asking for packaging reasons.
>
> It's just that there hasn't been a release since the move. New versions
> should land on kernel.org.
>
> I think Dave was looking into rebuilding and re-releasing old versions
> onto kernel.org, but I'm not sure if that has progressed.
No, I haven't made progress on that. Let me see if I've got the
original release tarballs for recent xfsdump releases still around
on my build machine. If I have, then I'll be able to resign and
upload them, otherwise I'll have to spend the time to regenerate
them.
In the mean time, just pull the git tree and set the head to the
release tag, and it will give you the same result...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2016-11-28 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 16:35 New package locations of xfsprogs vs. xfsdump Holger Hoffstätte
2016-11-28 18:00 ` Eric Sandeen
2016-11-28 21:37 ` Dave Chinner [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=20161128213709.GC28177@dastard \
--to=david@fromorbit.com \
--cc=holger@applied-asynchrony.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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).