On 05/05/2018 05:41 PM, Andreas Tille wrote:
This might depend on git config push.default . I think if the value is "simple", then you need --all to push the pristine-tar and upstream branches.Hi Benjamin, On Sat, May 05, 2018 at 02:56:56PM +0200, Benjamin Redelings wrote:uscan --verbose --force-download gbp import-orig --pristine-tar bali-phy_3.1+dfsg.orig.tar.xz since the pristine-tar branch was not populated. Either you forgot the import-orig step or you did not pushed.1. Hmm... yes I think I only pushed master. My workflow notes now look like this: % uscan --verbose --force-download % gbp import-orig --pristine-tar ../bali-phy_<version>+dfsg.orig.tar.xz % gbp dch <edit debian/changelog to get correct version> % git push origin --all % debuild -S % cd .. % sudo pdebuild --update % sudo pdebuild --build bali-phy_version.dsc Does this look right?This does not look wrong but it is not needed to force `git push --all`. I only use gbp clone ... git push
This is helpful. Currently, this is not calling the hook scripts, so I used cowbuilder to run the hook scripts, and then gbp-buildpackage to build a full package. I have modified /etc/pbuilder/buildd-config.sh to set HOOKDIR=/var/cache/pbuilder/hooks, and added a hookfile C10_something to /root/.pbuilder/hooks and /home/bredelings/.pbuilder/hooks and /var/cache/pbuilder/hooks but gbp-buildpackage is still not calling the hooks on failure.which pushes branch master, upstream and pristine-tar. Moreover, I'd recommend to use gbp-buildpackage
Hmm... I somehow have a hard time using the debian-med policy as a guide, whereas other documentation like the new maintainer's guide is easier to follow.instead of sudo pdebuild --build in any case the sudo should not be needed here. May be you re-read Debian Med policy about how to use gbp. Please also let us know if this documentation is not really helpful - than we need to enhance it to make it better.
It feels like the debian-med policy is aimed at people who already understand debian packaging. For example, it says "set the devscripts variables DEBEMAIL and DEBFULLNAME", but does not say that this means editting ~/.devscripts to set environment variables.
The "git tips" section also feels like it is full of lots of pieces of information that I have a hard time connecting. My apologies for being slow at this!
In general, I think learning how to package for Debian is a confusing process, because there are so many different documents one needs to read, and they all have a different style for managing packages. As a result, I think being able to ask questions in person has been very helpful.
1. For the debian-med policy, would it be possible to generate the HTML version so that the section headings are numbered? I think this would make the structure more clear.
2. The git tips section has many little tips, but perhaps it could be organized into (a) an overview of setting up and updating package repos and (b) an FAQ-type section. I mostly need part (a). This could maybe be chronologically organized into (a.1) setting up config files (a.2) creating a new local git repo, and (a.3) updating the repo for a new version.
3. There is a nice sequence of commands for "To create a new local git repository" (a.2). Can we add a recommended sequence of commands for "Adding a new upstream release to the repo"? (a.3) Maybe it would look a little bit like this?
% uscan --verbose --force-download
% gbp import-orig --pristine-tar ../PKG_VERSION.orig.tar.xz
% gbp dch
<maybe run git clean -x -d -i to delete files left behind from a build>
% gbp-buildpackage // run pbuilder to build in a chroot
% git push --all
% git push --tags
I think it is very
helpful to have a basic working set of commands like this.
People can then play around with these command, read the man
pages, etc. Right now the policy doesn't say anything about
uscan, and that is a big time-saver.
However, it does
seem like you have to set up a number of config files for
gbp-buildpackage to actually work, and also probably run
'pbuilder --create --distribution sid' first, or something like
5. It might be worth mentioning the pbuilder hook for debugging build problems. pbuilder has a large learning curve, and it wasn't immediately clear what the hooks were for. So, it could have taken me a very long time to figure this out.
Anyway, I hope I am not causing trouble, and I hope these comments from a beginner are helpful.
This was extremely helpful!
(BTW, if you are on vacation, I am not expecting a quick response!)