[Pkg-crosswire-devel] debian/control Maintainer field

[Teus Benschop]

Hi friends,

There is a resolution online that describes the situation of Debian
Maintainers.

http://www.debian.org/vote/2007/vote_003

After reading it I realized that the current maintainer field of
packages bibledit-gtk, bibledit-xiphos, bibledit-bibletime and
gobiblecreator would not allow me to become a Debian Maintainer, since
the field needs to be set to the one who is going to upload these
packages in the future - the very thing I am after. So I made the
appropriate changes in this field, and added the DM-Upload-Allowed field
as well.

To be more precise, it is this bit that drew my attention:

-----
The initial policy for the use of the Debian Maintainer keyring with the
Debian archive will be to accept uploads signed by a key in that keyring
provided:

  * none of the uploaded packages are NEW
  * the Maintainer: field of the uploaded .changes file corresponds with
    the owner of the key used (ie, non-developer maintainers may not
    sponsor uploads)
  * none of the packages are being taken over from other source packages
  * the most recent version of the package uploaded to unstable or
    experimental includes the field "DM-Upload-Allowed: yes" in the
    source section of its control file
  * the most recent version of the package uploaded to unstable or
    experimental lists the uploader in the Maintainer: or Uploaders:
    fields (ie, non-developer maintainers cannot NMU or hijack packages)
  * the usual checks applied to uploads from Debian developers pass

----

Teus.