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

Hi, for arm64 the method I uploaded has seemed to work but for mips and s390x it ends up in ... ERRORS ERROR collecting debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/io/test_stata.py

python-bayespy 0.5.11-1 MIGRATED to testing

FYI: The status of the python-bayespy source package in Debian's testing distribution has changed. Previous version: 0.5.8-1 Current version: 0.5.11-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you

pyzo 4.4.3-1 MIGRATED to testing

FYI: The status of the pyzo source package in Debian's testing distribution has changed. Previous version: 4.4.1-1 Current version: 4.4.3-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive

p4est 1.1-5 MIGRATED to testing

FYI: The status of the p4est source package in Debian's testing distribution has changed. Previous version: 1.1-4 Current version: 1.1-5 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive

scilab-ann is marked for autoremoval from testing

scilab-ann 0.4.2.4-1 is marked for autoremoval from testing on 2017-11-08 It (build-)depends on packages with these RC bugs: 876733: jeuclid: Unclear licensing -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

sciscipy is marked for autoremoval from testing

sciscipy 1.0.1-2 is marked for autoremoval from testing on 2017-11-08 It (build-)depends on packages with these RC bugs: 876733: jeuclid: Unclear licensing -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

scilab-plotlib is marked for autoremoval from testing

scilab-plotlib 0.42-1 is marked for autoremoval from testing on 2017-11-08 It (build-)depends on packages with these RC bugs: 876733: jeuclid: Unclear licensing -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

scilab-celestlab is marked for autoremoval from testing

scilab-celestlab 3.0.0-1-2 is marked for autoremoval from testing on 2017-11-08 It (build-)depends on packages with these RC bugs: 876733: jeuclid: Unclear licensing -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org

Bug#878617: libspooles-dev: installs .pc/ files into a binary package

Package: libspooles-dev Version: 2.2-12+b1 Severity: normal Hi! I'm afraid your package installs some quilt droppings: /usr/include/spooles/.pc /usr/include/spooles/.pc/fix_FTBFS_timings.patch /usr/include/spooles/.pc/fix_FTBFS_timings.patch/timings.h Meow! -- System Information: Debian

Bug#878596: theano: FTBFS on big-endian systems - test_pooling_with_tensor_vars fails

Package: python-theano Version: 0.9.0+dfsg-1 Severity: serious Suspect the problem is theano/theano/tensor/signal/pool.py:650, which effectively does int32 = *(int64 *)(pointer_to_some_int_type) - if some_int_type is int32, that works on little-endian but not big-endian. --

Bug#878595: gazebo7: please update depends on fonts-liberation

Package: gazebo7 Version: 0.3.2.1-1 Severity: important user: qa.debian@packages.debian.org usertags: transitional Please update gazebo7's depends and depend on fonts-liberation instead of ttf-liberation, which will be going away next week (after being a transitional package since wheezy),

pandas_0.20.3-4_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 14 Oct 2017 19:49:01 +0200 Source: pandas Binary: python-pandas python3-pandas python-pandas-doc python-pandas-lib python3-pandas-lib Architecture: source Version: 0.20.3-4 Distribution: unstable Urgency: medium

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

Hi Yaroslav, thanks for those hints that somehow came to late since I just read it after I implemented some hopefully working solution. I just uploaded and we'll see what might happen. Every reader here is invited to fix it if not / enhance it if not happy. :-) Kind regards Andreas. On

Processing of pandas_0.20.3-4_source.changes

pandas_0.20.3-4_source.changes uploaded successfully to localhost along with the files: pandas_0.20.3-4.dsc pandas_0.20.3-4.debian.tar.xz pandas_0.20.3-4_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) -- debian-science-maintainers mailing

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

On Sat, 14 Oct 2017, Ghislain Vaillant wrote: > On 14/10/17 07:54, Andreas Tille wrote: > > On Fri, Oct 13, 2017 at 08:00:36PM +0200, Andreas Tille wrote: > > ... > > pandas_datareader: None > > usage: pytest.py [options] [file_or_dir] [file_or_dir] [...] > > pytest.py: error: unrecognized

silx_0.6.0+dfsg-1~bpo9+1_i386.changes REJECTED

python-silx-dbg-dbgsym_0.6.0+dfsg-1~bpo9+1_i386.deb: trying to install to backports-new, but could not find source binary:python-silx-dbg is NEW. binary:python-silx is NEW. binary:python3-silx-dbg is NEW. binary:python3-silx is NEW. === Please feel free to respond to this email if you don't

Processing of silx_0.6.0+dfsg-1~bpo9+1_i386.changes

silx_0.6.0+dfsg-1~bpo9+1_i386.changes uploaded successfully to localhost along with the files: python-silx-dbg-dbgsym_0.6.0+dfsg-1~bpo9+1_i386.deb python-silx-dbg_0.6.0+dfsg-1~bpo9+1_i386.deb python-silx-dbgsym_0.6.0+dfsg-1~bpo9+1_i386.deb python-silx_0.6.0+dfsg-1~bpo9+1_i386.deb

Bug#867370: marked as done (src:theano: Unnecessary python3-all-dev build-depends complicate transition)

Your message dated Sat, 14 Oct 2017 09:10:09 + with message-id and subject line Bug#867370: fixed in theano 0.9.0+dfsg-1 has caused the Debian Bug report #867370, regarding src:theano: Unnecessary python3-all-dev build-depends complicate transition to be

theano_0.9.0+dfsg-1_multi.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 30 Sep 2017 13:50:38 +0100 Source: theano Binary: python-theano python3-theano theano-doc Architecture: all amd64 source Version: 0.9.0+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Science

r-cran-isocodes_2017.09.27-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 14 Oct 2017 10:39:22 +0200 Source: r-cran-isocodes Binary: r-cran-isocodes Architecture: source Version: 2017.09.27-1 Distribution: unstable Urgency: medium Maintainer: Debian Science Team

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

Processing of r-cran-isocodes_2017.09.27-1_source.changes

r-cran-isocodes_2017.09.27-1_source.changes uploaded successfully to localhost along with the files: r-cran-isocodes_2017.09.27-1.dsc r-cran-isocodes_2017.09.27.orig.tar.gz r-cran-isocodes_2017.09.27-1.debian.tar.xz r-cran-isocodes_2017.09.27-1_amd64.buildinfo Greetings, Your

Processing of theano_0.9.0+dfsg-1_multi.changes

theano_0.9.0+dfsg-1_multi.changes uploaded successfully to localhost along with the files: theano_0.9.0+dfsg-1.dsc theano_0.9.0+dfsg.orig.tar.gz theano_0.9.0+dfsg-1.debian.tar.xz python-theano_0.9.0+dfsg-1_amd64.deb python3-theano_0.9.0+dfsg-1_amd64.deb theano-doc_0.9.0+dfsg-1_all.deb

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

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 think the proper > way would be to