On 7 March 2005 at 16:59, Pascal A. Dupuis wrote: | Working on Sarge (octave_2.1.64-1, emacs_21.3+1-8), the bug is still | present. Maybe we could we until 2.1.65 is in Sarge ?
IMHO that is a bad idea. A bug gets reported when it is discovered. Once a new package gets uploaded, the bug should be closed ... as the passage from unstable to testing is independent of the bug (well, unless it is a RC bug), there is no gain in tieing the two. Moreover, if passage to testing is delayed, it is often simply to breakage of the toolchain on some unrelated architecture. You know you can always fetch the package manually, or even semi-automatically with apt pinning. "Not in sarge" is a fallacy, in my book. Dirk -- Better to have an approximate answer to the right question than a precise answer to the wrong question. -- John Tukey as quoted by John Chambers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
