Hi! On Sun, 2013-08-11 at 10:51:26 +0300, Jari Aalto wrote: > Package: dpkg-dev > Version: 1.17.1 > Severity: normal > > During build package with following version number results failed > build: > > $ git-buildpackage > ... > > dpkg-source -i -b splitpatch-0.0+20130626+gitbd6a83d > dpkg-source: error: can't build with source format '3.0 (quilt)': version > does not contain a revision > dpkg-buildpackage: error: dpkg-source -i -b > splitpatch-0.0+20130626+gitbd6a83d gave error exit status 255 > debuild: fatal error at line 1357: > dpkg-buildpackage -rfakeroot -D -us -uc -i failed > > If the version number is changed from initial "0.0" to "0.1" the build > succeeds.
That should not happen, when you say succeeds, do you mean that it fails instead because it cannot find the orig source tarball? Because if you provide it then it should fail again on the missing revision. Otherwise could you provide a reproducible test case? > Please consider allowing initial "0.0" for software that is packaged > directly from version control and which do not have any release > numbering (possibly not yet). If later upstream adds a version number, > it's easy to package when he original code has been prefixed with > "0.0". If the software is using “3.0 (quilt)” then it needs a revision otherwise make it “3.0 (native)”. Thanks, Guillem -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
