Bug#918206: pandas: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#918206: pandas: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Sebastiaan Couwenberg
Source: pandas
Version: 0.23.3-1
Severity: normal
Control: block 917323 by -1

Dear Maintainer,

The autopkgtest for your package fail with python-numpy
(1:1.16.0~rc1-3), this increased the required age of python-numpy which
blocks the gdal transition.

Please fix the autopkgtest of your package.

Kind Regards,

Bas

Reply | Threaded
Open this post in threaded view
|

Bug#918206: pandas: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Graham Inggs-3
Control: severity -1 serious
Control: tags -1 + ftbfs

On Fri, 4 Jan 2019 at 12:30, Bas Couwenberg <[hidden email]> wrote:
> The autopkgtest for your package fail with python-numpy
> (1:1.16.0~rc1-3), this increased the required age of python-numpy which
> blocks the gdal transition.

The autopkgtest failure seems to have started on 2018-12-21 [1] after
the upload of matplotlib.

Anyway, pandas now FTBFS and needs to be made compatible with the new
python-numpy and matplotlib packages.


[1] https://ci.debian.net/packages/p/pandas/unstable/amd64/

Reply | Threaded
Open this post in threaded view
|

Bug#918206: Pandas new version

Rebecca N. Palmer-2
In reply to this post by Sebastiaan Couwenberg
Control: tags -1 fixed-upstream patch

The test failure is that np.array @ pd.DataFrame (matrix product) tries
to keep both the DataFrame's indices, which fails because the new matrix
is a different shape.

This appears to be fixed in 0.24.1 from PyPI, but as previously noted,
this is a new major version and hence risks breaking rdeps.

The relevant change appears to be setting __array_priority__:

https://github.com/brute4s99/pandas/commit/a01fa791eafe704ea85e2acc956ad9077e8e7542#diff-03b380f521c43cf003207b0711bac67f

but I haven't actually tried applying only that to 0.23.

Reply | Threaded
Open this post in threaded view
|

Bug#918206: Pandas

Andreas Tille-2
In reply to this post by Sebastiaan Couwenberg
Dear Rebecca,

On Wed, Feb 27, 2019 at 07:25:26AM +0000, Rebecca N. Palmer wrote:
> On 27/02/2019 07:00, Andreas Tille wrote:
> > Dear Rebecca,
> > I do not think that there is any
> > need for a separate branch.  Just stick to the debian branch.
>
> It's needed because the debian branch contains the attempt at packaging 0.24
> described earlier in this thread, which it's now too late for.

You are right.  Considering the branching jungle (Yaroslav, could you possibly
cleanup branches that are not used any more?) I'd prefer if you would move the
0.24 packaging to some separate branch (debian-experimental is covered but may
be debian-0.24 or something like this?) and keep branch debian for what we are
really releasing.

Thanks again for your work on this

        Andreas.

--
http://fam-tille.de

Reply | Threaded
Open this post in threaded view
|

Bug#918206: Pandas

Yaroslav Halchenko-9

On Wed, 27 Feb 2019, Andreas Tille wrote:

> Dear Rebecca,

> On Wed, Feb 27, 2019 at 07:25:26AM +0000, Rebecca N. Palmer wrote:
> > On 27/02/2019 07:00, Andreas Tille wrote:
> > > Dear Rebecca,
> > > I do not think that there is any
> > > need for a separate branch.  Just stick to the debian branch.

> > It's needed because the debian branch contains the attempt at packaging 0.24
> > described earlier in this thread, which it's now too late for.

> You are right.  Considering the branching jungle (Yaroslav, could you possibly

for someone jungle is a sweet sweet home! ;)

        $> git br -a | grep salsa | grep -e bf- -e enh- -e cythoned | while read b; do git push salsa :${b//*salsa\//}; done
        To salsa.debian.org:science-team/pandas.git
         - [deleted]             __tent/debian-cythoned-quilt
        To salsa.debian.org:science-team/pandas.git
         - [deleted]             bf-cython
        To salsa.debian.org:science-team/pandas.git
         - [deleted]             bf-i386
        To salsa.debian.org:science-team/pandas.git
         - [deleted]             bf-native-endianness
        To salsa.debian.org:science-team/pandas.git
         - [deleted]             bf-skips
        To salsa.debian.org:science-team/pandas.git
         - [deleted]             bf-unser
        To salsa.debian.org:science-team/pandas.git
         - [deleted]             bf-versions-etc
        To salsa.debian.org:science-team/pandas.git
         - [deleted]             enh-tests-compat-pytables-2.1

and will try to not forget to not push them again ;)

        $> git br -a | grep salsa # -- with my annotations
          remotes/salsa/master     -- some upstream's point of master -- could also be removed if you like
          remotes/salsa/releases   -- linear progression of upstream releases
          remotes/salsa/debian     -- sits on top of releases and carries packaging
          remotes/salsa/debian-experimental -- the one for uploads to experimental

better now?

> cleanup branches that are not used any more?) I'd prefer if you would move the
> 0.24 packaging to some separate branch (debian-experimental is covered but may
> be debian-0.24 or something like this?) and keep branch debian for what we are
> really releasing.

well "releasing" is a loaded term. I guess you are talking about uploading to
unstable so it manages to get into buster.  Since "debian" branch already got
its 0.24, what about starting debian-buster branch off debian/0.23.3-1 ?

otherwise -- I am ok to hard-reset and force push debian to the debian/0.23.3-1
state -- everyone should just beware of it, and then progress
debian-experimental to current state of debian (v0.24.1-972-g1cfbd07c7)

your call

> Thanks again for your work on this

yeap, Thank you Rebecca!

--
Yaroslav O. Halchenko
Center for Open Neuroscience     http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834                       Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik