Bug#334697: apt-listbugs does not show several grave/serious bugs
Hi,
Apologies for my lack of movement on this bug recently, I have become
rather stuck.
I am attaching what I have so far so it does not get lost. It is a
python script that creates the index files used by apt-listbugs from the
output of apt-listbugs. It is in python as perl's LDIF parser doesn't
handle mulitple fields (e.g. debbugsAffected). I'm not sure if ruby
(like the rest of apt-listbugs can do it).
It should not be too difficult to generate the bug files that are also
used from this information as well, I just haven't done it yet as I have
hit a big problem.
I will first outline the current situation.
apt-listbugs is involed by a dpkg hook, and knows what version of the
package it is installing. It then looks in the index files for the
appropriate severities, and finds all bugs that are open against the
package it is considering.
It should then look in the bug report files for the title etc. and
should now look at the versions that it affects, then decide which bugs
to show.
The problem is that the output of bts2ldap has no version number
information, it has fields like
debbugsAffected: testing
and dpkg doesn't tell apt-listbugs what distribution a package is from
(or even know).
As I see it there are three options to deal with this.
1. modify bts2ldap to give a list of versions affected, or at least a
range of affected versions. I don't know if this is
possible/easy/wanted.
2. generate the version information when the index files are created on
the server. This requires a full list about what versions of each
package are in each distribution. Up to date Packages.gz for each
distribution would do, but I don't know if they are available on
merkel. There may be other ways to get this information on that
machine that I don't know about.
3. Do it at run time by doing something like parsing the output of
apt-cache madison. Will be more up to date that the other methods
probably (by hours I guess). However there are problems like you can
have a system that only refers to etch, rather than testing, so you
would need a mapping between them, but that can't be done as far as
I can see. Maybe the mapping could be hosted with the index files,
or the mapping done when they are generated.
So it seems to me like there are lots of problems with this. There are
also things to consider like skew between archive mirrors and the
apt-listbugs information. The user might be installing a version of the
package that apt-listbugs doesn't know about.
It seems like it is going to be very difficult to make apt-listbugs in
its current architecture work with the versioned bts. Maybe a new design
is needed.
It has been pointed out that as it is apt-listbugs is worse that
useless, so I think that unless someone has a good idea then
apt-listbugs should not ship with etch.
This would be a shame, hopefully a fix can be found. I have spent a
while thinking about it now, and I have been unable to come up with one
so far. I will keep thinking, butit would be good to get some help from
somewhere. Any volunteers should feel free to drop me a message to talk
about anything. Oh, and I still have a pacakage that fixes a lot of the
other bugs if anyone decides to adopt/qa upload/NMU.
James
--
James Westby --GPG Key ID: B577FE13-- http://jameswestby.net/
seccure key - (3+)k7|M*edCX/.A:n*N!|7U.L#9E)Tu)T0AM - secp256r1/nistp256
#!/usr/bin/python
# This script creates index files for use with apt-listbugs.
# iIt currently opens a plain text file named 'full' that is the output
# of bts2ldap, but I will add a different method to the front if requested.
#
# Copyright (C) 2006 James Westby [EMAIL PROTECTED]
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License with
# the Debian GNU/Linux distribution in file /usr/share/common-licenses/GPL;
# if not, write to the Free Software Foundation, Inc., 59 Temple Place,
# Suite 330, Boston, MA 02111-1307 USA
#
from ldif import LDIFParser
import sys
from gzip import GzipFile
from apt import Cache
severities = ['wishlist', 'minor', 'normal', 'important', 'serious',
'critical', 'grave']
class BugParser(LDIFParser):
def __init__(self, file):
LDIFParser.__init__(self, file)
self._files = {}
for severity in severities:
fp = GzipFile(index.db-+severity+-new.gz, 'w')
self._files[severity] = fp
self._cache = Cache()
def write_entry(self, severity, entry):
Bug#334697: apt-listbugs does not show several grave/serious bugs
Hi, This is quite difficult to debug with th above reports as it is long past the time when those particular bugs have been closed. Using the current RC bug list it is possible to find some that should currently be shown. While apt-listbugs does poorly on picking them out if the index-* files that it uses are downloaded (-d option can help here to see what it is using) and examined it can be seen that the missed bugs are not in these files. Therefore I think the serious problem may not lie in the logic of apt-listbugs itself, but in whatever creates these index files. Either it's logic is broken, or it is not updated regularly enough. Thanks, James -- James Westby [EMAIL PROTECTED] http://jameswestby.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#334697: apt-listbugs does not show several grave/serious bugs
Le Lun 17 Avril 2006 04:44, Kenshi Muto a écrit : Hi, At Fri, 14 Apr 2006 14:36:39 +0200, Pierre HABOUZIT wrote: On Tue, Apr 11, 2006 at 04:52:28PM +0900, Kenshi Muto wrote: I noticed maintainer's cron script at osdn.d.o.j had stopped since a long time ago by wrong permission. I fixed it and hope this bug is solved. Hi, I'm willing to fix that problem for good, by providing that service on qa.debian.org. Is it possible to have the relevant cron/scripts installed on qa.debian.org. Although I'm not a maintainer and am just a admin of target machine, maintainer's script looks very simple. Maintainer runs cron every hour: rsync -L -vaz --include=*/ --include=*.gz --include=*.status --exclude=* -e ssh merkel.debian.org:apt-listbugs public_html Yes, it means that original database already exists on merkel(aka qa.debian.org):~taru/apt-listbugs. The traffic is about 500,000-900,000 hits per week on our server. haha, that's marvelous. thank you, I think this service will be moved on qa.debian.org for etch, and the load will be transferwd quietly to merkel. tha ! -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgp56nVMKApcs.pgp Description: PGP signature
Bug#334697: apt-listbugs does not show several grave/serious bugs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, At Fri, 14 Apr 2006 14:36:39 +0200, Pierre HABOUZIT wrote: On Tue, Apr 11, 2006 at 04:52:28PM +0900, Kenshi Muto wrote: I noticed maintainer's cron script at osdn.d.o.j had stopped since a long time ago by wrong permission. I fixed it and hope this bug is solved. Hi, I'm willing to fix that problem for good, by providing that service on qa.debian.org. Is it possible to have the relevant cron/scripts installed on qa.debian.org. Although I'm not a maintainer and am just a admin of target machine, maintainer's script looks very simple. Maintainer runs cron every hour: rsync -L -vaz --include=*/ --include=*.gz --include=*.status --exclude=* -e ssh merkel.debian.org:apt-listbugs public_html Yes, it means that original database already exists on merkel(aka qa.debian.org):~taru/apt-listbugs. The traffic is about 500,000-900,000 hits per week on our server. Thanks, - -- Kenshi Muto [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.8 http://mailcrypt.sourceforge.net/ iEYEARECAAYFAkRDAQMACgkQQKW+7XLQPLFQgwCff3Od1zN4bAMmZJkTOTDHpuyG jpQAoKLCMLbUgJd7mfbolRy4ZuxPivNP =bK91 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#334697: apt-listbugs does not show several grave/serious bugs
subscribe 334697 [EMAIL PROTECTED] thanks On Tue, Apr 11, 2006 at 04:52:28PM +0900, Kenshi Muto wrote: I noticed maintainer's cron script at osdn.d.o.j had stopped since a long time ago by wrong permission. I fixed it and hope this bug is solved. Hi, I'm willing to fix that problem for good, by providing that service on qa.debian.org. Is it possible to have the relevant cron/scripts installed on qa.debian.org. could you please send me the relevant bits of it, or post them on that bug entry ? thanks -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org signature.asc Description: Digital signature
Bug#334697: apt-listbugs does not show several grave/serious bugs
tags 334697 + fixed thanks I noticed maintainer's cron script at osdn.d.o.j had stopped since a long time ago by wrong permission. I fixed it and hope this bug is solved. Thanks, -- Kenshi Muto [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#334697: apt-listbugs does not show several grave/serious bugs
tags 334697 -fixed severity 334697 serious thanks On Tue, Apr 11, 2006 at 04:52:28PM +0900, Kenshi Muto wrote: I noticed maintainer's cron script at osdn.d.o.j had stopped since a long time ago by wrong permission. I fixed it and hope this bug is solved. I'm afraid I don't think apt-listbugs is releasable as long as it depends on this external source for bug indices. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Processed: Re: Bug#334697: apt-listbugs does not show several grave/serious bugs
Processing commands for [EMAIL PROTECTED]: tags 334697 -fixed Bug#334697: apt-listbugs does not show several grave/serious bugs Tags were: fixed Tags removed: fixed severity 334697 serious Bug#334697: apt-listbugs does not show several grave/serious bugs Severity set to `serious'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
