From: Aurelien Jarno <aurelien@aurel32.net>
To: Dave Chinner <david@fromorbit.com>
Cc: 553875@bugs.debian.org, XFS Development Team <xfs@oss.sgi.com>
Subject: Bug#553875: replacing libreadline5-dev build dependency with libreadline-dev
Date: Mon, 22 Aug 2011 08:03:39 +0200 [thread overview]
Message-ID: <20110822060339.GA28146@hall.aurel32.net> (raw)
In-Reply-To: <20110821232913.GA3162@dastard>
On Mon, Aug 22, 2011 at 09:29:13AM +1000, Dave Chinner wrote:
> On Sun, Aug 21, 2011 at 12:01:23AM +0200, Aurelien Jarno wrote:
> > Hi,
> >
> > I have just done an NMU of xfsprogs to fix this longstanding issue. You
> > will find below the diff of the NMU.
>
> That was resolved in the upstream repository back in April:
But never uploaded to Debian, where the package has been unbuildable
for months due to this issue.
> commit 9de4c6df018f029d9266536a0ae961929a4a76ae
> Author: Nathan Scott <nathans@aconex.com>
> Date: Thu Apr 28 23:15:30 2011 +0000
>
> xfsprogs: resolve Debian readline build issue
>
> Address the recently reported build issue with libreadline5/6, via
> the gplv2 route. Since this appears to be a relatively recent pkg,
> I made its use conditional so the deb build continues to work for
> everyone not running a bleeding edge distro. Works For Me (tm).
>
> This addresses Debian bug 553875: libreadline5-dev removal pending
>
> Signed-off-by: Nathan Scott <nathans@debian.org>
> Signed-off-by: Alex Elder <aelder@sgi.com>
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@fromorbit.com
>
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-08-22 6:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-20 22:01 Bug#553875: replacing libreadline5-dev build dependency with libreadline-dev Aurelien Jarno
2011-08-21 23:29 ` Dave Chinner
2011-08-22 6:03 ` Aurelien Jarno [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=20110822060339.GA28146@hall.aurel32.net \
--to=aurelien@aurel32.net \
--cc=553875@bugs.debian.org \
--cc=david@fromorbit.com \
--cc=xfs@oss.sgi.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