Yes, that process completed fast, must faster than I expected. As you say,
it used to take much longer....
What is needed, as you say, is that permission is given to upload through
When I quote from https://wiki.debian.org/DebianMaintainer/Tutorial, it is
the "sponsor" who issues the dak command to grant permissions:
-- begin quote --
Once you have your key in the debian-maintainers keyring, you will be able
to upload packages, where the following conditions hold:
* the package does not have to pass through the NEW queue
* the sponsor has sent a dak command allowing you to upload as described in
-- end quote --
On Wed, 14 Feb 2018 at 15:06 Roberto C. Sánchez <robe...@debian.org> wrote:
> On Wed, Feb 14, 2018 at 02:01:55PM +0000, Teus Benschop wrote:
> > Hi Roberto,
> > It is true that I need to complete the Debian New Maintainer Process,
> > that then my key must be added to the Debian Maintainer key right.
> > Both of these two things have been done already.
> > Here is the link to the completed and approved Debian New Maintainers
> > Process:
> > https://nm.debian.org/process/426
> > And here is the email I received saying that the key has been added
> to the
> > active DM keyring:
> > ---------- Forwarded message ---------
> > From: Jonathan McDowell via RT <r...@rt.debian.org>
> > Date: Wed, 24 Jan 2018 at 20:28
> > Subject: [rt.debian.org #7055] Teus Benschop to become a Debian
> > Maintainer
> > To: <n...@debian.org>
> > Cc: <archive-...@nm.debian.org>, <teusjanne...@gmail.com>
> > This key has now been added to the active DM keyring.
> > -- end forwarded message ---
> Wow! That was fast. The process moves much more quickly now than it
> did when I became a Debian Developer :-)
> It looks like you are right and that what is needed is for the archive
> maintainers give you permissions through dak to upload bibledit.
> Roberto C. Sánchez
> Pkg-crosswire-devel mailing list
Pkg-crosswire-devel mailing list