No trouble at all. I'll upload the NMU shortly. Scott K
On Monday, January 11, 2016 09:57:05 AM Manu Garg wrote: > Hi Scott, > > Sorry for the delay in reply to your previous bug update. This patch looks > good to me. Please go ahead with the NMU, if it's not too much of work for > you. I don't have upload rights, so it will take me a bit to co-ordinate > the upload. > > Cheers, > Manu > > On Mon, Jan 11, 2016 at 8:57 AM, Scott Kitterman <sc...@kitterman.com> > > wrote: > > On Wed, 30 Dec 2015 16:39:51 -0500 Scott Kitterman <deb...@kitterman.com> > > > > wrote: > > > Source: pacparser > > > Version: 1.3.6-1 > > > Severity: important > > > Tags: patch > > > > > > Currently pacparser only builds support for the default python3 > > > > version. As > > a > > > > > result, once the default version switches from python3 3.4 to 3.5, > > > > python3- > > > > > pacparser will be unusable until it can be rebuilt. The best practice > > > > (as > > > > > described in the Debian Python policy) is to build for all supported > > > > versions. > > > > > Then whichever is default, the package still works. > > > > > > Additionally, while I was looking at the package, I noticed that the > > > > python > > > > > build directory isn't removed in clean and that the python and python3 > > > package descriptions were identical. I took care of those while I was > > > at > > > > it. > > > > > Please see the attached patch (formatted as an NMU because that's what > > > devscripts handed me, but I have no near term plans to NMU). > > > > Now that 3.5 is default (was just uploaded) this is unusable. Adjusting > > severity accordingly. I do intend to NMU now. Please let me know of > > you'd > > prefer to take care of it. > > > > Scott K
