Your message dated Sun, 18 Sep 2011 09:51:54 +0200
with message-id <[email protected]>
and subject line Re: Bug#641818: bts subscribe does not work
has caused the Debian Bug report #641818,
regarding bts subscribe does not work
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
641818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641818
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: devscripts
Version: 2.11.1
Severity: normal
File: /usr/bin/bts
Hi,
the command
bts subscribe 123456
does not seem to work, I get no response at all.
Using subscribe in a mail to control@ together with other commands results
in the following error:
======
Processing commands for [email protected]:
> subscribe 641344
There is no Debian Bug mailing list. If you wish to review bug reports
please do so via http://www.debian.org/Bugs/ or ask this mail server
to send them to you.
soon: MAILINGLISTS_TEXT
> #other commands ...
=====
But BTS(1) mentions
subscribe bug [email]
Subscribe the given email address to the specified bug report.
If no email address is specified, ...
Sending mail to 123456-subscribe@ does work.
Andreas
--- End Message ---
--- Begin Message ---
On 2011-09-17 14:57, James Vega wrote:
>> ======
>> Processing commands for [email protected]:
>>
>>> subscribe 641344
>> There is no Debian Bug mailing list. If you wish to review bug reports
>> please do so via http://www.debian.org/Bugs/ or ask this mail server
>> to send them to you.
>> soon: MAILINGLISTS_TEXT
>>> #other commands ...
>> =====
Eventually treat this as a wishlist bug for control@ (and
reopen/reassign/retitle/... in that case): forward the
subscribe nnn [!|email]
command to nnn-subscribe like the bts command would do, using [email] or
[From:] as sender.
Or state in the bts manual page that the "manipulation commands"
subscribe/unsubscribe cannot be used with control@
> One email was sent (to control@) to modify the tags and another sent (to
> nnn-subscribe@) to subscribe me to the bug.
>
> I suggest taking a look at your mail log to see if that sheds some light
> on what's happening.
More than a half day later I got replies for all my subscription tests.
The different path (control@ vs. nnn-subscribe@) may be a reason,
probably some greylisting rules delayed the mails somewhere.
I was just confused that all the other control@ activity at the same
time was fulfilled within minutes - as was a manual request to
nnn-subscribe@ (which was eventually graylisting-unlocked by an earlier
test).
Andreas
--- End Message ---
