Re: How to correct BTS error statistics
Hi! Am 07.12.2011 19:53, schrieb Don Armstrong: [..] affects 618125 + src:globus-gram-job-manager-setup-condor [..] Martin is talking about bugs like #618138, which was opened against globus-rsl/7.2-2 but closed with doxygen/1.7.3-6. Oh. These are actually bugs in doxygen/1.7.3-5 (I think?) which affected these packages. What actually has to happen here is the bugs need to be reassigned to doxygen, merged, then marked as found and fixed in the appropriate versions, and then marked as affecting the original package. The preceding control instructions do this. Thanks for the explanation! I didn't knew of the affects command. Best regards, Alexander -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4ee074e9.1040...@schmehl.info
Re: How to correct BTS error statistics
Hi! Am 06.12.2011 23:32, schrieb Don Armstrong: Found in version package-a/a.a-x Fixed in version package-b/b.b-y The Bugs show up in the UDD (1); the PTS (2) is clean (now bugs are shown); new versions of package-a have already been built. I was told to use the notfound control for the bug server, but I did not understand which version to use: x or x+1. It depends on precisely which bug you're talking about. The BTS itself is the definitive record of whether a bug is closed in a particular version or not. Martin is talking about bugs like #618138, which was opened against globus-rsl/7.2-2 but closed with doxygen/1.7.3-6. Martin the mail you send to 618125 was in principle correct, however it should have been send to cont...@bugs.debian.org. Mails send to 123...@bugs.debian.org are _not_ scanned for commands, they will just appear in the bug log. Please also note that mails send to cont...@bugs.debian.org will change a bugs state, but won't show up in the bug log. So please send such mails to 12345@bugs.debian,org and BCC them also to cont...@bugs.debian.org. Please also note, that there are quite a couple of bugs affected not just the one you tried to fix, which would need some bts cleanup, Best regards, Alexander -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4edf270f.6030...@schmehl.info
Re: How to correct BTS error statistics
forcemerge 618125 618126 618131 618134 618136 618138 618149 618156 618157 618160 618161 618162 618166 618171 618174 618177 618179 618187 618189 618192 618193 618213 618217 618222 618223 618230 618238 618247 reassign 618125 doxygen # guessing here found 618125 doxygen/1.7.3-5 fixed 618125 doxygen/1.7.3-6 affects 618125 + src:globus-gram-job-manager-setup-condor affects 618125 + src:globus-rsl-assist affects 618125 + src:globus-gsi-sysconfig affects 618125 + src:globus-gram-job-manager-setup-pbs affects 618125 + src:globus-gram-job-manager affects 618125 + src:globus-rsl affects 618125 + src:globus-gass-copy affects 618125 + src:globus-gram-job-manager-setup-lsf affects 618125 + src:globus-xio-gsi-driver affects 618125 + src:globus-gsi-openssl-error affects 618125 + src:globus-common affects 618125 + src:globus-gsi-callback affects 618125 + src:globus-gsi-proxy-core affects 618125 + src:globus-gram-job-manager-callout-error affects 618125 + src:globus-gram-job-manager-setup-fork affects 618125 + src:globus-gssapi-error affects 618125 + src:globus-callout affects 618125 + src:globus-authz affects 618125 + src:globus-authz-callout-error affects 618125 + src:globus-ftp-control affects 618125 + src:globus-gss-assist affects 618125 + src:globus-gsi-proxy-ssl affects 618125 + src:globus-ftp-client affects 618125 + src:globus-openssl-module affects 618125 + src:globus-rls-client affects 618125 + src:globus-xio affects 618125 + src:globus-gsi-credential affects 618125 + src:globus-gsi-cert-utils thanks On Wed, 07 Dec 2011, Alexander Reichle-Schmehl wrote: Martin is talking about bugs like #618138, which was opened against globus-rsl/7.2-2 but closed with doxygen/1.7.3-6. Oh. These are actually bugs in doxygen/1.7.3-5 (I think?) which affected these packages. What actually has to happen here is the bugs need to be reassigned to doxygen, merged, then marked as found and fixed in the appropriate versions, and then marked as affecting the original package. The preceding control instructions do this. Don Armstrong -- What prison taught me was that some people are born into a life where they're going to be subjected to intense life experiences and personal tragedy on an almost daily basis. [...] I don't think you get enlightenment after something like that. I think all anyone really wants, if they're honest with themselves, is a quiet, easy life surrounded by people that love them. Anything else is conceit[ed]. -- OP from 99chan http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111207185344.gb8...@rzlab.ucr.edu
Re: How to correct BTS error statistics
On Wed, 07 Dec 2011, Don Armstrong wrote:
[...]
affects 618125 + src:globus-gram-job-manager-setup-condor
affects 618125 + src:globus-rsl-assist
[...]
For those following along at home, you can generate this list of
affects by the following:
for a in $(cat ~/buglist.txt); do echo affects 618125 + $(bts status ${a}
fields:package); done;
Don Armstrong
--
Information wants to be free to kill again.
-- Red Robot http://www.dieselsweeties.com/archive.php?s=1372
http://www.donarmstrong.com http://rzlab.ucr.edu
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111207185641.gc8...@rzlab.ucr.edu
Re: How to correct BTS error statistics
On Tue, 06 Dec 2011, Martin Eberhard Schauer wrote: during my first bug squashing party I encountered some FTBS bugs of this kind Found in version package-a/a.a-x Fixed in version package-b/b.b-y The Bugs show up in the UDD (1); the PTS (2) is clean (now bugs are shown); new versions of package-a have already been built. I was told to use the notfound control for the bug server, but I did not understand which version to use: x or x+1. It depends on precisely which bug you're talking about. The BTS itself is the definitive record of whether a bug is closed in a particular version or not. Don Armstrong -- The state must declare the child to be the most precious treasure of the people. As long as the government is perceived as working for the benefit of the children, the people will happily endure almost any curtailment of liberty and almost any deprivation. -- Adolf Hitler _Mein Kampf_ p403 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111206223201.gd3...@rzlab.ucr.edu
