Your message dated Thu, 18 Dec 2014 16:46:07 +0100
with message-id <5492f6bf.2040...@debian.org>
and subject line Re: smartmontools throws errors even after the binNMU
has caused the Debian Bug report #728113,
regarding _dl_check_map_versions: Assertion `needed != ((void *)0)' failed!
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 ow...@bugs.debian.org
immediately.)


-- 
728113: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728113
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libselinux1
Version: 2.2-1
Severity: critical
Justification: breaks unrelated software

Hi!

The recent upgrade auf libselinux1 to version 2.2-1 in unstable causes
smartctl and smartd to fail with the following message:

system:~# smartctl
Inconsistency detected by ld.so: dl-version.c: 224: _dl_check_map_versions: 
Assertion `needed != ((void *)0)' failed!

Downgrading libselinux1 to 2.1.13-3 solves the problem.

So far only smartctl/smartd is affected, but since this bug affects an
unrelated package, the severity of critical seems correct.

Please also see and maybe merge bug #728507 against smartmontools.

Grüße,
Sven.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (600, 'unstable'), (500, 'experimental'), (400, 'testing')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 3.11-1-amd64 (SMP w/12 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message ---
[please always write to the bug report, not just to control@]

the binNMU was wrong, not using the most recent version of binutils. Please
check again, and maybe update selinux as well. Closing the bug for now.

--- End Message ---

Reply via email to