Bug#1058696: bugs.debian.org: Can we change the mail address of the release.debian.org pseudo package?
Hi all, On 20-12-2023 05:17, Don Armstrong wrote: On Tue, 19 Dec 2023, Cord Beermann wrote: So I need some examples. :0 * 1^0 ^X-Debian-PR-Package:.*release.debian.org $junkdir/debbugs.$YEARMONTH should be sufficient to get most (if not all of them). Please hold. Some of the members of the team not present at Cambridge now raise concerns about this change. I admit that at least I *thought* you could subscribe in the bts to packages, but apparently that can only be done via the tracker. The tracker has hurdles due to its subscribing feature no longer being properly supported by browsers, so it's rather clumsy (it can be done). Let us try to agree first. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1058696: bugs.debian.org: Can we change the mail address of the release.debian.org pseudo package?
On Tue, 19 Dec 2023, Cord Beermann wrote: > So I need some examples. :0 * 1^0 ^X-Debian-PR-Package:.*release.debian.org $junkdir/debbugs.$YEARMONTH should be sufficient to get most (if not all of them). -- Don Armstrong https://www.donarmstrong.com Whatever you do will be insignificant, but it is very important that you do it. -- Mohandas Karamchand Gandhi
Bug#1058696: bugs.debian.org: Can we change the mail address of the release.debian.org pseudo package?
Hi Cord, On 19-12-2023 19:38, Cord Beermann wrote: Hallo! Du (Don Armstrong) hast geschrieben: On Sat, 16 Dec 2023, Cord Beermann wrote: However: if we implement this, i'd consider this as a workaround as mails that should not be distributed, should not be sent out in the first place. That works for me; there's a missing feature in the BTS currently to turn off e-mails to maintainers, so when that is in place, this workaround can be removed. So I need some examples. Are links to the lists.d.o enough? Or should I send you messages (with full headers)? (I'll start with the former) https://lists.debian.org/debian-release/2023/11/msg0.html https://lists.debian.org/debian-release/2023/11/msg7.html https://lists.debian.org/debian-release/2023/11/msg00020.html https://lists.debian.org/debian-release/2023/11/msg00029.html Paul OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1058696: bugs.debian.org: Can we change the mail address of the release.debian.org pseudo package?
Hallo! Du (Don Armstrong) hast geschrieben: > On Sat, 16 Dec 2023, Cord Beermann wrote: > > However: if we implement this, i'd consider this as a workaround as > > mails that should not be distributed, should not be sent out in the > > first place. > > That works for me; there's a missing feature in the BTS currently to > turn off e-mails to maintainers, so when that is in place, this > workaround can be removed. So I need some examples. Yours, Cord, Debian Listmaster of the day -- https://lists.debian.org
Bug#1058696: bugs.debian.org: Can we change the mail address of the release.debian.org pseudo package?
On Sat, 16 Dec 2023, Cord Beermann wrote: > However: if we implement this, i'd consider this as a workaround as > mails that should not be distributed, should not be sent out in the > first place. That works for me; there's a missing feature in the BTS currently to turn off e-mails to maintainers, so when that is in place, this workaround can be removed. -- Don Armstrong https://www.donarmstrong.com For a moment, nothing happened. Then, after a second or so, nothing continued to happen. -- Douglas Adams
Bug#1058696: bugs.debian.org: Can we change the mail address of the release.debian.org pseudo package?
Hallo! Du (Paul Gevers) hast geschrieben: > In bug 1058696 [1] I requested for the bts to start sending the e-mails for > the release.debian.org pseudo package to a different place than > debian-release@l.d.o. Don suggested an alternative: have the list procmail > rules filter out the bts reports. Would you be willing to do that (and do > you think it makes sense)? > > Paul > [1] https://bugs.debian.org/1058696 > > On 15-12-2023 06:02, Don Armstrong wrote: > > On Thu, 14 Dec 2023, Paul Gevers wrote: > > > Does it make sense to you to use the tracker as the canonical point > > > where e-mail is send, it's already send there anyways? > > > > I'm OK with sending the e-mail wherever y'all would like it. I'm also OK > > if debian-rele...@lists.debian.org is kept as the "maintainer" but bug > > email for the release.debian.org pseudopackage is discarded by > > lists.debian.org. [listmaster can do this with a procmail rule on > > lists.debian.org.] > > > > The advantage of the procmail rule is that someone looking to get in > > contact with the release team won't accidentally send their e-mail to a > > mailbox which no one ever will look at. > > > > But at the end of the day, it's up to y'all. Can you point me to one or two of the unwanted mails currently going to debian-release? However: if we implement this, i'd consider this as a workaround as mails that should not be distributed, should not be sent out in the first place. Yours, Cord, Debian Listmaster of the day -- https://lists.debian.org
Bug#1058696: bugs.debian.org: Can we change the mail address of the release.debian.org pseudo package?
Dear listmaster, In bug 1058696 [1] I requested for the bts to start sending the e-mails for the release.debian.org pseudo package to a different place than debian-release@l.d.o. Don suggested an alternative: have the list procmail rules filter out the bts reports. Would you be willing to do that (and do you think it makes sense)? Paul [1] https://bugs.debian.org/1058696 On 15-12-2023 06:02, Don Armstrong wrote: On Thu, 14 Dec 2023, Paul Gevers wrote: Does it make sense to you to use the tracker as the canonical point where e-mail is send, it's already send there anyways? I'm OK with sending the e-mail wherever y'all would like it. I'm also OK if debian-rele...@lists.debian.org is kept as the "maintainer" but bug email for the release.debian.org pseudopackage is discarded by lists.debian.org. [listmaster can do this with a procmail rule on lists.debian.org.] The advantage of the procmail rule is that someone looking to get in contact with the release team won't accidentally send their e-mail to a mailbox which no one ever will look at. But at the end of the day, it's up to y'all. OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1058696: bugs.debian.org: Can we change the mail address of the release.debian.org pseudo package?
On Thu, 14 Dec 2023, Paul Gevers wrote: > Does it make sense to you to use the tracker as the canonical point > where e-mail is send, it's already send there anyways? I'm OK with sending the e-mail wherever y'all would like it. I'm also OK if debian-rele...@lists.debian.org is kept as the "maintainer" but bug email for the release.debian.org pseudopackage is discarded by lists.debian.org. [listmaster can do this with a procmail rule on lists.debian.org.] The advantage of the procmail rule is that someone looking to get in contact with the release team won't accidentally send their e-mail to a mailbox which no one ever will look at. But at the end of the day, it's up to y'all. -- Don Armstrong https://www.donarmstrong.com "She decided what she wished to happen and then assumed that reality would bend to her wishes." [...] "Reality doesn't indulge wishes." -- Terry Goodkind _Phantom_ p133
Bug#1058696: bugs.debian.org: Can we change the mail address of the release.debian.org pseudo package?
Package: bugs.debian.org Severity: normal Control: affects -1 release.debian.org Hi, The Release Team has discussed its ways of working at the Cambridge mini DebConf and as part of that the volume and purpose of our mail list (debian-de...@lists.debian.org). We recognize that that list mostly just mirrors BTS traffic. The BTS already archives all information, and there are multiple ways anyone can subscribe to the Release Team bugs, so this mirroring seems unnecessary. More importantly it inhibits the list from being a more useful discussion channel that we like it to be. Hence, we'd like to direct the BTS traffic away from it. Does it make sense to you to use the tracker as the canonical point where e-mail is send, it's already send there anyways? Paul OpenPGP_signature.asc Description: OpenPGP digital signature
