On Thursday, November 08, 2012 10:38:04 PM gregor herrmann wrote: > Control: found -1 1.2.3-348-g317f5a0-1 > Control: found -1 1.2.3-349-g315b5f5-2 > > On Thu, 08 Nov 2012 13:15:33 -0500, Chris Knadle wrote: > > On Thursday, November 08, 2012 01:57:23, Ron wrote: > > > But this seems to be new(ly reported) for the upload you prepared, and > > > it's still not clear yet why it is new and who it effects. So yes, > > > you will need to investigate that further. It's most certainly not > > > "expected behaviour" for a Debian package. > > > > This issue is /not/ related to my "349"-2.1 NMU upload. The "348"-1 > > package that's in Wheezy right now and the "349"-2 package both exhibit > > exactly this same behavior. > > Thanks for checking; I planned to do this but you were quicker :)
;-) Thanks for being ready to do the same. I've also checked the package I previously built using upstream version 412-g6c9694d and it shows the same error output on startup. Upstream has three other new tarballs that were just recently released I could build another mumble package from to see if this has been fixed upstream; the newest being 525-gcb22b39. > Since this happens also with the earlier versions, I'm setting the > affected versions for the BTS accordingly. > > My impression at the moment is: > - There's a bug but mumble still works, as confirmed by the submitter > of the LP bug and by Chris now. So the priority is probably fine. > - The bug is not new but, as Ron implied, newly reported. > > Is this correct? Yes AFAIK that's right. -- -- Chris Chris Knadle chris.kna...@coredump.us -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
