Bug#893729: sympy FTBFS: python3-distutils is now a separate package

Another option could be to patch the build system to use setuptools instead of distutils as recommended by the PyPA? Le mer. 21 mars 2018 à 20:45, Rebecca N. Palmer a écrit : > Source: sympy > Severity: serious > Control: tags -1 patch > X-Debbugs-Cc:

Bug#890364: pybind11-dev: Request migration to unstable

Hi Shane, thanks for reaching out, On Wed, 14 Feb 2018 00:48:14 + Shane Loretz wrote: > Would the maintainer be willing to migrate 2.2.1 from experimental to unstable? I'm a user of a distribution based on debian unstable. I have been using pybind11 from pip

Re: Changing maintainer for mpich to debian-hpc

Can't we have the Debian Science Maintainers just use debian-science@l.d.o instead of the Alioth address then? As long as the package continues to be maintained by a motivated packaging team, I personally have no objection to the transfer you propose. Cheers, Ghis Le 24 janv. 2018 10:01,

Bug#877316: Forwarded upstream

Control: forwarded -1 https://github.com/clMathLibraries/clBLAS/issues/321 -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#881837: Updating the h5py Uploaders list

Control: tags -1 + fixed pending On Wed, 15 Nov 2017 18:16:51 +0100 Tobias Frost wrote: Source: h5py Version: 2.6.0-2 2.7.1-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Soeren Sonnenburg wishes no longer to be uploader of h5py. We are

Bug#881054: libarrayfire-opencl3: "INTERNAL KERNEL BUILD ERROR" from af::matmulTN

Hi Ralf, Based on the content of your report, you are suggesting that the latest version (3.5.1 at this very time) would solve the issue you are experiencing, am I correct? Cheers, Ghis -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Bug#877419: [Help] Exclusion did not worked (Was: Bug#877419: Bug#877700: RM: pandas [arm64 armel armhf mips mips64el mipsel s390x] ...)

On 14/10/17 07:54, Andreas Tille wrote: On Fri, Oct 13, 2017 at 08:00:36PM +0200, Andreas Tille wrote: I might try to pick some of the failed tests from the logs. I did so once with kind of iterative uploads for python-cogent package by checking the logs of the failing architectures. If you

Bug#877109: pybtex FTBFS with Sphinx 1.6.4-1

On 10/10/17 11:58, Adrian Bunk wrote: On Tue, Oct 10, 2017 at 12:08:29AM +0100, Ghislain Vaillant wrote: On 09/10/17 23:06, Adrian Bunk wrote: On Mon, Oct 09, 2017 at 12:28:22PM +0100, Ghislain Vaillant wrote: ... I was complaining about the insufficiencies behind this RC, more than

Bug#877109: pybtex FTBFS with Sphinx 1.6.4-1

On 09/10/17 23:06, Adrian Bunk wrote: On Mon, Oct 09, 2017 at 12:28:22PM +0100, Ghislain Vaillant wrote: ... I was complaining about the insufficiencies behind this RC, more than the situation with Sphinx. No offense to Adrian, but getting an RC bug reported without much context to work

Bug#877109: pybtex FTBFS with Sphinx 1.6.4-1

On 03/10/17 12:28, Dmitry Shachnev wrote: Control: forwarded -1 https://bitbucket.org/pybtex-devs/pybtex/pull-requests/9/ Hi Ghislain, On Sat, Sep 30, 2017 at 10:40:52AM +0100, Ghislain Vaillant wrote: And what the hell am I supposed to do with this?! Nice of you to report the issue

Bug#877316: clblas: Crashes on single-precision-only hardware, due to double-precision literals

Hi Rebecca, On Sat, 30 Sep 2017 14:47:03 +0100 "Rebecca N. Palmer" wrote: Package: libclblas2 Version: 2.12-1 Control: tags -1 upstream Control: affects -1 beignet-opencl-icd Some clblas operations use '0.0' (a double-precision literal) not '0.0f' (a

Bug#877109: pybtex FTBFS with Sphinx 1.6.4-1

sphinx (1.6.4-1) unstable; urgency=medium ... * dh_sphinxdoc: Turn warning about missing SOURCELINK_SUFFIX to an error. ... -- Dmitry Shachnev Tue, 26 Sep 2017 17:47:54 +0300 And what the hell am I supposed to do with this?! Nice of you to report the issue but, without

Bug#853658: Forwarded upstream

On 18/08/17 17:26, Sebastiaan Couwenberg wrote: On Mon, 7 Aug 2017 08:49:19 +0100 Ghislain Vaillant wrote: control: forwarded -1 https://github.com/Shark-ML/Shark/issues/194 Instead of packaging a snapshot as suggested by upstream, I suggest to explicitly build the package with GCC 6 (as per

Bug#871927: forwarded upstream

control: forwarded -1 https://github.com/QuantStack/xtensor-python/issues/102 -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#853658: Forwarded upstream

control: forwarded -1 https://github.com/Shark-ML/Shark/issues/194 -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#870128: libgpuarray: broken autopkgtests

On Sun, 2017-07-30 at 17:35 +0200, Graham Inggs wrote: > Can you test your package with mesa-opencl-icd instead of pocl- > opencl-icd? mesa-opencl-icd is for devices compatible with amdgpu. > This will allow the test suite to run on more architectures than only > amd64 and i386. Not really,

Bug#870128: libgpuarray: broken autopkgtests

On Sat, 29 Jul 2017 23:33:21 -0700 Steve Langasek wrote: > > Your latest upload of libgpuarray has replaced the previous python > autopkgtest with one based on pocl. Indeed, which allows running the upstream test suite on our CPU-based builders. This is better than

Bug#868992: python-ltfatpy: FTBFS on hurd-i386: No module named 'matplotlib._path'

On Wed, 19 Jul 2017 21:40:57 -0400 "Aaron M. Ucko" > Thanks for taking care of #861094.  Alas, the build of python-ltfatpy > on hurd-i386 (admittedly not a release architecture) is still failing: >  >   E   ModuleNotFoundError: No module named 'matplotlib._path' >  > I see that

Bug#868991: fixed in packaging VCS

control: tags -1 + fixed pending The fix will be rolled in the next iteration of the package. Thanks Aaron, Ghis -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#868877: forwarded upstream

control: forwarded -1 https://github.com/Theano/libgpuarray/issues/481 Thanks for reporting. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#867987: h5py: FTBFS on sparc64 due to unaliged accesses in test suite

On Mon, 10 Jul 2017 22:18:53 +0100 James Clarke wrote: > Source: h5py > Version: 2.7.0-1 > Tags: upstream patch > Forwarded: https://github.com/h5py/h5py/pull/904 > User: debian-sp...@lists.debian.org > Usertags: sparc64 > X-Debbugs-Cc: debian-sp...@lists.debian.org > > Hi, >

Fixed in python-bayespy/0.5.8-1 [Was: Re: python-bayespy_0.5.6-1_amd64.changes REJECTED]

On Fri, 2017-05-12 at 19:00 +, Thorsten Alteholz wrote: > Hi, > > > at least > bayespy-0.5.6/bayespy/inference/vmp/nodes/logistic.py > should be also mentioned in your debian/copyright. Thanks for spotting this, Thorsten. As suspected, it turned out to be an omission from a relicensing

Bug#826457: Forwarded upstream

control: forwarded -1 https://github.com/sympy/sympy/issues/12619 Forwarded upstream. Next time, please consider filing feature requests directly to the upstream bug tracker. Thanks, Ghis -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Bug#824073: Marked as wontfix

control: tags -1 wontfix I am marking your request as "wontfix" for the following reasons: - This bug does not affect src:sympy anymore, since the missing galgebra module is unlikely to reappear in a future release. - If a new source package were to be introduced for galgebra, an ITP or RFP bug

Bug#822296: Forwarded upstream

control: forwarded -1 https://github.com/spyder-ide/spyder/issues/4423 -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#861095: python-ltfatpy: FTBFS: ValueError: Little-endian buffer not supported

Thanks for breaking this issues down. Forwarding upstream. On Mon, 24 Apr 2017 11:55:24 -0400 "Aaron M. Ucko" wrote: Source: python-ltfatpy Version: 1.0.8-1 Severity: important Justification: fails to build from source The builds of python-ltfatpy for s390x and the

Bug#861094: python-ltfatpy: FTBFS (32-bit): TypeError: dim should be an integer

Thanks for breaking this issues down. Forwarding upstream. On Mon, 24 Apr 2017 11:51:25 -0400 "Aaron M. Ucko" wrote: Source: python-ltfatpy Version: 1.0.8-1 Severity: important Justification: fails to build from source Builds of python-ltfatpy for 32-bit architectures such as

Bug#859080: Forwarded to proposed PR

control: forwarded -1 https://github.com/spyder-ide/spyder/pull/4311 -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#859080: spyder-memory-profiler: FTBFS: AttributeError: 'NoneType' object has no attribute 'toUtf8'

control: reassign -1 spyder control: affects -1 spyder-memory-profiler On Fri, 2017-03-31 at 10:33 +0100, Chris Lamb wrote: > Ghislain Vaillant wrote: > > > I am going to need some more context here. The build ran fine on the > > builders when the package was initially upload

Bug#859080: spyder-memory-profiler: FTBFS: AttributeError: 'NoneType' object has no attribute 'toUtf8'

Hi Chris, On Thu, 30 Mar 2017 08:26:36 +0100 Chris Lamb wrote: Source: spyder-memory-profiler Version: 0.1.0-1 Severity: serious Justification: fails to build from source User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-Cc:

Bug#844601: reassigned to python-qtawesome

control: reassign -1 src:python-qtawesome control: fixed -1 src:python-qtawesome/0.4.4 control: affects -1 src:spyder -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#854502: No longer blocked by #854692

control: unblock -1 by 854692 Upstream provided a fix for the gcc-6 LTO regression affecting the build of pybind11. As a result, I am removing the block relationship. Ghis -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Bug#854502: Blocked by #854692

control: block -1 by 854692 -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#848634: python-cartopy: FTBFS on *i386: test_lambert_azimuthal_equal_area fails

control: reassign -1 src:proj Reassigning this bug to src:proj, following Aaron's investigation. On Thu, 26 Jan 2017 11:34:40 -0500 u...@debian.org (Aaron M. Ucko) wrote: > Ghislain Vaillant <ghisv...@gmail.com> writes: > > > So, you think it would help to request sr

Bug#848634: python-cartopy: FTBFS on *i386: test_lambert_azimuthal_equal_area fails

On Thu, 2017-01-26 at 10:41 -0500, Aaron M. Ucko wrote: > Ghislain Vaillant <ghisv...@gmail.com> writes: > > > I tried your suggestion out but it did not work on a test build in > > debomatic. The same errors are reported at the test stage. > > I'm sor

Bug#844601: forwarded to new upstream bug

control: forwarded -1 https://github.com/spyder-ide/spyder/issues/4049 -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#844601: forwarded upstream

control: forwarded -1 https://github.com/spyder-ide/spyder/issues/4014 -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#732949: spyder: Internal console spamming

On Mon, 23 Dec 2013 00:27:56 +0100 =?utf-8?q?=C3=89lie_Gouzien?= wrote: > Package: spyder > Version: 2.1.10-2 > Severity: important This version is now significantly outdated. Could you please verify whether the issue is still happening on one of the recent versions being

Bug#851162: Still unresolved upstream, help needed

Cc'd to debian-powerpc On Fri, 13 Jan 2017 10:17:18 + Ghislain Vaillant <ghisv...@gmail.com> wrote: control: forwarded -1 https://github.com/h5py/h5py/issues/817 Upstream is running out of ideas, so any help from the team would be warmly welcome. Cheers, Ghis -- debian-s

Bug#851162: forwarded upstream

control: forwarded -1 https://github.com/h5py/h5py/issues/817 -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#850699: Focus on mips / s390x issue, fixed upstream

control: retitle -1 h5py: FTBFS [mips, s390x]: test failures control: usertag -1 - ppc64el Splitting this FTBFS into 2 different issues. This one for mips / s390x and one for ppc* architectures. There is a fix pending upstream for the mips / s390x issue. Ghis -- debian-science-maintainers

Bug#850027: libfreeimage3: freeimage 3.17.0+ds1-4 makes rviz unusable

On Thu, 2017-01-12 at 12:27 +, James Cowgill wrote: > Hi, > > On 12/01/17 12:11, Ghislain Vaillant wrote: > > On Wed, 11 Jan 2017 11:37:47 +0100 Jochen Sprickerhof <jspri...@debian.org> > > wrote: > > > Package: libfreeimage3 > > &

Bug#850027: libfreeimage3: freeimage 3.17.0+ds1-4 makes rviz unusable

On Wed, 11 Jan 2017 11:37:47 +0100 Jochen Sprickerhof wrote: > Package: libfreeimage3 > Followup-For: Bug #850027 > > Hi, > > is there anything I can do to speed this up? Would be nice to get rviz back > ;). > > Cheers Jochen I now have very limited time for this and

Bug#850027: libfreeimage3: freeimage 3.17.0+ds1-4 makes rviz unusable

have enough time for now. Cheers Anton 2017-01-08 11:16 GMT+01:00 Ghislain Vaillant <ghisv...@gmail.com>: On Thu, 5 Jan 2017 21:57:53 + James Cowgill <jcowg...@debian.org> wrote: Control: block 849696 by -1 Control: tags -1 patch Hi, This is of course the same bug as #84

Bug#850027: libfreeimage3: freeimage 3.17.0+ds1-4 makes rviz unusable

On Thu, 5 Jan 2017 21:57:53 + James Cowgill wrote: Control: block 849696 by -1 Control: tags -1 patch Hi, This is of course the same bug as #849696 in OGRE, but I still think it should be fixed in freeimage. I'd like to propose this patch (a new version of

Bug#850243: forge: FTBFS on multiple architectures

Now CC'd to the Debian CMake Team On 05/01/17 12:26, Ghislain Vaillant wrote: CC'd the Debian CMake Team, who might be able to help. On 05/01/17 10:48, Ghislain Vaillant wrote: CC'd to the src:glm maintainer, On Thu, 05 Jan 2017 10:37:06 + Ghislain Antony Vaillant <ghisv...@gmail.

Bug#850243: forge: FTBFS on multiple architectures

CC'd the Debian CMake Team, who might be able to help. On 05/01/17 10:48, Ghislain Vaillant wrote: CC'd to the src:glm maintainer, On Thu, 05 Jan 2017 10:37:06 + Ghislain Antony Vaillant <ghisv...@gmail.com> wrote: Source: forge Version: 0.9.2-2 Severity: serious Justification:

Bug#850243: forge: FTBFS on multiple architectures

CC'd to the src:glm maintainer, On Thu, 05 Jan 2017 10:37:06 + Ghislain Antony Vaillant wrote: Source: forge Version: 0.9.2-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, Since the latest update of

Bug#850027: libfreeimage3: freeimage 3.17.0+ds1-4 makes rviz unusable

Hi Erik, thanks for reporting this issue, freeimage/3.17.0+ds1-4 fixed an issue with the patch used to remove the vendored dependencies and use the system one instead. See #841089 [1]. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841089 The updated patch introduces a null-node for

Bug#849593: libfftw3-single3: dependencies in shlibs file not tight enough (Was: Bug#849589: ardour: undefined symbol: fftwf_make_planner_thread_safe)

CC'd to d-science, On Fri, 30 Dec 2016 01:24:07 + James Cowgill <jcowg...@debian.org> wrote: Hi, On 30/12/16 00:50, Ghislain Vaillant wrote: > On Thu, 29 Dec 2016 00:30:58 + James Cowgill <jcowg...@debian.org> wrote: >> Control: severity -1 serious >> Cont

Bug#849593: Bug#849589: ardour: undefined symbol: fftwf_make_planner_thread_safe

On Thu, 29 Dec 2016 00:30:58 + James Cowgill wrote: > Control: severity -1 serious > Control: clone -1 -2 > Control: reassign -2 libfftw3-single3 3.3.5-1 > Control: block -1 by -2 > Control: retitle -2 libfftw3-single3: dependencies in shlibs file not tight > enough > >

Bug#848761: ovito: FTBFS: Test failures, now fixed upstream

On Fri, 23 Dec 2016 19:28:09 + Ghislain Vaillant <ghisv...@gmail.com> wrote: > I have forwarded the issue upstream with a build log on the latest > upstream version done on debomatic. Alright, upstream claims the issue is fixed on `master`. I intend to cherry-pick the fix onto 2

Bug#848761: ovito: FTBFS: Test failures

Hopefully, updating the package to the latest upstream (2.8.1) may fix these test problems. That's what I am trying now. Ghis -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Bug#848771: numexpr: FTBFS: Test failures

control: forwarded -1 https://github.com/pydata/numexpr/issues/239 -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#848634: python-cartopy: FTBFS on *i386: test_lambert_azimuthal_equal_area fails

control: forwarded -1 https://github.com/SciTools/cartopy/issues/799 This issue is already forwarded upstream and was recently pinged for update. I would not hold my breath though , as upstream has not been responsive to any requests / questions I have raised so far. We shall see. Ghis --

Bug#844403: src:nfft: FTBFS on ppc64el

On Mon, 12 Dec 2016 13:09:10 -0200 Breno Leitao wrote: > Sure. Since the problem is only related to long double, you can bypass > either all the tests on ppc64el, or, disable long double on ppc64el and keep > the tests. Either way it should work. In fact, I came up with a

Bug#844403: src:nfft: FTBFS on ppc64el

On Mon, 28 Nov 2016 11:24:27 -0200 Breno Leitao <bren...@br.ibm.com> wrote: On 11/27/2016 07:16 PM, Ghislain Vaillant wrote: > On Thu, 24 Nov 2016 18:49:29 -0200 Breno Leitao <bren...@br.ibm.com> wrote: >> I am looking at this issue, and the first test set is checkall. >

Bug#846351: h5py NMU for HDF5 1.10

On 01/12/16 10:01, Iain Lane wrote: On Thu, Dec 01, 2016 at 08:27:16AM +, Ghislain Vaillant wrote: Hi Ian, Thanks for looking into this issue. Indeed the HDF5 transition has made quite a few RCs pop the last few days. Please drop the deferred and let me prepare a conventional update

Bug#838908: awaiting version 3.4.2

This is currently on hold due to upstream working on the last hotfix update of the 3.4.x series. It is scheduled for Dec. 5th. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Bug#846351: h5py NMU for HDF5 1.10

On 01/12/16 08:27, Ghislain Vaillant wrote: Hi Ian, Thanks for looking into this issue. Indeed the HDF5 transition has made quite a few RCs pop the last few days. Please drop the deferred and let me prepare a conventional update with your changes in, plus some cleaning of the packaging. Can I

Bug#846351: h5py NMU for HDF5 1.10

Hi Ian, Thanks for looking into this issue. Indeed the HDF5 transition has made quite a few RCs pop the last few days. Please drop the deferred and let me prepare a conventional update with your changes in, plus some cleaning of the packaging. Can I ping you back for sponsorship when I am

Bug#844403: src:nfft: FTBFS on ppc64el

On Thu, 24 Nov 2016 18:49:29 -0200 Breno Leitao wrote: I am looking at this issue, and the first test set is checkall. If I run it inside dpkg-buildpackage, it fails as in the log, but, if I run it isolated, I see no errors, as showed: $ ./checkall 2>&1 | grep -i fail

Bug#836599: RE: Bug#836599: shark: FTBFS on mips/mipsel: test errors

On Tue, 18 Oct 2016 11:36:52 + Dejan Latinovic wrote: Control: tags -1 + patch Control: user -1 debian-m...@lists.debian.org Control: usertags -1 mips-patch Hi Ghislain, I have updated the patch that reduces optimization level with requested information,

Bug#845279: freeimage FTCBFS: uses build architecture compiler and pkg-config

Hi Helmut, Thanks for looking into this issue with cross-compilation. I'll prepare an upload with your patch + fix for #841089 soon. Cheers, Ghis -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Bug#841089: Bug and patch acknowledged

Hi Boris, Thanks for looking into this issue with the FreeImage plugins. Your explanation makes sense and I should have probably looked more carefully at the details of the patch when cherry-picking this from the Fedora packaging. I'll find some time to try out your patch and roll it out

Bug#844008: src:clsparse: FTBFS on ppc64el

tag -1 pending thanks On Mon, 14 Nov 2016 17:37:52 -0200 Fernando Seiti Furusato wrote: Source: clsparse Followup-For: Bug #844008 I have created a patch that basically undefines "bool" and "vector" as macros, because it is how they come from altivec.h. I have

Re: Typo in Changelog

On 12/10/16 06:41, Salvatore Bonaccorso wrote: Hi, On Tue, Oct 11, 2016 at 07:20:47PM +, Ghislain Antony Vaillant wrote: [ Ghislain Antony Vaillant ] * Fix CVE-2016-5864: apply patch from wheezy-security. Thanks to Salvatore Bonaccorso, Balint Reczey and Chris Lamb (Closes:

Bug#839827: freeimage: CVE-2016-5684

Dear Salvatore, Balint, Thanks for forwarding the CVE to us and verifying which versions of the package were affected. I'll monitor the progress of this CVE. The CVE reporter offered some clues as to how to mitigate the problem, but I wonder how appropriate closure of this vulnerability can be

Bug#539975: tagged as wontfix

control: tag -1 wontfix Debian now has automatic debug packages so a separate -dbg package is no longer necessary. Ghis -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Bug#836677: pysparse: still worth maintaining?

2016-09-22 9:33 GMT+02:00 Ghislain Vaillant <ghisv...@gmail.com>: I have had a look at updating the package to the newest upstream release and fixing this FTBFS. However, I have got strong concerns as to whether it is worth keeping this package maintained in the archive: - The latest release o

Bug#836677: pysparse: still worth maintaining?

I have had a look at updating the package to the newest upstream release and fixing this FTBFS. However, I have got strong concerns as to whether it is worth keeping this package maintained in the archive: - The latest release on PyPI [1] is busted (missing files). The issue was reported [2] but

Bug#806616: fixed + pending

control: tags -1 + fixed pending I am working on it. The issue is fixed in my fork, and the fix should be rolled with the next update which will include a new upstream release. Thanks, Ghis -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Bug#836599: downgrading severity to normal

control: severity -1 normal Previous builds on mips and mipsel have been removed [1]. Downgrading the severity of this bug to allow the updated package to transition. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836740 Cheers, Ghis -- debian-science-maintainers mailing list

Bug#836599: forwarded upstream

control: forwarded -1 https://github.com/Shark-ML/Shark/issues/112 Forwarded upstream. Not sure whether this package was intended to work on these architectures, so upstream might just not care about this. I'll wait for their reply. The options are: - Upstream fixes it hopefully. - Disable

Bug#836413: forwarded upstream

control: forwarded -1 https://github.com/opengm/opengm/issues/477 Thanks for monitoring this package Aaron. This issue has been forwarded upstream. Ghis -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Bug#831669: forwarded upstream

control: forwarded -1 https://github.com/pyFFTW/pyFFTW/issues/128 Upstream confirmed the non-portability of the package due to both heavy reliance on x86 alignment, and availability of the long-double precision of the FFTW library. The latter is not supported by all architectures. Solving this

Bug#836216: opengm: FTBFS (32-bit): SelfFusion/LazyFlipper type mismatch

control: forwarded -1 https://github.com/opengm/opengm/issues/475 Thanks for reporting this issue. Upstream has been notified. Perhaps an explicit cast to size_t where appropriate could solve the compile error then. Best regards, Ghislain -- debian-science-maintainers mailing list

Bug#820701: shark: FTBFS on various architectures - testsuite failures

control: forwarded -1 https://github.com/Shark-ML/Shark/issues/110 Indeed, some tests were fixed but not all. Forwarded upstream. Ghis -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Bug#826042: Spyder crashes on start

On 24/07/16 21:49, Ghislain Vaillant wrote: Regarding rope, the package has a wishlist bug for Python 3 and also a CVE (which is bad). It might be worth checking with the package maintainer whether he still actively maintains it, and propose a migration to the DPMT Git. I'll contact him

Bug#826042: Spyder crashes on start

On 24/07/16 21:10, Jitse Niesen wrote: On 18/07/16 15:15, Ghislain Vaillant wrote: If you want to be helpful, please consider reviewing whether the current state of Debian unstable and check whether it contains all the necessary dependencies for the packaging of Spyder 3.x to happen. It's

Bug#826042: Spyder crashes on start

aging if you're interested. Thanks for the offer. I was hoping for something less time consuming :) but I will look into packaging Spyder for Debian if that's what it takes. Spyder is already packaged for Debian FYI. I believe Ghislain Vaillant (copied in) was thinking at some point to work on upda

Re: Comments regarding python-vispy_0.4.0-1_i386.changes

On 02/07/16 16:40, Chris Lamb wrote: please check vispy/util/svg/geometry.py (and maybe a few others, I stopped looking) /lamby This is covered by: Files: vispy/util/svg/* Copyright: 2013 Nicolas P. Rougier License: BSD-2-Clause All these files have the original copyright of the C++ library

Re: python-vispy_0.4.0-1_i386.changes REJECTED

On 17/06/16 12:59, Ghislain Vaillant wrote: Hi Chris, thanks for looking in my package. Please find my comments below: On 16/06/16 20:00, Chris Lamb wrote: please clarify twitter.js, Which file are you referring to? I have: find . -name *.js ./debian/missing-sources/bootstrap.js

Re: python-vispy_0.4.0-1_i386.changes REJECTED

Hi Chris, thanks for looking in my package. Please find my comments below: On 16/06/16 20:00, Chris Lamb wrote: please clarify twitter.js, Which file are you referring to? I have: >>> find . -name *.js ./debian/missing-sources/bootstrap.js ./debian/missing-sources/vispy.js

Re: hdf-compass_0.6.0b5-1_amd64.changes is NEW

Could you guys hold off the review upload. I still need to sort something out with the d-python team. Many thanks, Ghis Le 15 mai 2016 07:33, "Debian FTP Masters" a écrit : > binary:hdf-compass is NEW. > binary:python-hdf-compass is NEW. > source:hdf-compass is

Re: Comments regarding pyfr_1.3.0-1_amd64.changes

On 18/04/16 11:02, Chris Lamb wrote: Please check (at least) doc/ext/tikz.py Indeed, I missed that file (BSD-2-Clause). Double-checked the output of licensecheck and I could not find any other files that slipped under my radar. I'll update the packaging accordingly. Thanks for spotting this

Re: Comments regarding python-arrayfire_3.3.20160328-1_amd64.changes

Hi Chris, On 03/04/16 09:06, Chris Lamb wrote: Check examples/financial/heston_model.py etc for next upload please Thanks for spotting this. I forgot to scan for new files when rebasing the packaging on top of the latest release. Is that something I can address with a subsequent iteration of

Re: Regarding VTK 7.0.0

I will try to find some time to send an email around to the team this weekend. Cheers, Ghis On 23/02/16 14:28, Elvis Stansvik wrote: 2016-02-04 15:41 GMT+01:00 Ghislain Vaillant <ghisv...@gmail.com <mailto:ghisv...@gmail.com>>: It is next on my TODO list, I had a bunch of RCs

shark_3.0.1+ds1-1 ready for upload

On 10/02/16 16:13, Ghislain Vaillant wrote: On 05/02/16 23:00, Thorsten Alteholz wrote: Hi Ghislain, please mention the BSD license of doc/* in your debian/copyright. Thanks! Thorsten === Please feel free to respond to this email if you don't understand why your files were rejected

Re: shark_3.0.1+ds1-1_amd64.changes REJECTED

On 05/02/16 23:00, Thorsten Alteholz wrote: Hi Ghislain, please mention the BSD license of doc/* in your debian/copyright. Thanks! Thorsten === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our

Re: shark_3.0.1+ds1-1_amd64.changes REJECTED

On 05/02/16 23:00, Thorsten Alteholz wrote: Hi Ghislain, please mention the BSD license of doc/* in your debian/copyright. Thanks! Thorsten === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our

Re: Your nfft upload to unstable

On 07/02/16 18:13, Jonathan Wiltshire wrote: On 2016-02-07 17:47, Jonathan Wiltshire wrote: Hi, On 2016-02-03 you uploaded nfft 3.3.0-5 to unstable triggering a transition. The reverse dependencies are pynfft and yorick-ynfft. This is not an issue in itself, because that's quite a manageable

Re: Regarding VTK 7.0.0

It is next on my TODO list, I had a bunch of RCs to clear out before. I will soon be contacting the VTK 6 maintainers to coordinate our efforts towards VTK 7. Cheers, Ghis On 04/02/16 14:28, Anton Gladky wrote: Hi Elvis, we discussed it a couple of days ago with other people, interested in

Bug#742560: freeimage: diff for NMU version 3.17.0+ds1-1.1

I was about to submit an update for the reproducibility problem. I can prepare a proper update with your patch in it. How does that sound? Ghis On Fri, 22 Jan 2016 06:33:52 +0100 Tobias Frost wrote: Control: tags 742560 + patch Control: tags 742560 + pending Dear

Bug#742560: freeimage: diff for NMU version 3.17.0+ds1-1.1

;gl...@debian.org> wrote: Thanks, Tobias, for the patch and NMU. I have pushed your changes to ou git. Ghis, if you have a fixed reproducibility, please push it to git and I will upload a new version with both changes. Regards Anton 2016-01-25 14:57 GMT+01:00 Ghislain Vaillant <ghisv...@

Bug#742560: freeimage: diff for NMU version 3.17.0+ds1-1.1

://freeimage.sourceforge.net/download.html So how come that Fedora does not patch for libpng16 and we do? AFAIK, the main difference packaging-wise between Debian and Fedora is that we run the testsuite. Cheers, Ghis On 25/01/16 19:30, Tobias Frost wrote: Am Montag, den 25.01.2016, 17:58 + schrieb Ghislain

Bug#805678: pyoperators: FTBFS: NameError: global name 'FFTW_DEFAULT_NUM_THREADS' is not defined

Forwarded upstream. Thanks for reporting this issue. Ghis. -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers

Bug#808320: fails to upgrade from 'testing'

Hi Andreas, Thanks for reporting this bug. I am not quite sure what the appropriate course of action is here. My thinking was the following: libarrayfire-cpu-dev [3.0.2] shipped all CMake configuration files, since it was the only backend available at the time. With the recent inclusion

Bug#808320: Proposed fix with breaks / replaces

On 19/12/15 10:49, Ghislain Vaillant wrote: Hi Andreas, Thanks for reporting this bug. I am not quite sure what the appropriate course of action is here. My thinking was the following: libarrayfire-cpu-dev [3.0.2] shipped all CMake configuration files, since it was the only backend available

Bug#806379: opengm: FTBFS: test suite errors

> Those builds of opengm that got as far as running the test suite > nearly all encountered at least one failure. Some builds failed > earlier, due to errors I'll report separately. The only architecture > on which an automatic build fully succeeded was mips64el, not a > release architecture

  1   2   >