Hi, On Wed, 2008-12-31 at 12:23 +0100, Robert Luberda wrote: > Package: devscripts > Version: 2.10.43 > Severity: normal > User: [email protected]
"[email protected]". Thanks for the thought though. :-) > > dch --news > dch: fatal error at line 1006: > Error parsing version number: 1.11.0.dfsg-1~ > > I assume it's because the `~' characted I use for marking local, not yet > released versions of packages I'm working on. It would be great if dch > either remove the character or just allow it. The problem is that debchange is attempting to automatically determine what the new version number should be, based on the current version by splitting it in to two parts - one which should remain static and one which should be modified to create the new version - and it's unsure how to determine what the version following 1.11.0.dfsg-1~ should be. I've been having a quick look at a solution that would attempt to be "sensible" given such a version number. The mapping would be: dch -i -> 1.11.0.dfsg-1-2~ dch --nmu -> 1.11.0.dfsg-1.1 dch --security -> 1.11.0.dfsg-1.1 dch --binnmu -> 1.11.0.dfsg-1+b1 dch --qa -> 1.11.0.dfsg-1-2 dch --bpo -> 1.11.0.dfsg-1~bpo40+1 (helpfully highlighting a bug in --bpo support at the same time :-/) which at least at first glance seems reasonable imho. "dch --news" on its own maintains the version number; in combination with any other option it gives the results above. My main problem with allowing this for NEWS files specifically is that it runs the risk of the package versions in NEWS and changelog getting out of step when the package is released - the changelog will presumably then say 1.11.0.dfsg-1, but NEWS.Debian will still say 1.11.0.dfsg-1~. Thinking about it a little more, simply setting the version in NEWS to 1.11.0.dfsg-1 (i.e. dropping the tilde) would probably suffice in that case. Regards, Adam -- To unsubscribe, send mail to [email protected].
