cross-toolchain-base-devs team mailing list archive
Mailing list archive
Debian Packages and lists.launchpad.net in maintainer field
Cross Toolchain Base Team <cross-toolchain-base-devs@xxxxxxxxxxxxxxxxxxx>, Epoptes Developers <epoptes@xxxxxxxxxxxxxxxxxxx>, GNOME-Colors Packagers <gnome-colors-packagers@xxxxxxxxxxxxxxxxxxx>, Linaro Packagers <linaro-pkg@xxxxxxxxxxxxxxxxxxx>, OpenJDK Team <openjdk@xxxxxxxxxxxxxxxxxxx>,
Vagrant Cascadian <vagrant@xxxxxxxxxx>
Thu, 23 Mar 2017 15:19:55 -0000
Benjamin Drung <bdrung@xxxxxxxxxx>, Damien Raude-Morvan <drazzib@xxxxxxxxxx>, Dimitri John Ledkov <xnox@xxxxxxxxxx>, Alkis Georgopoulos <alkisg@xxxxxxxxx>, Wookey <wookey@xxxxxxxxxx>, Vagrant Cascadian <vagrant@xxxxxxxxxx>, Fathi Boudra <fabo@xxxxxxxxxx>, Andrew Starr-Bochicchio <a.starr.b@xxxxxxxxx>, Fotis Tsamis <ftsamis@xxxxxxxxx>
I noticed that some bug reports from bugs.debian.org were not getting
sent to the epoptes@xxxxxxxxxxxxxxxxxxx list when reported against the
Debian packages. I confirmed with the bugs.debian.org maintainers that
the messages were sent successfully from their end, but but it appears
that launchpad lists silently discard messages from email addresses
without an associated launchpad account.
I searched for other packages in presumably the same situation:
I've included the relevent teams in "To" on this mail, and all marked
Uploaders in "Cc".
Apparently, this is a violation of Debian policy:
3.3. The maintainer of a package
The maintainer must be specified in the `Maintainer' control field
with their correct name and a working email address. The email
address given in the `Maintainer' control field must accept mail
from those role accounts in Debian used to send automated mails
regarding the package. This includes non-spam mail from the
bug-tracking system, all mail from the Debian archive maintenance
software, and other role accounts or automated processes that are
commonly agreed on by the project
I haven't been able to figure out a way to configure launchpad lists to
comply with debian policy, but maybe there is some well-hidden way I
haven't been able to figure out.
Maybe we can convince the launchpad team to add some set of exceptions
for teams wanting use a launchpad list for Debian packages?
Description: PGP signature