Re: The BTS and bug subscriptions
On Tue, Jul 26, 2005 at 01:13:04PM +1000, Pascal Hakim wrote: It's trivial to add uids to a GPG key, and headers aren't actually signed anyway, so you could replay signed messages to the server. A global, confirmed by default subscribe me to all my bugs might do the trick, though. -- You grabbed my hand and we fell into it, like a daydream - or a fever. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The BTS and bug subscriptions
Steve Langasek wrote: This is nice to see. IME, as a release manager/bug triager and as a member of package maintenance teams, the distributions I want to be able to use for bug mails are: - to the submitter and to the maintainer (most common) - to the maintainer only and IME as a sole maintainer of packages, the distributions I want are: - to the submitter only This is problimatic when a maintainer vanishes or drops a bug half way through. I'd rather see to the submitter and the maintainer unless the maintainer sent the mail, which works in both this case and the one above. - -quiet As implemented this is problimatic for those of us who read debian-bugs-dist (only in a semi-automated fashion nowadays though). But to the maintainer unless the maintainer sent the mail handles this case and the second one above. as a single destination address on bugs.d.o, and even better if the reply-to's on bugs mail were set so that I never had to fiddle with headers again when replying to bugs :) Well, if it's narrowed down to the two cases I've mentioned above, it's sort oflike doing a list reply vs a personal reply. Although I'm not sure which maps better to which. Anyway, should be possible to set up the headers so that works in mail clients. -- see shy jo signature.asc Description: Digital signature
Re: The BTS and bug subscriptions
As in once you confirmed one subscription the next one doesn't ask anymore? Sort of greylisting? Sounds good. It should always ask for confirmation unless someone has specifically made the decision that they don't want to have to opt-in. Maybe it should honour subscription requests without confirmation if request is GPG-signed by the key with uid equal to address being subscribed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The BTS and bug subscriptions
On Fri, 2005-07-22 at 15:30 -0700, Don Armstrong wrote: On Fri, 22 Jul 2005, Peter Samuelson wrote: Now ... how hard would it be to add 'submit-subscribe@' support? Most of the time, when I submit a bug report, I'd like to subscribe to it. Would this be a straightforward hack? What has actually been discussed is automatically subscribing submitters to the bug report unless some special header/pseudo-header is added to prevent that. [It's possible that this subscription would happen without even needing to confirm the subscription... but that's still undecided.] As an update to this, AJ has posted a note on the stuff he'd like to see in the BTS[1]. This really relates to his point 4 relating to the refactoring of the mail distribution. Expect more on the subject in the upcoming future. Pasc [1]: http://lists.debian.org/debian-debbugs/2005/07/msg00089.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The BTS and bug subscriptions
On Sat, 2005-07-23 at 06:25 -0500, Peter Samuelson wrote: [Don Armstrong] What has actually been discussed is automatically subscribing submitters to the bug report unless some special header/pseudo-header is added to prevent that. Sounds good. But since this information was already tracked, I figured there must have been a (good?) reason this hasn't been done in the past. Not that I can think of one. The discussions we had on the topic at Debconf revolved around whether someone who submits a bug wants to know the technical discussions relating to the bug fix, whether we should send it to them, and how do we make sure they get a copy if the maintainer needs to ask the bug submitter for more information. Cheers, Pasc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The BTS and bug subscriptions
On Tue, 2005-07-26 at 00:33 +0400, Nikita V. Youshchenko wrote: As in once you confirmed one subscription the next one doesn't ask anymore? Sort of greylisting? Sounds good. It should always ask for confirmation unless someone has specifically made the decision that they don't want to have to opt-in. Maybe it should honour subscription requests without confirmation if request is GPG-signed by the key with uid equal to address being subscribed. I'm afraid this doesn't give us much. It's trivial to add uids to a GPG key, and headers aren't actually signed anyway, so you could replay signed messages to the server. Cheers, Pasc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The BTS and bug subscriptions
On Tue, Jul 26, 2005 at 01:05:51PM +1000, Pascal Hakim wrote: On Fri, 2005-07-22 at 15:30 -0700, Don Armstrong wrote: On Fri, 22 Jul 2005, Peter Samuelson wrote: Now ... how hard would it be to add 'submit-subscribe@' support? Most of the time, when I submit a bug report, I'd like to subscribe to it. Would this be a straightforward hack? What has actually been discussed is automatically subscribing submitters to the bug report unless some special header/pseudo-header is added to prevent that. [It's possible that this subscription would happen without even needing to confirm the subscription... but that's still undecided.] As an update to this, AJ has posted a note on the stuff he'd like to see in the BTS[1]. This really relates to his point 4 relating to the refactoring of the mail distribution. Expect more on the subject in the upcoming future. This is nice to see. IME, as a release manager/bug triager and as a member of package maintenance teams, the distributions I want to be able to use for bug mails are: - to the submitter and to the maintainer (most common) - to the maintainer only and IME as a sole maintainer of packages, the distributions I want are: - to the submitter only - -quiet It would be great to see each of these mail distribution targets available as a single destination address on bugs.d.o, and even better if the reply-to's on bugs mail were set so that I never had to fiddle with headers again when replying to bugs :) -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: The BTS and bug subscriptions
[Re-sent, gmane seems to have swallowed the original version.] Petter Reinholdtsen [EMAIL PROTECTED] wrote: [Florian Weimer] Developers must be careful to Cc: the submitters, otherwise they probably never receive the message. What about the [EMAIL PROTECTED] address? I thought it send a message both to BTS and to the submitter? I use it all the time when I want the submitter to get the message. I almost never CC to the submitter. Hello, [EMAIL PROTECTED] is archived in the BTS (http://b.d.o/nnn) *and* forwarded to the submitter but _not_ forwarded to the maintainer. Iirc it sets Reply-To: yoursenderaddress, [EMAIL PROTECTED] in the forwared mail, so the submitter's answer will not reach the maintainer either, as it is sent to -quiet. Iirc the bts is now smart enough to not show a mail sent To: [EMAIL PROTECTED],[EMAIL PROTECTED] twice on http://b.d.o/nnn. cu andreas -- See, I told you they'd listen to Reason, [SPOILER] Svfurlr fnlf, fuhggvat qbja gur juveyvat tha. Neal Stephenson in Snow Crash http://downhill.aus.cc/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The BTS and bug subscriptions
On Sat, Jul 23, 2005 at 12:39:19PM +0200, Florian Weimer wrote: * Petter Reinholdtsen: [Florian Weimer] Developers must be careful to Cc: the submitters, otherwise they probably never receive the message. What about the [EMAIL PROTECTED] address? It's an alias for the email address of the submitter. AFAICS, messages to this address do not end up in the BTS. They do. They're not sent to the maintainer, but they are recorded in the bug log and displayed when viewing the bug. (If you send a mail to both nn@ and nn-submitter@, though, bugreport.cgi will spot the two messages with duplicate Message-IDs and only show you the first one.) Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The BTS and bug subscriptions
On Sat, Jul 23, 2005 at 10:37:02PM +0200, Goswin von Brederlow wrote:
Kurt Roeckx [EMAIL PROTECTED] writes:
On Fri, Jul 22, 2005 at 06:11:14PM +1000, Pascal Hakim wrote:
It is now possible to subscribe and unsubscribe from individual bugs in
the Bug Tracking System. To do so, simply send an email to
[EMAIL PROTECTED], or [EMAIL PROTECTED], where
nnn is the bug number you wish to {,un}subscribe to. You will then need to
reply to the confirmation email for the action to take effect.
I would like that I don't have to confirm each time I subscribe
to a bug. Could there be some list added so that you don't need
to confirm your subscription?
Kurt
As in once you confirmed one subscription the next one doesn't ask
anymore? Sort of greylisting?
Sounds good.
It should always ask for confirmation unless someone has specifically
made the decision that they don't want to have to opt-in.
Cheers,
Pasc
--
Pascal Hakim 0403 411 672
Do Not Bend
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The BTS and bug subscriptions
* Jochen Voss: Hi Goswin, On Sat, Jul 23, 2005 at 01:55:19AM +0200, Goswin von Brederlow wrote: subscribing [the initial submitter] is already the current way. Really? Since when is this the case? Just to stress Jochen's point: only closing a bug report automatically triggers mail to the initial submitter, unless something has changed very recently. Developers must be careful to Cc: the submitters, otherwise they probably never receive the message. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The BTS and bug subscriptions
* Don Armstrong: No, it wouldn't. The messages are only sent to people after they have made it through the spam filters, and for sumitter, it's even more difficult, because the message must be formatted properly to actually generate a new bug instead of an error. The idea was for the submitter,[1] not random commenters to the bug, to receive this special treatment. And this would be a very, very useful change. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The BTS and bug subscriptions
[Florian Weimer] Developers must be careful to Cc: the submitters, otherwise they probably never receive the message. What about the [EMAIL PROTECTED] address? I thought it send a message both to BTS and to the submitter? I use it all the time when I want the submitter to get the message. I almost never CC to the submitter. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The BTS and bug subscriptions
On Sat, Jul 23, 2005 at 01:55:19AM +0200, Goswin von Brederlow wrote: Not subscribing the initial submitter would be insane and subscribing him is already the current way. Not in the sense that's being discussed here, it isn't. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The BTS and bug subscriptions
* Petter Reinholdtsen: [Florian Weimer] Developers must be careful to Cc: the submitters, otherwise they probably never receive the message. What about the [EMAIL PROTECTED] address? It's an alias for the email address of the submitter. AFAICS, messages to this address do not end up in the BTS. But my point is that you actually have to put this address in the Cc: field if you send mail to the [EMAIL PROTECTED] address. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The BTS and bug subscriptions
Florian Weimer [EMAIL PROTECTED] writes: * Jochen Voss: Hi Goswin, On Sat, Jul 23, 2005 at 01:55:19AM +0200, Goswin von Brederlow wrote: subscribing [the initial submitter] is already the current way. Really? Since when is this the case? Just to stress Jochen's point: only closing a bug report automatically triggers mail to the initial submitter, unless something has changed very recently. Developers must be careful to Cc: the submitters, otherwise they probably never receive the message. You are right, my bad. Only closing gets send out to the submitter. And with that in mind I'm very much for subscribing the submitter automatically. Half the time I forget to CC the submitter when I write something to a bug and I guess many other people forget that when commentating too. There should be a pseudo header that reportbug can add if subscribtion isn't automatic. When submitting a bug one can't mail nnn-subscribe as the number isn't known yet but it would be nice to do both in one go. MfG Goswin PS: sorry for doing a 180, I wasn't thinking clearly before. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The BTS and bug subscriptions
[Don Armstrong] What has actually been discussed is automatically subscribing submitters to the bug report unless some special header/pseudo-header is added to prevent that. Sounds good. But since this information was already tracked, I figured there must have been a (good?) reason this hasn't been done in the past. Not that I can think of one. signature.asc Description: Digital signature
Re: The BTS and bug subscriptions
Hello Don, Am 2005-07-22 15:30:35, schrieb Don Armstrong: What has actually been discussed is automatically subscribing submitters to the bug report unless some special header/pseudo-header is added to prevent that. [It's possible that this subscription would happen without even needing to confirm the subscription... but that's still undecided.] But what abourt people which are subscribed to packages like me ? Do they get the messages twice ? I think, the BTS should prevent sending messages twice. Greetings Michelle -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSM LinuxMichi 0033/3/8845235667100 Strasbourg/France IRC #Debian (irc.icq.com) signature.pgp Description: Digital signature
Re: The BTS and bug subscriptions
On Fri, Jul 22, 2005 at 06:11:14PM +1000, Pascal Hakim wrote:
It is now possible to subscribe and unsubscribe from individual bugs in
the Bug Tracking System. To do so, simply send an email to
[EMAIL PROTECTED], or [EMAIL PROTECTED], where
nnn is the bug number you wish to {,un}subscribe to. You will then need to
reply to the confirmation email for the action to take effect.
I would like that I don't have to confirm each time I subscribe
to a bug. Could there be some list added so that you don't need
to confirm your subscription?
Kurt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The BTS and bug subscriptions
Kurt Roeckx [EMAIL PROTECTED] writes:
On Fri, Jul 22, 2005 at 06:11:14PM +1000, Pascal Hakim wrote:
It is now possible to subscribe and unsubscribe from individual bugs in
the Bug Tracking System. To do so, simply send an email to
[EMAIL PROTECTED], or [EMAIL PROTECTED], where
nnn is the bug number you wish to {,un}subscribe to. You will then need to
reply to the confirmation email for the action to take effect.
I would like that I don't have to confirm each time I subscribe
to a bug. Could there be some list added so that you don't need
to confirm your subscription?
Kurt
As in once you confirmed one subscription the next one doesn't ask
anymore? Sort of greylisting?
Sounds good.
MfG
Goswin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The BTS and bug subscriptions
[Pascal Hakim] It is now possible to subscribe and unsubscribe from individual bugs in the Bug Tracking System. To do so, simply send an email to [EMAIL PROTECTED], or [EMAIL PROTECTED] THANK YOU, those of you who coded and deployed this! This is something I've wanted as long as I can remember. It's right up there between versioned provides and sliced bread. Now ... how hard would it be to add 'submit-subscribe@' support? Most of the time, when I submit a bug report, I'd like to subscribe to it. Would this be a straightforward hack? Thanks, Peter signature.asc Description: Digital signature
Re: The BTS and bug subscriptions
Pascal Hakim [EMAIL PROTECTED] writes: Hi everyone, One of the oft-requested features for the BTS had been the ability to subscribe to bugs. It is now possible to subscribe and unsubscribe from individual bugs in the Bug Tracking System. ... Many thanks to Joachim Breitner and Don Armstrong who provided most of the code, Anthony Towns and Colin Watson for their advice, and everyone at Debconf who piped in with suggestions along the way. You rock. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The BTS and bug subscriptions
On 22/07/05, Pascal Hakim [EMAIL PROTECTED] wrote:
Hi everyone,
One of the oft-requested features for the BTS had been the ability to
subscribe to bugs.
It is now possible to subscribe and unsubscribe from individual bugs in
the Bug Tracking System. To do so, simply send an email to
[EMAIL PROTECTED], or [EMAIL PROTECTED], where
now, how about [EMAIL PROTECTED] because I have a
feeling that co-maintainers/uploaders get bug reports for a project.
nnn is the bug number you wish to {,un}subscribe to. You will then need to
reply to the confirmation email for the action to take effect.
You will then receive any emails sent to the bug number, as well as
related messages such as bug closing messages.
This can be pretty useful to:
-Keep track of bugs that affect you
-Know when bug 400,000 gets filed
-Monitor your NMs
-Do many other things...
Many thanks to Joachim Breitner and Don Armstrong who provided most of
the code, Anthony Towns and Colin Watson for their advice, and everyone
at Debconf who piped in with suggestions along the way.
Cheers,
Pasc
--
Pascal Hakim+61 403 411 672
Do Not Bend
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFC4Koh3+27IiW81b8RAgt6AKDcJiiY1Utq1veaj4C8UwFkaM/uvwCcC3Tg
JEI8xPZ/4tGql0bQvpVCxJQ=
=nt+a
-END PGP SIGNATURE-
--
N Jones
Blogging @ http://nigelj.blogspot.com
Proud Debian FOSS User
Debian Maintainer of: html2ps ipkungfu
Re: The BTS and bug subscriptions
On Sat, 2005-07-23 at 00:33 +1200, Nigel Jones wrote: now, how about [EMAIL PROTECTED] because I have a feeling that co-maintainers/uploaders get bug reports for a project. Use the package tracking system[1] for this. Kind regards, Philipp Kern [1] http://packages.qa.debian.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The BTS and bug subscriptions
On Fri, 22 Jul 2005, Peter Samuelson wrote: Now ... how hard would it be to add 'submit-subscribe@' support? Most of the time, when I submit a bug report, I'd like to subscribe to it. Would this be a straightforward hack? What has actually been discussed is automatically subscribing submitters to the bug report unless some special header/pseudo-header is added to prevent that. [It's possible that this subscription would happen without even needing to confirm the subscription... but that's still undecided.] Don Armstrong -- My spelling ability, or rather the lack thereof, is one of the wonders of the modern world. http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The BTS and bug subscriptions
Don Armstrong [EMAIL PROTECTED] writes: On Fri, 22 Jul 2005, Peter Samuelson wrote: Now ... how hard would it be to add 'submit-subscribe@' support? Most of the time, when I submit a bug report, I'd like to subscribe to it. Would this be a straightforward hack? What has actually been discussed is automatically subscribing submitters to the bug report unless some special header/pseudo-header is added to prevent that. [It's possible that this subscription would happen without even needing to confirm the subscription... but that's still undecided.] Don Armstrong That would subscribe every spam the BTS recieves. Very bad I think. I would rather add a pseudo-header to subscribe and have reportbug ask if it should add it (or always add it before the editor is forked). MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The BTS and bug subscriptions
* Goswin von Brederlow: What has actually been discussed is automatically subscribing submitters to the bug report unless some special header/pseudo-header is added to prevent that. [It's possible that this subscription would happen without even needing to confirm the subscription... but that's still undecided.] That would subscribe every spam the BTS recieves. Very bad I think. Even if we restrict it to initial submitters? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The BTS and bug subscriptions
Florian Weimer [EMAIL PROTECTED] writes: * Goswin von Brederlow: What has actually been discussed is automatically subscribing submitters to the bug report unless some special header/pseudo-header is added to prevent that. [It's possible that this subscription would happen without even needing to confirm the subscription... but that's still undecided.] That would subscribe every spam the BTS recieves. Very bad I think. Even if we restrict it to initial submitters? Not subscribing the initial submitter would be insane and subscribing him is already the current way. So there would be no change to discuss. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The BTS and bug subscriptions
On Sat, 23 Jul 2005, Goswin von Brederlow wrote: Don Armstrong [EMAIL PROTECTED] writes: On Fri, 22 Jul 2005, Peter Samuelson wrote: Now ... how hard would it be to add 'submit-subscribe@' support? Most of the time, when I submit a bug report, I'd like to subscribe to it. Would this be a straightforward hack? What has actually been discussed is automatically subscribing submitters to the bug report unless some special header/pseudo-header is added to prevent that. [It's possible that this subscription would happen without even needing to confirm the subscription... but that's still undecided.] That would subscribe every spam the BTS recieves. Very bad I think. No, it wouldn't. The messages are only sent to people after they have made it through the spam filters, and for sumitter, it's even more difficult, because the message must be formatted properly to actually generate a new bug instead of an error. The idea was for the submitter,[1] not random commenters to the bug, to receive this special treatment. Everyone else can just send two messages, one to [EMAIL PROTECTED], the other to [EMAIL PROTECTED] Don Armstrong 1: Mainly because the submitter doesn't know yet what the bug number is that they're supposed to subscribe to. -- Build a fire for a man, an he'll be warm for a day. Set a man on fire, and he'll be warm for the rest of his life. -- Jules Bean http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The BTS and bug subscriptions
Hi Goswin, On Sat, Jul 23, 2005 at 01:55:19AM +0200, Goswin von Brederlow wrote: subscribing [the initial submitter] is already the current way. Really? Since when is this the case? Jochen -- http://seehuhn.de/ signature.asc Description: Digital signature
