Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1178726 > unrolled thread

Bug#1058696: bugs.debian.org: Can we change the mail address of the release.debian.org pseudo package?

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#1058696: bugs.debian.org: Can we change the mail address of the release.debian.org pseudo package? Paul Gevers <elbrus@debian.org> - 2023-12-14 18:10 +0100
    Bug#1058696: bugs.debian.org: Can we change the mail address of the release.debian.org pseudo package? Don Armstrong <don@debian.org> - 2023-12-15 06:20 +0100
      Bug#1058696: bugs.debian.org: Can we change the mail address of the release.debian.org pseudo package? Paul Gevers <elbrus@debian.org> - 2023-12-15 22:30 +0100
        Bug#1058696: bugs.debian.org: Can we change the mail address of the release.debian.org pseudo package? Cord Beermann <cord@debian.org> - 2023-12-16 11:20 +0100
          Bug#1058696: bugs.debian.org: Can we change the mail address of the release.debian.org pseudo package? Don Armstrong <don@debian.org> - 2023-12-19 00:10 +0100
            Bug#1058696: bugs.debian.org: Can we change the mail address of the release.debian.org pseudo package? Cord Beermann <cord@debian.org> - 2023-12-19 19:40 +0100
              Bug#1058696: bugs.debian.org: Can we change the mail address of the release.debian.org pseudo package? Don Armstrong <don@debian.org> - 2023-12-20 05:30 +0100

#1178726 — Bug#1058696: bugs.debian.org: Can we change the mail address of the release.debian.org pseudo package?

[Multipart message — attachments visible in raw view] — view raw

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-devel@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

[toc] | [next] | [standalone]

#1178778

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-release@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

[toc] | [prev] | [next] | [standalone]

#1178867

[Multipart message — attachments visible in raw view] — view raw

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-release@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.
> 

[toc] | [prev] | [next] | [standalone]

#1178894

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-release@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

[toc] | [prev] | [next] | [standalone]

#1179237

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

[toc] | [prev] | [next] | [standalone]

#1179345

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

[toc] | [prev] | [next] | [standalone]

#1179427

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web