Re: Bug 510765 won't appear as closed

2009-05-17 Thread Don Armstrong
On Fri, 15 May 2009, Adeodato Simó wrote:
 + Don Armstrong (Thu, 14 May 2009 13:24:29 -0700):
  a message to control with 'close ' (deprecated, because it doesn't
  tell the submitter that it was fixed, [...])
 
 Well, AFAIK they do get a mail that the bug has been closed, with
 subject acknowledged by developer and a generic blurb about the
 closure.

Yeah, my sentence should read tell the submitter *why* it was fixed.


Don Armstrong

-- 
No amount of force can control a free man, a man whose mind is free
[...] You can't conquer a free man; the most you can do is kill him.
 -- Robert Heinlein _Revolt in 2010_ p54

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



Re: Bug 510765 won't appear as closed

2009-05-15 Thread Adeodato Simó
+ Don Armstrong (Thu, 14 May 2009 13:24:29 -0700):

 a message to control with 'close ' (deprecated, because it doesn't
 tell the submitter that it was fixed, [...])

Well, AFAIK they do get a mail that the bug has been closed, with
subject acknowledged by developer and a generic blurb about the
closure. I'm sure you know this, but I thought I'd mention in case
somebody thought they can get away with the submitters not getting
notice at all of the closure. :-P

-- 
- Are you sure we're good?
- Always.
-- Rory and Lorelai


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug 510765 won't appear as closed

2009-05-14 Thread Rodrigo Gallardo
Can someone help me understand why 510765 keeps on appearing on
liferea's bug page?

It's been closed in all the relevant versions, and the little graph on
the left shows nothing but green boxes, but everything (the bts, the
pts, my qa page) show liferea as having 1 open rc bug.


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: Bug 510765 won't appear as closed

2009-05-14 Thread Didier Raboud
Rodrigo Gallardo wrote:

 Can someone help me understand why 510765 keeps on appearing on
 liferea's bug page?
 
 It's been closed in all the relevant versions, and the little graph on
 the left shows nothing but green boxes, but everything (the bts, the
 pts, my qa page) show liferea as having 1 open rc bug.

Hi, 

AFAIK, the correct way of closing bugs is a mail to #-cl...@bugs.debian.org
or #-d...@bugs.debian.org. By making a versioned done- (Version: 123-1 as
first line), you can also tell from which version the bug is fixed.

Regards,

OdyX

-- 
Swisslinux.org − Le carrefour GNU/Linux en Suisse −
http://www.swisslinux.org


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: Bug 510765 won't appear as closed

2009-05-14 Thread Don Armstrong
found 510765 1.4.1-1
found 510765 1.4.23-1
close 510765
thanks


On Thu, 14 May 2009, Rodrigo Gallardo wrote:
 Can someone help me understand why 510765 keeps on appearing on
 liferea's bug page?
 
 It's been closed in all the relevant versions, and the little graph on
 the left shows nothing but green boxes, but everything (the bts, the
 pts, my qa page) show liferea as having 1 open rc bug.

Because it's not -done.

In order for a bug to be shown as resolved two things has to be true:

1) the bug has to have been marked as done, either by a message to
nnn-d...@b.d.o explaining why it should be closed, or a message to
control with 'close ' (deprecated, because it doesn't tell the
submitter that it was fixed, but I'm using it in this message.)

2) the bug has to be either fixed or absent in the distribution which
you're querying for all architectures the bts cares about.

Finally, if you don't know why it's not being fixed, feel free to ask
here or in #debbugs on irc.debian.org; mucking with the found/fixed
versions when the bug was actually found in that version generally
isn't a good idea.


Don Armstrong

-- 
Judge if you want.
We are all going to die.
I intend to deserve it.
 -- a softer world #421
http://www.asofterworld.com/index.php?id=421

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



Re: Bug 510765 won't appear as closed

2009-05-14 Thread Paul Gevers
Rodrigo Gallardo wrote:
 Can someone help me understand why 510765 keeps on appearing on
 liferea's bug page?
 
 It's been closed in all the relevant versions, and the little graph on
 the left shows nothing but green boxes, but everything (the bts, the
 pts, my qa page) show liferea as having 1 open rc bug.

I guess you didn't close the bug. Only marked it fixed.
See: http://www.debian.org/Bugs/server-control#fixed

Paul



signature.asc
Description: OpenPGP digital signature


Re: Bug 510765 won't appear as closed

2009-05-14 Thread Rodrigo Gallardo
On Thu, May 14, 2009 at 01:24:29PM -0700, Don Armstrong wrote:
 On Thu, 14 May 2009, Rodrigo Gallardo wrote:
  Can someone help me understand why 510765 keeps on appearing on
  liferea's bug page?
 
 Because it's not -done.

Thanks, I get it now.

 Finally, if you don't know why it's not being fixed, feel free to ask
 here or in #debbugs on irc.debian.org; mucking with the found/fixed
 versions when the bug was actually found in that version generally
 isn't a good idea.

So, what exactly is the use case for fixed?


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: Bug 510765 won't appear as closed

2009-05-14 Thread Don Armstrong
On Thu, 14 May 2009, Rodrigo Gallardo wrote:
 On Thu, May 14, 2009 at 01:24:29PM -0700, Don Armstrong wrote:
  Finally, if you don't know why it's not being fixed, feel free to
  ask here or in #debbugs on irc.debian.org; mucking with the
  found/fixed versions when the bug was actually found in that
  version generally isn't a good idea.
 
 So, what exactly is the use case for fixed?

fixed is there for cases where you've already -done'ed the bug, and
want to directly modify the fixed list (say you forgot to mention that
you fixed it in the changelog, or made a mistake, or someone found it
improperly, or...)

In most normal cases, you shouldn't need to use the fixed, found,
notfixed, or notfound commands directly. [Mails to n...@b.d.o with a
Version: psuedoheader do found (and reopen if appropriate), and mails
to nnn-d...@b.d.o with a Version: pseudoheader do fixed and done.]


Don Armstrong

-- 
We have to face the fact that either all of us are going to die
together or we are going to learn to live together and if we are to
live together we have to talk. 
 -- Eleanor Roosevelt

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