Bug#901377: ping (was: Re: skimage: FTBFS and Debci failure with NumPy 1.14)

2018-06-23 Thread Graham Inggs
Hi Stefan, Yaroslav On 22 June 2018 at 21:15, Stefan van der Walt wrote: > That sounds like a good solution to me. That said, scikit-image in > Debian is now maintained by the science team, so it would be good to > hear from a member of that team. Lumin is a member of Debian Science Team. :)

Bug#853682: [Debichem-devel] Bug#853682: tiledarray: diff for NMU version 0.6.0-5.2

2018-06-24 Thread Graham Inggs
Hi Adrian On 24 June 2018 at 17:44, Adrian Bunk wrote: > I've prepared an NMU for tiledarray (versioned as 0.6.0-5.2) and > uploaded it to DELAYED/10. Please feel free to tell me if I should > cancel it. Thanks for your work on this. Please upload directly to avoid the delay if you wish. Regar

Bug#900485: python-pbcore: FTBFS and Debci failure with NumPy 1.14

2018-06-24 Thread Graham Inggs
Control: tags -1 + patch Hi Sandro I have cherry-picked the attached patch from pbcore upstream which fixes the problems with NumPy 1.14. However, with this patch in place, pbcore will need a build-dependency on python-numpy (>= 1:1.14~) and its autopkgtests will fail with NumPy 1.13. I thought

Bug#901377: ping (was: Re: skimage: FTBFS and Debci failure with NumPy 1.14)

2018-06-25 Thread Graham Inggs
On 25 June 2018 at 18:21, Yaroslav Halchenko wrote: > I am loosely involved and highly interested ;-) If someone could help > maintaining it, I would appreciate. > > meanwhile since there were no other activity regarding this issue, I > will look into updating it for 0.14.0 In case you didn't re

Bug#900486: python-pydap: FTBFS and Debci failure with NumPy 1.14

2018-06-28 Thread Graham Inggs
tps://bugs.debian.org/900486 Author: Graham Inggs Last-Update: 2018-06-20 --- a/src/pydap/tests/test_responses_ascii.py +++ b/src/pydap/tests/test_responses_ascii.py @@ -48,7 +48,7 @@ ('XDODS-Server', 'pydap/' + __version__), ('Conte

Bug#902945: igraph: FTBFS with ARPACK 3.6

2018-07-03 Thread Graham Inggs
Source: igraph Version: 0.7.1-2.1 Severity: serious Tags: ftbfs Hi maintainer Since the upload of arpack 3.6.0-1 to unstable, igraph FTBFS [1] with the following test failures: BLAS, LAPACK and ARPACK based functions 191: Basic BLAS functions (igraph_blas_*): ok 192: Dense symmetric e

Bug#903129: unicode-data: unicode-data 11 causes FTBFS in unstable

2018-07-06 Thread Graham Inggs
Source: unicode-data Version: 11.0.0-1 Severity: serious Tags: ftbfs Control: affects -1 gucharmap libxmlada utf8proc wine wine-development Hi Maintainer The recent upload of unicode-data 11 causes several packages to FTBFS in unstable. This bug is to prevent the migration of unicode-data to

Bug#873408: [Pkg-julia-devel] Bug#873408: julia: Please update to llvm-toolchain 4.0 or, better, 5.0

2018-07-09 Thread Graham Inggs
Hi Emilio On 09/07/2018 10:37, Emilio Pozuelo Monfort wrote: #832798 is fixed now. Is that enough to get julia updated? Yes! \o/ Note that we now have llvm 5.0 and 6.0. Updating to a newer version would be best as we will eventually look at removing 4.0. But for now 4.0 would obviously be be

Bug#903381: utf8proc: FTBFS with unicode-data 11

2018-07-09 Thread Graham Inggs
Source: utf8proc Version: 2.1.0-1 Severity: serious Tags: ftbfs sid Control: block 903129 by -1 Hi Maintainer The recent upload of unicode-data 11 causes your package to FTBFS in unstable. Please update your package to be compatible with the latest version of unicode-data. Regards Graham

Bug#903382: wine: FTBFS with unicode-data 11

2018-07-09 Thread Graham Inggs
Source: wine Version: 3.0.2-1 Severity: serious Tags: ftbfs sid Control: block 903129 by -1 Hi Maintainer The recent upload of unicode-data 11 causes your package to FTBFS in unstable. Please update your package to be compatible with the latest version of unicode-data. Regards Graham

Bug#903380: libxmlada: FTBFS with unicode-data 11

2018-07-09 Thread Graham Inggs
Source: libxmlada Version: 17.1.2017-6 Severity: serious Tags: ftbfs sid Control: block 903129 by -1 Hi Maintainer The recent upload of unicode-data 11 causes your package to FTBFS in unstable. Please update your package to be compatible with the latest version of unicode-data. Regards Gr

Bug#903379: gucharmap: FTBFS with unicode-data 11

2018-07-09 Thread Graham Inggs
Source: gucharmap Version: 1:10.0.4-1 Severity: serious Tags: ftbfs sid Control: block 903129 by -1 Hi Maintainer The recent upload of unicode-data 11 causes your package to FTBFS in unstable. Please update your package to be compatible with the latest version of unicode-data. Regards Gra

Bug#903378: fonttools: FTBFS with unicode-data 11

2018-07-09 Thread Graham Inggs
Source: fonttools Version: 3.21.2-1 Severity: serious Tags: ftbfs sid Control: block 903129 by -1 Hi Maintainer The recent upload of unicode-data 11 causes your package to FTBFS in unstable. Please update your package to be compatible with the latest version of unicode-data. Regards Graha

Bug#903383: wine-development: FTBFS with unicode-data 11

2018-07-09 Thread Graham Inggs
Source: wine-development Version: 3.11-1 Severity: serious Tags: ftbfs sid Control: block 903129 by -1 Hi Maintainer The recent upload of unicode-data 11 causes your package to FTBFS in unstable. Please update your package to be compatible with the latest version of unicode-data. Regards

Bug#903129: unicode-data: unicode-data 11 causes FTBFS in unstable

2018-07-09 Thread Graham Inggs
Control: affects -1 = Dropping the affects in favour of RC bugs against the packages requiring an update.

Bug#906349: doublecmd: FTBFS in buster/sid (tries to write in /usr)

2018-09-21 Thread Graham Inggs
Hi Abou On 27/08/2018 18:03, Abou Al Montacir wrote: Maybe we shall think more about this change. Removing the manually flag leads to a deeper question: Do we need to distribute LCL units in binary form if they will get recompiled anyway? Have you had any time to consider this? Both doublecmd

Bug#906349: doublecmd: FTBFS in buster/sid (tries to write in /usr)

2018-09-24 Thread Graham Inggs
Hi Abou On 23 September 2018 at 22:44, Abou Al Montacir wrote: > I've reverted this in b9ccece9. However this means that Bug#898310 needs to > be reopen. Thanks, I have a reassigned #906349 so it can be closed when lazarus is uploaded. Shall I go ahead with an upload, or do you wish to make more

Bug#877670: [Debian-med-packaging] Bug#877670: Bug#877670: bcftools FTBFS on armel armhf and ppc64el

2017-11-07 Thread Graham Inggs
://bugs.debian.org/877670 Forwarded: https://github.com/samtools/htslib/pull/617 Author: Graham Inggs Last-Update: 2017-11-08 --- a/errmod.c +++ b/errmod.c @@ -82,10 +82,11 @@ double le1 = log(1.0 - e); for (n = 1; n <= 255; ++n) { double *beta = em->beta + (q<

Bug#881149: htslib FTBFS: test failures on i386

2017-11-08 Thread Graham Inggs
Package: htslib Version: 1.5-1 Severity: serious Tags: buster sid As per logs from reproducible builds [1], htslib 1.5-1 recently (around 2017-09-25) started to FTBFS on i386 with the following test failures: test_vcf_api: /build/1st/htslib-1.5/test/test-vcf-api /tmp/o6gEIzeYrS/test-vcf-api.bcf b

Bug#881149: htslib FTBFS: test failures on i386

2017-11-08 Thread Graham Inggs
Better link: https://tests.reproducible-builds.org/debian/history/i386/htslib.html

Bug#881149: htslib FTBFS: test failures on i386

2017-11-08 Thread Graham Inggs
On 8 November 2017 at 17:10, Adrian Bunk wrote: > The relevant change is gcc 6 -> 7. Thanks. I've just checked, and the last successful i386 build in Ubuntu was on 2017-08-04 against gcc 6. > With multiarch allowing installation of amd64 packages even on an i386 > installation, I'm wondering wh

Bug#881149: htslib FTBFS: test failures on i386

2017-11-08 Thread Graham Inggs
On 8 November 2017 at 19:57, Adrian Bunk wrote: > All combinations are possible, for example: ... > bash: /usr/bin/hello: cannot execute binary file: Exec format error OK, but you can't actually execute amd64 binaries on i386, right? So I don't understand how being able to install amd64 packages

Bug#881149: htslib FTBFS: test failures on i386

2017-11-08 Thread Graham Inggs
On 8 November 2017 at 20:21, Adrian Bunk wrote: > Assuming your CPU and kernel support 64bit, this is working. TIL, thanks!

Bug#881149: htslib FTBFS: test failures on i386

2017-11-08 Thread Graham Inggs
So it turns out this is a re-hash of #865012. See upstream issue reported by Sascha: https://github.com/samtools/htslib/issues/565 Also proposed patch (which was not accepted by upstream): https://github.com/samtools/htslib/pull/571 FWIW, the proposed patch "works for me" on amd64 and i386.

Bug#881149: htslib FTBFS: test failures on i386

2017-11-18 Thread Graham Inggs
Another FWIW, building on i386 with -O1 instead of -O2 and dropping -fno-strict-aliasing is successful. Where can one find the differences between -O1 and -O2 in GCC 7? What changed between GCC 6 and 7 would be useful too. --- a/debian/rules +++ b/debian/rules @@ -7,7 +7,10 @@ include /usr/sha

Bug#881149: htslib FTBFS: test failures on i386

2017-11-20 Thread Graham Inggs
Control: tags -1 + patch I found the documentation of the optimization flags for GCC 7.2.0 [1]. I was then able to bisect the list of flags enabled for -O2 and determine which ones needed to be disabled in order to build htslib on i386. Patch follows. --- a/debian/rules +++ b/debian/rules @@ -7,

Bug#873408: [Pkg-julia-devel] Bug#873408: julia: Please update to llvm-toolchain 4.0 or, better, 5.0

2017-11-24 Thread Graham Inggs
On 20 November 2017 at 20:54, Emilio Pozuelo Monfort wrote: > It should be fine now with 4.0. Would be good if this could move to either > unversioned llvm/clang (which defaults to 4.0 now) or to versioned 4.0. > Bumping > to serious as we want to remove 3.8 soon to reduce the high number of llvm

Bug#811634: meshlab: FTBFS with GCC 6: cannot convert x to y

2016-11-17 Thread Graham Inggs
In addition to Gert Wollny's patch, the attached patch fixes narrowing conversions with GCC 6 on architectures where char is unsigned by default. Copying to debian-science-maintainers list in case someone is interested in rescuing this package. narrowing-conversion.patch Description: application

Bug#835416: imagevis3d: FTBFS: singleton.hpp:131: undefined reference to `boost::serialization::singleton_module::is_locked()'

2016-11-17 Thread Graham Inggs
Control: tags -1 patch Hi Maintainer The attached patch links libboost_serialization, as suggested by Tom Fogal, and fixes the FTBFS with Boost 1.61. I also found the build dependency on libboost-all-dev can be replaced by libboost-serialization-dev, as follows: --- a/debian/control +++ b/debia

Bug#811634: meshlab: FTBFS with GCC 6: cannot convert x to y

2016-11-18 Thread Graham Inggs
On 17 November 2016 at 18:27, Graham Inggs wrote: > Copying to debian-science-maintainers list in case someone is > interested in rescuing this package. Meshlab is already maintained in the debian-science's git repository [1]. All of Teemu Ikonen's other packages have Debian Sci

Bug#811907: music: FTBFS with GCC 6: invalid conversion

2016-11-23 Thread Graham Inggs
Control: tags -1 patch The patch below fixes the FTBFS with GCC 6. --- a/src/connectivity.cc +++ b/src/connectivity.cc @@ -89,7 +89,7 @@ std::map::iterator info = connectivityMap.find (portName); if (info == connectivityMap.end ()) - return NO_CONNECTIVITY; + return (C

Bug#811986: qwtplot3d: FTBFS with GCC 6: symbol changes

2016-11-27 Thread Graham Inggs
Control: tags - 1 patch Hi Maintainer The attached patch works for me. Regards Graham --- a/debian/libqwtplot3d-qt4-0v5.symbols +++ b/debian/libqwtplot3d-qt4-0v5.symbols @@ -243,10 +243,10 @@ _ZN5Qwt3D4Axis9setMajorsEi@Base 0.2.7 _ZN5Qwt3D4Axis9setMinorsEi@Base 0.2.7 _ZN5Qwt3D4AxisC1ENS_6T

Bug#845082: (no subject)

2016-11-28 Thread Graham Inggs
On 29 November 2016 at 00:29, Breno Leitao wrote: > We just created a pull request to have this fixed upstream. Thanks! > Should we create a Debian patch also? This bug is tagged 'pending' and there's already a patch in the packaging git [1]. I did notice the patch uses round() while your PR us

Bug#920982: deal.ii: FTFBFS with doxygen 1.8.15 draft package

2019-02-09 Thread Graham Inggs
Control: severity -1 important Hi Paolo On Thu, 31 Jan 2019 at 11:09, Paolo Greppi wrote: > I tested your package against a draft package for doxygen 1.8.15: > https://bugs.debian.org/919413 > https://salsa.debian.org/paolog-guest/doxygen/-/jobs/107680/artifacts/browse/debian/output/ > > and it

Bug#921732: hg-git: incompatible with mercurial 4.9

2019-02-18 Thread Graham Inggs
Control: tags -1 + ftbfs Hi Julien I'm neither a user of mercurial nor hg-git. On 2019/02/08 16:52, Julien Cristau wrote: Guess there's two parts here, splitting them. hg-git has been in need of upstream love for a while AFAICT... Do you have any ideas on how to suppress the deprecation war

Bug#922739: r-cran-vegan: autopkgtest regression

2019-02-19 Thread Graham Inggs
Source: r-cran-vegan Version: 2.5-4+dfsg-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Hi Maintainer Since the upload of 2.5-4+dfsg-1, r-cran-vegan has been failing its own autopkgtests [1] with the following error: autopkgtest

Bug#923104: h5py: autopkgtest regression

2019-02-24 Thread Graham Inggs
Source: h5py Version: 2.9.0-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Hi Maintainer Since the upload of 2.9.0-1, h5py has been failing its own autopkgtests [1] with the following error: Testing with python3.7: ...s.

Bug#921732: hg-git: incompatible with mercurial 4.9

2019-02-28 Thread Graham Inggs
Hi Julien This autopkgtest failure still prevents mercurial 4.9-2 from migrating to testing. On 2019/02/18 14:08, Graham Inggs wrote: Do you have any ideas on how to suppress the deprecation warnings? I didn't figure out how to do this, but I patched them out of mercurial. With this

Bug#856926: rekall: package not installable after no-change rebuild

2017-03-06 Thread Graham Inggs
Source: rekall Version: 1.6.0+dfsg-1 Severity: serious Hi Maintainer Rebuilding rekall in sid or testing results in package python-rekall-core not being installable due to a strict versioned dependency on python-crypto (= 2.6.1). See contents of python-rekall-core.substvars: python:Provides

Bug#904247: pytest-sugar: FTBFS and test failure with pytest 3.6

2018-07-22 Thread Graham Inggs
Source: pytest-sugar Version: 0.9.1-2 Severity: serious Tags: ftbfs buster sid X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: needs-update Hi Maintainer Since the upload of pytest 3.6.2-2 to unstable, pytest-sugar's autopkgtests have been failing [1], with the

Bug#904319: FTBFS when building binary-packages only

2018-07-23 Thread Graham Inggs
Control: severity -1 normal Control: tags -1 + moreinfo unreproducible Hi Daniel On 23/07/2018 11:54, Daniel Baumann wrote: However, when locally rebuilding the package I saw that it wants to check the md5sum of the upstream tarball. This fails when building binary packages only, which should b

Bug#904709: python-cobra ftbfs (test failures)

2018-07-27 Thread Graham Inggs
Hi Andreas On 27 July 2018 at 10:01, Andreas Tille wrote: > I think the problem is here: > > ... > /usr/lib/python3/dist-packages/_pytest/config/__init__.py:412: in > _importconftest > raise ConftestImportFailure(conftestpath, sys.exc_info()) > E _pytest.config.ConftestImportFailure: Impor

Bug#904709: python-cobra ftbfs (test failures)

2018-07-27 Thread Graham Inggs
Control: block -1 by 904359 Control: user: debian...@lists.debian.org Control: usertags: needs-update On 28 July 2018 at 00:37, Andreas Tille wrote: > I did a local build and assumed that this can be reproduced. Ah OK, that is because pandas is not yet built for Python 3.7. If you built in testi

Bug#900486: python-pydap: FTBFS and Debci failure with NumPy 1.14

2018-07-28 Thread Graham Inggs
Control: clone -1 -2 Control: tags -1 + patch Control: retitle -2 FTBFS and Debci failure with Python 3.7 Control: tags -2 + ftbfs Hi Maintainer On 28 July 2018 at 07:38, Matthias Klose wrote: > === FAILURES > === > ___

Bug#906118: openmpi: some builds and autopkgtests time out on i386, armhf

2018-08-14 Thread Graham Inggs
Source: openmpi Version: 3.1.1.real-6 Severity: serious Hi Alastair We noticed in Ubuntu, builds and autopkgtests of a couple of openmpi-related packages time out on i386 and armhf. At least some of these have been successful with previous versions of libopenmpi3. I have been able to reprod

Bug#906349: [Pkg-pascal-devel] Bug#906349: doublecmd: FTBFS in buster/sid (tries to write in /usr)

2018-08-17 Thread Graham Inggs
Hi Santiago, Abou On 17 August 2018 at 13:19, Santiago Vila wrote: > I tried to build this package in buster but it failed: Thanks for the report! According to reproducible builds, doublecmd started to FTBFS in unstable on 2018-07-20 [1]. This was shortly after the upload of lazarus 1.8.4+dfsg-

Bug#906458: ddrescueview: FTBFS in buster/sid (tries to write in /usr/lib/lazarus)

2018-08-23 Thread Graham Inggs
Hi Santiago On 17/08/2018 21:20, Santiago Vila wrote: Hint: (lazarus) source file missing of FCL 1.0.1: /usr/lib/lazarus/1.8.4/packager/registration/fcllaz.pas Hint: (lazarus) normal output directory of package FCL 1.0.1 is not writable: "/usr/lib/lazarus/1.8.4/packager/units/x86_64-linux/" TP

Bug#906349: [Pkg-pascal-devel] Bug#906349: Bug#906349: doublecmd: FTBFS in buster/sid (tries to write in /usr)

2018-08-23 Thread Graham Inggs
Hi Abou On 17/08/2018 18:37, Graham Inggs wrote: Abou, do you have an opinion on whether this is a bug in lazarus, or does the doublecmd packaging need to be fixed? The same problem occurs in ddrescueview, reported in #906458. I found it was introduced by the changes to debian/rules in this

Bug#907267: openmpi: liggghts build on i386 times out

2018-08-25 Thread Graham Inggs
Source: openmpi Version: 3.1.1.real-6 Severity: serious Hi Alastair The last two builds of liggghts on i386 [1] against openmpi 3.1.1.real-6 and 3.1.1.real-7 have timed out. Regards Graham [1] https://buildd.debian.org/status/logs.php?pkg=liggghts&arch=i386

Bug#907407: openmpi: arpack builds on i386 and armhf time out

2018-08-27 Thread Graham Inggs
Source: openmpi Version: 3.1.1.real-6 Severity: serious Hi Alastair Recent reproducible builds of arpack have timed out on i386 [1] and armhf [2]. From the dates of previous builds, it appears that builds against openmpi 3.1.1.real-4 were successful. Regards Graham [1] https://tests.reproduci

Bug#905418: openmpi: elpa builds hang on multiple architectures

2018-08-27 Thread Graham Inggs
Hi Alastair Elpa seems to be another package with builds timing out. Confirmed on reproducible builders for i386 [1] and armhf [2]. Regards Graham [1] https://tests.reproducible-builds.org/debian/history/i386/elpa.html [2] https://tests.reproducible-builds.org/debian/history/armhf/elpa.html

Bug#905418: openmpi: elpa builds hang on multiple architectures

2018-08-30 Thread Graham Inggs
Hi Alastair On 30/08/2018 13:07, Alastair McKinstry wrote: Can you redo tests with  openmpi 3.1.2 ? Thanks for the new upload. I'm redoing the tests on elpa, ligghts and arpack. I'll update the bugs in due course. I think this new release fixes the hang issues, i've done some tests on ar

Bug#907267: openmpi: liggghts build on i386 times out

2018-08-30 Thread Graham Inggs
Latest build of liggghts on i386 against openmpi 3.1.2-1 timed out. https://buildd.debian.org/status/fetch.php?pkg=liggghts&arch=i386&ver=3.7.0%2Brepack1-1.1&stamp=1535641058&raw=0

Bug#905418: openmpi: elpa builds hang on multiple architectures

2018-08-31 Thread Graham Inggs
Hi Alastair A rebuild of elpa on armel failed yesterday [1]. It doesn't look like a time out, but it seems to have gotten to the point where it usually does. Maybe someone killed the build. Reproducible builds on i386 and armhf timed out yesterday [2][3]. Regards Graham [1] https://build

Bug#907407: openmpi: arpack builds on i386 and armhf time out

2018-08-31 Thread Graham Inggs
Hi Alastair Reproducible builds of arpack on i386 and armhf still time out against openmpi 3.1.2-1. Regard Graham

Bug#918157: openmpi seems broken on 32 bits architectures

2019-01-04 Thread Graham Inggs
Control: user debian...@lists.debian.org Control: usertag -1 regression Hi In Ubuntu, the upload of openmpi 3.1.3-7 has caused numerous autopkgtest failures on i386 and armhf [1]. Some affected packages are: combblas; dune-grid, lammps, liggghts, petsc, ray and superlu-dist. I re-tried these te

Bug#918479: freecad: autopkgtest regression

2019-01-06 Thread Graham Inggs
Source: freecad Version: 0.17+dfsg1-5 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer Since the upload of 0.17+dfsg1-5, freecad has been failing its own autopkgtests [1] with the following error: autopkgtest [04:10:57]: test freecadtest: [---

Bug#918558: mercurial: autopkgtest regression

2019-01-07 Thread Graham Inggs
Source: mercurial Version: 4.8-2 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Hi Maintainer Since the upload of 4.8-2, mercurial has been failing its own autopkgtests [1] with the following error: test-logtoprocess.t test-log

Bug#918676: r-cran-worrms: autopkgtest regression

2019-01-08 Thread Graham Inggs
Source: r-cran-worrms Version: 0.3.0+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer Since 2019-01-01, r-cran-worrms fails its autopkgtests with the following error: > library("testthat") > test_check("worrms") Loading required package: worrms Load

Bug#918833: node-browserify-lite: autopkgtest regression

2019-01-09 Thread Graham Inggs
Source: node-browserify-lite Version: 0.5.0-2 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Hi Maintainer Since the upload of 0.5.0-2, node-browserify-lite has been failing its own autopkgtests [1], where it succeeded in the past,

Bug#918833: closed by Bastien Roucariès (Bug#918833: fixed in node-browserify-lite 0.5.0-3)

2019-01-10 Thread Graham Inggs
Control: reopen -1 Autopkgtest of node-browserify-lite 0.5.0-5 still fails with: autopkgtest [22:30:54]: test command2: node test.js autopkgtest [22:30:54]: test command2: [--- extract requires tests: basic...OK multiple...OK trick...OK unescape...OK spaces...OK ignore braces.

Bug#914804: fixed in pycuda 2018.1.1-2

2019-01-11 Thread Graham Inggs
Control: severity -1 important Hi Santiago On 2019/01/11 14:54, Santiago Vila wrote: Hi. Sorry for the reopening but this is apparently still happening. The error is now slightly different: /usr/bin/ld: cannot find -lcuda collect2: error: ld returned 1 exit status error: command 'x86_64-linux-

Bug#918401: python-pygments must depend on python3-pygments (or a new package for pygmentize)

2019-01-13 Thread Graham Inggs
Control: affects -1 + src:julia Worked around in julia by adding python3-pygments and python3-pkg-resources to Build-Depends-Indep.

Bug#919370: deal.ii: FTBFS on s390x: p4est.debug test fails

2019-01-15 Thread Graham Inggs
Source: deal.ii Version: 9.0.1-1 Severity: serious Tags: ftbfs Hi Maintainer Recent rebuilds of deal.ii on s390x have been failing with the following errors: Test project /<>/obj-s390x-linux-gnu/tests/quick_tests Start 1: step.debug 1/19 Test #1: step.debug ...

Bug#919778: [Debian-med-packaging] Bug#919778: Bug#919778: mash FTBFS on armhf when built on arm64 hardware

2019-01-27 Thread Graham Inggs
Ubuntu has a patch that might help. https://patches.ubuntu.com/m/mash/mash_2.0-2ubuntu2.patch

Bug#920711: r-cran-repr: autopkgtest regression

2019-01-28 Thread Graham Inggs
Source: r-cran-repr Version: 0.19.1-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Hi Maintainer Since the upload of r-cran-tibble 2.0.0-1 to unstable, r-cran-repr has been failing its autopkgtests [1] with the following error:

Bug#920712: r-cran-repr: autopkgtest regression

2019-01-28 Thread Graham Inggs
Source: r-cran-repr Version: 0.19.1-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Hi Maintainer Since the upload of r-cran-tibble 2.0.0-1 to unstable, r-cran-repr has been failing its autopkgtests [1] with the following error:

Bug#920821: gcc-8: regression: ICE while compiling Trilinos

2019-01-29 Thread Graham Inggs
Source: gcc-8 Version: 8.2.0-15 Severity: serious Affects: src:trilinos Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88995 Hi Maintainer Trilinos FTBFS with an ICE with gcc-8 8.2.0-15 (8.2.0-14 was fine). Confirmed on reproducible builds [1]. In file included from /build/1st/trilin

Bug#921338: r-cran-taxize: autopkgtest regression

2019-02-04 Thread Graham Inggs
Source: r-cran-taxize Version: 0.9.5+dfsg-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: regression Hi Maintainer Since the upload of 0.9.5+dfsg-1 to unstable, r-cran-taxize has been failing its own autopkgtests [1] with the following err

Bug#921352: gmsh: breaks octave-msh autopkgtest

2019-02-04 Thread Graham Inggs
Source: gmsh Version: 4.1.3+ds1-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks Hi Maintainer The recent upload of gmsh 4.1.3+ds1-1 to unstable breaks the autopkgtest of octave-msh 1.0.10-6 in testing with the following error: [in

Bug#920711: Test suite seems to uncover conflict between new version of tibble and repr (Was: Bug#920711: r-cran-repr: autopkgtest regression)

2019-02-05 Thread Graham Inggs
Hi! On Tue, 5 Feb 2019 at 22:34, Andreas Tille wrote: > I can also add r-cran-tibble via > > apt-get install --no-install-recommends r-cran-tibble > > and the test suite keeps on succeeding! However, after intalling > r-cran-dplyr the described error occures while after deinstalling > r-cran

Bug#849991: breathe: FTBFS with new doxygen?

2017-01-03 Thread Graham Inggs
Control: affects -1 src:gyoto Control: tags -1 patch I found a similar problem building the gyoto package. Confirming that Albert's patch from the upstream bug report fixes building breathe and gyoto. --- a/src/xmlgen.cpp +++ b/src/xmlgen.cpp @@ -620,7 +620,7 @@ if (md->isInline()) t << "ye

Bug#850229: dune-grid: FTBFS (not enough slots available)

2017-01-05 Thread Graham Inggs
Hi On 05/01/2017 12:05, Santiago Vila wrote: Status:FAILED Output: -- There are not enough slots available in the system to satisfy the 2 slots that were requested by the application:

Bug#850456: [Debichem-devel] Bug#850456: elpa: FTBFS (not enough slots available)

2017-01-06 Thread Graham Inggs
Hi On 6 January 2017 at 20:00, Santiago Vila wrote: > -- > There are not enough slots available in the system to satisfy the 2 slots > that were requested by the application: > ./elpa2_test_complex_c_version > > Either requ

Bug#848917: nautic FTBFS on architectures where char is unsigned: error: narrowing conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]

2017-01-10 Thread Graham Inggs
://bugs.debian.org/848917 Author: Graham Inggs Last-Update: 2017-01-10 --- a/plant.h +++ b/plant.h @@ -30,7 +30,7 @@ char maxargs; char max_harmonic[NARGS]; char max_power_of_t; - char *arg_tbl; + signed char *arg_tbl; void *lon_tbl; void *lat_tbl; void *rad_tbl; @@ -1531,7

Bug#850229: dune-grid: FTBFS (not enough slots available)

2017-01-10 Thread Graham Inggs
On 5 January 2017 at 13:46, Ansgar Burchardt wrote: > On my laptop with 4 cores + HT (so 8 threads), I see `mpirun` complain > once I start more than 4 processes, i.e. more processes than real > cores. Did you count threads or cores when you tried? I haven't been able to duplicate that behaviour

Bug#848917: nautic FTBFS on architectures where char is unsigned: error: narrowing conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]

2017-01-13 Thread Graham Inggs
Thanks for the upload, Andreas! If this bug had been tagged [1] like #811740 was, I might have seen it sooner. I only saw it when I noticed nautic was not migrating in Ubuntu. :( [1] https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-gcc-6;users=debian-...@lists.debian.org

Bug#848917: nautic FTBFS on architectures where char is unsigned: error: narrowing conversion of '-1' from 'int' to 'char' inside { } [-Wnarrowing]

2017-01-13 Thread Graham Inggs
On 13/01/2017 14:02, Andreas Beckmann wrote: you could have done that QA upload yourself (even without filing a bug) :-) Yeah, I know :( and I would have, seeing it is a QA package, but I thought it was too late for Stretch.

Bug#848781: [Debichem-devel] Bug#848781: tiledarray: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

2017-01-13 Thread Graham Inggs
On 13 January 2017 at 13:40, Graham Inggs wrote: > Do we need to request ageing of 0.6.0-4, or will this email be sufficient to > reset the autoremoval counter? The previous mail was sufficient. Version 0.4.4-2 of tiledarray is marked for autoremoval from testing on 2017-01-28.

Bug#851726: liggghts: FTBFS on single-CPU machines (not enough slots available)

2017-01-18 Thread Graham Inggs
See #850229.

Bug#852283: libopenblas-dev: missing on mips64el

2017-01-22 Thread Graham Inggs
Source: openblas Version: 0.2.19-1 Severity: serious Hi Maintainer Architecture: mips64el was added to libopenblas-base but not libopenblas-dev. Was this an oversight? Regards Graham

Bug#852296: yade FTBFS on arm64: compiler processes terminated (machine runs out of RAM?)

2017-01-23 Thread Graham Inggs
On 23/01/2017 14:08, Adrian Bunk wrote: This buildd has 6 CPUs, but it has only 8 GB of RAM. From the last changelog entry: * [d763fbf] Set compat level to 10. The switch to debhelper 10 enabled parallel builds. Yade 2017.01a-1 FTBFS on most architectures in Ubuntu. The following changed h

Bug#1030653: pyemd: autopkgtest regression

2023-02-05 Thread Graham Inggs
Source: pyemd Version: 0.5.1.54.g802fa86-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer The autopkgtests of pyemd 0.5.1.54.g802fa86-1 are failing in testing [1] and unstable [2]. I've copied what I hope is the relevant part of the log below. Regards Grah

Bug#1031524: fuse3: setxattr is broken

2023-02-17 Thread Graham Inggs
Source: fuse3 Version: 3.13.0-1 Severity: serious Forwarded: https://github.com/libfuse/libfuse/issues/730 Control: affects -1 src:ostree Hi Maintainer Since the upload of 3.13.0-1, the 'name' string passed to fs->op.setxattr has the first 8 characters missing. Steps to reproduce: $ dget https:

Bug#1032120: tiledb: uses atomic operations, but is not linked to libatomic

2023-02-28 Thread Graham Inggs
Source: tiledb Version: 2.14.1-1 Severity: serious Tags: ftbfs patch Control: affects -1 src:tiledb-py Hi Dirk TileDB uses atomic operations but it is not linked to libatomic on the architectures that need it. This can be seen in recent build logs for armel[1], mipsel[2], powerpc[3], riscv64[4]

Bug#1032120: tiledb: uses atomic operations, but is not linked to libatomic

2023-02-28 Thread Graham Inggs
Hi Dirk Thanks for the quick upload! Already got a successful build of tiledb-py on riscv64[1]. On Tue, 28 Feb 2023 at 17:14, Dirk Eddelbuettel wrote: > TileDB upstream does everything in CMake (which I do not fully speak) so > "eventually" it would be nice to port this. After testing the patch

Bug#1031964: libtrilinos-{globi,opti}pack-{13.2,dev} are empty

2023-03-08 Thread Graham Inggs
Hi Sorry for missing this. I noticed the empty packages (or at least, Lintian did!) while sponsoring the upload of 13.4.1-1 to experimental and fixed it there, but didn't think it important enough to fix for bookworm. If someone is willing to do a (team) upload, I'll be happy to unblock it. Ple

Bug#977027: rhino breaks dojo autopkgtest: Cannot set property "dojo" of null to "[object Object]"

2023-03-26 Thread Graham Inggs
Control: reassign -1 src:rhino, src:dojo Control: found -1 rhino/ 1.7.14-1 Control: found -1 dojo/ 1.17.2+dfsg1-2 It appears that dojo needs to be rebuilt against the new rhino, and rebuilding dojo against the new rhino makes it incompatible with the old rhino. The changes that the new rhino make

Bug#977027: rhino breaks dojo autopkgtest: Cannot set property "dojo" of null to "[object Object]"

2023-03-26 Thread Graham Inggs
Hi Markus On Sun, 26 Mar 2023 at 16:34, Markus Koschany wrote: > 1. There is no transition needed because only shrinksafe is affected by the > new > rhino version. How did you determine this? > 2. shrinksafe has no reverse-dependencies That is true, but src:dojo has ledgersmb and tt-rss as re

Bug#1034524: libretro-bsnes-mercury: uses invalid architecture wildcards

2023-04-17 Thread Graham Inggs
Source: libretro-bsnes-mercury Version: 094+git20220807-6 Severity: serious Hi Maintainer Since the upload of 094+git20220807-6, the kodi-game-libretro-bsnes-mercury-* binary packages are no longer built on armel and armhf [1][2][3]. This is due to the use of invalid architecture wildcards 'any-

Bug#1029316: r-cran-spatstat.core: autopkgtest regression in testing

2023-01-21 Thread Graham Inggs
Source: r-cran-spatstat.core Version: 2.4-4-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer Somehow, r-cran-spatstat.core has regressed its autopkgtests in testing [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] ht

Bug#1029326: intel-mkl: autopkgtest regression in testing

2023-01-21 Thread Graham Inggs
Source: intel-mkl Version: 2020.4.304-3 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer Sometime in February 2021, intel-mkl's autopkgtests regressed in testing [1]. I've copied what I hope are relevant parts of the log below. Regards Graham [1] https://c

Bug#1027943: regina-normal FTBFS with Python 3.11 as default version

2023-01-22 Thread Graham Inggs
Control: tags -1 + patch fixed-upstream There's an upstream commit [1] that seems to fix the build with Python 3.11. [1] https://github.com/regina-normal/regina/commit/8a583ee4ed8066103c530b91c6df4efa512203aa From 8a583ee4ed8066103c530b91c6df4efa512203aa Mon Sep 17 00:00:00 2001 From: Benjamin

Bug#1029452: python-skbio: (autopkgtest) needs update for NumPy 1.24

2023-01-22 Thread Graham Inggs
Source: python-skbio Version: 0.5.8-1 Severity: serious User: debian...@lists.debian.org Usertags: needs-update Hi Maintainer The autopkgtests of python-skbio fail with NumPy 1.24 [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/pack

Bug#1029550: scipy: (s390x autopkgtest) needs update for NumPy 1.24

2023-01-24 Thread Graham Inggs
Source: scipy Version: 1.8.1-21 Severity: serious User: debian...@lists.debian.org Usertags: needs-update Hi Maintainer The autopkgtests of scipy fail with NumPy 1.24 on s390x [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages

Bug#1029593: nibabel: (armel autopkgtest) needs update for NumPy 1.24

2023-01-24 Thread Graham Inggs
Source: nibabel Version: 4.0.2-1 Severity: serious User: debian...@lists.debian.org Usertags: needs-update Hi Maintainer The autopkgtests of nibabel fail with NumPy 1.24 on armel [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packa

Bug#1029440: opm-common: FTBFS in bookworm (cc1plus: fatal error: [...]/builtin_pybind11.cpp: No such file or directory)

2023-01-27 Thread Graham Inggs
Control: severity -1 important Hi Markus, Santiago As opm-common is no longer in bookworm, this bug is currently unreproducible. Please feel free to raise the severity once opm-common has migrated and this bug is still reproducible. Regards Graham

Bug#1029593: nibabel: (armel autopkgtest) needs update for NumPy 1.24

2023-01-28 Thread Graham Inggs
Control: reopen -1 autopkgtests of nibabel/5.0.0-1 still fail in the same way on armel. https://ci.debian.net/packages/n/nibabel/testing/armel/

Bug#1030025: yt: misses versioned dependencies on numpy

2023-01-30 Thread Graham Inggs
Source: yt Version: 4.1.4-1 Severity: serious Tags: patch Hi Maintainer python3-yt has a hard-coded dependency on numpy-abi-9 and misses a versioned dependency on python3-numpy. The patch below should ensure these are automatically added correctly. Regards Graham --- a/debian/control +++ b/deb

Bug#1030109: zfp: misses versioned dependencies on numpy

2023-01-30 Thread Graham Inggs
Source: zfp Version: 1.0.0-5 Severity: serious Tags: patch Hi Maintainer python3-zfpy misses a dependency on python3-numpy-abi and a versioned dependency on python3-numpy. The patch below should ensure these are automatically added correctly. Regards Graham --- a/debian/control +++ b/debian/c

  1   2   3   4   5   6   7   8   9   10   >