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

[Luca Capello]

Hi Bart!

On Thu, 28 Jun 2012 11:51:24 +0200, Bart Swedrowski wrote:
> Thanks for lengthy response and all the tips.  Much appreciate that!

You are welcome, I should probably take all the tips about the
pkg-bacula's "policy" and put it somewhere on the Alioth webspace.

> On 27 June 2012 16:01, Luca Capello <luca at pca.it> wrote:
>> 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).

First, have you tried without git-buildpackage, but simply with
`debuild`?  You will discover that debuild does not clean the
environment after having built the package, but only at the beginning.
Thus, git-buildpackage is correct *if* --git-builder is the default
(i.e. debuild).

However, building packages on a "dirty" setup is not good and you should
always use pbuilder.  Unfortunately, git-pbuilder is *not* for pbuilder,
but for cowbuilder :-(

>   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).

You have two different kinds of binaries: -all and -arch.  The former
are built once (the first time you upload a new package version), the
second are built for any arch you have defined in debian/control
Architecture: field for binary packages.  In this way, .dsc files are
not overwritten, .changes are different and you can upload both :-)

Hint: `man dpkg-buildpackage`:

	4. It calls  dpkg-source -b  to generate the  source package
	   (unless a  binary-only build has been  requested with -b,
	   -B or -A).

>>  $ 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).

The problem is that even if my snippet could be useful, they should be
reported upstream via the BTS and I do not want to pollute the world
with something too much custom.  Finding the time to do that is the
bottleneck in my life :-)

Nevertheless, everything is available on people.d.o, please give me any
feedback for the reason I just explained:

  <http://people.debian.org/~gismo/debian/>

> 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.

Basically, my advice would be to Do It Right™ from the beginning:
obviously it takes more time, but then you are safe.  You should read
some docs, in order of difficulty and completeness:

- Debian New Maintainers' Guide

    <http://www.debian.org/doc/manuals/maint-guide/>

- Debian Developer's Reference

    <http://www.debian.org/doc/manuals/developers-reference/>

- Debian Policy

    <http://www.debian.org/doc/debian-policy/>

Thx, bye,
Gismo / Luca
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-bacula-devel/attachments/20120704/def8ec03/attachment.pgp>