[Python-modules-team] Bug#671321: pyfribidi: FTBFS if built twice in a row: unrepresentable changes to source

Jakub Wilk jwilk at debian.org
Thu May 3 15:57:56 UTC 2012


* أحÙ
د الÙ
Ø­Ù
ودي <aelmahmoudy at sabily.org>, 2012-05-03, 17:48:
>> |  dpkg-source -b pyfribidi-0.11.0
>> | dpkg-source: info: using source format `3.0 (quilt)'
>> | dpkg-source: info: building pyfribidi using existing ./pyfribidi_0.11.0.orig.tar.bz2
>> | dpkg-source: error: cannot represent change to pyfribidi-0.11.0/_pyfribidi_d.so:
>> | dpkg-source: error:   new version is symlink to /build/pyfribidi-NGtp9f/pyfribidi-0.11.0/build/lib.linux-i686-2.7-pydebug/_pyfribidi_d.so
>> | dpkg-source: error:   old version is nonexistent
>> | dpkg-source: error: cannot represent change to pyfribidi-0.11.0/_pyfribidi.so:
>> | dpkg-source: error:   new version is symlink to /build/pyfribidi-NGtp9f/pyfribidi-0.11.0/build/lib.linux-i686-2.7/_pyfribidi.so
>> | dpkg-source: error:   old version is nonexistent
>> | dpkg-source: error: unrepresentable changes to source
>> | dpkg-buildpackage: error: dpkg-source -b pyfribidi-0.11.0 gave error exit status 2
>---end quoted text---
>
>  Shouldn't a debian/rules clean be run first before dpkg-source ?

dpkg-buildpackage did run "debian/rules clean" before invoking 
dpkg-source, but this didn't remove the symlinks.

-- 
Jakub Wilk





More information about the Python-modules-team mailing list