Custom Query (894 matches)

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.

There is a backport of python-ssl under source:/trunk/bcfg2/misc/python-ssl-1.15/debian - it would be good to get this vetted and then in upstream official backports repositories (lenny-backports, hardy-backports, intrepid-backports).

Test r5624 - not 100% sure that's valid debian control syntax (same thing in 2 sections).