[pkg-bacula-devel] Incomplete upload found in Debian upload queue

Bart Swedrowski bart at timedout.org
Thu Jun 28 09:51:24 UTC 2012

Hi Luca,

Thanks for lengthy response and all the tips.  Much appreciate that!

On 27 June 2012 16:01, Luca Capello <luca at pca.it> wrote:
> Some more, then:
> 1) you should add yourself to the Uploaders: field, so even if you can
>   not directly upload you appear as an official maintainer:

Sure, will do that.

> 2) I do not remember if I have already written about it or not, but you
>   should use git-buildpackage to easy build everything:
>     <https://honk.sigxcpu.org/piki/projects/git-buildpackage/>

Yep I did try to use git-buildpackage but ran into some problems
(probably very basic):

  1).  When I run git-buildpackage and it finishes it seems as
git-buildpackage doesn't really clean after itself.  This leaves the
repo which I'm working on in a really messy state.  I did try to clean
it up manually using 'debuild clean' however it doesn't really help.
Could you tip me on how do you deal with this stuff?  I did notice
when I use pbuilder, it's not happening (as probably its messing
around in the pbuilder environment).

  2).  More general question - how do you deal with building package
for multiple archs?  When I build (even using pbuilder) for i386 and
amd64, the first one overwrites .dsc file of the other one and if that
gets signed the former packages have incorrect checksums.  How do you
deal with that? (this is also the reason why you couldn't find .dsc
file in my repo - I simply built the packages with --debbuildopts "-B"
option not to include them; embarassing).

>   I pushed a change to debian/gbp.conf that should be propagated and
>   then adapted to squeeze-backports, so git-buildpackage will stop
>   complaining.

Aha!  Thanks for the tip - I'll get that over to "my" branch ;-)

>  Wait, the problem is another one: you did not upload the full set of
>  packages: it seems that the metapackages (bacula, -client and -server)
>  are missing while the real packages are there.

I shall investigate this (embarassing it slipped my attention in first place!).

>  $ DIST=base-squeeze gismo-pdebuild.sh --debbuildopts "-sa" \
>     --debbuildopts "-v5.0.2-1~bpo50+1"

I was wondering if you could share gismo-pdebuild.sh and your
.pbuilderrc file for reference for me?  I could probably work my way
through and get it finally to the state when it's optimal, but it'd be
a great help if I could use someone elses as an example one (I did
google around and found some, however there's so many its quite
difficult to judge which one is good and which ones are bad).

As you can see, the questions are really a bit embarassing ones, but
this happens when you build stuff just for yourself for quite a while
-- you can afford having nasty hacks as long as it works.  Public
packaging puts much more pressure on general state and best practices
(which I really like!) but it takes a bit to get aligned with.

Thanks for your patience!


More information about the pkg-bacula-devel mailing list