> Unfortunately for Debian/Ubuntu, it is not that easy. There is a bug in CDBS, > which is not setting pkglibexecdir correctly. That makes the updated upstream > FTBFS differently. > > I have all the fixes there > http://git.remlab.net/gitweb/?p=miredo-debian.git;a=summary > But the release is being held by CDBS bug #661983.
ping? #661983 now claims to be fixed. However, the bug in miredo is not: src/Makefile.am:35: `pkglibdir' is not a legitimate directory for `PROGRAMS' src/Makefile.am:59: variable `miredo_privproc_SOURCES' is defined but no program or (in a clean pbuilder chroot and on my typical unstable box) ii automake 1:1.11.3-1 ii cdbs 0.4.109 I've tried with your changes applied to the upstream miredo-1.2.5.tar.xz: SHA256: 9d6c6aacfbde0e152481273cda4dc9a62f8724c4c941fa8e0806e89ab9992262 and your debian directory from http://git.remlab.net/gitweb/?p=miredo-debian.git;a=summary copied in. The upstream code builds but then I get a packaging error: cp: cannot stat `debian/tmp/usr/lib/miredo/miredo-privproc': No such file or directory dh_install: cp -a debian/tmp/usr/lib/miredo/miredo-privproc debian/miredo//usr/lib/miredo/ returned exit code 1 (Note, I'm not interested in miredo per se, just scanning through the RC bugs.) Any news on a fixed upload of miredo? -- Neil Williams ============= http://www.linux.codehelp.co.uk/
pgpKU9oXyygVU.pgp
Description: PGP signature
