Is the something wrong ? If so, why no announcement ?  If not, will
some one PLEASE tell me what I am doing wrong ? How I can diagnose this problem ?
I have in the past uploaded several packages, I am not totally new to
this process.
Thanks for answering Hilmar, I was really wondering what is happening !
On 25/11/22 19:05, Hilmar Preuße wrote:
Things like these could for example happen if your GPG expired or yourrecently refreshed key did not make it into the keyring yet. Could this
be the case?
No, I don't think so Hilmar, I have checked my (debian) account, it has the same key as I am using to sign. I have checked the files and, yes, they are signed with that key. And its "expire never".
I have also checked that email I registered in my account works, that the
one hard wired in that cert works. And, obviously, debut checks some of that before uploading too.
Things like these could for example happen if your GPG expired or yourrecently refreshed key did not make it into the keyring yet. Could this
be the case?
Trying to upload package to ftp-master (ftp.upload.debian.org)
Acknowlegde on "it didn't work the first time"
My .dput.cfg requests ftp and is exactly as recommended.
Share it with us.
Thanks for any suggestions !
On Fri, Nov 25, 2022 at 09:37:53PM +1100, David Bannon wrote:
On 25/11/22 21:08, Geert Stappers wrote:Acknowlegde on "it didn't work the first time"
Do another upload.OK, this will be the third upload.
Share with us how it was done.
I move the .upload file out of the way, check the signature, dputShare it with us.
dbannon@debTestMate:~/Build35qt5$
dbannon@debTestMate:~/Build35qt5$ gpg --verify tomboy-ng_0.35-1_source.changes
gpg: Signature made Tue 22 Nov 2022 16:47:32 AEDT
gpg: using RSA key 264989F41EDA507BBF7FD2A339C055F6E2617741 >> gpg: issuer"tomboy-ng@bannons.id.au"
gpg: Good signature from "David Bannon<tomboy-ng@bannons.id.au>" [unknown] >> gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 2649 89F4 1EDA 507B BF7F D2A3 39C0 55F6 E261 7741 >> dbannon@debTestMate:~/Build35qt5$
dbannon@debTestMate:~/Build35qt5$
dbannon@debTestMate:~/Build35qt5$ dput tomboy-ng_0.35-1_source.changes
Trying to upload package to ftp-master (ftp.upload.debian.org)
Checking signature on .changes
gpg: /home/dbannon/Build35qt5/tomboy-ng_0.35-1_source.changes: Error checking signature from 39C055F6E2617741: SignatureVerifyError: 0
Checking signature on .dsc
gpg: /home/dbannon/Build35qt5/tomboy-ng_0.35-1.dsc: Error checking signature from 39C055F6E2617741: SignatureVerifyError: 0
Uploading to ftp-master (via ftp toftp.upload.debian.org):
Uploading tomboy-ng_0.35-1.dsc: done.
Uploading tomboy-ng_0.35.orig.tar.gz: done.
Uploading tomboy-ng_0.35-1.debian.tar.xz: done.
Uploading tomboy-ng_0.35-1_source.buildinfo: done.
Uploading tomboy-ng_0.35-1_source.changes: done.
Successfully uploaded packages.
dbannon@debTestMate:~/Build35qt5$
dbannon@debTestMate:~/Build35qt5$ cat tomboy-ng_0.35-1_source.ftp-master.upload
Successfully uploaded tomboy-ng_0.35-1.dsc toftp.upload.debian.org for ftp-master.
Successfully uploaded tomboy-ng_0.35.orig.tar.gz toftp.upload.debian.org for ftp-master.
Successfully uploaded tomboy-ng_0.35-1.debian.tar.xz toftp.upload.debian.org for ftp-master.
Successfully uploaded tomboy-ng_0.35-1_source.buildinfo toftp.upload.debian.org for ftp-master.
Successfully uploaded tomboy-ng_0.35-1_source.changes toftp.upload.debian.org for ftp-master.
dbannon@debTestMate:~/Build35qt5$
My .dput.cfg requests ftp and is exactly as recommended.
Thanks for any suggestions !Wait for a "works for me" message.
Groeten<html>
Geert Stappers
↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑↑I move the .upload file out of the way, check the signature, dput
dbannon@debTestMate:~/Build35qt5$ dput tomboy-ng_0.35-1_source.changes Trying to upload package to ftp-master (ftp.upload.debian.org)
On 25/11/22 21:08, Geert Stappers wrote:
Do another upload.
Share with us how it was done.
OK, this will be the third upload.
I move the .upload file out of the way, check the signature, dput
dbannon@debTestMate:~/Build35qt5$
dbannon@debTestMate:~/Build35qt5$ gpg --verify tomboy-ng_0.35-1_source.changes
gpg: Signature made Tue 22 Nov 2022 16:47:32 AEDT
gpg: using RSA key 264989F41EDA507BBF7FD2A339C055F6E2617741 gpg: issuer"tomboy-ng@bannons.id.au"
gpg: Good signature from "David Bannon<tomboy-ng@bannons.id.au>" [unknown] gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 2649 89F4 1EDA 507B BF7F D2A3 39C0 55F6 E261 7741 dbannon@debTestMate:~/Build35qt5$
dbannon@debTestMate:~/Build35qt5$
dbannon@debTestMate:~/Build35qt5$ dput tomboy-ng_0.35-1_source.changes
Trying to upload package to ftp-master (ftp.upload.debian.org)
Checking signature on .changes
gpg: /home/dbannon/Build35qt5/tomboy-ng_0.35-1_source.changes: Error checking signature from 39C055F6E2617741: SignatureVerifyError: 0
Checking signature on .dsc
gpg: /home/dbannon/Build35qt5/tomboy-ng_0.35-1.dsc: Error checking signature from 39C055F6E2617741: SignatureVerifyError: 0
Uploading to ftp-master (via ftp toftp.upload.debian.org):
Uploading tomboy-ng_0.35-1.dsc: done.
Uploading tomboy-ng_0.35.orig.tar.gz: done.
Uploading tomboy-ng_0.35-1.debian.tar.xz: done.
Uploading tomboy-ng_0.35-1_source.buildinfo: done.
Uploading tomboy-ng_0.35-1_source.changes: done.
Successfully uploaded packages.
dbannon@debTestMate:~/Build35qt5$
dbannon@debTestMate:~/Build35qt5$ cat tomboy-ng_0.35-1_source.ftp-master.upload
Successfully uploaded tomboy-ng_0.35-1.dsc toftp.upload.debian.org for ftp-master.
Successfully uploaded tomboy-ng_0.35.orig.tar.gz toftp.upload.debian.org for ftp-master.
Successfully uploaded tomboy-ng_0.35-1.debian.tar.xz toftp.upload.debian.org for ftp-master.
Successfully uploaded tomboy-ng_0.35-1_source.buildinfo toftp.upload.debian.org for ftp-master.
Successfully uploaded tomboy-ng_0.35-1_source.changes toftp.upload.debian.org for ftp-master.
dbannon@debTestMate:~/Build35qt5$
My .dput.cfg requests ftp and is exactly as recommended.
Thanks for any suggestions !
Do another upload.
Share with us how it was done.
On Fri, Nov 25, 2022 at 08:55:26PM +1100, David Bannon wrote:
Thanks for answering Hilmar, I was really wondering what is happening !Take that further
On 25/11/22 19:05, Hilmar Preuße wrote:Do another upload.
No, I don't think so Hilmar, I have checked my (debian) account, it has the >> same key as I am using to sign. I have checked the files and, yes, they are >> signed with that key. And its "expire never".Things like these could for example happen if your GPG expired or yourrecently refreshed key did not make it into the keyring yet. Could this
be the case?
I have also checked that email I registered in my account works, that the
one hard wired in that cert works. And, obviously, debut checks some of that >> before uploading too.
Share with us how it was done.
Groeten<html>
Geert Stappers
Did see the "not the wanted outcome message",
did not see yet what is happening at the transmitting end.
You are not uploading to mentors, but to ftp-master, which will silently discard your uploads.
You need to specify an upload target, since the default is ftp-master,
like so:
dput mentors tomboy-ng_0.35-1_source.changes
dbannon@debTestMate:~/Build35qt5$ dput tomboy-ng_0.35-1_source.changes
Trying to upload package to ftp-master (ftp.upload.debian.org)
Checking signature on .changes
gpg: /home/dbannon/Build35qt5/tomboy-ng_0.35-1_source.changes: Error
checking signature from 39C055F6E2617741: SignatureVerifyError: 0
Checking signature on .dsc
gpg: /home/dbannon/Build35qt5/tomboy-ng_0.35-1.dsc: Error checking
signature from 39C055F6E2617741: SignatureVerifyError: 0
Uploading to ftp-master (via ftp toftp.upload.debian.org):
Uploading tomboy-ng_0.35-1.dsc: done.
Uploading tomboy-ng_0.35.orig.tar.gz: done.
Uploading tomboy-ng_0.35-1.debian.tar.xz: done.
Uploading tomboy-ng_0.35-1_source.buildinfo: done.
Uploading tomboy-ng_0.35-1_source.changes: done.
Successfully uploaded packages.
dbannon@debTestMate:~/Build35qt5$
dbannon@debTestMate:~/Build35qt5$ cat tomboy-ng_0.35-1_source.ftp-master.upload
Successfully uploaded tomboy-ng_0.35-1.dsc toftp.upload.debian.org
for ftp-master.
Successfully uploaded tomboy-ng_0.35.orig.tar.gz
toftp.upload.debian.org for ftp-master.
Successfully uploaded tomboy-ng_0.35-1.debian.tar.xz
toftp.upload.debian.org for ftp-master.
Successfully uploaded tomboy-ng_0.35-1_source.buildinfo toftp.upload.debian.org for ftp-master.
Successfully uploaded tomboy-ng_0.35-1_source.changes
toftp.upload.debian.org for ftp-master.
dbannon@debTestMate:~/Build35qt5$
My .dput.cfg requests ftp and is exactly as recommended.
Thanks for any suggestions !
Davo
On 25/11/22 21:08, Geert Stappers wrote:
On Fri, Nov 25, 2022 at 08:55:26PM +1100, David Bannon wrote:
Thanks for answering Hilmar, I was really wondering what isTake that further
happening !
On 25/11/22 19:05, Hilmar Preuße wrote:Do another upload.
No, I don't think so Hilmar, I have checked my (debian) account,Things like these could for example happen if your GPG expiredrecently refreshed key did not make it into the keyring yet.
or your
Could this be the case?
it has the same key as I am using to sign. I have checked the
files and, yes, they are signed with that key. And its "expire
never".
I have also checked that email I registered in my account works,
that the one hard wired in that cert works. And, obviously, debut
checks some of that before uploading too.
Share with us how it was done.
Groeten
Geert Stappers
Did see the "not the wanted outcome message",
did not see yet what is happening at the transmitting end.
OK, my dput.cf has "fqdn = mentors.debian.net", I assumed that was that was for.It has it in a section named "mentors" and you didn't tell dput to use
On Fri, Nov 25, 2022 at 10:23:26PM +1100, David Bannon wrote:
OK, my dput.cf has "fqdn = mentors.debian.net", I assumed that was that was for.It has it in a section named "mentors" and you didn't tell dput to use
that section.
And https://mentors.debian.net/intro-maintainers/ tells to both create the section and pass its name to dput.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 299 |
Nodes: | 16 (2 / 14) |
Uptime: | 78:35:55 |
Calls: | 6,695 |
Files: | 12,229 |
Messages: | 5,347,583 |