Bug#659064: marked as done (libc6 - Includes file in /lib64)
Your message dated Wed, 8 Feb 2012 11:00:44 +0100
with message-id <20120208100044.GA9274@wavehammer.waldi.eu.org>
and subject line Re: Bug#659064: full story
has caused the Debian Bug report #659064,
regarding libc6 - Includes file in /lib64
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.)
--
659064: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659064
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libc6
Version: 2.13-24
Severity: important
libc6 includes the file /lib64/ld-linux-x86-64.so.2. It was decided that
this should not happen, because neither dpkg nor any of the bootstrap
tools handles this properly. See #514015 for further informations.
Bastian
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libc6 depends on:
ii libc-bin 2.13-24
ii libgcc1 1:4.6.2-12
libc6 recommends no packages.
Versions of packages libc6 suggests:
ii debconf [debconf-2.0] 1.5.41
ii glibc-doc <none>
ii locales 2.13-24
-- debconf information excluded
--- End Message ---
--- Begin Message ---
On Wed, Feb 08, 2012 at 10:48:42AM +0100, Aurelien Jarno wrote:
> On Wed, Feb 08, 2012 at 10:42:01AM +0100, Bastian Blank wrote:
> > After that, the OP bootstrapped a Wheezy system over the existing
> > Squeeze root.
> Do we really want to support bootstrapping Wheezy over Squeeze? I expect
> much more problems than that, like libraries installed in the tree but
> not appearing in the dpkg database.
It is not really about supporting it, but about not breaking other stuff
in the process. But frankly speaking, I don't know a way to avoid this,
short of hacking the symlink resolution in tar.
Bastian
--
Violence in reality is quite different from theory.
-- Spock, "The Cloud Minders", stardate 5818.4
--- End Message ---
Reply to: