Hi Mark, Archive Administrator wrote: > > Accepted: > gob2_2.0.16-3.debian.tar.gz > to main/g/gob2/gob2_2.0.16-3.debian.tar.gz > gob2_2.0.16-3.dsc > to main/g/gob2/gob2_2.0.16-3.dsc > gob2_2.0.16-3_amd64.deb > to main/g/gob2/gob2_2.0.16-3_amd64.deb > > > Override entries for your package: > gob2_2.0.16-3.dsc - source devel > gob2_2.0.16-3_amd64.deb - extra devel > > Announcing to debian-devel-chan...@lists.debian.org
>From the changelog: > * Orphan package. Right, but orphaned packages are _not_ set to this discussion ML. A quick look at the devref or at any of the over 436 orphaned packages would have told you the correct address. Even running lintian on the package you uploaded points you to the right direction: $ lintian gob2_2.0.16-3.dsc W: gob2 source: _changelog-should-mention-nmu_ W: gob2 source: source-nmu-has-incorrect-version-number 2.0.16-3 W: gob2 source: debhelper-but-no-misc-depends gob2 W: gob2 source: package-uses-deprecated-debhelper-compat-version 4 E: gob2 source: *wrong-debian-qa-address-set-as-maintainer* Debian QA <debian-qa@lists.debian.org> W: gob2 source: _no-human-maintainers_ W: gob2 source: out-of-date-standards-version 3.8.2 (current is 3.8.4) $ lintian-info -t wrong-debian-qa-address-set-as-maintainer N: wrong-debian-qa-address-set-as-maintainer N: N: Orphaned packages should no longer have the address N: <debian-qa@lists.debian.org> in the Maintainer field. N: N: The correct Maintainer field for orphaned packages is Debian QA Group N: <packa...@qa.debian.org>. N: N: Refer to Debian Developer's Reference section 5.9.4 (Orphaning a N: package) for details. N: N: Severity: important, Certainty: certain N: If tools are written for the purpose of catching mistakes (and bugs) beforehand *please use them*. Thanks. Kind regards, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4bd78b2c.1608c00a.4fc5.ffffc...@mx.google.com
