Hi Peter, On Thu, Apr 16, 2009 at 10:44:14PM +0300, Peter Eisentraut wrote: > Package: devscripts > Version: 2.10.48 > Severity: normal > > I used to use dch -r habitually before releasing a package because it sets > the > release in the changelog and updates the timestamp. In the new devscripts > version, if you don't do any other editing, it will then say, "changelog not > modified" and not apply the changes. I think this was broken as the fix to > #422450. I think I want the old behavior back. What is the purpose of dch > -r > otherwise?
thanks for your report. Some of us devscripts maintainers discussed these topic on work today. The change was made because it was been requested and is consistent with the rest of dch (usually if you request an action from dch it spawns an editor and if you save it (!), the changes (including the s/UNRELEASED/unstable/) will be saved to the changelog). bzed requested to make the behaviour configurable, which is probably the best way to make debchange fit all usage scenarios. Regards, Patrick
signature.asc
Description: Digital signature
