On Tue, Aug 23, 2005 at 10:48:53AM +0900, Horms wrote:
> On Mon, Aug 22, 2005 at 04:47:14PM -0700, Tony Godshall wrote:
> >
> > Hi.
> >
> > Looks like building the initrd required an upgraded
> > Depends: directly or indirectly to e2fsprogs.
> >
> > Not sure the minimum version required, but I had
> > 1.35-6 when installing linux-image-2.6.12-1-686 failed
> > and 1.38-1.1 when installing linux-image-2.6.12-1-686
> > succeeded.
>
> I'm not sure either. Could you give some more details
> of how it failed with 1.35-6?
What's going on is that ldd running on unstable now produces a
pseudo-entry for linux-gate.so.1:
<[EMAIL PROTECTED]> {/usr/projects/e2fsprogs/e2fsprogs}
521% ldd /usr/lib/e2initrd_helper
linux-gate.so.1 => (0xffffe000)
libext2fs.so.2 => /lib/libext2fs.so.2 (0x46d18000)
libcom_err.so.2 => /lib/libcom_err.so.2 (0x4737c000)
libblkid.so.1 => /lib/libblkid.so.1 (0x46404000)
libuuid.so.1 => /lib/libuuid.so.1 (0x4642b000)
libe2p.so.2 => /lib/libe2p.so.2 (0x463fd000)
libc.so.6 => /lib/tls/libc.so.6 (0x462c3000)
/lib/ld-linux.so.2 (0x462aa000)
It doesn't do this if you run ldd on the exact same binary on sarge:
<[EMAIL PROTECTED]> {/vicepa/home/tytso/src}
733% ldd /tmp/e2initrd_helper
libext2fs.so.2 => /lib/libext2fs.so.2 (0x40021000)
libcom_err.so.2 => /lib/libcom_err.so.2 (0x4003a000)
libblkid.so.1 => /lib/libblkid.so.1 (0x4003d000)
libuuid.so.1 => /lib/libuuid.so.1 (0x40045000)
libe2p.so.2 => /lib/libe2p.so.2 (0x40048000)
libc.so.6 => /lib/libc.so.6 (0x4004e000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
I think it's based on which version of glibc happens to be installed.
So the dependency isn't on e2fsprogs, per-se, but rather that
e2fsprogs's initrd script has to filter out the linux-gate.so.1 entry,
but if you have a newer than a certain glibc, it is incompatible with
e2fsprogs 1.35-2, and you need to upgrade to a newer version of
e2fsprogs.
I originally added the linux-gate.so filtration in response to a bug
filed from the amd64 port, but apparently it is now required for all
platforms given the newer glibc in unstable. The only way to fix this
with dependencies is to ask glibc to add a conflicts with (e2fsprogs <
1.35-7).
- Ted
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
