Accepted debian-bts-applet 0.3 (source all)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sat, 26 Jul 2008 04:56:05 +0100
Source: debian-bts-applet
Binary: debian-bts-applet
Architecture: source all
Version: 0.3
Distribution: unstable
Urgency: low
Maintainer: Chris Lamb [EMAIL PROTECTED]
Changed-By: Chris Lamb [EMAIL PROTECTED]
Description:
debian-bts-applet - GNOME panel applet for monitoring the status of Debian bugs
Closes: 466708 472293
Changes:
debian-bts-applet (0.3) unstable; urgency=low
.
* Don't use dbus-open when calling gnome-open; this is not required for
recent versions of Epiphany: it previously caused complete lack of GTK
theming, etc. This also prevents Epiphany prompting with Epiphany
appears to have exited unexpectedly the last time it was run when a
URL is requested (Closes: #466708)
* Allow applet icon to resize when the underlying panel resizes. Additionally
transform the returned size hint such that we never display an icon that
does not fit. (Closes: #472293)
* Tidy thread handling in an attempt to fix #478155. I did not manage to fix
it, but I am fairly confident the bug is in another package. In the
meantime, we disable bug-buddy before we shutdown so as not to annoy users
logging out, etc.
* Rename Bonobo server ID from GNOME_PyDebianBTSApplet to DebianBTSApplet
as we are not an official GNOME applet and our implementation language
is irrelevant here.
* Don't segfault if DISPLAY is not set.
* Bump Standards-Version to 3.8.0.
* Update package description.
* Tidy debian/rules:
- Use debian/{dirs,install} instead of calling commands manually
- Remove useless dependencies from targets
- Use find -delete instead of find | xargs
Checksums-Sha1:
d0441d4ca8d6f6e5558c4cd881c7471affbad6e9 892 debian-bts-applet_0.3.dsc
5d968044689659abb7c7cd26b0c96fd7c89b1302 28893 debian-bts-applet_0.3.tar.gz
797dc322e08c0748361b4929cc2e5552f2f85171 15918 debian-bts-applet_0.3_all.deb
Checksums-Sha256:
161c1f9472c72ed081b3ec7452259cbc46b12a846cfff19d722d3e43dc035f66 892
debian-bts-applet_0.3.dsc
8d38f36e07a508e46b30d749b042666024986036893ddeb74f604a3cc9ec4b02 28893
debian-bts-applet_0.3.tar.gz
eeef7633acd15fe6de7d0e56608563705d322929bb93e72fa9e1fd48e52ab119 15918
debian-bts-applet_0.3_all.deb
Files:
c5f9ee7713b4ce428f1ff46fa2e96edc 892 misc optional debian-bts-applet_0.3.dsc
54aa2fa8db01010b1efeb21bdb1d3ac9 28893 misc optional
debian-bts-applet_0.3.tar.gz
61bfbf5299d24ff6ffcddea30efed644 15918 misc optional
debian-bts-applet_0.3_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Signed by Ana Guerrero
iEYEARECAAYFAkiK8aoACgkQn3j4POjENGF0zQCeI617/5T6ir4Ioq3rPKVVNGGw
clMAn0SZMR+lgwyLE82cM7jD//Dvsqez
=Goeh
-END PGP SIGNATURE-
Accepted:
debian-bts-applet_0.3.dsc
to pool/main/d/debian-bts-applet/debian-bts-applet_0.3.dsc
debian-bts-applet_0.3.tar.gz
to pool/main/d/debian-bts-applet/debian-bts-applet_0.3.tar.gz
debian-bts-applet_0.3_all.deb
to pool/main/d/debian-bts-applet/debian-bts-applet_0.3_all.deb
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted debian-bts-applet 0.2 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 18 Mar 2008 03:13:11 + Source: debian-bts-applet Binary: debian-bts-applet Architecture: source all Version: 0.2 Distribution: unstable Urgency: low Maintainer: Chris Lamb [EMAIL PROTECTED] Changed-By: Chris Lamb [EMAIL PROTECTED] Description: debian-bts-applet - GNOME Panel applet for monitoring Debian bugs Closes: 466457 Changes: debian-bts-applet (0.2) unstable; urgency=low . * Don't open /tmp/debian-bts-applet as sys.stderr (Closes: #466457) Files: 46c81009432d36ba9a612ef7a7410973 638 misc optional debian-bts-applet_0.2.dsc 843770f02dcce0baa54484f428bcdfb9 28266 misc optional debian-bts-applet_0.2.tar.gz 9bb71c35c2c3ff5b79395d6125428e85 14686 misc optional debian-bts-applet_0.2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFH5SOF+C5cwEsrK54RAj/OAKC6K3tBF2aN1qg7hsXqjYZ2tv4YAgCdGv7A OtlSO6YQhObHC5HLdatylDA= =N73W -END PGP SIGNATURE- Accepted: debian-bts-applet_0.2.dsc to pool/main/d/debian-bts-applet/debian-bts-applet_0.2.dsc debian-bts-applet_0.2.tar.gz to pool/main/d/debian-bts-applet/debian-bts-applet_0.2.tar.gz debian-bts-applet_0.2_all.deb to pool/main/d/debian-bts-applet/debian-bts-applet_0.2_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted debian-bts-applet 0.1 (source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 24 Jan 2008 19:21:13 + Source: debian-bts-applet Binary: debian-bts-applet Architecture: source all Version: 0.1 Distribution: unstable Urgency: low Maintainer: Chris Lamb [EMAIL PROTECTED] Changed-By: Chris Lamb [EMAIL PROTECTED] Description: debian-bts-applet - GNOME Panel applet for monitoring Debian bugs Closes: 461015 Changes: debian-bts-applet (0.1) unstable; urgency=low . * Initial release. (Closes: #461015) Files: 1f247b7e5eb353c1168edbe929da638c 638 misc optional debian-bts-applet_0.1.dsc 22e7439c9c9e247f4c05d261f0e789ac 28058 misc optional debian-bts-applet_0.1.tar.gz f1cacaf93990d0e666e3e63308859e83 14604 misc optional debian-bts-applet_0.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHmX76+C5cwEsrK54RAhrhAJ43BstEkM/rVlnR1rCpxNt0M7O7gQCgwenF EnunvQqM4iM7VdXlZW3dhk4= =GOnN -END PGP SIGNATURE- Accepted: debian-bts-applet_0.1.dsc to pool/main/d/debian-bts-applet/debian-bts-applet_0.1.dsc debian-bts-applet_0.1.tar.gz to pool/main/d/debian-bts-applet/debian-bts-applet_0.1.tar.gz debian-bts-applet_0.1_all.deb to pool/main/d/debian-bts-applet/debian-bts-applet_0.1_all.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
About Debian BTS
Hi, I am a student from the University Putra Malaysia. Now i am doing a study about Debian in my final year project. i am interested about Debian's bugs tracking system. http://www.debian.org/doc/developers-reference/ch-resources after i have go through above page, i think is better i ask if there have any statistical analysis or anything related to Debian's bugs? if there has any of it, it maybe a big help for my project. poayhua
Re: About Debian BTS
On 07/01/2008, PoayHua wrote: after i have go through above page, i think is better i ask if there have any statistical analysis or anything related to Debian's bugs? if there has any of it, it maybe a big help for my project. Christian Perrier posted some figures [1,2] on [3] yesterday. Some stats about release-critical bugs are available at [4], and a bit differently at [5] (which might be out of sync from what I've read some days ago). 1. http://www.perrier.eu.org/weblog/2008/01/06#bugs-per-year 2. http://www.perrier.eu.org/weblog/2008/01/06#oldest-bugs 3. http://planet.debian.org/ 4. http://bugs.debian.org/release-critical/ 5. http://bts.turmzimmer.net/ Cheers, -- Cyril Brulebois pgpfW6KZKLhiX.pgp Description: PGP signature
Upstream bugs in Debian BTS [was: Firefox bugs mass-closed.]
As a maintainer and a user, I have often wondered lately if the practice of tracking numerous upstream bugs in the Debian BTS is something that should be ended. Please don't. I always ask my downstream DDs to forward bugs to me together with the Debian bug number, and to leave the bug open until it is fixed in the Debian version. (I also try to drop a note to the Debian BTS when the bug is closed upstream, indicating the upstream version or changeset.) From an upstream maintainer's point of view, a bug report forwarded From the Debian BTS has particular value. For a start, it has been read, and sometimes reproduced, by your friendly DD[1]. Second, the DD may have thought about it -- there's a good chance he'll provide you with a hint or two. And third, it usually comes with precise version information. If upstream bugs from the Debian BTS are not being attended properly, then somebody f*cked up, either the DD or the upstream maintainer. Juliusz [1] DDs actually are friendly, they just express their friendliness differently from the rest of us ;-) pgp3imcLh5zkW.pgp Description: PGP signature
Debian BTS down ?
This morning I reported two bugs (using reportbug), which have not been acknowledged by BTS. Now I've just received an update on a bug which was CC:'ed to my personal email. I've answered, but http//bugs.debian.org has not been updated and the update wasn't ack'ed either. Is there a maintenance running or something that could prevent BTS to work ? Regards, -- Yves-Alexis Perez -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian BTS down ?
On Sat, 29 Apr 2006, Yves-Alexis Perez wrote: This morning I reported two bugs (using reportbug), which have not been acknowledged by BTS. Now I've just received an update on a bug which was CC:'ed to my personal email. I've answered, but http//bugs.debian.org has not been updated and the update wasn't ack'ed either. Is there a maintenance running or something that could prevent BTS to work ? No; messages were processed as recently as 9 minutes ago. Please give me the Message-Id: if the affected messages, and ideally the time and which they were sent so I can see what happened to them. Don Armstrong -- Taxes are not levied for the benefit of the taxed. -- Robert Heinlein _Time Enough For Love_ p250 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: a few tips on proper use of version tracking in the Debian BTS
On Mon, Oct 24, 2005 at 11:50:11PM +0900, Osamu Aoki wrote: On Sat, Oct 22, 2005 at 05:14:20PM -0700, Steve Langasek wrote: On Sun, Oct 23, 2005 at 09:41:15AM +1000, Brian May wrote: Brian == Brian May [EMAIL PROTECTED] writes: Along similar lines, if a have a closes: #nnn in my changelog for package X, but the bug is for package Y, is this going to mess things up? Well, things will be messed up, as there's no possible way for the BTS to correctly infer your meaning. :) If the bug is closed in an upload of package X, then either the bug belongs to package X[1], or it shouldn't have been closed. That is what I did few days ago and BTS seems to be quite comfortable dealing with it on the BTS web. Resolved bugs ... #126438: Nested file and url tags produce bad pdf hyperlinks Package: debiandoc-sgml (fixed: debiandoc-sgml-doc 1.1.17); Severity: minor; Reported by: Chris Tillman [EMAIL PROTECTED] Am I causing problem to BTS? No, it doesn't cause any problems for the BTS; it's just confusing and inconsistent for people trying to get information out of the BTS. If the bug was in debiandoc-sgml-doc, *not* in debiandoc-sgml, then it's helpful to have the bug assigned to debiandoc-sgml-doc. Cheers, -- 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
Re: a few tips on proper use of version tracking in the Debian BTS
On Sat, Oct 22, 2005 at 05:14:20PM -0700, Steve Langasek wrote: On Sun, Oct 23, 2005 at 09:41:15AM +1000, Brian May wrote: Brian == Brian May [EMAIL PROTECTED] writes: Along similar lines, if a have a closes: #nnn in my changelog for package X, but the bug is for package Y, is this going to mess things up? Well, things will be messed up, as there's no possible way for the BTS to correctly infer your meaning. :) If the bug is closed in an upload of package X, then either the bug belongs to package X[1], or it shouldn't have been closed. That is what I did few days ago and BTS seems to be quite comfortable dealing with it on the BTS web. Resolved bugs ... #126438: Nested file and url tags produce bad pdf hyperlinks Package: debiandoc-sgml (fixed: debiandoc-sgml-doc 1.1.17); Severity: minor; Reported by: Chris Tillman [EMAIL PROTECTED] Am I causing problem to BTS? Osamu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: a few tips on proper use of version tracking in the Debian BTS
Brian == Brian May [EMAIL PROTECTED] writes: Brian What is the preferred way of closing bugs that are not bugs Brian (e.g. mistake by the submitter)? -- Brian May Brian [EMAIL PROTECTED] Has the reassign command changed? What versions apply if you reassign a bug to another package based on a different source? Along similar lines, if a have a closes: #nnn in my changelog for package X, but the bug is for package Y, is this going to mess things up? -- Brian May [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: a few tips on proper use of version tracking in the Debian BTS
On Sun, Oct 23, 2005 at 09:41:15AM +1000, Brian May wrote: Brian == Brian May [EMAIL PROTECTED] writes: Brian What is the preferred way of closing bugs that are not bugs Brian (e.g. mistake by the submitter)? -- Brian May Brian [EMAIL PROTECTED] Has the reassign command changed? What versions apply if you reassign a bug to another package based on a different source? It is possible to say reassign $bugnum $package $version If you don't specify a version, then the bug is assumed to apply to all versions as before. Along similar lines, if a have a closes: #nnn in my changelog for package X, but the bug is for package Y, is this going to mess things up? Well, things will be messed up, as there's no possible way for the BTS to correctly infer your meaning. :) If the bug is closed in an upload of package X, then either the bug belongs to package X[1], or it shouldn't have been closed. -- 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/ [1] with the exception, currently, of wnpp, but maybe usertags will change that soon too signature.asc Description: Digital signature
Re: a few tips on proper use of version tracking in the Debian BTS
On Fri, Oct 21, 2005 at 02:08:17AM +0200, Pierre THIERRY wrote: It seems. I did it for #297927: after sending a 'close 297927' to [EMAIL PROTECTED], the BTS informed me that it was deprecated. I sent another mail to [EMAIL PROTECTED] with 'Version: 0.9.23-1', and it is now in the BTS as ``Fixed in version 0.9.23-1''. Great, I will do it for a couple of bugs closed erroneously as well. Besides that, does bts close NN x.y.z do the correct thing? -- Stefano Zacchiroli -*- Computer Science PhD student @ Uny Bologna, Italy [EMAIL PROTECTED],debian.org,bononia.it} -%- http://www.bononia.it/zack/ If there's any real truth it's that the entire multidimensional infinity of the Universe is almost certainly being run by a bunch of maniacs. -!- signature.asc Description: Digital signature
Re: a few tips on proper use of version tracking in the Debian BTS
Scribit Stefano Zacchiroli dies 19/10/2005 hora 11:06: 1) once a bug as been closed - erroneously I would say - mailing [EMAIL PROTECTED] without the Version: pseudo header, is there a way to push the version information to the bts? It seems. I did it for #297927: after sending a 'close 297927' to [EMAIL PROTECTED], the BTS informed me that it was deprecated. I sent another mail to [EMAIL PROTECTED] with 'Version: 0.9.23-1', and it is now in the BTS as ``Fixed in version 0.9.23-1''. Precisely, Nowhere man -- [EMAIL PROTECTED] OpenPGP 0xD9D50D8A signature.asc Description: Digital signature
Re: a few tips on proper use of version tracking in the Debian BTS
Joey == Joey Hess [EMAIL PROTECTED] writes: Joey 2. If you forget a changelog entry, or find out about a Joey fix (such as a fix for a security hole) after your upload, Joey send mail to [EMAIL PROTECTED] as before, but Joey include a Version: pseudo-header[2]. What is the preferred way of closing bugs that are not bugs (e.g. mistake by the submitter)? -- Brian May [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: a few tips on proper use of version tracking in the Debian BTS
On Wed, Oct 19, 2005 at 05:56:47PM +1000, Brian May wrote: Joey == Joey Hess [EMAIL PROTECTED] writes: Joey 2. If you forget a changelog entry, or find out about a Joey fix (such as a fix for a security hole) after your upload, Joey send mail to [EMAIL PROTECTED] as before, but Joey include a Version: pseudo-header[2]. What is the preferred way of closing bugs that are not bugs (e.g. mistake by the submitter)? Closing without a version header retains the traditional semantics of marking the bug closed in all versions. Cheers, -- 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
Re: a few tips on proper use of version tracking in the Debian BTS
On Wed, Oct 19, 2005 at 01:44:38AM -0700, Steve Langasek wrote: Closing without a version header retains the traditional semantics of marking the bug closed in all versions. Two questions: 1) once a bug as been closed - erroneously I would say - mailing [EMAIL PROTECTED] without the Version: pseudo header, is there a way to push the version information to the bts? 2) AFAICT the bts parses changelog to understand in which version a given bug has been closed. Assume that the version of package p in unstable is x and that I upload version x+2, with two entries in the changelog one for x+1 and for for x+2. Entry x+1 has a closes:#nnn entry. Is this enough for the bts or do I need to mail it as well? Many TIA, Cheers. -- Stefano Zacchiroli -*- Computer Science PhD student @ Uny Bologna, Italy [EMAIL PROTECTED],debian.org,bononia.it} -%- http://www.bononia.it/zack/ If there's any real truth it's that the entire multidimensional infinity of the Universe is almost certainly being run by a bunch of maniacs. -!- signature.asc Description: Digital signature
Re: a few tips on proper use of version tracking in the Debian BTS
On Wed, Oct 19, 2005 at 11:06:14 +0200, Stefano Zacchiroli wrote: On Wed, Oct 19, 2005 at 01:44:38AM -0700, Steve Langasek wrote: Closing without a version header retains the traditional semantics of marking the bug closed in all versions. Two questions: 1) once a bug as been closed - erroneously I would say - mailing [EMAIL PROTECTED] without the Version: pseudo header, is there a way to push the version information to the bts? If the bug is still open in some version of your package, I guess found nnn version would give this information to the bts. You could probably also use reopen nnn together with close nnn version if the bug is only closed in that version of your package. 2) AFAICT the bts parses changelog to understand in which version a given bug has been closed. Assume that the version of package p in unstable is x and that I upload version x+2, with two entries in the changelog one for x+1 and for for x+2. Entry x+1 has a closes:#nnn entry. Is this enough for the bts or do I need to mail it as well? The bugs closed in your upload are determined by the changes file, so you can use the -vversion switch with dpkg-buildpackage or dpkg-genchanges to use changelog information for versions version+1 and version+2. Cheers, Julien Cristau -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: a few tips on proper use of version tracking in the Debian BTS
Hi Joey Joey Hess wrote: In the process of my work on the testing security team, I've noticed that many developers still seem to be unfamiliar with how to use the new version tracking features[1] of the Debian BTS. ... I thought I'd conclude with an example of how to do it right, and wrong. right: http://bugs.debuan.org/329839 cut s/debuan/debian/ ;-) I think this will take some time to spread among all DD's and other Developers. But it's always a good thing to mention the consequences and show the benefit! Thanks Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[Ann] debian-bts-control.el
I rarely announce software, but this could be useful to DDs. Whenever I wanted to add tags or something to a bug report, I'd start my browser to http://www.debian.org/ - Bug Reports - Developers' information on manipulating bugs by email. Just to get the syntac right. So I wrote debian-bts-control.el, an Emacs interface to build the email messages. It knows all the commands and their options with TAB completions. If you want to try it, install `dpkg-dev-el' from unstable, and do: M-x debian-bts-control Subsequent invocations add a directive to the same email message. Hope you like it! Peter
Re: Debian BTS
On Tue, Sep 14, 1999 at 12:03:42PM -0700, Darren Benham wrote: Well, we did it. The software used by Debian for it's bug tracking, debbugs, was pacakged for distribution several months ago and resides in Potato. Last weekend, Debian upgraded it's bug server (bugs.debian.org) to the save version that's packaged. Great work guys. Just a query though -- is the web server on www.debian.org working properly? It takes me several minutes to retrieve the home page lately! No other sites exhibit this problem. Hamish -- Hamish Moffatt VK3SB (ex-VK3TYD). CCs of replies from mailing lists are welcome. pgp7vCyzg9Xw7.pgp Description: PGP signature
