[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[fis-gtm] git-buildpackage is working



FYI,
Thanks to questions from Luis and Andreas, I have moved forward. :) My first mistake was not using sudo to start git-buildpacakge. I dropped cowbuilder and the build works. But, you knew  there was one, I cannot complete the build because I don't have GPG keys!

This is how the build log finishes.
-----------------------------------------------
Finished running lintian.
Now signing changes and any dsc files...
 signfile fis-gtm_6.0-001-1.dsc Amul Shah <Amul.Shah@fisglobal.com>
gpg: skipped "Amul Shah <Amul.Shah@fisglobal.com>": secret key not available
gpg: /tmp/debsign.lPOutHj4/fis-gtm_6.0-001-1.dsc: clearsign failed: secret key not available
debsign: gpg error occurred!  Aborting....
-----------------------------------------------

I did create a GPG key for myself defined for my personal email address, not my work email address. How do others handle this? Do you create two keys? Or do you create just one for your personal email address?

thanks,
Amul


On 02/18/2013 01:03 PM, Amul Shah wrote:
Hello Yaroslav,
Following the instructions that Andreas pointed to, I created a GIT repo on alioth for fis-gtm. When I try to debcheckout, I hit an error.

---------------------------------------------------------------------------------------------------------------------------
12:41pm [shaha@shaha:/home/shaha/debmed/testbuild] >debcheckout --git-track='*' git+ssh://git.debian.org/git/debian-med/fis-gtm.git
declared git repository at git+ssh://git.debian.org/git/debian-med/fis-gtm.git
git clone git+ssh://git.debian.org/git/debian-med/fis-gtm.git fis-gtm ...
Cloning into 'fis-gtm'...
remote: Counting objects: 3115, done.
remote: Compressing objects: 100% (2005/2005), done.
remote: Total 3115 (delta 1103), reused 3111 (delta 1103)
Receiving objects: 100% (3115/3115), 4.74 MiB | 446 KiB/s, done.
Resolving deltas: 100% (1103/1103), done.
Branch pristine-tar set up to track remote branch pristine-tar from origin.
Branch upstream set up to track remote branch upstream from origin.
Use of uninitialized value $srcpkg in substitution (s///) at /usr/bin/debcheckout line 822.
---------------------------------------------------------------------------------------------------------------------------

I found a thread with a similar error, http://lists.debian.org/debian-med/2012/10/msg00057.html, but I did push all my changes up with git push --all --set-upstream. For instance:
---------------------------------------------------------------------------------------------------------------------------
12:42pm [shaha@shaha:/home/shaha/debmed/fis-gtm-6.0.001] >git push --all --set-upstream
Branch master set up to track remote branch master from origin.
Branch pristine-tar set up to track remote branch pristine-tar from origin.
Branch upstream set up to track remote branch upstream from origin.
Everything up-to-date

---------------------------------------------------------------------------------------------------------------------------

I can debcheckout from the repo on my machine. But when I try to use git-buildpackage, it complains about "cp: cannot stat `/var/cache/pbuilder/base.cow': No such file or directory". I guess I'm missing some setup. If so, is there a quick start guide? Otherwise, what doc do I need to read?

thanks,
Amul
_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.

Reply to: