Adding pyliblzma.egg-info/PKG-INFO to debian/clean appears to resolve the
issue. It is
regenerated each build. I am not sure if actually removing it on clean is the
correct
thing to do though.
Regards,
Jordan Metzmeier
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
wi
Source: python-lzma
Version: 0.5.3-2
Severity: important
User: debian...@lists.debian.org
Usertags: qa-doublebuild
python-lzma FTBFS if built twice in a row:
| dpkg-source -b python-lzma-0.5.3
| dpkg-source: info: using source format `3.0 (quilt)'
| dpkg-source: info: building python-lzma using
2 matches
Mail list logo