Hi Andreas, On Thu, Aug 28, 2014, at 02:09 AM, Andreas Tille wrote:
> > [amul:3] The HTML doc link above indicated going to the initial source > > import. I tried that (see the bit about COMMIT_ID), but the merge resulted > > in numerous conflicts. I fired up gitk and saw prior upstream commits had > > already chained off the initial source import until the upstream/6.0-003. I > > used the commit ID of the upstream/6.0-003 below. > > > > git clone ssh://git.debian.org/git/debian-med/fis-gtm.git fis-gtm-debmed.git > > cd fis-gtm-debmed.git > > git branch upstream d883233f4018839ce9f3da6faa57a5de8e2de98f > > git-import-orig --pristine-tar ~/Downloads/fis-gtm-V6.1-000.tar.gz -u > > 6.1-000 > > <commit> > > dch -v 6.1-000 > > <commit> > > rm -rf .pc > > While `rm -rf .pc` is sensible before commiting you should make sure > that you do not forget `quilt pop -a` before. [amul:4] I check git status -s before moving forward. > > [amul:3] I ended up hitting the same error that stopped me in my tracks > > last time. Here's the error. I'll try to correct it tomorrow. > > > > Finished running lintian. > > Now signing changes and any dsc files... > > signfile fis-gtm_6.1-000.dsc Amul Shah <[email protected]> > > gpg: directory `/home/shaha/.gnupg' created > > gpg: new configuration file `/home/shaha/.gnupg/gpg.conf' created > > gpg: WARNING: options in `/home/shaha/.gnupg/gpg.conf' are not yet active > > during this run > > gpg: keyring `/home/shaha/.gnupg/secring.gpg' created > > gpg: keyring `/home/shaha/.gnupg/pubring.gpg' created > > gpg: skipped "Amul Shah <[email protected]>": secret key not > > available > > gpg: /tmp/debsign.BbZPAaF6/fis-gtm_6.1-000.dsc: clearsign failed: secret > > key not available > > debsign: gpg error occurred! Aborting.... > > debuild: fatal error at line 1271: > > running debsign failed > > Well, do you have a valid GPG key? If not please create one (I hope > there are pointers in new maintainer guide - if not a web search like > site:debian.org create gpg key > will uncover reasonable docs. [amul:4] The regular docs were good. > > [amul:3] Where I am right now: I committed my changes, but could not test > > them. If someone else could give it a try that would be a great help. I > > also have a git push error that I don't understand. I try doing some more > > searches tomorrow. > > To give a short summary: > > 0. create gpg key > 1. gbp-clone ssh://git.debian.org/git/debian-med/fis-gtm.git > 2. cd fis-gtm > 3. git import-orig --pristine-tar <new_upstream_tarball> > 4. dch -i > 5. git commit > 6. git-buildpackage > 7. git push [amul:4] This helps, thanks. I hit an error at step 6. I'm going to go search for answers, but wanted to let you know that I am making progress. dpkg-source: info: using source format `3.0 (quilt)' dpkg-source: info: building fis-gtm using existing ./fis-gtm_6.1-000.orig.tar.gz dpkg-source: error: cannot represent change to fis-gtm/fis-gtm_6.0-003.orig.tar.gz.delta: binary file contents changed dpkg-source: error: add fis-gtm_6.0-003.orig.tar.gz.delta in debian/source/include-binaries if you want to store the modified binary in the debian tarball dpkg-source: error: cannot represent change to fis-gtm/fis-gtm_6.0-001.orig.tar.gz.delta: binary file contents changed dpkg-source: error: add fis-gtm_6.0-001.orig.tar.gz.delta in debian/source/include-binaries if you want to store the modified binary in the debian tarball dpkg-source: error: unrepresentable changes to source dpkg-buildpackage: error: dpkg-source -i -I -b fis-gtm gave error exit status 2 [amul:4] You asked in another mail if port 22 is blocked and it is. We have tools for allowed out-bound SSH connections but they don't work for git.debian.org. I'm guessing that host is disallowed for port 22 access. Best Regards, Amul -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/1409314443.3808090.158164749.40a4a...@webmail.messagingengine.com
