Marc 'HE' Brockschmidt wrote: > Lior Kaplan <[EMAIL PROTECTED]> writes: >> The library was renamed again from Sarge to Etch, the the >> provides/conflicts are fine in the control file. > > So that version fixes the bug, right? And what do you do when a new > version fixes a bug?
Nope, the bug still exists on Sarge. But I've checked provides/conflicts to make sure it won't happen on the Sarge->Etch upgrade due to the *second* rename. That's why it's "etch-ignore" and not "fixed". I've marked it as not found in 2.0.0-8 (the etch/sid version). But I still need release team approval for etch-ignore tag. -- Lior Kaplan [EMAIL PROTECTED] GPG fingerprint: C644 D0B3 92F4 8FE4 4662 B541 1558 9445 99E8 1DA0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]