[pkg-bacula-devel] debcheckout & gbp, the workflow

[Alexander Golovko]

В Tue, 13 Aug 2013 12:55:34 +0200
Geert Stappers <stappers at stappers.nl> пишет:

> Op 2013-08-13 om 11:26 schreef Alexander Golovko:
> > ?? Mon, 12 Aug 2013 23:45:18 +0200 Geert Stappers ??????????:
> > 
> > > Hello,
> > 
> > Hi!
> > 
> > > During an attempt to build bacula, I did encounter a FTBFS.
> > > Most likely it is me doing something wrong.
> > > 
> > > I have done `debcheckout bacula`, `cd bacula`,
> > > `dpkg-checkbuilddeps`. Full filled the build depends on a fresh
> > > Debian unstable install. And then `fakeroot debian/rules binary`
> > > gives me a lot of ../lib/lib.h:62:18: fatal error: sha1.h: No
> > > such file or directory #include "sha1.h"
> > > and then dies with
> > >  chmod 755 debian/scripts/install-dbconfig
> > >  dh_install
> > >  cp: cannot stat 'debian/tmp/etc/bacula/scripts/btraceback.gdb':
> > > No such file or directory dh_install: cp -a
> > > debian/tmp/etc/bacula/scripts/btraceback.gdb
> > > debian/bacula-common//etc/bacula/scripts/ returned exit code 1
> > > make[1]: *** [override_dh_install] Error 2
> > > 
> > 
> > This is look like quilt patches was not applied.
> > Try to add "quilt push -a" before building. Or use
> > "git-buildpackage -b"
> 
> started with `git-buildpackage -b` and got messages as
>  gbp:warn: Pristine-tar branch "pristine-tar" not found
>  gbp:error: Couldn't run 'debuild -i -I -b': debuild -i -I returned 29

Are all build-dependencies installed?

If you run git-buildpackage without pbuilder/cowbuilder, you should
manually install all build-depends.


> 
> got the warning about pristine-tar branch fixed with
>  git checkout pristine-tar
>  git checkout master
> 
> (the "gbp:error: Couldn't run 'debuild -i -I -b'" remains)
> 
> 
> `quilt push -a` replied to me with
>   No series file found 
> 
> `cd debian` plus `quilt push -a` replied with several
>   No file to patch.  Skipping patch.
>   1 out of 1 hunk ignored

I'm sorry, quilt by-default search patches in other directory.
For use it directly, add to ~/.quiltrc:

QUILT_PATCHES=debian/patches
QUILT_NO_DIFF_INDEX=1
QUILT_NO_DIFF_TIMESTAMPS=1
QUILT_REFRESH_ARGS="-p ab"


> 
> 
> > > My own research got me the file debian/gbp.conf, so now I'm
> > > reading
> > > http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.html
> > > the git build package documentation. Yes, that means that I'm new
> > > to GBP.
> > > 
> > > My question:
> > >  Does "pkg-bacula at alioth" flow the same workflow as GBP
> > > documentation?
> > 
> > I'm not sure, that our workflows absolutely the same, but we use
> > git-buildpackage and pbuilder/cowbuilder for building bacula
> > packages.
> 
> What I'm looking for, is the workflow of bacula packaging.
> 
> I'm willing the read the fine manual. Please tell me which manual.
> Currently I assume it is the generic git buildpackage documentation.
> Please let know if bacula-pkg does something special that newbies
> should be aware off.
> 
> 
> > > Groeten
> > > Geert Stappers
> > > Dealing with two new compoments: bacula build and git build
> > > package
> 
> and cowbuilder would be a third NEW compoment for me.
> That is an investment that I'm willing to make,
> please guide^Wpoint me to documentation.

Add to your ~/.gbp.conf:

[DEFAULT]
pbuilder = True

and use "cowbuilder --create ..." for create environment.


PS: Also you can use "dpkg-buildpackage -b"


-- 
with best regards,
Alexander Golovko
email: alexandro at ankalagon.ru
xmpp: alexandro at ankalagon.ru
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-bacula-devel/attachments/20130813/96a9afa8/attachment.sig>