On Tue, 2013-03-19 at 15:47 -0400, Benjamin Kaduk wrote: > reopen 702633
Why? Do you believe that the 1.10.1+dfsg-4+nmu1 package does not contain a fix for this bug? If the answer to my first question is "because it's not fixed in stable yet", then the re-opening was incorrect, as the actual effect was to mark it as not fixed in _unstable_. Regards, Adam -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
