[Pkg-crosswire-devel] trying to get started ....

Roberto C. Sánchez roberto at connexer.com
Sat Mar 29 11:39:07 GMT 2014

Hi Barry,

On Sat, Mar 29, 2014 at 10:09:29AM +0000, Barry Drake wrote:
> Hi there .....  I've been around the Sword project for years.
> Recently, it was pointed out that the Sword debian packages are all
> well out of date, and I'm beginning to regret saying that I'd look
> into it.  I've studies the Debian packaging information at:

Thanks for pitching in to help!

> https://www.debian.org/doc/manuals/maint-guide/index.en.html  and
> installed all the recommended packages.  I've tried to make a
> package, but it fails with the same error, which is:
> dh build
>    dh_testdir
>    debian/rules override_dh_auto_build
> make[1]: Entering directory `/home/barry/prog/sword-1.7.2'
> dh_auto_build -Scmake --parallel
> dh_auto_build: error: unable to chdir to obj-i686-linux-gnu
> make[1]: *** [override_dh_auto_build] Error 2
> make[1]: Leaving directory `/home/barry/prog/sword-1.7.2'
> make: *** [build] Error 2
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
Which package are you trying to build?  What version?  Have you made any
changes, or are you trying to build what is currently in the archive?
What distro/version is your build host running?

> I get the same error whatever I try.  The above is from
> 'dpkg-buildpackage'.  I have tried creating a obj-i686-linux-gnu
> directory in the sword directory, but it gets removed immediately
> prior to the error message.
First, let me recommend steering clear of dpkg-buildpackage.  For my
workflow, I use exclusively pbuilder, in order to assure that the
package builds cleanly.  For example, packages and other things you have
installed on your system may inadvertently affect the build process and
you may not be aware of it.  The standard for building packages for
upload into Debian is that they build in a clean "sid" chroot.

There is plenty of documentation out there, and you can consult it if
you need additional detail, but it basically goes like this:

Create pbuilder chroot:
 - Create your configuration file (usually /etc/pbuilderrc)
 - Create the chroot: `pbuilder create --configfile /etc/pbuilderrc`

Build the package:
 - From within the unpacked package source: `pdebuild --configfile
   /etc/pbuilderrc --buildsourceroot fakeroot --pbuilderroot sudo
   --buildresult /var/lib/chroot/pbuilder-sid/results

Keep the chroot up to date periodically:
 - `pbuilder update --configfile /etc/pbuilderrc`

These are the commands that I use with the options that I like.  You can
basically tweak it to suit your specific needs.


Roberto C. Sánchez
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-crosswire-devel/attachments/20140329/83b51cc9/attachment.sig>

More information about the Pkg-crosswire-devel mailing list