On 05/03/2025 02:45, Adam D. Barratt wrote:
On Wed, 2025-03-05 at 01:32 +0800, Blair Noctis wrote:On 04/03/2025 21:43, Marc Haber wrote:On Tue, 4 Mar 2025 19:15:16 +0800, Blair Noctis <n...@debian.org> wrote: [...]Honestly I never understood how exactly @p.d.o addresses work. Devref says it's "a simple email alias" that "provides a way to email the maintainer", "whatever their individual email address (or addresses) may be", but doesn't tell which kind of email addresses it forwards to.[...]though it seems further clarification can only come from p.d.o staff."Staff" is a weird term to use in free software contexts. :-)
p.d.o is a service, after all ;)
In any case you're looking for https://salsa.debian.org/webmaster-team/packages/-/blob/debian-master/bin/build-maintainerdb
Thanks, this seems to be the canonical source of an answer. Though with my limited Perl knowledge, I can only see that it 0. reads an override file, 1. searches through the indices/Maintainers file in an archive, whose naming presumably means the Maintainer field of packages, 2. records found email, but ignores when it ends with @p.d.o or @tracker.d.o, 3. writes remaining email, along with tracker dispatch address, for each package. So IIUC, @p.d.o address forwards to 1. the Maintainer if it's not again a @p.d.o, nor @tracker.d.o, 2. tracker subscribers. So if the "staff" agrees, we can make @p.d.o addresses forward also to Uploaders, thus with @p.d.o address as Maintainer, also forwarding bug reports to Uploaders, achieving the goal. Aside: I'm amused, and horrified at the same time, that such a maintainer "database" is a plain text file. -- Sdrager, Blair Noctis
OpenPGP_signature.asc
Description: OpenPGP digital signature
