#904449 Forward BTS mails to tracker.debian.org, not packages.qa.debian.org

#904449#5
Date:
2018-07-24 13:15:36 UTC
From:
To:
Package: bugs.debian.org
Severity: important

Hello Don, it's been multiple years since I announced the need to
use tracker.debian.org instead of packages.qa.debian.org to forward
mails to package tracker subscribers:
https://lists.debian.org/debian-devel-announce/2015/12/msg00001.html

We discussed this last year before DebConf and you planned to work on
it during DebConf, alas nothing happened. I'm now filing a bug report
to have a trace of former discussions and considerations.

I won't be at DebConf this year either but I'd love to see this fixed
in the not-too-distant future.

[2017-06-20 16:41:39] <buxy> People keep asking me about an "official switch" from packages.qa to tracker.d.o but for me the switch is done, it's just that the BTS and packages.d.o are the last services linking to it
[2017-06-20 16:43:49] <dondelelcaro> OK; does tracker.debian.org also now handle subscriptions? Or is tha t still packages.qa.debian.org?
[2017-06-20 16:44:34] <buxy> tracker.d.o handles all the subscriptions and all the mails, yes
[2017-06-20 16:44:57] <dondelelcaro> awesome; that's super easy then.
[2017-06-20 16:45:38] <buxy> In what way was that question relevant? Is there some way the BTS is relying on PTS subscriptions?
[2017-06-20 16:46:01] <dondelelcaro> the BTS sends emails to pkg@packages.qa.debian.org
[2017-06-20 16:46:17] <dondelelcaro> so now it will instead send to pkg@tracker.debian.org
[2017-06-20 16:46:34] <buxy> Please send it to dispatch@tracker.debian.org.
[2017-06-20 16:46:38] <dondelelcaro> uh...
[2017-06-20 16:47:19] <buxy> Or dispatch+<source>@tracker.debian.org if you really want to indicate the source package, but the code figures it out already with the headers that you are adding.
[2017-06-20 16:48:11] <dondelelcaro> ah; OK. this is going to require some engineering time
[2017-06-20 16:48:14] <dondelelcaro> sorry. :(
[2017-06-20 16:48:29] <buxy> https://lists.debian.org/debian-devel-announce/2015/12/msg00001.html
[2017-06-20 16:49:20] <dondelelcaro> got it; thanks
[2017-06-20 16:51:09] <dondelelcaro> I'll try to work on that shortly
[2017-06-20 16:51:10] <buxy> In that case, can you please update the web links quickly and handle the mail part when you have more time?
[2017-06-20 16:51:20] <dondelelcaro> they're combined
[2017-06-20 16:51:24] <buxy> ah, ok
[2017-06-20 16:51:59] <dondelelcaro> probably should fix that so they're not too
[2017-06-20 16:54:51] <buxy> How do you feel about not handling the list of maintainers yourself so that you would only send mails to a generic email instead of the email documented in Maintainer?
[2017-06-20 16:55:39]  * buxy would like to get rid of the discrepancy between maintainers and uploaders and handle all subscriptions at the package tracker level
[2017-06-20 16:58:51] <dondelelcaro> I'll have to keep the feature, but we could certainly make it configurable
[2017-06-20 16:59:37] <dondelelcaro> are you going to be at debconf?
[2017-06-20 16:59:50] <buxy> Cool. No, not this year unfortunately.
[2017-06-20 16:59:54] <dondelelcaro> ah, ok.
[2017-06-20 17:00:33] <dondelelcaro> might be good to hash out a plan to migrate to that so maintainers/developers/interested parties can manage their package subscriptions in a single place
[2017-06-20 17:03:40] <buxy> definitely, http://dep.debian.net/deps/dep2/ could be it but the scope I gave it a long-long-time ago is a bit large
[2017-06-20 17:10:28] <dondelelcaro> makes sense
[2017-06-20 17:10:45] <dondelelcaro> I'll try to figure that all out, and if I have questions, I'll bug you
[2017-06-22 03:44:35] <dondelelcaro> thinking about this some more, is there any reason why you couldn't just subscribe to debian-bugs-dist?
[2017-06-22 03:45:09] <dondelelcaro> then I could just change the link on the web page, disable the Cc: to package@packages.qa.debian.org, and wham-bam, we're done.
[2017-06-22 08:57:06] <buxy> I don't think it's that easy. How are handled mails which are cced to multiple bugs on different packages? or those that are control replies affecting multiple packages?
[2017-06-22 08:58:33] <buxy> Hum, if we have X-Debian-PR-Source with all the sources packages, then it would work, yes.
[2017-06-22 08:58:46] <buxy> I already coded distro tracker that way.
[2017-06-22 08:59:10] <buxy> But then we need a single copy of the mail with multiple values in that field.
[2017-06-22 21:40:15] <dondelelcaro> hrm; I'll have to double check that; I don't know of those mails get all of the headers.


FWIW I'm not a big fan of having an explicit mail subscription, the subscription
could be ended by a malicious request or by some  automatic bounce handling in
case we have a temporary mail configuration issue. And at that point we will
take a lot of time to remember that there is a subscription and to figure out
that the subscription is in fact gone.

Cheers,

#904449#10
Date:
2025-08-16 17:41:55 UTC
From:
To:
Control: tags -1 + patch

Hello Don & the team,

time flies, already 7 years since I filed that bug :)

As we were trying to get rid of packages.qa.debian.org with Philip Kern, I
rediscovered that the BTS still sends mails to packages.qa.debian.org
instead of tracker.debian.org.

So I had a quick look at the code and tried to produce a patch. Please
find it attached.

It looks like we have two different ways to figuring out the recipients,
and one might not yet be in active use... not exactly sure. In any case,
I updated both places.

It would be really nice if you could review and fix/merge as appropriate,
and deploy it so that we can rid of packages.qa.debian.org for good.

Thank you in advance.

#904449#17
Date:
2025-08-16 19:04:21 UTC
From:
To:
I noticed that I made this patch on the master branch of the git
repository. However it applies fine on the debian branch too
and I couldn't find any further changes to make.

However I added an extra commit to change the name of the service
in the web page, so I'm attaching the two patches that I have against
the debian branch now.

BTW I noticed that the debian branch uses a $config{package_tracking_domain}
but there's no $gPackageTrackingDomain in example/config.debian, you might
want to add it in the tracker-related section that I added.

Cheers,