Debian packages require really new (7.3.x) debhelper

[dclark]

This is bad as it would make packaging o nanything earlier than jaunty really hard.

It seems like before 7.3.x, stuff goes to debian/tmp/usr/local, but in 7.3.x, stuff goes to debian/tmp/usr (as the package expects)

See this mailing list thread for more details:

• http://thread.gmane.org/gmane.comp.sysutils.bcfg2.devel/3560/focus=3650

> Hmm.. I've opted for an older debhelper, 7.0.52 should be easier to
> backport. It already has the features we need for the package and
> doesn't need a backported perl-base to work on hardy.

So something one of us has done seems to now make something around
debhelper 7.3.15ubuntu3 required - even  7.2.6~bpo50+1 does not work.

The complete build log for jaunty with 7.0.52 is at:
http://tinyurl.com/yh7aev4

The relevant error looks like it is:

Writing /build/buildd/bcfg2-1.0.0/debian/tmp/usr/local/lib/python2.6/dist-packages/Bcfg2-1.0.0.egg-info
   dh_install
cp: cannot stat `./debian/tmp/usr/bin/bcfg2': No such file or directory
dh_install: command returned error code 256
make: *** [binary] Error 1
dpkg-buildpackage: failure: /usr/bin/fakeroot debian/rules binary gave
error exit status 2
******************************************************************************
Build finished at 20091106-0138
FAILED [dpkg-buildpackage died]

Maybe can just override dh_auto_install in debian/rules and be sure DESTDIR is set to same thing or something along those lines.

[dclark]

debhelper 7.2.6~bpo50+1 does:

dh_auto_install
        python setup.py install --root=/bcfg2-trunk/debian/tmp --no-compile -O0

debhelper 7.3.15ubuntu3 does:

dh_auto_install
        python setup.py install --root=/bcfg2-trunk/debian/tmp --no-compile -O0 --install-layout=deb

The --install-layout=deb is what's different. Need to see if we can add this somehow in older debhelper in an override_dh_auto_install: section of rules...

[dclark]

r5564 at least lets jaunty build, but there is some other issue now with hardy and intrepid. Will look at intrepid first:

Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  python-dev: Depends: python (= 2.6.2-0ubuntu1~testing1~intrepid1) but it is not going to be installed
              Depends: python2.6-dev (>= 2.6.2) but it is not installable
  python-support: Depends: python (>= 2.4) but it is not going to be installed
E: Broken packages
apt-get failed.
Package installation failed
Trying to reinstall removed packages:
Trying to uninstall newly installed packages:
Source-dependencies not satisfied; skipping bcfg2

[dclark]

The 2.6.2 problem was due to PEBKAC - nothing to do with the bcfg2 package, there was another package in the repo that was causing the issue that has now been removed. This problem is now fixed - Bcfg2 verified to build in lenny, hardy, intrepid, jaunty, karmic, lucid.