Bug#849150: [Debian-science-sagemath] patch proposal

2017-07-23 Thread Ximin Luo
whoops, I forgot to CC Frédéric, the Debian BTS does not do this automatically. :( see my message below: Ximin Luo: > On Tue, 11 Jul 2017 13:24:02 +0200 Frédéric Bonnard > wrote: >> Tags: patch >> User: debian-powe...@lists.debian.org >> Usertags: ppc64el >> >> --

Processing of pybtex_0.21-1_amd64.changes

2017-07-23 Thread Debian FTP Masters
pybtex_0.21-1_amd64.changes uploaded successfully to localhost along with the files: pybtex_0.21-1.dsc pybtex_0.21.orig.tar.gz pybtex_0.21-1.debian.tar.xz pybtex_0.21-1_all.deb pybtex_0.21-1_amd64.buildinfo python-pybtex-doc_0.21-1_all.deb python-pybtex_0.21-1_all.deb

pybtex_0.21-1_amd64.changes is NEW

2017-07-23 Thread Debian FTP Masters
binary:python-pybtex is NEW. binary:python-pybtex-doc is NEW. binary:python3-pybtex is NEW. binary:python-pybtex-doc is NEW. binary:python3-pybtex is NEW. binary:python-pybtex is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The

Bug#849150: patch proposal

2017-07-23 Thread Ximin Luo
On Tue, 11 Jul 2017 13:24:02 +0200 Frédéric Bonnard wrote: > Tags: patch > User: debian-powe...@lists.debian.org > Usertags: ppc64el > > -- > > Hi, > it just seems that there's too many space taken by different libraries > in the static TLS space. I contacted some

Bug#868894: find_package option COMPONENTS ineffective because of hard-coded includes in TrilinosConfig.cmake

2017-07-23 Thread Nico Schlömer
Thanks, Joachim, for the report! This definitely sounds like an upstream bug. Would you mind reporting it on [1]? Together with the Trilinos devs, we'll be able to take it from there. That being said, at first glance the inclusion of the subpackage configs doesn't seem to override anything. I'd

Bug#869493: cld2 FTCBFS: runs tests despite DEB_BUILD_OPTIONS=nocheck

2017-07-23 Thread Helmut Grohne
Source: cld2 Version: 0.0.0-git20150806-5 Tags: patch User: helm...@debian.org Usertags: rebootstrap cld2 fails to cross build from source, because it fails running tests that should have been skipped due to DEB_BUILD_OPTIONS=nocheck. After honouring DEB_BUILD_OPTIONS=nocheck (see attached

cld2_0.0.0-git20150806-6_source.changes ACCEPTED into unstable

2017-07-23 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 23 Jul 2017 20:13:07 +0200 Source: cld2 Binary: libcld2-0 libcld2-dev Architecture: source Version: 0.0.0-git20150806-6 Distribution: unstable Urgency: medium Maintainer: Debian Science Team

Processing of cld2_0.0.0-git20150806-6_source.changes

2017-07-23 Thread Debian FTP Masters
cld2_0.0.0-git20150806-6_source.changes uploaded successfully to localhost along with the files: cld2_0.0.0-git20150806-6.dsc cld2_0.0.0-git20150806-6.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- debian-science-maintainers mailing list

sumo_0.30.0+dfsg1-1_source.changes ACCEPTED into unstable

2017-07-23 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 23 Jul 2017 16:19:12 +0200 Source: sumo Binary: sumo sumo-doc sumo-tools Architecture: source Version: 0.30.0+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

numba_0.34.0-2_multi.changes ACCEPTED into unstable

2017-07-23 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 23 Jul 2017 17:14:38 +0200 Source: numba Binary: python-numba python3-numba numba-doc Architecture: all source Version: 0.34.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers

libmatio_1.5.10-1_source.changes ACCEPTED into unstable

2017-07-23 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 23 Jul 2017 18:24:41 +0200 Source: libmatio Binary: libmatio-dev libmatio4 libmatio-doc Architecture: source Version: 1.5.10-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Team

Processing of sumo_0.30.0+dfsg1-1_source.changes

2017-07-23 Thread Debian FTP Masters
sumo_0.30.0+dfsg1-1_source.changes uploaded successfully to localhost along with the files: sumo_0.30.0+dfsg1-1.dsc sumo_0.30.0+dfsg1.orig.tar.xz sumo_0.30.0+dfsg1-1.debian.tar.xz sumo_0.30.0+dfsg1-1_source.buildinfo Greetings, Your Debian queue daemon (running on host

Processing of numba_0.34.0-2_multi.changes

2017-07-23 Thread Debian FTP Masters
numba_0.34.0-2_multi.changes uploaded successfully to localhost along with the files: numba_0.34.0-2.dsc numba_0.34.0.orig.tar.xz numba_0.34.0-2.debian.tar.xz numba-doc_0.34.0-2_all.deb Greetings, Your Debian queue daemon (running on host usper.debian.org) --

Bug#868873: dependence on libmumps-4.10.0 _AND_ libmumps-5.1.1 breaks make

2017-07-23 Thread Nico Schlömer
Hm, funny! I don't get how libtrilinos-amesos12 should depend on libmumps-4.10.0 when 5.1.1 is available. I've rebuild this on ubuntu artsy [1] and it selects all the right versions. Perhaps this got corrupted in the transition somehow? We've recently uploaded 12.10.1-4, perhaps this rebuild will

Processing of libmatio_1.5.10-1_source.changes

2017-07-23 Thread Debian FTP Masters
libmatio_1.5.10-1_source.changes uploaded successfully to localhost along with the files: libmatio_1.5.10-1.dsc libmatio_1.5.10.orig.tar.gz libmatio_1.5.10-1.debian.tar.xz libmatio_1.5.10-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) --

Bug#869493: marked as done (cld2 FTCBFS: runs tests despite DEB_BUILD_OPTIONS=nocheck)

2017-07-23 Thread Debian Bug Tracking System
Your message dated Sun, 23 Jul 2017 18:18:49 + with message-id and subject line Bug#869493: fixed in cld2 0.0.0-git20150806-6 has caused the Debian Bug report #869493, regarding cld2 FTCBFS: runs tests despite DEB_BUILD_OPTIONS=nocheck to be marked as

Bug#869536: numba: segfault on examples/mergesort.py

2017-07-23 Thread Daniel Stender
Package: numba Version: 0.34.0-2 Severity: important There's a segfault on /usr/share/doc/numba-doc/examples/mergesort.py, both, running on python2 and python3: $ ./mergesort.py ===Running mergesort Warmup unsorted [ 0.70995183

Processed: retitle 869536

2017-07-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 869536 numba: segfault on examples/mergesort.py [s390x] Bug #869536 [numba] numba: segfault on examples/mergesort.py Changed Bug title to 'numba: segfault on examples/mergesort.py [s390x]' from 'numba: segfault on examples/mergesort.py'.

Bug#869538: numba: use python-versioneer from the archive

2017-07-23 Thread Daniel Stender
Package: numba Severity: wishlist Control: block -1 by 766132 Once Versioneer becomes available, Numba should use that from the archive instead of the embedded versioneer.py. DS -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture:

Processed: numba: use python-versioneer from the archive

2017-07-23 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 766132 Bug #869538 [numba] numba: use python-versioneer from the archive 869538 was not blocked by any bugs. 869538 was not blocking any bugs. Added blocking bug(s) of 869538: 766132 -- 869538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869538

liggghts is marked for autoremoval from testing

2017-07-23 Thread Debian testing autoremoval watch
liggghts 3.7.0+repack1-1 is marked for autoremoval from testing on 2017-08-18 It (build-)depends on packages with these RC bugs: 867037: python-txaio: python-txaio FTBFS: test_chained_callback[asyncio] failed 867771: python-trollius: python-trollius FTBFS with python 3.6 as supported version

cg3 1.0.0~r12254-1 MIGRATED to testing

2017-07-23 Thread Debian testing watch
FYI: The status of the cg3 source package in Debian's testing distribution has changed. Previous version: 0.9.9~r11624-1 Current version: 1.0.0~r12254-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you

hkl is marked for autoremoval from testing

2017-07-23 Thread Debian testing autoremoval watch
hkl 5.0.0.2173-2 is marked for autoremoval from testing on 2017-08-28 It is affected by these RC bugs: 868481: hkl: hkl FTBFS with Bullet 2.86.1 -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

liggghts 3.7.0+repack1-1 MIGRATED to testing

2017-07-23 Thread Debian testing watch
FYI: The status of the liggghts source package in Debian's testing distribution has changed. Previous version: 3.5.0+repack1-10 Current version: 3.7.0+repack1-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a

seaborn is marked for autoremoval from testing

2017-07-23 Thread Debian testing autoremoval watch
seaborn 0.7.1-4 is marked for autoremoval from testing on 2017-08-30 It is affected by these RC bugs: 868616: seaborn: seaborn FTBFS: ImportError: No module named pytest -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

apertium-nno-nob is marked for autoremoval from testing

2017-07-23 Thread Debian testing autoremoval watch
apertium-nno-nob 1.1.0~r66076-1 is marked for autoremoval from testing on 2017-08-29 It (build-)depends on packages with these RC bugs: 868604: apertium-nno: apertium-nno FTBFS: Error: Position on line 6990 near `O inf)␊;␊#sjeldent i` - stand-alone o or O doesn't make sense - maybe you

sardana is marked for autoremoval from testing

2017-07-23 Thread Debian testing autoremoval watch
sardana 2.2.2-3 is marked for autoremoval from testing on 2017-08-28 It (build-)depends on packages with these RC bugs: 868481: hkl: hkl FTBFS with Bullet 2.86.1 -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

apertium-dan-nor is marked for autoremoval from testing

2017-07-23 Thread Debian testing autoremoval watch
apertium-dan-nor 1.3.0~r67099-1 is marked for autoremoval from testing on 2017-08-29 It (build-)depends on packages with these RC bugs: 868604: apertium-nno: apertium-nno FTBFS: Error: Position on line 6990 near `O inf)␊;␊#sjeldent i` - stand-alone o or O doesn't make sense - maybe you

esys-particle 2.3.5+dfsg1-1 MIGRATED to testing

2017-07-23 Thread Debian testing watch
FYI: The status of the esys-particle source package in Debian's testing distribution has changed. Previous version: 2.3.4+dfsg1-4 Current version: 2.3.5+dfsg1-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a

apertium-swe-nor is marked for autoremoval from testing

2017-07-23 Thread Debian testing autoremoval watch
apertium-swe-nor 0.2.0~r69544-1 is marked for autoremoval from testing on 2017-08-14 It is affected by these RC bugs: 868607: apertium-swe-nor: apertium-swe-nor FTBFS: Error: Position on line 6990 near `O inf)␊;␊#sjeldent i` - stand-alone o or O doesn't make sense - maybe you meant 0? It

apertium-nno is marked for autoremoval from testing

2017-07-23 Thread Debian testing autoremoval watch
apertium-nno 0.9.0~r69513-1 is marked for autoremoval from testing on 2017-08-29 It is affected by these RC bugs: 868604: apertium-nno: apertium-nno FTBFS: Error: Position on line 6990 near `O inf)␊;␊#sjeldent i` - stand-alone o or O doesn't make sense - maybe you meant 0? --

libgpuarray 0.6.8-1 MIGRATED to testing

2017-07-23 Thread Debian testing watch
FYI: The status of the libgpuarray source package in Debian's testing distribution has changed. Previous version: (not in testing) Current version: 0.6.8-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day

Bug#869537: numba should use python-six from the archive

2017-07-23 Thread Daniel Stender
Package: numba Severity: wishlist The current Numba packages run on the embedded numba/six.py, but instead python-six from the archive should be used. DS -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel:

apertium-hbs-mkd is marked for autoremoval from testing

2017-07-23 Thread Debian testing autoremoval watch
apertium-hbs-mkd 0.1.0~r57554-1 is marked for autoremoval from testing on 2017-08-14 It is affected by these RC bugs: 868608: apertium-hbs-mkd: apertium-hbs-mkd FTBFS: Error: Position on line 323 near `O A) (-1 BOS) (0 Gen` - stand-alone o or O doesn't make sense - maybe you meant 0? --

esys-particle is marked for autoremoval from testing

2017-07-23 Thread Debian testing autoremoval watch
esys-particle 2.3.5+dfsg1-1 is marked for autoremoval from testing on 2017-08-18 It (build-)depends on packages with these RC bugs: 867037: python-txaio: python-txaio FTBFS: test_chained_callback[asyncio] failed 867771: python-trollius: python-trollius FTBFS with python 3.6 as supported version

apertium-is-sv is marked for autoremoval from testing

2017-07-23 Thread Debian testing autoremoval watch
apertium-is-sv 0.1.0~r56030-1 is marked for autoremoval from testing on 2017-08-14 It is affected by these RC bugs: 868597: apertium-is-sv: apertium-is-sv FTBFS: Error: Position on line 129 near `O Prop + Ant + Fem) ` - stand-alone o or O doesn't make sense - maybe you meant 0? --

arduino-mk is marked for autoremoval from testing

2017-07-23 Thread Debian testing autoremoval watch
arduino-mk 1.5.2-1 is marked for autoremoval from testing on 2017-08-21 It (build-)depends on packages with these RC bugs: 859535: avr-libc: please drop the build-dependency on autoconf2.59 -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Bug#868873: dependence on libmumps-4.10.0 _AND_ libmumps-5.1.1 breaks make

2017-07-23 Thread Graham Inggs
On 23 July 2017 at 18:07, Nico Schlömer wrote: > Hm, funny! I don't get how libtrilinos-amesos12 should depend on > libmumps-4.10.0 when 5.1.1 is available. libtrilinos-amesos12/12.10.1-3 depends on libmumps-4.10.0 because libtrilinos_amesos.so.12 is linked to