Bug#570328: FTBFS: rm: cannot remove […]/pyshared/quodlibet/qltk/config.py: ENOENT

2010-02-17 Thread Cyril Brulebois
Source: quodlibet
Version: 2.2-1
Severity: serious
Justification: FTBFS

Hi,

your package looks like trying to mess with python-support's internal
affairs, and fails to do so:
|debian/rules override_dh_pysupport
| make[1]: Entering directory 
`/build/buildd-quodlibet_2.2-1-alpha-2sKZ6e/quodlibet-2.2'
| dh_pysupport
| # kill all the architecture-dependent files in the exfalso package,
| # what's left after pysupport has moved arch-indep files elsewhere
| rm -rf debian/exfalso/usr/lib
| # Kill this modification after the next release. It's just a stray file
| # that got into upstream's release tarball.
| rm debian/exfalso/usr/share/pyshared/quodlibet/qltk/config.py
| rm: cannot remove 
`debian/exfalso/usr/share/pyshared/quodlibet/qltk/config.py': No such file or 
directory
| make[1]: *** [override_dh_pysupport] Error 1
| make[1]: Leaving directory 
`/build/buildd-quodlibet_2.2-1-alpha-2sKZ6e/quodlibet-2.2'
| make: *** [binary-arch] Error 2

Full build logs:
  https://buildd.debian.org/status/package.php?suite=unstablep=quodlibet

Mraw,
KiBi.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#570328: FTBFS: rm: cannot remove […]/pyshared/quodlibet/qltk/config.py: ENOENT

2010-02-17 Thread A. Christine Spang
On Thu, Feb 18, 2010 at 04:51:49AM +0100, Cyril Brulebois wrote:
 Source: quodlibet
 Version: 2.2-1
 Severity: serious
 Justification: FTBFS
 
 Hi,
 
 your package looks like trying to mess with python-support's internal
 affairs, and fails to do so:
 |debian/rules override_dh_pysupport
 | make[1]: Entering directory 
 `/build/buildd-quodlibet_2.2-1-alpha-2sKZ6e/quodlibet-2.2'
 | dh_pysupport
 | # kill all the architecture-dependent files in the exfalso package,
 | # what's left after pysupport has moved arch-indep files elsewhere
 | rm -rf debian/exfalso/usr/lib
 | # Kill this modification after the next release. It's just a stray file
 | # that got into upstream's release tarball.
 | rm debian/exfalso/usr/share/pyshared/quodlibet/qltk/config.py
 | rm: cannot remove 
 `debian/exfalso/usr/share/pyshared/quodlibet/qltk/config.py': No such file or 
 directory
 | make[1]: *** [override_dh_pysupport] Error 1
 | make[1]: Leaving directory 
 `/build/buildd-quodlibet_2.2-1-alpha-2sKZ6e/quodlibet-2.2'
 | make: *** [binary-arch] Error 2

Hi,

I just re-uploaded this package, stripping the stray file
from upstream's tarball beforehand instead of trying to
clean it up later. (Leaving it in would probably cause
byte-compilation explosions on installation.) I find it sort
of bizarre that the build did not fail on my local machine
while it did on the buildds, however. Do you have any idea
why that was the case?

regards,
Christine



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#570328: FTBFS: rm: cannot remove […]/pyshared/quodlibet/qltk/config.py: ENOENT

2010-02-17 Thread Cyril Brulebois
Heya,

A. Christine Spang sp...@mit.edu (17/02/2010):
 I just re-uploaded this package, stripping the stray file from
 upstream's tarball beforehand instead of trying to clean it up
 later. (Leaving it in would probably cause byte-compilation
 explosions on installation.)

probably a good idea indeed.

 I find it sort of bizarre that the build did not fail on my local
 machine while it did on the buildds, however. Do you have any idea
 why that was the case?

OK. 2 guesses:

1) It looks like python-defaults and python-support at least are at
the same version in unstable and testing, so probably not a timing
issue (with a new version getting uploaded behind your back). Maybe
your build environment was lagging behind a bit? Given the python2.6
thingies going on, it *could* have been related, but it's probably
not, read on.

2) One big difference between local and buildd builds is the use of -B
(as option to dpkg-buildpackage) on the buildds. And if you try to
locally build your package with -b, it builds successfully; if you try
to locally build your package with -B, it will fail as it did on the
buildds.

Mraw,
KiBi.


signature.asc
Description: Digital signature