Re: Rampart does not migrate - complaining about closed bugs
Dear Adam, dear Ansgar,
On 05/14/2012 12:58 AM, Adam D. Barratt wrote:
> On Mon, 2012-05-14 at 00:37 +0200, Ansgar Burchardt wrote:
>> Steffen Möller <email@example.com> writes:
>>> I was sponsoring
>>> which fixes a number of bugs but does not migrate to testing, even
>>> though those bugs are closed. Should we upload another version that
>>> closes those bugs in the changelog?
>> Testing migration is handled by the release team, but I believe you just
>> have to mark the bugs as fixed in the last version in the archive. As
>> there is another fixed version ("1.3.0-1+rm"), the BTS believes this
>> still affects the version currently in unstable.
> Yep, as there's no package in the archive of which 1.3.0-1+rm is an
> ancestor. The version graph on the bug report pages shows this - see
> the lack of any green and the lack of that version appearing.
>> There's no need to upload a new version just for this, `bts fixed'
>> should be enough.
> Indeed. As would having performed a versioned -done back in March -
> just using -done with no version information for a bug that you agree
> exists in some version of the package is wrong.
This was very helpful. Lights are green now. Have many thanks!