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

Bug#671715: marked as done (libc6: Fail to upgrade from 2.13-27 to newer version !)



Your message dated Sun, 1 Jul 2012 14:01:34 +0200
with message-id <20120701120134.GB10734@ohm.aurel32.net>
and subject line Re: Bug#671715: libc6: Fail to upgrade from 2.13-27 to newer version !
has caused the Debian Bug report #671715,
regarding libc6: Fail to upgrade from 2.13-27 to newer version !
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 owner@bugs.debian.org
immediately.)


-- 
671715: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671715
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.13-27
Severity: important

Dear Maintainer,

   * What led up to the situation?
My system (debian/testing) is using 2.13-27 version of libc6 and I'm trying to
upgrade to the current testing version...

   * What exactly did you do (or not do) that was effective (or
     ineffective)?
I'm trying to do an "aptitude install libc6"

   * What was the outcome of this action?
It didn't finish well, I obtain the following messages :
A copy of the C library was found in an unexpected directory:
  '/lib/x86_64-linux-gnu/libc-2.13.so'
It is not safe to upgrade the C library in this situation;
please remove that copy of the C library or get it out of
'/lib/x86_64-linux-gnu' and try again.

   * What outcome did you expect instead?
An upgrade without problem !

I have tryied :
 - to move that file -> nothing work after that so I cannot redo the upgrade !
 - to use a rescue CD (PartedMagic), chroot the environement and try to force
the upgrade, but I get the same result !

Is there any solution to make the upgrade happen without reinstalling the whole
system ?

Regards

Mourad



-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.3.0-trunk-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libc6 depends on:
ii  libc-bin  2.13-32
ii  libgcc1   1:4.7.0-3

libc6 recommends no packages.

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.42
ii  glibc-doc              <none>
ii  locales                2.13-32

-- debconf information:
  glibc/upgrade: true
  glibc/disable-screensaver:
  glibc/restart-failed:
  glibc/restart-services:
  libraries/restart-without-asking: false



--- End Message ---
--- Begin Message ---
On Sat, Jun 30, 2012 at 10:00:02AM +0200, newbeewan wrote:
> On 30/06/2012 01:27, Aurelien Jarno wrote:
> >On Wed, May 23, 2012 at 07:07:05PM +0200, Aurelien Jarno wrote:
> >>On Sun, May 06, 2012 at 11:14:56AM +0200, Mourad Jaber wrote:
> >>>Package: libc6
> >>>Version: 2.13-27
> >>>Severity: important
> >>>
> >>>Dear Maintainer,
> >>>
> >>>    * What led up to the situation?
> >>>My system (debian/testing) is using 2.13-27 version of libc6 and I'm trying to
> >>>upgrade to the current testing version...
> >>>
> >>>    * What exactly did you do (or not do) that was effective (or
> >>>      ineffective)?
> >>>I'm trying to do an "aptitude install libc6"
> >>>
> >>>    * What was the outcome of this action?
> >>>It didn't finish well, I obtain the following messages :
> >>>A copy of the C library was found in an unexpected directory:
> >>>   '/lib/x86_64-linux-gnu/libc-2.13.so'
> >>>It is not safe to upgrade the C library in this situation;
> >>>please remove that copy of the C library or get it out of
> >>>'/lib/x86_64-linux-gnu' and try again.
> >>>
> >>>    * What outcome did you expect instead?
> >>>An upgrade without problem !
> >>>
> >>>I have tryied :
> >>>  - to move that file ->  nothing work after that so I cannot redo the upgrade !
> >>>  - to use a rescue CD (PartedMagic), chroot the environement and try to force
> >>>the upgrade, but I get the same result !
> >>>
> >>>Is there any solution to make the upgrade happen without reinstalling the whole
> >>>system ?
> >>>
> >>This looks like your dpkg database is corrupted, or at least not in sync
> >>with the files installed in your system. Can you please provide us the
> >>contents of all the files named /var/lib/dpkg/info/libc6*.list ?
> >>
> >Ping ?
> Sorry for the lack of response !
> 
> Unfortunately I have reinstalled the system using the CUT
> installation CD (http://cut.debian.net/) and it works like a charm !
> 
> I received your first mail just after my reinstall and I haven't any copy of the old /var :(
> 
> I think you can close that bug.

Ok, thanks for the answer, doing that with this mail.

> I will reopen it if it happened again and in that case I will save
> the /var/lib to have some post mortem datas.

Ok, though I hope it won't happen to you again.

Aurelien

-- 
Aurelien Jarno                          GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net


--- End Message ---

Reply to: