From: Scott James Remnant <scott@ubuntu.com>
To: Theodore Tso <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, util-linux-ng@vger.kernel.org
Subject: Re: [PATCH] configure: Disable libblkid by default
Date: Sun, 19 Jul 2009 15:59:21 +0100 [thread overview]
Message-ID: <1248015561.4524.26.camel@quest> (raw)
In-Reply-To: <20090719115617.GF2416@mit.edu>
[-- Attachment #1: Type: text/plain, Size: 1774 bytes --]
On Sun, 2009-07-19 at 07:56 -0400, Theodore Tso wrote:
> > > > I've done the packaging for him, it's just waiting on him to get back
> > > > home to sponsor the uploads.
> > >
> > > Are the .deb packages somewhere where I can examine them?
> > >
> > Yes, they're in Ubuntu.
>
> I just took a quick look at them, and it appears that they are missing
> the libblkid1-dbg, libuuid1-dbg, and uuid-runtime-dbg packages.
>
We auto-generate debug packages for all binaries in Ubuntu, extracted
from the compiler, e.g.:
http://ddebs.ubuntu.com/pool/main/u/util-linux/libblkid1-dbgsym_2.16-1ubuntu1_i386.ddeb
Since I'm not a Debian maintainer, I don't know how such things are done
in Debian so left this for you and/or Lamont to fill in.
> Also, apparently no once noticed until now, but there's a bug in the
> util-linux-ng's uuid.sym file. The uuid_pack and uuid_unpack symbols
> are missing, because someone forgot to include them in the uuid.sym
> file. The debian symbol generation system which I see you carefully
> moved over detected the problem, but you apparently didn't take a
> close enough look at its output to detect the warning messages.
>
I just copied the symbols file over and applied the update your output
said.
> BTW, **why** is util-linux-ng gratuitously introducing backwards
> incompatibility such that packages built with util-linux-ng won't work
> with the older shared libraries? There's no reason to do this.
>
> There is a hint in the (obsolete) comments in uuid.sym that suggests a
> reason why, but it's not justified for libuuid:
>
You'd have to ask Karel about that one.
However I think now it's happened, we shouldn't back it out again.
Scott
--
Scott James Remnant
scott@ubuntu.com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-07-19 14:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 18:46 [PATCH] configure: Disable libblkid by default Scott James Remnant
[not found] ` <E1MRWBp-0000yN-9a-eEhpo0tUqaMrEHDPZeG1zdBPR1lH4CV8@public.gmane.org>
2009-07-17 14:36 ` Theodore Tso
[not found] ` <20090717143637.GM8508-3s7WtUTddSA@public.gmane.org>
2009-07-17 14:54 ` Scott James Remnant
2009-07-17 15:02 ` Theodore Tso
2009-07-17 15:14 ` Scott James Remnant
2009-07-19 11:56 ` Theodore Tso
2009-07-19 14:59 ` Scott James Remnant [this message]
2009-07-19 21:27 ` Karel Zak
[not found] ` <20090719212714.GA6886-sHeGUpI7y9L/9pzu0YdTqQ@public.gmane.org>
2009-07-20 14:23 ` Theodore Tso
2009-07-20 14:26 ` Christoph Hellwig
[not found] ` <20090720142337.GH2416-3s7WtUTddSA@public.gmane.org>
2009-07-20 14:37 ` Scott James Remnant
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=1248015561.4524.26.camel@quest \
--to=scott@ubuntu.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=util-linux-ng@vger.kernel.org \
/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).