I'm having problems deciding how to fix a bug filed against a package I maintain: here is the report:
Package: dnsmasq Version: 1.4-2 Severity: normal cvs-inject say this is a violation of policy, and it certainly is odd to have a debian-revision but no diff. I'm not sure what the best solution is. -David $ cvs-inject dnsmasq_1.5-1.dsc -W/home/dwhedon/temp/ . . . snip snip . . . Warning!!!!!! No /home/dwhedon/temp//temp-cvs-inject/dnsmasq-1.5 Though the version number indicates this is not a Debian Native Package, it seems to be one. This is a policy violation. This should be corrected. Do you wish to continue?[y/N]y OK. Continuing anyway. cd dnsmasq-1.5.orig /usr/bin/cvs-inject: cd: dnsmasq-1.5.orig: No such file or directory $ -------- end bug report ------------------. Since I am the upstream maintainer of dnsmasq it suits me to develop it like a native package, I have one source tree which includes the debian subdirectory (and control files for RedHat, Suse...). The total code is only around 30k, so there's no problem doing a complete source upload even for packaging changes. OTOH I want to keep a version number which includes a Debian revision, since I want to be able to make changes which only affect the Debian package without making a general release on Freshmeat etc. It appears from the bug report that I can't do that. Can anybody point to where in policy it's forbidden, and suggest how I can fix the problem? Do I really have to start including the source as a tarball inside the package? Help, please? Simon. -- ------------------------------------------------------------------------- Simon Kelley. GPG public key at http://www.thekelleys.org.uk/srkgpg.txt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
