Bug#626082: marked as done (apt: rred segfault at ... error 6 in libc-2.7.so)
Your message dated Mon, 9 May 2011 11:08:33 +0200
with message-id <BANLkTikWxnnwr4YhPpuEZpgK5_Vks_oMPw@mail.gmail.com>
and subject line Re: Bug#626082: apt: rred segfault at ... error 6 in libc-2.7.so
has caused the Debian Bug report #626082,
regarding apt: rred segfault at ... error 6 in libc-2.7.so
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.)
--
626082: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626082
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: apt
Version: 0.7.20.2+lenny2
Severity: normal
May 8 16:57:50 debian kernel: [32789607.458747] rred[3134]: segfault at
bf7fefd4 ip b74d724f sp bf7fefd8 error 6 in libc-2.7.so[b746d000+155000]
This is, AFAICT, a consequence of:
http://lists.debian.org/debian-devel-announce/2011/03/msg00015.html
I do agree, it is a somwhat extreme situation: oldstable with pinned
unstable. For me useful, as I can easily look att package version numbers
and descriptions. Historically, I also used this to port newer package
versions to lenny. That is harder to do now, but not impossible.
Workaround is to remove 'unstable' from sources.list.
Eventually, I will upgrade to squeeze and try to reinstate pinned unstable.
-- Package-specific info:
-- /etc/apt/preferences --
Package: *
Pin: release a=unstable
Pin-Priority: 99
-- System Information:
Debian Release: 5.0.8
APT prefers oldstable
APT policy: (500, 'oldstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE= (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages apt depends on:
ii debian-archive-keyring 2010.08.28~lenny1 GnuPG archive keys of the Debian a
ii libc6 2.7-18lenny7 GNU C Library: Shared libraries
ii libgcc1 1:4.3.2-1.1 GCC support library
ii libstdc++6 4.3.2-1.1 The GNU Standard C++ Library v3
apt recommends no packages.
Versions of packages apt suggests:
ii apt-doc 0.7.20.2+lenny2 Documentation for APT
ii aptitude 0.4.11.11-1~lenny1 terminal-based package manager
ii bzip2 1.0.5-1+lenny1 high-quality block-sorting file co
ii dpkg-dev 1.14.31 Debian package development tools
ii lzma 4.43-14 Compression method of 7z format in
ii python-apt 0.7.7.1+nmu1 Python interface to libapt-pkg
ii synaptic 0.62.1+nmu1 Graphical package manager
-- no debconf information
Cheers,
--
Cristian
--- End Message ---
--- Begin Message ---
Version: 0.7.25.1
On Sun, May 8, 2011 at 18:45, Cristian Ionescu-Idbohrn
<cristian.ionescu-idbohrn@axis.com> wrote:
> May 8 16:57:50 debian kernel: [32789607.458747] rred[3134]: segfault at
> bf7fefd4 ip b74d724f sp bf7fefd8 error 6 in libc-2.7.so[b746d000+155000]
>
> This is, AFAICT, a consequence of:
>
> http://lists.debian.org/debian-devel-announce/2011/03/msg00015.html
Thanks for your bugreport: You are right, its caused by the switch of
the Metadata creator tools as they change the order of fields and therefore
the diff is unusually big (more than 5MB of compressed data).
We had something similar in #554349 and friends, so i think this is
fixed in everything, but oldstable now, so i am closing it.
(Its to unusual to ratify an oldstable upgrade - and user hit by it now
doesn't get the update anyway)
After your workaround (an 'apt-get update' will remove the 'old' Packages
file) it should be possible to add unstable again (a following
'apt-get update' will download a fresh Packages file instead of trying to
download pdiffs) and work with it as usual.
If it's not fixed feel free to reopen the bug, of course.
Best regards
David Kalnischkies
--- End Message ---
Reply to: