Re: [Pkg-crosswire-devel] First upload

[Roberto C . Sánchez]

On Wed, Feb 14, 2018 at 01:27:52PM +, Teus Benschop wrote:
>If I had waited an hour or so, I could have answered my own question -
>duh! :)
>The answer lies in the followup message from the Debian FTP Masters:
>ACL dm: not allowed to upload source package 'bibledit'
>The Debian Wiki
>at [1]https://wiki.debian.org/DebianMaintainer/Tutorial says that
>permission for a maintainer to upload can be set through a "dak" command.
>As described
>in 
> [2]https://lists.debian.org/debian-devel-announce/2012/09/msg8.html. 
>Could it be that this dak command would resolve the upload permission
>issue?
>Teus.
> 
Hi Teus,

Your key must first be added to the keyring and then you must be granted
upload permissions for the package(s) you will be uploading.  However,
for your key to be added to the keyring, you must complete the Debian
New Maintainer process.  I will look at your changes as soon as I can
and sponsor your upload.

Regards,

-Roberto

-- 
Roberto C. Sánchez

___
Pkg-crosswire-devel mailing list
Pkg-crosswire-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel

Re: [Pkg-crosswire-devel] First upload

[Teus Benschop]

If I had waited an hour or so, I could have answered my own question - duh!
:)

The answer lies in the followup message from the Debian FTP Masters:

ACL dm: not allowed to upload source package 'bibledit'

The Debian Wiki at https://wiki.debian.org/DebianMaintainer/Tutorial says
that permission for a maintainer to upload can be set through a "dak"
command. As described in
https://lists.debian.org/debian-devel-announce/2012/09/msg8.html.

Could it be that this dak command would resolve the upload permission issue?

Teus.
___
Pkg-crosswire-devel mailing list
Pkg-crosswire-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel

Re: [Pkg-crosswire-devel] First upload

[Teus Benschop]

Hi Roberto,

It is true that I need to complete the Debian New Maintainer Process, and
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 
Date: Wed, 24 Jan 2018 at 20:28
Subject: [rt.debian.org #7055] Teus Benschop to become a Debian Maintainer
To: 
Cc: , 

This key has now been added to the active DM keyring.

-- end forwarded message ---

When I read and interpret the information at
https://lists.debian.org/debian-devel-announce/2012/09/msg8.html well,
then the upload permission for one or more packages is described there, and
also at https://wiki.debian.org/DebianMaintainer/Tutorial.

If I receive this permission through the "dak" command, I believe, then I
should just be able to upload the packages I have received permission for
through that "dak" command.

Or am I reading or interpreting this information not in a correct way?

Teus.
___
Pkg-crosswire-devel mailing list
Pkg-crosswire-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel

[Pkg-crosswire-devel] Processing of bibledit_5.0.441-1_amd64.changes

[Debian FTP Masters]

bibledit_5.0.441-1_amd64.changes uploaded successfully to localhost
along with the files:
  bibledit_5.0.441-1.dsc
  bibledit_5.0.441.orig.tar.gz
  bibledit_5.0.441.orig.tar.gz.asc
  bibledit_5.0.441-1.debian.tar.xz
  bibledit-data_5.0.441-1_all.deb
  bibledit-dbgsym_5.0.441-1_amd64.deb
  bibledit_5.0.441-1_amd64.buildinfo
  bibledit_5.0.441-1_amd64.deb

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

___
Pkg-crosswire-devel mailing list
Pkg-crosswire-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel

[Pkg-crosswire-devel] bibledit_5.0.441-1_amd64.changes REJECTED

[Debian FTP Masters]

ACL dm: not allowed to upload source package 'bibledit'



===

Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.


___
Pkg-crosswire-devel mailing list
Pkg-crosswire-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel

Re: [Pkg-crosswire-devel] First upload

[Roberto C . Sánchez]

On Wed, Feb 14, 2018 at 02:01:55PM +, Teus Benschop wrote:
>Hi Roberto,
>It is true that I need to complete the Debian New Maintainer Process, and
>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:
>[1]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 <[2]r...@rt.debian.org>
>Date: Wed, 24 Jan 2018 at 20:28
>Subject: [[3]rt.debian.org #7055] Teus Benschop to become a Debian
>Maintainer
>To: <[4]n...@debian.org>
>Cc: <[5]archive-...@nm.debian.org>, <[6]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.

Regards,

-Roberto

-- 
Roberto C. Sánchez

___
Pkg-crosswire-devel mailing list
Pkg-crosswire-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel

Re: [Pkg-crosswire-devel] First upload

[Roberto C . Sánchez]

On Wed, Feb 14, 2018 at 03:00:18PM +, Teus Benschop wrote:
>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
>dak.
>When I quote from [1]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 [2]http://lists.debian.org/debian-devel-announce/2012/09/msg8.html
>-- end quote --

I will take a look at that later on today and I will let you know when
it is complete.

Regards,

-Roberto

-- 
Roberto C. Sánchez

___
Pkg-crosswire-devel mailing list
Pkg-crosswire-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel

Re: [Pkg-crosswire-devel] First upload

[Teus Benschop]

>
> I will take a look at that later on today and I will let you know when
> it is complete.
>
> Thank you, bro!
___
Pkg-crosswire-devel mailing list
Pkg-crosswire-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel

[Pkg-crosswire-devel] First upload

[Teus Benschop]

Hi Roberto,

I am trying to do my first upload of a bibledit package, in preparation of
uploading more packages to get some of the bugs fixed in them.

This is the upload command together with its output:

teus@sid:~$ dupload --to anonymous-ftp-master bibledit*.changes
dupload note: no announcement will be sent.
Checking signatures before upload..signatures are ok
Uploading (ftp) to ftp.upload.debian.org:/pub/UploadQueue/
[ job bibledit_5.0.441-1_amd64 from bibledit_5.0.441-1_amd64.changes
 bibledit-data_5.0.441-1_all.deb, size ok, md5sum ok, sha1sum ok, sha256sum
ok
 bibledit_5.0.441-1_amd64.buildinfo, size ok, md5sum ok, sha1sum ok,
sha256sum ok
 bibledit-dbgsym_5.0.441-1_amd64.deb, size ok, md5sum ok, sha1sum ok,
sha256sum ok
 bibledit_5.0.441-1_amd64.deb, size ok, md5sum ok, sha1sum ok, sha256sum ok
 bibledit_5.0.441.orig.tar.gz.asc, size ok, md5sum ok, sha1sum ok,
sha256sum ok
 bibledit_5.0.441.orig.tar.gz, size ok, md5sum ok, sha1sum ok, sha256sum ok
 bibledit_5.0.441-1.debian.tar.xz, size ok, md5sum ok, sha1sum ok,
sha256sum ok
 bibledit_5.0.441-1.dsc, size ok, md5sum ok, sha1sum ok, sha256sum ok
 bibledit_5.0.441-1_amd64.changes ok ]
Uploading (ftp) to anonymous-ftp-master (ftp.upload.debian.org)
+ FTP passive mode selected
[ Uploading job bibledit_5.0.441-1_amd64
 bibledit-data_5.0.441-1_all.deb 37967.0 kB, ok (14 s, 2711.93 kB/s)
 bibledit_5.0.441-1_amd64.buildinfo 14.7 kB, ok (0 s, 14.68 kB/s)
 bibledit-dbgsym_5.0.441-1_amd64.deb 20297.3 kB, ok (9 s, 2255.26 kB/s)
 bibledit_5.0.441-1_amd64.deb 2455.8 kB, ok (1 s, 2455.80 kB/s)
 bibledit_5.0.441.orig.tar.gz.asc 0.8 kB, ok (1 s, 0.81 kB/s)
 bibledit_5.0.441.orig.tar.gz 59532.8 kB, ok (21 s, 2834.89 kB/s)
 bibledit_5.0.441-1.debian.tar.xz 11.6 kB, ok (0 s, 11.59 kB/s)
 bibledit_5.0.441-1.dsc 2.5 kB, ok (1 s, 2.53 kB/s)
 bibledit_5.0.441-1_amd64.changes 3.6 kB, ok (0 s, 3.58 kB/s) ]

The documentation at the wiki at
https://wiki.debian.org/DebianMaintainer/Tutorial says to upload to either
ftp-master or ftp-eu. The above upload was done to anonymous-ftp-master and
seemed to be successful. I then tried to upload to ftp-master also:

teus@sid:~$ dupload --to ftp-master bibledit*.changes
dupload note: no announcement will be sent.
Checking signatures before upload..signatures are ok
Uploading (scpb) to ssh.upload.debian.org:/srv/
upload.debian.org/UploadQueue/
[ job bibledit_5.0.441-1_amd64 from bibledit_5.0.441-1_amd64.changes
 bibledit_5.0.441-1_amd64.deb, size ok, md5sum ok, sha1sum ok, sha256sum ok
 bibledit-data_5.0.441-1_all.deb, size ok, md5sum ok, sha1sum ok, sha256sum
ok
 bibledit_5.0.441.orig.tar.gz, size ok, md5sum ok, sha1sum ok, sha256sum ok
 bibledit_5.0.441.orig.tar.gz.asc, size ok, md5sum ok, sha1sum ok,
sha256sum ok
 bibledit_5.0.441-1.dsc, size ok, md5sum ok, sha1sum ok, sha256sum ok
 bibledit-dbgsym_5.0.441-1_amd64.deb, size ok, md5sum ok, sha1sum ok,
sha256sum ok
 bibledit_5.0.441-1_amd64.buildinfo, size ok, md5sum ok, sha1sum ok,
sha256sum ok
 bibledit_5.0.441-1.debian.tar.xz, size ok, md5sum ok, sha1sum ok,
sha256sum ok
 bibledit_5.0.441-1_amd64.changes ok ]
Uploading (scp) to ftp-master (ssh.upload.debian.org)
[ Uploading job bibledit_5.0.441-1_amd64
 bibledit_5.0.441-1_amd64.deb 2455.8 kB, ok
 bibledit-data_5.0.441-1_all.deb 37967.0 kB, ok
 bibledit_5.0.441.orig.tar.gz 59532.8 kB, ok
 bibledit_5.0.441.orig.tar.gz.asc 0.8 kB, ok
 bibledit_5.0.441-1.dsc 2.5 kB, ok
 bibledit-dbgsym_5.0.441-1_amd64.deb 20297.3 kB, ok
 bibledit_5.0.441-1_amd64.buildinfo 14.7 kB, ok
 bibledit_5.0.441-1.debian.tar.xz 11.6 kB, ok
 bibledit_5.0.441-1_amd64.changes 3.6 kB, ok
The authenticity of host 'ssh.upload.debian.org (128.31.0.69)' can't be
established.
ED25519 key fingerprint is
SHA256:/2BewgKzUVkFOkgYWwf4g6PAwWA6F6xBGHk1Nu5+k00.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'ssh.upload.debian.org,128.31.0.69' (ED25519) to
the list of known hosts.
t...@ssh.upload.debian.org: Permission denied (publickey).
lost connection

dupload: error: scp bibledit_5.0.441-1_amd64.deb
bibledit-data_5.0.441-1_all.deb bibledit_5.0.441.orig.tar.gz
bibledit_5.0.441.orig.tar.gz.asc bibledit_5.0.441-1.dsc
bibledit-dbgsym_5.0.441-1_amd64.deb bibledit_5.0.441-1_amd64.buildinfo
bibledit_5.0.441-1.debian.tar.xz bibledit_5.0.441-1_amd64.changes  failed
 at /usr/bin/dupload line 802

So at this stage I am not sure whether the upload to the anonymous ftp
server was sufficient, or whether it really should go to "ftp-master". In
case of the latter, my public key was denied.

My question now is whether the upload of the bibledit package was
successful or whether it was not.

Thanks for any help that clarifies this.

Teus.
___
Pkg-crosswire-devel mailing list
Pkg-crosswire-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-crosswire-devel