On Wed, Dec 05, 2007 at 09:24:27AM +0100, Marcus Better wrote:
> ~$ sudo grep -C1 libc6-i686 /var/log/installer/*
> /var/log/installer/syslog-Aug 21 11:26:57 apt-install: Queueing package acpid
> for later installation
> /var/log/installer/syslog:Aug 21 11:26:58 apt-install: Queueing package
> li
Marcus Better a écrit :
> Aurelien Jarno wrote:
>> The file comes from libc6-i686 version 2.6.1-1. According to the symlink
>> it has been installed on 2007-08-21 (ie the date it migrates to
>> testing).
>
> In fact this system was installed on that day.
>
>> Could you please look to /var/log/dpk
Aurelien Jarno wrote:
> The file comes from libc6-i686 version 2.6.1-1. According to the symlink
> it has been installed on 2007-08-21 (ie the date it migrates to
> testing).
In fact this system was installed on that day.
> Could you please look to /var/log/dpkg.log.* if you see a
> mention of l
On Wed, Dec 05, 2007 at 03:03:51AM +, peter green wrote:
> This would seem to indicate that libc6-i686 was previously installed and
> being updated normally but at some point during or after the update to
> 2.6.1-1 it's entry in the dpkg status file completely dissapeared.
Perhaps leaving /v
+++-==-==-
un libc6-i686 (no description available)
The file comes from libc6-i686 version 2.6.1-1. According to the symlink
it has been installed on 2007-08-21 (ie the date it migrates to
testing).
After a bit o
Marcus Better a écrit :
>> this looks rotten, on a machine I have access to (an i386):
>
> Seems the file is from version 2.6.1:
>
> ~$ md5sum /lib/i686/cmov/libc.so.6
> 76e00ba611b3bcb7827bd3f4e3b4930f /lib/i686/cmov/libc.so.6
> ~$ ls -l /lib/i686/cmov/libc.so.6
> lrwxrwxrwx 1 root root 13 20
Marcus Better a écrit :
> Should these files really be on my system if I don't have libc6-i686?
>
> ~$ ls /lib/i686/cmov/
> ld-2.6.1.so libmemusage.so libnss_nis.so.2@
> ld-linux.so.2@libm.so.6@ libpcprofile.so
> libanl-2.6.1.so libnsl-2.
Should these files really be on my system if I don't have libc6-i686?
~$ ls /lib/i686/cmov/
ld-2.6.1.so libmemusage.so libnss_nis.so.2@
ld-linux.so.2@libm.so.6@ libpcprofile.so
libanl-2.6.1.so libnsl-2.6.1.so libpthread-2.6.1.so
> this looks rotten, on a machine I have access to (an i386):
Seems the file is from version 2.6.1:
~$ md5sum /lib/i686/cmov/libc.so.6
76e00ba611b3bcb7827bd3f4e3b4930f /lib/i686/cmov/libc.so.6
~$ ls -l /lib/i686/cmov/libc.so.6
lrwxrwxrwx 1 root root 13 2007-08-21 13:05 /lib/i686/cmov/libc.so.6
> are you using pax execshield or anything like that ?
No, not on this machine.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Tue, Dec 04, 2007 at 02:53:05PM +, Marcus Better wrote:
> > Could you provide an md5sum (or any non too trivial checksum) of
> > /lib/i686/cmov/libc.so.6 ?
>
> 76e00ba611b3bcb7827bd3f4e3b4930f /lib/i686/cmov/libc.so.6
this looks rotten, on a machine I have access to (an i386):
$ dpkg
On Tue, Dec 04, 2007 at 12:57:14PM +, Marcus Better wrote:
> Pierre Habouzit wrote:
> > Could you touch /etc/ld.so.nohwcap and see if it looks like that fixes
> >your system ?
>
> Yes, that fixes it!
okay so there is an issue with the optimized version of the library.
touching /etc/ld.so.n
> Could you provide an md5sum (or any non too trivial checksum) of
> /lib/i686/cmov/libc.so.6 ?
76e00ba611b3bcb7827bd3f4e3b4930f /lib/i686/cmov/libc.so.6
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Pierre Habouzit wrote:
Could you touch /etc/ld.so.nohwcap and see if it looks like that fixes
your system ?
Yes, that fixes it!
Attempting the upgrade again makes the problem re-appear, and the
upgrade fails with the following messages:
Setting up libc6 (2.7-3) ...
dpkg[3484]: segfault at
Aurelien Jarno wrote:
That looks ok. Which kernel are you using?
2.6.24-rc3 when it broke, but using 2.6.23 didn't help. Both are
self-compiled.
Marcus
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Marcus Better a écrit :
> retitle 454266 upgrade to 2.7 fails, leaving system unusable
> notfound 454266 2.7-2
> thanks
>
> Aurelien Jarno wrote:
>> This is clearly a differentl problem than the one that has been
>> reported.
>
> Ok, cloning accordingly.
>
>> What is the state of your system?
>
Processing commands for [EMAIL PROTECTED]:
> retitle 454266 upgrade to 2.7 fails, leaving system unusable
Bug#454266: "upgrade to 2.7 fails, leaving system unusable"
Changed Bug title to `upgrade to 2.7 fails, leaving system unusable' from
`"upgrade to 2.7 fails,
retitle 454266 upgrade to 2.7 fails, leaving system unusable
notfound 454266 2.7-2
thanks
Aurelien Jarno wrote:
This is clearly a differentl problem than the one that has been
reported.
Ok, cloning accordingly.
What is the state of your system?
Serious but stable :-)
If you still have a s
18 matches
Mail list logo
