Bug#868977: Confirm that I'm able to verify the problem

2017-07-28 Thread Yaroslav Halchenko
On Thu, 27 Jul 2017, Andreas Tille wrote: > > would need to dig in, may be later, meanwhile pushed my slight tune ups, > > feel > > welcome to fix up. You do know where to get the .orig.tar.gz ;) > Sure I know and I used it for building. What about simplifying things > for your team mates and

Bug#868977: Confirm that I'm able to verify the problem

2017-07-27 Thread Andreas Tille
Hi Yaroslav, On Thu, Jul 27, 2017 at 10:21:35AM -0400, Yaroslav Halchenko wrote: > > would need to dig in, may be later, meanwhile pushed my slight tune ups, feel > welcome to fix up. You do know where to get the .orig.tar.gz ;) Sure I know and I used it for building. What about simplifying th

Bug#868977: Confirm that I'm able to verify the problem

2017-07-27 Thread Andreas Tille
Hi Yaroslav, On Thu, Jul 27, 2017 at 09:44:10AM -0400, Yaroslav Halchenko wrote: > Is there any demand/requirement for debhelper 10 for this package? > Could we settle on 9 (to ease backportability to old jessie and alike)? Just to answer this question: 1. There is no demand - I just choose th

Bug#868977: Confirm that I'm able to verify the problem

2017-07-27 Thread Yaroslav Halchenko
On Thu, 27 Jul 2017, Andreas Tille wrote: > Hi, > I was hoping that taking over the version from experimental to unstable > might help to fix this bug but I can only confirm that I can reproduce eh -- plain rebuild doesn't suffice -- tests still fail and some new failures happen:

Bug#868977: Confirm that I'm able to verify the problem

2017-07-27 Thread Yaroslav Halchenko
On Thu, 27 Jul 2017, Yaroslav Halchenko wrote: > Is there any demand/requirement for debhelper 10 for this package? > Could we settle on 9 (to ease backportability to old jessie and alike)? I would guess that the answers are no and yes, fixed up, building now, will upload whenever done Cheers a

Bug#868977: Confirm that I'm able to verify the problem

2017-07-27 Thread Yaroslav Halchenko
On July 27, 2017 9:23:16 AM EDT, Andreas Tille wrote: >Hi, > >I was hoping that taking over the version from experimental to unstable >might help to fix this bug but I can only confirm that I can reproduce >the problem here. So it also happens for version 0.8.0. I've commited >my attempt to Git

Bug#868977: Confirm that I'm able to verify the problem

2017-07-27 Thread Yaroslav Halchenko
On Thu, 27 Jul 2017, Andreas Tille wrote: > Hi, > I was hoping that taking over the version from experimental to unstable > might help to fix this bug but I can only confirm that I can reproduce > the problem here. So it also happens for version 0.8.0. I've commited > my attempt to Git and hop

Bug#868977: Confirm that I'm able to verify the problem

2017-07-27 Thread Andreas Tille
Hi, I was hoping that taking over the version from experimental to unstable might help to fix this bug but I can only confirm that I can reproduce the problem here. So it also happens for version 0.8.0. I've commited my attempt to Git and hope that somebody else might have a better clue. BTW, I