Package: beepcore-c Version: 0.2+cvs20030603-1 "debuild; debuild clean" leaves cruft lying around that dpkg-source can't handle for the next build:
dpkg-source: building beepcore-c in beepcore-c_0.2+cvs20030603-1.diff.gz dpkg-source: cannot represent change to unix/.libs/libbeepcore-c.so.0.1.0: binary file contents changed dpkg-source: cannot represent change to unix/.libs/libbeepcore-c.so.0: dpkg-source: new version is symlink dpkg-source: old version is nonexistent dpkg-source: cannot represent change to unix/.libs/libbeepcore-c.so: dpkg-source: new version is symlink dpkg-source: old version is nonexistent dpkg-source: cannot represent change to unix/.libs/libbeepcore-c.a: binary file contents changed dpkg-source: cannot represent change to unix/.libs/libbeepcore-c.la: dpkg-source: new version is symlink dpkg-source: old version is nonexistent dpkg-source: cannot represent change to config.sub: dpkg-source: new version is symlink dpkg-source: old version is something else dpkg-source: cannot represent change to config.guess: dpkg-source: new version is symlink dpkg-source: old version is something else dpkg-source: building beepcore-c in beepcore-c_0.2+cvs20030603-1.dsc dpkg-source: unrepresentable changes to source I don't know if this counts as a serious bug [FTBFS], since it builds immediately after extracting the source tarball, and I don't know if repeated in-place builds are required by policy. -- Sam "Eddie" Couter | mailto:[EMAIL PROTECTED] Debian Developer | mailto:[EMAIL PROTECTED] | jabber:[EMAIL PROTECTED] OpenPGP fingerprint: A46B 9BB5 3148 7BEA 1F05 5BD5 8530 03AE DE89 C75C
signature.asc
Description: Digital signature
