[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ls, cp, mv etc. in sid kaputt



Moin,

On Mon, 2006-12-18 at 16:14 +0100, Marc Schröder wrote:
> Hallo,
> 
> habe bei sämtlichen file operationen in sid momentan folgende fehlermeldung:
> 
> sr-3:/# ls /tmp/ -lh
> ls: relocation error: /lib/libacl.so.1: symbol getxattr, version
> ATTR_1.0 not defined in file libattr.so.1 with link time reference
> 
> kann das jemand bestätigen?
> kann jemand den grund nennen?
> kommen da noch neue pakete für libattr1?
> 
> 
> sr-3:/# apt-cache policy libattr1 libacl1
> libattr1:
>   Installed: 2.4.35-1
>   Candidate: 2.4.35-1
>   Version table:
>  *** 2.4.35-1 0
>         500 http://ftp.debian.org sid/main Packages
>         100 /var/lib/dpkg/status

Und genau dafür gibt es auch "apt-listbugs", das mich heute morgen davor
warnte:
----------------------8<----------------------
xxx:~# apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
[...]
The following packages will be upgraded:
  libacl1 libattr1
2 upgraded, 0 newly installed, 0 to remove and 8 not upgraded.
Need to get 0B/23.8kB of archives.
After unpacking 4096B disk space will be freed.
Do you want to continue [Y/n]?
Reading package fields... Done
Reading package status... Done
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
critical bugs of libattr1 (2.4.32-1 -> 2.4.35-1) <done>
 #403601 - tex-common: unable to install because of cp (Fixed:
attr/1:2.4.32-1.1)
   Merged with: 403592
 #403585 - Regression in 2.4.35-1 (Fixed: attr/1:2.4.32-1.1)
 #403599 - Regression in 2.2.42-1 (Fixed: 1:2.4.32-1.1)
grave bugs of libattr1 (2.4.32-1 -> 2.4.35-1) <done>
 #403645 - libattr1: kdeinit fails to start (Fixed: 1:2.4.32-1.1)
serious bugs of libattr1 (2.4.32-1 -> 2.4.35-1) <done>
 #403590 - ls -l does not work any longer (Fixed: attr/1:2.4.32-1.1)
Summary:
 libattr1(5 bugs)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...]
----------------------8<----------------------

Und da waren sie noch als <pending> statt <done> beschrieben. Super
Tool!

Gruß
Amir



Reply to: