Stephen Gran wrote: [snip] > > > > "The maintainer name and email address used in the changelog should > > > > be the details of the person uploading this version. They are not > > > > necessarily those of the usual package maintainer." > > [snip] > > > I think that are two distinct concepts here. The first is the maintainer > > > of the package, which should receive any e-mail messages related to the > > > package. This name appears in the debian/changelog entry as well as in > > > the Maintainer field. All correspondence must be directed to this entity > > > (either a person or a mailing list). > > > > You apparently missed the quote above, which specifically talks about > > "the person uploading". > > And we are in danger of allowing policy to drive practice, rather than > vice versa.
This rule is in policy for a long time now. If you want to have it changed, please propose a policy change instead of simply violating policy. > The problem is, there are many packages currently being group > maintained. These groups generally have some sort of group contact > email address: > grep-dctrl -n -s Maintainer '' /var/lib/apt/lists/*Sources | grep list | wc -l > 843 > > I see exactly one false positive in that rather simple minded test, so > the number of packages maintined in this way is rather high. > > So, the complaint was that this: > > > > Maintainer: s390 Build Daemon <[EMAIL PROTECTED]> > > > Changed-By: Debian Octave Group <[EMAIL PROTECTED]> > > Doesn't have a real person behind it. When I look at the original, > though, I see: > > Maintainer: Debian Octave Group <[EMAIL PROTECTED]> > Changed-By: Rafael Laboissiere <[EMAIL PROTECTED]> > > That looks fine. > > It seems to me policy is lagging behind actual practice here, and the > right thing to do is add something to the effect that "the maintainer > field may also contain the contact information for the group maintaining > a package if it is group maintianed, so long as the Changed-By: field in > the original upload still contains the real name of the uploader." How could the autobuilder find out what the original Changed-By: content was? That is, short of reverse-engineering it from the signed .dsc, which may still choose the wrong key uid. Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]