Your message dated Fri, 16 Nov 2018 14:46:00 -0800
with message-id <[email protected]>
and subject line Re: wpasupplicant: /sbin/wpasupplicant references dyn libs in
/usr/lib .. won't run at boot
has caused the Debian Bug report #537790,
regarding wpasupplicant: /sbin/wpasupplicant references dyn libs in /usr/lib ..
won't run at boot
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
537790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537790
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: wpasupplicant
Version: 0.6.4-3
Severity: normal
ldd /sbin/wpa_supplicant shows that it depends on /usr, which makes
it difficult to square with a boot that has separate / and /usr
partitions, or indeed an nfs mounted /usr. Chicken and egg.
linux-gate.so.1 => (0xffffe000)
libpcsclite.so.1 => /usr/lib/libpcsclite.so.1 (0xb7ff6000)
libssl.so.0.9.8 => /usr/lib/i686/cmov/libssl.so.0.9.8 (0xb7fb0000)
libcrypto.so.0.9.8 => /usr/lib/i686/cmov/libcrypto.so.0.9.8 (0xb7e5d000)
libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0xb7e25000)
libc.so.6 => /lib/libc.so.6 (0xb7ce7000)
libpthread.so.0 => /lib/libpthread.so.0 (0xb7ccf000)
libdl.so.2 => /lib/libdl.so.2 (0xb7cca000)
libz.so.1 => /usr/lib/libz.so.1 (0xb7cb5000)
/lib/ld-linux.so.2 (0xb8012000)
The fix is to move the libraries to /lib, or compile it statically
against those in /usr.
-- System Information
Debian Release: 5.0.2
Kernel Version: Linux pebbles.it.uc3m.es 2.6.30.1-SMP #6 SMP PREEMPT Mon Jul 13
16:57:00 CEST 2009 i686 GNU/Linux
Versions of the packages wpasupplicant depends on:
--- End Message ---
--- Begin Message ---
Control: tag 537790 wontfix
Hi,
> ldd /sbin/wpa_supplicant shows that it depends on /usr, which makes
> it difficult to square with a boot that has separate / and /usr
> partitions, or indeed an nfs mounted /usr. Chicken and egg.
I think it would be fair to close this now, since in addition to
arguments above, we’re likely to have usrmerge by default soon (or
already?) which means /usr/{s,}bin and /{s,}bin will be the same.
--
Cheers,
Andrej
--- End Message ---
