*Change GPG key* Current GPG key: 2048R/DE8473B0 Delete current key: GPG key: Please use the output of gpg ...
On Thu, Apr 7, 2016 at 3:08 AM, Gianfranco Costamagna < [email protected]> wrote: > strange, I did look at ftp://mentors.debian.net/ and I didn't see them > (they disappear once accepted) > > > maybe you can double check your gpg key here > https://mentors.debian.net/my > > gpg --recv-keys DE8473B0 > gpg: requesting key DE8473B0 from hkp server keys.gnupg.net > gpgkeys: key DE8473B0 not found on keyserver > gpg: no valid OpenPGP data found. > gpg: Total number processed: 0 > > > seems that your key isn't on global keyservers, check at least it is on > mentors. > > G. > > Il Giovedì 7 Aprile 2016 8:35, Herbert Elwood Gilliland III < > [email protected]> ha scritto: > > > > G, > > I wasn't able to use that dput.cf, but I did use your dpkg-* info .. I > will see if this time using Steffen's upload method worked. > > log: > > [02:33:54 main]$ dput mentors-ftp fed_0.94a-1_source.changes > Checking signature on .changes > gpg: Signature made Thu Apr 7 02:32:10 2016 EDT using RSA key ID DE8473B0 > gpg: Good signature from "Herb Gilliland (fed author) < > [email protected]>" > Good signature on /home/main/temp/fed_0.94a-1_source.changes. > Checking signature on .dsc > gpg: Signature made Thu Apr 7 02:32:07 2016 EDT using RSA key ID DE8473B0 > gpg: Good signature from "Herb Gilliland (fed author) < > [email protected]>" > Good signature on /home/main/temp/fed_0.94a-1.dsc. > Uploading to mentors-ftp (via ftp to mentors.debian.net): > Uploading fed_0.94a-1.dsc: done. > Uploading fed_0.94a.orig.tar.gz: done. > Uploading fed_0.94a-1.debian.tar.gz: done. > Uploading fed_0.94a-1_source.changes: done. > Successfully uploaded packages. > > > On Thu, Apr 7, 2016 at 2:26 AM, Gianfranco Costamagna < > [email protected]> wrote: > > I usually do > >dpkg-buildpackage -S -sa > > > >dput mentors ../packagename_version_source.changes > > > >this should work. > > > >my ~/.dput.cf > >[mentors] > >method = ftp > >fqdn = mentors.debian.net > >incoming = . > >login = anonymous > > > > > >I use dput-ng, and I have my public key on mentors, under my account. > > > > > >(well, I don't use mentors anymore, but I used to) > > > >G. > > > > > > > >Il Giovedì 7 Aprile 2016 6:32, Herbert Elwood Gilliland III < > [email protected]> ha scritto: > > > > > > > >Well, it's not large.. um, yeah no dice still no packages appearing under > "my packages" > > > > > >On Wed, Apr 6, 2016 at 8:37 PM, Steffen Möller <[email protected]> > wrote: > > > >Sounds large ;) > >> > >>Thumbs pressed. > >> > >>Steffen > >> > >> > >>On 07/04/16 02:32, Herbert Elwood Gilliland III wrote: > >>> I guess AFAIK from FAQ > >>> > >>> > >>> How long will it take until my upload is available to sponsors? > >>> > >>> If you upload via FTP, which you must do if a package is too large for > >>> the HTTP uploader, then there can be up to a 30 minute delay before > >>> your package gets processed. > >>> > >>> > >>> > >>> On Wed, Apr 6, 2016 at 8:30 PM, Herbert Elwood Gilliland III > >>> <[email protected] <mailto:[email protected]>> wrote: > >>> > >>> Steffen, > >>> > >>> Thanks. One discrepancy was that I was attempting HTTP before, > >>> though I did switch to ftp ... regardless, following your > >>> instructions, I was able to FTP properly! > >>> > >>> However, after uploading, my package did not appear under "my > >>> packages" at mentors.debian.net <http://mentors.debian.net> -- is > >>> this not instantaneous, or does it take some amount of time longer > >>> than a few minutes? > >>> > >>> My name on mentors: Herbert Elwood Gilliland III > >>> My name in signage: Herb Gilliland > >>> > >>> Email is identical, though. > >>> > >>> Doesn't appear on mentors.debian.net <http://mentors.debian.net> > >>> either for today.. but maybe I'm just expecting it too soon? > >>> > >>> -h > >>> > >>> p.s. log: > >>> > >>> [20:25:16 main]$ dput mentors-ftp fed_0.94a-1_i386.changes > >>> Checking signature on .changes > >>> gpg: Signature made Wed Apr 6 20:24:49 2016 EDT using RSA key ID > >>> DE8473B0 > >>> gpg: Good signature from "Herb Gilliland (fed author) > >>> <[email protected] <mailto:[email protected]>>" > >>> Good signature on /home/main/temp/fed_0.94a-1_i386.changes. > >>> Checking signature on .dsc > >>> gpg: Signature made Wed Apr 6 20:24:46 2016 EDT using RSA key ID > >>> DE8473B0 > >>> gpg: Good signature from "Herb Gilliland (fed author) > >>> <[email protected] <mailto:[email protected]>>" > >>> Good signature on /home/main/temp/fed_0.94a-1.dsc. > >>> Uploading to mentors-ftp (via ftp to mentors.debian.net > >>> <http://mentors.debian.net>): > >>> Uploading fed_0.94a-1.dsc: done. > >>> Uploading fed_0.94a.orig.tar.gz: done. > >>> Uploading fed_0.94a-1.debian.tar.gz: done. > >>> Uploading fed_0.94a-1_i386.deb: done. > >>> Uploading fed_0.94a-1_i386.changes: done. > >>> Successfully uploaded packages. > >>> > >>> > >>> On Wed, Apr 6, 2016 at 8:19 PM, Steffen Möller > >>> <[email protected] <mailto:[email protected]>> wrote: > >>> > >>> > >>> > >>> On 07/04/16 01:12, Herbert Elwood Gilliland III wrote: > >>> > Thanks all.. except: > >>> > > >>> > > >>> > [19:11:24 main]$ dput -f mentors fed_0.94a-1_i386.changes > >>> > Checking signature on .changes > >>> > gpg: Signature made Tue Apr 5 10:07:24 2016 EDT using RSA > >>> key ID DE8473B0 > >>> > gpg: Good signature from "Herb Gilliland (fed author) > >>> > <[email protected] <mailto:[email protected]> > >>> <mailto:[email protected] > >>> <mailto:[email protected]>>>" > >>> > Good signature on /home/main/temp/fed_0.94a-1_i386.changes. > >>> > Checking signature on .dsc > >>> > gpg: Signature made Tue Apr 5 10:07:20 2016 EDT using RSA > >>> key ID DE8473B0 > >>> > gpg: Good signature from "Herb Gilliland (fed author) > >>> > <[email protected] <mailto:[email protected]> > >>> <mailto:[email protected] > >> > >>> <mailto:[email protected]>>>" > >>> > Good signature on /home/main/temp/fed_0.94a-1.dsc. > >>> > Checksum doesn't match for > /home/main/temp/fed_0.94a-1_i386.deb > >>> > > >>> > > >>> > Is this " done "? > >>> > > >>> Admittedly - not so. Your previous email has shown that you > >>> already know > >>> much more about it all than )you need to know to produce a > >>> working > >>> package. It must be something ... weird. I expect you to > >>> experience > >>> what you experienced if you once ran everything successfully > >>> and then > >>> decided to run "fakeroot ./debian/rules binary" again or so, > >>> such that > >>> debs and the changes are no longer in sync. > >>> > >>> If you do not mind too much, please remove all the debs of > >>> yours and the > >>> changes and dsc files, i.e. only leave the source tree with > >>> the debian > >>> folder and you orig.tar.xz (gz, bz2, whatever) file and > >>> rebuild the > >>> package. > >>> > >>> To build, I use > >>> dpkg-buildpackge -rfakeroot -uc -us > >>> from within the source tree and the compressed tarball in .. . > >>> > >>> You then find the newly created .changes and .dsc and .debs in > >>> .., too. > >>> > >>> I then typically > >>> cd.. > >>> and > >>> debsign -kMYK3YID *.changes > >>> > >>> This -k option to debsign is helpful for sponsoring, i.e. when > the > >>> maintainer is not the one signing for the upload. It also > helps to > >>> disambiguate should you have multiple keys matching your email > >>> address, > >>> so I was mentioning it here. > >>> > >>> And dput should just work, then. Send me (or Gianfranco) a > >>> reference to > >>> your packaging work if not. Sponsoring implies to rebuild, > anyway. > >>> > >>> Good luck! > >>> > >>> Steffen > >>> > >>> > >>> > >> > >> > > >
