Bug#867660: ball: FTBFS with sip 4.19.x: sip: File::CannotWrite has not been defined

2017-09-20 Thread Andreas Tille
On Wed, 20 Sep 2017, you wrote: > I suspect the tests are just flaky and fail randomly. > > Can you try running them not in parallel, i.e. with the attached patch? I tried: diff --git a/debian/rules b/debian/rules index 9d23042..350d537 100755 --- a/debian/rules +++ b/debian/rules @@ -49,7

Bug#867660: ball: FTBFS with sip 4.19.x: sip: File::CannotWrite has not been defined

2017-09-20 Thread Dmitry Shachnev
Hi Andreas! On Tue, Sep 19, 2017 at 09:49:26PM +0200, Andreas Tille wrote: > I would love to upload as commited in Git (including the dh_sip call) but > when trying to build in a clean chroot I get: > > The following tests FAILED: > 13 - Vector4_test (Failed) > 69 -

Bug#867660: ball: FTBFS with sip 4.19.x: sip: File::CannotWrite has not been defined

2017-09-19 Thread Andreas Tille
On Tue, Sep 19, 2017 at 08:53:28PM +0300, Dmitry Shachnev wrote: > Control: block 876205 by -1 > > On Tue, Sep 05, 2017 at 04:00:50PM +0300, Dmitry Shachnev wrote: > > I just tested on a clean sid amd64 chroot (with sip 4.19 from experimental) > > and all the tests pass for me: > > > > 100%

Bug#867660: ball: FTBFS with sip 4.19.x: sip: File::CannotWrite has not been defined

2017-09-19 Thread Dmitry Shachnev
Control: block 876205 by -1 On Tue, Sep 05, 2017 at 04:00:50PM +0300, Dmitry Shachnev wrote: > I just tested on a clean sid amd64 chroot (with sip 4.19 from experimental) > and all the tests pass for me: > > 100% tests passed, 0 tests failed out of 333 > > Maybe it was some temporary issue? I

Bug#867660: ball: FTBFS with sip 4.19.x: sip: File::CannotWrite has not been defined

2017-09-05 Thread Dmitry Shachnev
Hi again Andreas! On Thu, Aug 24, 2017 at 08:40:57PM +0300, Dmitry Shachnev wrote: > On Tue, Aug 22, 2017 at 03:53:05PM +0200, Andreas Tille wrote: > > Thanks for the hint. I can confirm that the executable builds with this > > patch. Unfortunately the package does not build due to test errors:

Bug#867660: ball: FTBFS with sip 4.19.x: sip: File::CannotWrite has not been defined

2017-08-24 Thread Dmitry Shachnev
Hi Andreas! On Tue, Aug 22, 2017 at 03:53:05PM +0200, Andreas Tille wrote: > Thanks for the hint. I can confirm that the executable builds with this > patch. Unfortunately the package does not build due to test errors: > > ... > 98% tests passed, 5 tests failed out of 333 Sorry, I was mostly

Bug#867660: ball: FTBFS with sip 4.19.x: sip: File::CannotWrite has not been defined

2017-08-22 Thread Andreas Tille
Hi Dmitry, On Tue, Aug 22, 2017 at 11:42:12AM +0300, Dmitry Shachnev wrote: > Control: tags -1 +patch > > On Sat, Jul 08, 2017 at 12:03:24PM +0300, Dmitry Shachnev wrote: > > ball fails to build with sip4 4.19 from experimental, which is blocking the > > update of sip4 in unstable: > > > > [...]

Bug#867660: ball: FTBFS with sip 4.19.x: sip: File::CannotWrite has not been defined

2017-08-22 Thread Dmitry Shachnev
Control: tags -1 +patch On Sat, Jul 08, 2017 at 12:03:24PM +0300, Dmitry Shachnev wrote: > ball fails to build with sip4 4.19 from experimental, which is blocking the > update of sip4 in unstable: > > [...] This diff from upstream fixes the build for me:

Bug#867660: ball: FTBFS with sip 4.19.x: sip: File::CannotWrite has not been defined

2017-07-08 Thread Dmitry Shachnev
Source: ball Version: 1.4.3~beta1-3 Severity: important Forwarded: https://github.com/BALL-Project/ball/issues/606 Dear maintainer, ball fails to build with sip4 4.19 from experimental, which is blocking the update of sip4 in unstable: [ 81%] Generating VIEWmodule/sipVIEWpart0.cpp,