Re: Volunteer(s) wanted to help with owner@bugs.debian.org
Steve Dunham [EMAIL PROTECTED] writes:
James R. Van Zandt [EMAIL PROTECTED] writes:
I'd sure like a mechanism, with either email or a browser, to get a
list of the bugs registered against a particular package.
What about http://www.debian.org/Bugs/db/ix/packages.html?
Currently, that page is 187k.
Joey's idea is closer to what I had in mind:
package=your-package
lynx http://www.debian.org/Bugs/db/pa/l${package}.html
I have now installed this script in /usr/local/bin/bugsin:
lynx http://www.debian.org/Bugs/db/pa/l$1.html
Thanks!
- Jim Van Zandt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Volunteer(s) wanted to help with owner@bugs.debian.org
In article [EMAIL PROTECTED] you wrote: : What will you record as fixing-version ? If we reorganize the server the way I've been discussing recently, this problem would go away... because no package could ever get into a stable tree without going through unstable... one version stream should be enough. If we persist in managing the archive as we have been for the last year or so, you are correct that recording the version that closes a bug is problematic. Bdale -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Volunteer(s) wanted to help with owner@bugs.debian.org
On Wed, Jun 10, 1998 at 01:01:36PM +0100, Ian Jackson wrote: I'd like to offload some of the admin stuff for the bug system. I don't know how Guy (the other admin of the bug system) feels, but I'd like to reduce the amount of time I spend running the bug system. As there were enough people there is no need for another one but fwiw I'd also be willing to help in cases something needs to be done. I'm mainly speaking of small/quick admin tasks not the longterm ones. (for the record) Regards, Joey -- / Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg / / Experience is a useful thing. Unfortunately it is / / only acquired just after one could have used it. / -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Volunteer(s) wanted to help with owner@bugs.debian.org
Bdale Garbee wrote: In article [EMAIL PROTECTED] you wrote: : What will you record as fixing-version ? If we reorganize the server the way I've been discussing recently, this problem would go away... because no package could ever get into a stable tree without going through unstable... one version stream should be enough. I think there will still be a need for back-patching versions in the 'stable' tree. Consider a situation with xfree86 3.3 in 'stable' and xfree86 3.4 in 'unstable'. A security bug is found in the wrapper we use, and has to be fixed in both. We will have to offer the people who use 'stable' a way to secure their versions without having to upgrade to xfree86 3.4. However, since such cases will (one hopes :) be rare, it should be sufficient if the bug system has an escape hatch for such cases. And it will have one, since there is no need to do away with the unconditional close bugreport, and that can be used for such backpatches. Security bugfixes are normally tracked pretty closely on their way through the archive anyway. If we persist in managing the archive as we have been for the last year or so, you are correct that recording the version that closes a bug is problematic. A more complicated scheme might still be useful. If a bug is fixed in version 1.5, that does not mean that version 1.0 has the problems -- perhaps the bug wasn't introduced until version 1.3. Thus, it would be nice if the system could handle ranges of version numbers as an option. Alternately, such ranges could be keyed to distributions. This bug is fixed by version 1.5, but it only existed in unstable. It's probably safe to assume that the earlier buggy versions are not going to make it into stable. I think this method is less robust, though. Richard Braakman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Volunteer(s) wanted to help with owner@bugs.debian.org
Raul Miller [EMAIL PROTECTED] writes: Where should I start? I'd sure like a mechanism, with either email or a browser, to get a list of the bugs registered against a particular package. It would help cut down duplicate bug reports. Now, I'm forced to download a list of *all* the bugs. - Jim Van Zandt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Volunteer(s) wanted to help with owner@bugs.debian.org
On Fri, Jun 12, 1998 at 11:24:21PM -0400, James R. Van Zandt wrote:
Raul Miller [EMAIL PROTECTED] writes:
Where should I start?
I'd sure like a mechanism, with either email or a browser, to get a
list of the bugs registered against a particular package. It would
help cut down duplicate bug reports. Now, I'm forced to download a
list of *all* the bugs.
Isn't there a search function to get the particular package?
Anyway, I guess you come with a little knowledge about programming,
yes?
package=your-package
lynx http://www.debian.org/Bugs/db/pa/l${package}.html
And you're done.
Next thing please.
Regards,
Joey
--
/ Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg /
/ Experience is a useful thing. Unfortunately it is /
/ only acquired just after one could have used it. /
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Volunteer(s) wanted to help with owner@bugs.debian.org
James R. Van Zandt [EMAIL PROTECTED] writes: I'd sure like a mechanism, with either email or a browser, to get a list of the bugs registered against a particular package. It would help cut down duplicate bug reports. Now, I'm forced to download a list of *all* the bugs. What about http://www.debian.org/Bugs/db/ix/packages.html? Steve [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Volunteer(s) wanted to help with owner@bugs.debian.org
Bdale == Bdale Garbee [EMAIL PROTECTED] writes: Bdale Perl5 now. However, he got really over-zealous and changed a Bdale lot of other things, too, so that I'm sure how well what he did Bdale would transfer back. Heh, that's unavoidable when adapting the system for use at a NOC or Helpdesk -- some bug-tracking assumptions aren't configurable yet. :-) Bdale Having said that, if someone is going to do work to package the Bdale bug tracking system and would like a copy of what he did to Bdale review, I can try and scrape the pieces together... I would love to see them. Bdale My personal wish-list for the bug system is pretty short. I would Also its been suggested that the BTS not delete bugs, but store them in some kind of long-term archive. Full-text searching couldn't hurt either. :-) - PGP E4 70 6E 59 80 6A F5 78 63 32 BC FB 7A 08 53 4C __ _Debian GNU Johnie Ingram [EMAIL PROTECTED] mm mm / /(_)_ __ _ ___ __netgod irc.debian.org mm mm / / | | '_ \| | | \ \/ / m m m / /__| | | | | |_| |Yes, I'm Linus, and I am your God. mm mm \/_|_| |_|\__,_/_/\_\ -- Linus, keynote address, Expo 98 GO BLUE -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Volunteer(s) wanted to help with owner@bugs.debian.org (fwd)
Dear all, I replied to this as well, but didn't cc to the list. Here is the original message for reference. Matthew -- Elen sila lumenn' omentielvo Steward-elect of the Cambridge Tolkien Society Selwyn College Computer Support http://www.geocities.com/Area51/Chamber/8841/ http://www.cam.ac.uk/CambUniv/Societies/tolkien/ http://pick.sel.cam.ac.uk/ -- Forwarded message -- Date: Wed, 10 Jun 1998 13:31:23 +0100 (BST) From: M.C. Vernon [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: Ian Jackson [EMAIL PROTECTED] Subject: Re: Volunteer(s) wanted to help with [EMAIL PROTECTED] 1. Reading and responding to [EMAIL PROTECTED] mail. Usually this is routine, and just means you have to mail people saying `you sent this to [EMAIL PROTECTED] when [EMAIL PROTECTED] was not the right place'. Many messages are followups of various kinds to bug reports, and there are occasional messages with instructions for [EMAIL PROTECTED] sent there too. This is not a technically skilled job, but some familiarity with the Debian Project's organisation would be necessary. Ian, I'll do this if you like, but: 1)My connectivity over the summer vac is slow 2)I don't claim to be a technical wizard of any description 3)You might not want a student doing that sort of official stuff But yes, I am quite happy to give it a go. HTH, Matthew -- Elen sila lumenn' omentielvo Steward-elect of the Cambridge Tolkien Society Selwyn College Computer Support http://www.geocities.com/Area51/Chamber/8841/ http://www.cam.ac.uk/CambUniv/Societies/tolkien/ http://pick.sel.cam.ac.uk/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Volunteer(s) wanted to help with owner@bugs.debian.org
In article [EMAIL PROTECTED] you wrote: : Also its been suggested that the BTS not delete bugs, but store them : in some kind of long-term archive. Full-text searching couldn't hurt : either. :-) The approach we used at work is that bug closure causes the file to get moved to a different directory... so, in effect, there's a database of open bugs and a database of closed bugs. Maybe not optimal, but simple to implement. The biggest feature-creeps are that we take serious advantage of Apache's server-side include features, which cuts down drastically on the amount of file-whacking in the database... and we don't batch processing, we do each request as it arrives. The combination allow us to have near-instant gratification on bug status changes showing up on the web pages, without driving the resource requirements on the server way up. Bdale -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Volunteer(s) wanted to help with owner@bugs.debian.org
-BEGIN PGP SIGNED MESSAGE- On Thu, 11 Jun 1998, Bdale Garbee wrote: [...] and we don't batch processing, we do each request as it arrives. Yes! Please! [ Bug #14650: The bug system is a little bit slow ] -BEGIN PGP SIGNATURE- Version: 2.6.3ia Charset: latin1 iQCVAgUBNX+ooyqK7IlOjMLFAQFtHgP9FnnfwXD9WWEZs5ru/PEmaiqUEFXxpLlh l++awXYL4O+QEKzoGOQIlf4mBO5p3AQ5hyZh/v+dmxAsJr+eJtE7MSmWvZa1kMmt pQrDbFRc5N0sMAJ3ISrrGdE2fDwVLd42GFVqQBiWe/EUjRQFhra566wpo8kTEzDm s0FLF6TFsIg= =vaWc -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Volunteer(s) wanted to help with owner@bugs.debian.org
Bdale Garbee writes: My personal wish-list for the bug system is pretty short. I would really like it if the process of closing a bug recorded the version of the package that supposedly fixed the bug. That may not be so simple: think of package dummy_1.2-3 in hamm, and dummy_2.3-4 in slink only because of the freeze. One bug is discovered which affects both, and gets fixed in 1.2-4 and 2.3-5. What will you record as fixing-version ? 1.2-4 is definitely wrong as 2.3-4 is buggy; 2.3-5 is highly suboptimal, and makes the info useless :( This reminds me of a recent suggestion of mine (An idea for the BTS (Was: Weeding out slink bug reports), debian-devel@lists.debian.org archive/latest/6227) to really add support for distributions in the BTS. Nobody seems interested in talking about that, though... -- Yann Dirson[EMAIL PROTECTED] | Stop making M$-Bill richer richer, isp-email: [EMAIL PROTECTED] | support Debian GNU/Linux: debian-email: [EMAIL PROTECTED] | more powerful, more stable ! http://www.mygale.org/~ydirson/ | Check http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Volunteer(s) wanted to help with owner@bugs.debian.org
In article [EMAIL PROTECTED] you write: Ian Jackson [EMAIL PROTECTED] wrote: 3. Obviously additional development of the bug system would be good. This can be done either by the person doing 2., or independently. In any case the patches generated need to be sent upstream to me. I'm interested in taking a look at this. I don't want to promise anything until I'm reasonably certain I understand how you've laid out the code [I'm still stumped by dpkg, to the point where I'm not even sure how to form reasonable questions, but I think I know a fair bit about the mechanisms I'd expect in the bug system]. Where should I start? i don't think i can do much, but i'm willing to look at changes, give comments, test etc. i'm diging in the bug system, as i try to install it on bugs.kde.org ... (maybe it was not wise to ask will i ever get an answer of my bug report ?). andreas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Volunteer(s) wanted to help with owner@bugs.debian.org
Put me down as a 'volunteer of last resort'. There are other debian related tasks I'd rather do, probably, but if no one else steps up, I will fill any of the above roles. I probably have the necessary expertise (I know perl4/5 well, I understand m4, I know SMTP related issues reasonably well). Yours, Jules Bean [I'm not *actually* a maintainer yet, but my new-maintainer application is going off in about 10 minutes...] /+---+-\ | Jelibean aka | [EMAIL PROTECTED] | 6 Evelyn Rd| | Jules aka | | Richmond, Surrey | | Julian Bean | [EMAIL PROTECTED]| TW9 2TF *UK* | ++---+-+ | War doesn't demonstrate who's right... just who's left. | | When privacy is outlawed... only the outlaws have privacy. | \--/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Volunteer(s) wanted to help with owner@bugs.debian.org
I will volunteer to work on: 1. Reading and responding to [EMAIL PROTECTED] mail, and 2. Actual administration and maintenance of the bug system (to the extent of my capabilities - I will yell quickly if I get stuck). I would prefer to share these functions with someone else, since I will be unavailable for several weeks during the summer. Bob -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Volunteer(s) wanted to help with owner@bugs.debian.org
On Wed, Jun 10, 1998 at 02:31:10PM -0400, Bob Hilliard wrote: I will volunteer to work on: 1. Reading and responding to [EMAIL PROTECTED] mail, and 2. Actual administration and maintenance of the bug system (to the extent of my capabilities - I will yell quickly if I get stuck). I would prefer to share these functions with someone else, since I will be unavailable for several weeks during the summer. I'm willing to share the work with Bob, although my capabilities of administration will be limited (but hopefully growing :) Marcus -- Rhubarb is no Egyptian god.Debian GNU/Linuxfinger brinkmd@ Marcus Brinkmann http://www.debian.orgmaster.debian.org [EMAIL PROTECTED]for public PGP Key http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ PGP Key ID 36E7CD09 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Volunteer(s) wanted to help with owner@bugs.debian.org
Ian Jackson [EMAIL PROTECTED] wrote: 3. Obviously additional development of the bug system would be good. This can be done either by the person doing 2., or independently. In any case the patches generated need to be sent upstream to me. I'm interested in taking a look at this. I don't want to promise anything until I'm reasonably certain I understand how you've laid out the code [I'm still stumped by dpkg, to the point where I'm not even sure how to form reasonable questions, but I think I know a fair bit about the mechanisms I'd expect in the bug system]. Where should I start? -- Raul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Volunteer(s) wanted to help with owner@bugs.debian.org
Ian Jackson writes: Current tasks include: * Indices of bugs by submitter. * Implement `interested list' for each bug. * Given `interested list', a way to submit a bug that puts you on the interested list, so that you get notified of any status change and not just closure. What about another one: building a deb of it ? I would be of interest to people basing a new dist on Debian - it would also make it easy for people willing to study it and submit small patches (eg. the Fixed severity) -- Yann Dirson[EMAIL PROTECTED] | Stop making M$-Bill richer richer, isp-email: [EMAIL PROTECTED] | support Debian GNU/Linux: debian-email: [EMAIL PROTECTED] | more powerful, more stable ! http://www.mygale.org/~ydirson/ | Check http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Volunteer(s) wanted to help with owner@bugs.debian.org
Yann == Yann Dirson [EMAIL PROTECTED] writes: Yann What about another one: building a deb of it ? I would be of Yann interest to people basing a new dist on Debian - it would also Yann make it easy for people willing to study it and submit small Yann patches (eg. the Fixed severity) I've had it packaged since the first week of January, actually -- just never uploaded it because its too flaky even when using its own copy of perl4 (included with the package, stolen from Ian's home dir). It seems that two files, process and errorlib, need to be rewritten to work with modern perls. Unfortunately I've never found time to do this. But 99% of the time debbugs works as intended, and it was easily twisted to my own purposes: http://www.tln.org/Tickets/ From what I've seen, RedHat needs something like debbugs bad. :-) - PGP E4 70 6E 59 80 6A F5 78 63 32 BC FB 7A 08 53 4C __ _Debian GNU Johnie Ingram [EMAIL PROTECTED] mm mm / /(_)_ __ _ ___ __netgod irc.debian.org mm mm / / | | '_ \| | | \ \/ / m m m / /__| | | | | |_| |Yes, I'm Linus, and I am your God. mm mm \/_|_| |_|\__,_/_/\_\ -- Linus, keynote address, Expo 98 GO BLUE -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Volunteer(s) wanted to help with owner@bugs.debian.org
On Wed, Jun 10, 1998 at 06:08:36PM -0300, Johnie Ingram wrote: From what I've seen, RedHat needs something like debbugs bad. :-) They now have something. I'm not sure about the quality, or the backend, but.. they recently instituted a bug tracking system. http://www.developer.redhat.com/bugs/index.phtml Ciao, -- David Welton http://www.efn.org/~davidw Debian GNU/Linux - www.debian.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Volunteer(s) wanted to help with owner@bugs.debian.org
David == David Welton [EMAIL PROTECTED] writes: David They now have something. I'm not sure about the quality, or David the backend, but.. they recently instituted a bug tracking David system. Hehe, I've seen it, and thats what I mean. :-) - PGP E4 70 6E 59 80 6A F5 78 63 32 BC FB 7A 08 53 4C __ _Debian GNU Johnie Ingram [EMAIL PROTECTED] mm mm / /(_)_ __ _ ___ __netgod irc.debian.org mm mm / / | | '_ \| | | \ \/ / m m m / /__| | | | | |_| |Yes, I'm Linus, and I am your God. mm mm \/_|_| |_|\__,_/_/\_\ -- Linus, keynote address, Expo 98 GO BLUE -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Volunteer(s) wanted to help with owner@bugs.debian.org
In article [EMAIL PROTECTED] you wrote: : I've had it packaged since the first week of January, actually -- just : never uploaded it because its too flaky even when using its own copy : of perl4 (included with the package, stolen from Ian's home dir). It : seems that two files, process and errorlib, need to be rewritten to : work with modern perls. I had one of the folks who works for me at HP adapt the bug system to the needs of the small support group I manage. He fixed a bunch of these problems, so that it's entirely based on Perl5 now. However, he got really over-zealous and changed a lot of other things, too, so that I'm sure how well what he did would transfer back. Having said that, if someone is going to do work to package the bug tracking system and would like a copy of what he did to review, I can try and scrape the pieces together... My personal wish-list for the bug system is pretty short. I would really like it if the process of closing a bug recorded the version of the package that supposedly fixed the bug. There would of course need to be special case handling for pseudo-packages like ftp.debian.org, where the date might be a good substitute. Having this additional information would allow us to know what bugs exist against different releases, by looking at the package version information... Bdale -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
