Package: eatmydata
Version: 82-2
Severity: important
When I run cowbuilder --update on a wheezy chroot, I now get
dozens of messages like:
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnux32/libeatmydata.so' from
LD_PRELOAD cannot be preloaded: ignored.
This is apparently because the eatmydata sets LD_PRELOAD from
outside the chroot, which gets inherited, but cannot be solved
from inside the chroot (especially as the M-A paths differ, as
I have x32, i386 *and* amd64 chroots).
To add insult to injury, eatmydata is *still* not M-A safe, as
can easily be seen here:
tglase@tglase:~ $ eatmydata bzip2 -h 2>&1 | head -2
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnux32/libeatmydata.so' from
LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored.
bzip2, a block-sorting file compressor. Version 1.0.6, 6-Sept-2010.
ii bzip2 1.0.6-7 i386 high-quality
block-sorting file compressor - ut
ii eatmydata 82-2 all Library and utilities
designed to disable fsync
ii libeatmydata1:i386 82-2 i386 Library and utilities
to disable fsync and frie
ii libeatmydata1:x32 82-2 x32 Library and utilities
to disable fsync and frie
(My host system is x32.)
So, running “eatmydata foo” *still* does not properly load the
libeatmydata.so required for foo’s architecture. (Even if it did,
“foo” may run “bar”, which can be yet *another* architecture, in
a subshell.)
To make things short, the M-A changes do not help anything but
add breakage. Sorry about that.
-- System Information:
Debian Release: jessie/sid
APT prefers unreleased
APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable')
Architecture: x32 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Versions of packages eatmydata depends on:
ii dpkg-dev 1.17.18
ii libeatmydata1 82-2
eatmydata recommends no packages.
eatmydata suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
