On Mon, Feb 28, 2011 at 16:40 +0100, dirkydirk wrote: > On Mon, 2011-02-28 at 15:17 +0000, Wolodja Wentland wrote: > > On Mon, Feb 28, 2011 at 15:37 +0100, dirkydirk wrote:
> > Which version of libc-bin do you have installed (dpkg -l libc-bin). If you > > have 2.11.2-12 you might have run into [...] > > [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%23615806#10 > That's it! Pulled version 2.11.2-13 of the libc-involved libraries, run > dpkg-reconfigure linux-image-2.6.37-1-amd64 to generate a new ramdisc > and it works! Wonderful :) > P.S. Heard about apt-listbugs the 1st time, installed it but it seems to > have an issue itself: > apt-listbugs apt > > E: apt Pre-Install-Pkgs is not giving me expected 'VERSION 2' string. I have never attempted to run apt-listbugs manually. It is typically automatically invoked during the install/upgrade process and queried for applicable bugs for the packages you are about to install/upgrade. If there are indeed serious or grave bugs that apply to one of these packags, you can choose to abort the installation altogether or pin selected packages to the version you have installed. While we are at it, another useful tool that is comparable to apt-listbugs is apt-listchanges, which will bring important changes to your attention. A quick look at the manpage reveals that you have to specify one of the supported commands. Let's try "list": $ apt-listbugs list apt/0.8.11.5 serious bugs of apt (0.8.11.5 -> 0.8.11.5) <unfixed> #558784 - apt: re-adds removed keys Summary: apt(1 bug) voilà! -- .''`. Wolodja Wentland <wolodja.wentl...@ed.ac.uk> : :' : `. `'` 4096R/CAF14EFC `- 081C B7CD FF04 2BA9 94EA 36B2 8B7F 7D30 CAF1 4EFC
signature.asc
Description: Digital signature
