Bartosz Fenski aka fEnIo <[EMAIL PROTECTED]> writes: > Hello. > > I've got question related to closing bugs. > > Let's say I adopted some package, and with the new upstream version > I should close some outstanding bugs. And I did it in 1.1-1 version. > Then I ask previous maintainer to upload it, and he pointed me out some > other needed changes. So I made another release 1.1-2 with those fixes. > > Then previous maintainer uploaded it, but he built package without > `-v1.0` switch so only latest changelog was included. > > This led to non-closed bugs which are fixed in fact. > What now? Should I close those bugs manually, or is it correct way to > upload another version (1.1-3) including changelogs from 1.1-1 to 1.1-3? > > I mean is it good way? Then changelog from version 1.1-2 will be parsed > two times.
Either method is fine. If you're planning to make another upload soon anyway, I'd just wait and build with the -v switch. Otherwise, just close them by hand, preferably inserting the text of the relevant changelog entry in the closing message. -- You win again, gravity! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
