Re: ITP: buglist?
On Mon, 4 Oct 1999, Joey Hess wrote: Thomas Schoepf wrote: Have you tried Ben's getbugs.pl? Is it good enough? I looked at it briefly, but it seemsed very slow. wget is easier. I get: Error: IO::Socket::INET: Connection refused (use --help for usage) ... any comments? Ben? (I am most definitely, NOT a perl guru.) Michael Beattie ([EMAIL PROTECTED]) - Of all the things I have lost, I miss my mind the most! - Debian GNU/Linux Ooohh You are missing out!
Re: ITP: buglist?
On Tue, Oct 05, 1999 at 04:36:58PM +1300, Michael Beattie wrote: On Mon, 4 Oct 1999, Joey Hess wrote: Thomas Schoepf wrote: Have you tried Ben's getbugs.pl? Is it good enough? I looked at it briefly, but it seemsed very slow. wget is easier. I get: Error: IO::Socket::INET: Connection refused (use --help for usage) Yeah, my ldap server died :) Should work now though. Ben
ITP: buglist?
Hi, this is a perl script I've written, because I was fed up with manually fetching bug reports and storing them into a directory structure so that browsing still works. Now, when I type 'buglist -r -d ~/debian/Bugs less', all reports regarding 'less' are saved into ~/debian/Bugs, structured as they are on the BTS, so I can easily click through the reports. I'm also able to download individual reports: 'buglist 42610'. I'm posting this because I'd like to know whether there's popular interest in this script or if I'm just so egocentric that I just think, everything I use would be useful for everyone else ;) Package: buglist Priority: extra Section: utils Installed-Size: 18 Maintainer: Thomas Schoepf [EMAIL PROTECTED] Version: 0.1 Depends: perl5, libwww-perl Description: Download bug reports from the Debian BTS buglist can download individual bug reports from the Bug Tracking System based on package names or bug numbers. But it is also able to fetch all bug reports filed against packages and let's you store them on your local filesystem. Proxy servers are supported. Thomas -- GnuPG: ID=B0FA4F49, http://www.in.tum.de/~schoepf/gpgkey.txt Fingerprint: FA38 2D7E 408F 61E4 BF49 B48F 04BD F5BE B0FA 4F49 PGP 2: ID=2EA7BBBD, http://www.in.tum.de/~schoepf/pgpkey.txt Fingerprint: 08 96 1F CD AD 55 03 0F 95 92 B0 F2 04 32 4B 52 pgp3PdOHQmRQY.pgp Description: PGP signature
Re: ITP: buglist?
Thomas Schoepf wrote: this is a perl script I've written, because I was fed up with manually fetching bug reports and storing them into a directory structure so that browsing still works. Now, when I type 'buglist -r -d ~/debian/Bugs less', all reports regarding 'less' are saved into ~/debian/Bugs, structured as they are on the BTS, so I can easily click through the reports. I'm also able to download individual reports: 'buglist 42610'. I'm interested in this. I have occasionally been disconnected from the network for days while traveling; getting a mirror of your pages on the BTS so you can work on bugs during that time is a little annoying. -- see shy jo
Re: ITP: buglist?
On Sun, Oct 03, 1999 at 05:35:11PM -0700, Joey Hess wrote: Thomas Schoepf wrote: this is a perl script I've written, because I was fed up with manually fetching bug reports and storing them into a directory structure so that browsing still works. Now, when I type 'buglist -r -d ~/debian/Bugs less', all reports regarding 'less' are saved into ~/debian/Bugs, structured as they are on the BTS, so I can easily click through the reports. I'm also able to download individual reports: 'buglist 42610'. I'm interested in this. I have occasionally been disconnected from the network for days while traveling; getting a mirror of your pages on the BTS so you can work on bugs during that time is a little annoying. On the same subject I invite everyone to test out getbugs which is at http://www.debian.org/~bcollins/getbugs.pl. It's a Net::LDAP script that interfaces to the BTS directly (no waiting for the bugs to be generated), and it also has some nice features. Run it with --help on first exec. Some common incantations: getbugs -c debian/control This will download a summary of all the bugs for the packages in the control file. getbugs -b 2 report This will page the output of the bug report to your screen getbugs -p foo This will get a summary for all the bugs in package foo getbugs -x -i This will recursively search for debian/control files and download summaries for all the bug reports in all the packages in all the control files it finds (from cwd). The -x makes it output some statistics (total bugs in each severity, total RC bugs...). The -i option makes it not keep closed bugs. Make sure you have the libnet-ldap-perl package installed. I'll accept requests for features, but I'm sure that alot of them I've already thought of and plan to implement. Ben pgpQuFRcTGbIV.pgp Description: PGP signature
Re: ITP: buglist?
On Sun, Oct 03, 1999 at 09:13:56PM -0400, Ben Collins wrote: On the same subject I invite everyone to test out getbugs which is at http://www.debian.org/~bcollins/getbugs.pl. It's a Net::LDAP script that This needs a direct connection, right? I'm behind a firewall :( Thomas -- GnuPG: ID=B0FA4F49, http://www.in.tum.de/~schoepf/gpgkey.txt Fingerprint: FA38 2D7E 408F 61E4 BF49 B48F 04BD F5BE B0FA 4F49 PGP 2: ID=2EA7BBBD, http://www.in.tum.de/~schoepf/pgpkey.txt Fingerprint: 08 96 1F CD AD 55 03 0F 95 92 B0 F2 04 32 4B 52 pgpa0EXSQUlVq.pgp Description: PGP signature
Re: ITP: buglist?
On Mon, Oct 04, 1999 at 12:08:13PM +0200, Thomas Schoepf wrote: On Sun, Oct 03, 1999 at 09:13:56PM -0400, Ben Collins wrote: On the same subject I invite everyone to test out getbugs which is at http://www.debian.org/~bcollins/getbugs.pl. It's a Net::LDAP script that This needs a direct connection, right? I'm behind a firewall :( I'm using it behind a firewall, not sure how yours is configured. Ben
Re: ITP: buglist?
On Sun, Oct 03, 1999 at 05:35:11PM -0700, Joey Hess wrote: Thomas Schoepf wrote: this is a perl script I've written, because I was fed up with manually fetching bug reports and storing them into a directory structure so that browsing still works. Now, when I type 'buglist -r -d ~/debian/Bugs less', all reports regarding 'less' are saved into ~/debian/Bugs, structured as they are on the BTS, so I can easily click through the reports. I'm also able to download individual reports: 'buglist 42610'. I'm interested in this. I have occasionally been disconnected from the network for days while traveling; getting a mirror of your pages on the BTS so you can work on bugs during that time is a little annoying. Have you tried Ben's getbugs.pl? Is it good enough? Thomas -- GnuPG: ID=B0FA4F49, http://www.in.tum.de/~schoepf/gpgkey.txt Fingerprint: FA38 2D7E 408F 61E4 BF49 B48F 04BD F5BE B0FA 4F49 PGP 2: ID=2EA7BBBD, http://www.in.tum.de/~schoepf/pgpkey.txt Fingerprint: 08 96 1F CD AD 55 03 0F 95 92 B0 F2 04 32 4B 52 pgpn7IKQQhsmm.pgp Description: PGP signature
Re: ITP: buglist?
On Mon, Oct 04, 1999 at 09:29:58AM -0400, Ben Collins wrote: This needs a direct connection, right? I'm behind a firewall :( I'm using it behind a firewall, not sure how yours is configured. It's not really a firewall: there's no default route, http and ftp (over http) work via squid. Thomas -- GnuPG: ID=B0FA4F49, http://www.in.tum.de/~schoepf/gpgkey.txt Fingerprint: FA38 2D7E 408F 61E4 BF49 B48F 04BD F5BE B0FA 4F49 PGP 2: ID=2EA7BBBD, http://www.in.tum.de/~schoepf/pgpkey.txt Fingerprint: 08 96 1F CD AD 55 03 0F 95 92 B0 F2 04 32 4B 52 pgpBTZaLmBqyw.pgp Description: PGP signature
Re: ITP: buglist?
Thomas Schoepf wrote: Have you tried Ben's getbugs.pl? Is it good enough? I looked at it briefly, but it seemsed very slow. wget is easier. -- see shy jo
Release Critical Buglist for October 23
Bug stamp-out list for Oct 23 11:59 (CET) Changes since Oct 15 02:56 (CET) 21 release-critical bugs were closed and 45 were opened. (I won't list the complete list of opened and closed bugs here, it's huge) Total number of release-critical bugs: 89 -- Package: amaya Maintainer: Steve Dunham [EMAIL PROTECTED] 28390 Pages not displayed Package: apache-common Maintainer: Johnie Ingram [EMAIL PROTECTED] 25990 apache-common: apache expects passwd.db but not dbmmanage Package: balsa Maintainer: Ole J. Tetlie [EMAIL PROTECTED] 27726 balsa cannot be run 27894 balsa is linked against ancient version of gtk Package: base-passwd Maintainer: Galen Hazelwood [EMAIL PROTECTED] 25882 various system users inherited my personal gid (100) ! Package: binutils-multiarch Maintainer: Christopher C. Chimelis [EMAIL PROTECTED] 28409 binutils-multiarch: binutils_multiarch tries to overwrite files Package: boot-floppies Maintainer: Enrique Zanardi [EMAIL PROTECTED] 26584 lomem install doesn't activate swap 27061 boot-floppies' .bash_profile for root prompt for pkgsel is confusing 27970 newt dependencies 28201 boot floppies for 2.0 do not make system bootable Package: bsdmainutils Maintainer: Austin Donnelly [EMAIL PROTECTED] 27321 wordlists moving to /usr/share/dict Package: cron Maintainer: Steve Greenland [EMAIL PROTECTED] 26705 RedHat (possible) buffer overflow fixes Package: cvs-pcl Maintainer: Tom Lees [EMAIL PROTECTED] 20625 cvs-pcl: Compilation of elc files fails Package: dhcp-client-beta Maintainer: Rich Sahlender [EMAIL PROTECTED] 18322 dhclient-script problem with EXPIRE 19767 dhcp-client-beta has no /usr/doc directory Package: dpkg Maintainer: Klee Dienes and Ian Jackson [EMAIL PROTECTED] 17624 dpkg: installs regular dir when .deb contains symlink ! 1797 upgrade/downgrade dependency calculation problem 20401 Problems updating bo - hamm 21182 dpkg: dpkg can go into an infinite loop with --force-configure-any Package: fakeroot Maintainer: joost witteveen [EMAIL PROTECTED] 27794 fakeroot: fakeroot depends on missing library Package: ftp.debian.org Maintainer: Guy Maor [EMAIL PROTECTED] 25761 ftp.debian.org: No standard naming convention for mirrors.. 26920 ftp.debian.org: package installation procedure problem 27381 libg++272-dev and libstdc++2.8-dev conflict, being both standard!! 27642 exim needs to be made standard, smail needs to be made optional 28397 tmview_96.05-3.deb in Packages.gz, but not in archive! Package: gcc Maintainer: Galen Hazelwood [EMAIL PROTECTED] 26100 gcc: -dynamic is not default as it should be Package: gnome-gxsnmp Maintainer: Jim Pick [EMAIL PROTECTED] 25866 gnome-gxsnmp belongs in contrib Package: groff Maintainer: Fabrizio Polacco [EMAIL PROTECTED] 27790 groff depends on missing libary. Package: isapnptools Maintainer: Frederic Lepied [EMAIL PROTECTED] 28136 compiled for dev kernel Package: junkbuster Maintainer: Paul Haggart [EMAIL PROTECTED] 25258 junkbuster: junkbuster has security holes Package: kbackup Maintainer: Jens Ritter [EMAIL PROTECTED] 26903 kbackup: kbackup splits exclude dir/files on vfat partitions with spaces at the space Package: lg-issue15 Maintainer: Adrian Bridgett [EMAIL PROTECTED] 28025 Debian Installation Doc Package: libapache-mod-put Maintainer: Michael Alan Dorman [EMAIL PROTECTED] 28135 libapache-mod-put: Bad dependency! Package: libc6 Maintainer: Dale Scheetz [EMAIL PROTECTED] 26147 dlopen() corrupts heap, dlclose() reads free()'d memory 27314 libc6: wrong shlibs file 27334 libc6: breaks sendmail, probably problem in resolver 27403 libc6: fsck error occure after ldconfig 28251 libc should cause programs which leave stuff in stdio to fail Package: libjpeg6b Maintainer: Mark Mickan [EMAIL PROTECTED] 28341 libjpeg6b: Doesn't use upstream soname (and other
Buglist philosophy, (was bug 4164: ferret extended description...)
Susan G. Kleinmann wrote: So, except where the ratio of triviality-of-bug / responsiveness-of-maintainer is near 0, or (better) where the reporter realizes the maintainer has his own motivations for fixing the bug right away, I agree with Ian that the right thing to do is to log the bug. I believe the bug tracking system may be the single most important aspect of the Debian system. As a maintainer whose responsiveness is probably less than ideal[1], I must say I rather like having the bug tracking system, and I would just as soon have people report stuff there. It saves me from having to keep a separate list of private bugs, and while it may not be a pole of shame, if the list gets long, it tends to inspire some effort to reduce it to something a little less personally embarrasing :-). One enhancement I would like to see is the ability to access the buglist by package. No, not sorted by package, but a single page of the outstanding bugs for a given package, so that I can have a link to http://www.debian.org/bugs/bypackage/nvi.html; or some such. Or maybe a form, so that somebody can enter a package name and get the appropriate list. I think this would make it much more likely that people would look to see if a bug has been reported before submitting a new one, and would make it easier for maintainers. (I have no idea how hard this would be; I'm just throwing the idea out there...) Steve [1] I enjoy contributing in a small way to a community (both Debian and the free software community in general) that has provided a lot of benefit for me over the years, but the reality is that Debian is a spare time thing for me, and I haven't had much spare time this year. -- The Mole - I think, therefore I scream Calling all units! Leading monster stampede through the bottomlands to lower forty!... Set up ambush on flanks!... Also, do not shoot me!... Repeat!... Do not shoot me!!! [FLAMING CARROT vs the Giant Japanese Monsters!]
Re: Buglist
Sven Rudolph writes (Re: Buglist): Some suggestions for the bug reporting system: - It is possible to mark a message quiet in order to get it not echoed at debian-devel. Is there a way to make answers to it be not echoed too ? (e.g. by introducing a debian-bugs-quiet alias) That might be a good idea. Bruce, could we do that ? This is probably better than that horrible thing with `X-Debian-PR: quiet' in the main mail header. - Or what do you think about moving all bug-system messages to another mailing list ? - There was a suggestion that bug reports are directly sent to the package maintainer. Is this still planned ? How about having most bug reports still go to debian-devel, so that people can comment if they see something that touches on their `area', but make debian-bugs-quiet available so that the submitter can send things only to the maintainer ? Ian.
Re: Buglist
On Thu, 21 Dec 1995, Bruce Perens wrote: I have a bunch of bugs I haven't closed out, and there are bugs on packages I've transferred to other maintainers that the other maintainers have not closed out. I will not be able to deal with this until after New Years. I, too, have some work to do wrt to closing bug reports, etc., and I won't be able to get to them until the new year.
Re: Buglist
In article [EMAIL PROTECTED] Lauri Tischler [EMAIL PROTECTED] writes: From: Lauri Tischler [EMAIL PROTECTED] Date: Wed, 20 Dec 1995 09:22:46 GMT +2 X-Mailing-List: [EMAIL PROTECTED] archive/latest/3596 Last night, not having anything sensible, like sleeping, to do, I was browsing thru the BugList. It appears that there is a number of Bugs reported which are really no longer valid, they point to old Debian (0.95) or maybe to a really old application package which has been replaced long time ago. What could be done about them ? Could I help ? How ? I'm not much of a C-programmer but I can read and bang the keyboard :) I sent him the following answer: : By default the package maintainer handles the bug reports. So you : should ask the maintainer of the package whether you could assist him : in handling bug reports. : : If it is really obvious that the bug doesn't exist anymore, close the : bug and send a Cc to the maintainer. : : If you send the originator a mail (e.g. a request for details), send a : Cc to debian-bugs. (You might use the 'quiet' Header entry.) : : There were some maintainership-giveaways recently, so some people who : received these packages didn't release corrected versions yet. : : I used to keep some private comments regarding the state of some bug : report in private files, but when more than one person handles bugs, : this won't share the knowledge. So everything should be Cc-ed to : debian-bugs. Any comments ? Some suggestions for the bug reporting system: - It is possible to mark a message quiet in order to get it not echoed at debian-devel. Is there a way to make answers to it be not echoed too ? (e.g. by introducing a debian-bugs-quiet alias) - Or what do you think about moving all bug-system messages to another mailing list ? - There was a suggestion that bug reports are directly sent to the package maintainer. Is this still planned ? Sven -- Sven Rudolph ([EMAIL PROTECTED]); WWW : http://www.sax.de/~sr1/
Re: Buglist
I have a bunch of bugs I haven't closed out, and there are bugs on packages I've transferred to other maintainers that the other maintainers have not closed out. I will not be able to deal with this until after New Years. Thanks Bruce -- Bruce Perens [EMAIL PROTECTED] Pixar Animation Studios
