Bug#169361: ITP: apt-listbugs -- Retrieves bugs from BTS and lists them
At Sat, 16 Nov 2002 13:00:20 -0500,
Matt Zimmerman wrote:
> > Hi, I'm writing a tool 'apt-listbugs' which retrieves bugs from
> > the Debian Bug Tracking System and lists them. Especially,
> > apt-listbugs is invoked before each installation by apt
> > in order to check whether the upgrade is safe. If it finds
> > critical bugs, you can stop the installation and save your
> > system. This package should be useful for developers and/or
> > users of sid.
> >
> > Of cource, it's needed that anyone reports the critical bug
> > to BTS to save our own system :)
>
> At what phase of the upgrade will this tool run?
At DPkg::Pre-Install-Pkgs.
The following logs are of current apt-listbugs.
% sudo apt-get install libstdc++2.10-glibc2.2
Reading Package Lists... Done
Building Dependency Tree... Done
1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/130kB of archives. After unpacking 16.4kB will be freed.
Critical bugs of libstdc++2.10-glibc2.2
(#169065) error while loading shared libraries: libstdc++-libc6.2-2.so.3: cannot open shared object file: No such file or directory
(#169063) libstdc++-libc6.2-2.so.3 missing or not symlinked properly
(#169061) Must rename /usr/lib/libstdc++libc6.2-2.so.3 to /usr/lib/libstdc++-libc6.2-2.so.3
(#169060) Possible misnaming of symlink for library name.
(#169059) Bad symbolic link to libstdc++-3libc6.2-2-2.10.0.so
(#169042) Upgrading libstdc++ breaks lots of stuff
(#160977) suck: Broken handling of per-host configuration with the option -AL
Grave bugs of libstdc++2.10-glibc2.2
(#169072) base: typo in library-dependencies for glibc
Are you sure to install/upgrade these packages? [Y/n] n
E: Sub-process /usr/sbin/apt-listbugs --apt -c returned an error code (1)
E: Failure running script /usr/sbin/apt-listbugs --apt -c
According to BTS (currently it needs to use other programs like querybts),
these bugs are fixed in 1:2.95.4-15.
vass% LANG=C sudo apt-get install libstdc++2.10-glibc2.2=1:2.95.4-15
Reading Package Lists... Done
Building Dependency Tree... Done
1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/130kB of archives. After unpacking 16.4kB will be freed.
Critical bugs of libstdc++2.10-glibc2.2
(#169065) error while loading shared libraries: libstdc++-libc6.2-2.so.3: cannot open shared object file: No such file or directory
(#169063) libstdc++-libc6.2-2.so.3 missing or not symlinked properly
(#169061) Must rename /usr/lib/libstdc++libc6.2-2.so.3 to /usr/lib/libstdc++-libc6.2-2.so.3
(#169060) Possible misnaming of symlink for library name.
(#169059) Bad symbolic link to libstdc++-3libc6.2-2-2.10.0.so
(#169042) Upgrading libstdc++ breaks lots of stuff
(#160977) suck: Broken handling of per-host configuration with the option -AL
Grave bugs of libstdc++2.10-glibc2.2
(#169072) base: typo in library-dependencies for glibc
Are you sure to install/upgrade these packages? [Y/n]
(Reading database ... 55925 files and directories currently installed.)
Preparing to replace libstdc++2.10-glibc2.2 1:2.95.4-12 (using .../libstdc++2.10-glibc2.2_1%3a2.95.4-15_i386.deb) ...
Unpacking replacement libstdc++2.10-glibc2.2 ...
Setting up libstdc++2.10-glibc2.2 (2.95.4-15) ...
Once I upgrade the package, some bugs are no longer displayed.
vass% sudo apt-get --reinstall install libstdc++2.10-glibc2.2
Reading Package Lists... Done
Building Dependency Tree... Done
0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0B/130kB of archives. After unpacking 0B will be used.
Do you want to continue? [Y/n]
Critical bugs of libstdc++2.10-glibc2.2
(#169042) Upgrading libstdc++ breaks lots of stuff
(#160977) suck: Broken handling of per-host configuration with the option -AL
Grave bugs of libstdc++2.10-glibc2.2
(#169072) base: typo in library-dependencies for glibc
Are you sure to install/upgrade these packages? [Y/n]
> How will it determine whether the bug actually applies to the version of the
> package being installed? Or will it rely on the user's manual review to
> approve every package?
apt-listbugs does a non-accurate analysis to determine that the bug applies
to the version. This tool is expected to save many machines from broken
packages and not to flood many bug reports which is the same bug as many as
possible.
In upgrade phase, the following situations are under considerations:
submit current new
--------------------------------->
In above situation, you have already gotten the bug -> not care.
(submit means the version where the bug has been submitted)
You can select whether apt-listbugs list it or not. It doesn't
list it by default.
current new submit
--------------------------->
In above situaion, the new package maybe doesn't have the bug yet.
You can select whether apt-listbugs list it or not. It doesn't list
it by default.
current submit new
--------------------------->
In above situation, the new package may have the bug (it may be
fixed and still archived in BTS).
Currently apt-listbugs lists it.
I guess the above simple algorithm can probe most of critical
(I mean this is not a term of serverity) bugs.
apt-listbugs isn't a tool that lists accurate bugs that actually
apply to the version, but that warns that the version may have
critical bugs. At least it's useful for me.
Thanks
Reply to: