Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#41239 - [python2-pandas] revert to 0.14.0?

Attached to Project: Community Packages
Opened by Ted To (zoof) - Thursday, 17 July 2014, 18:38 GMT
Last edited by Andrzej Giniewicz (Giniu) - Saturday, 02 August 2014, 15:10 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Andrzej Giniewicz (Giniu)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

There is a pretty serious bug with 0.14.1:

https://github.com/pydata/pandas/issues/7746

It may be worth reverting to the prior version.

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Andrzej Giniewicz (Giniu)
Saturday, 02 August 2014, 15:10 GMT
Reason for closing:  Upstream
Additional comments about closing:  I don't think patching or rolling back a release is good solution. If you really need to rollback a release, there are solutions like Arch Rollback Machine. Also, if someone finds this bug important, he can switch to python-pandas-git where this bug is already fixed.

Please reopen if you think otherwise. Thanks.
Comment by Andrzej Giniewicz (Giniu) - Friday, 18 July 2014, 08:35 GMT
Thanks for report. I will investigate it and decide about potential revert this week.
Comment by Andrzej Giniewicz (Giniu) - Thursday, 24 July 2014, 18:27 GMT
I looked at it and I don't think that revert is good thing to do in this case. Reverting packages introduces epoch to package, so it should be avoided.

I think that bugfix release will come soon if this bug turns out to be such bad - if not, can you try python2-pandas-git or python-pandas-git? It should have this bug fixed already.

If such solution does not suit you, we might consider backporting the fix to 0.14.1 by including patch, but then if porting this issue, why not port others - and package can quickly turn into patchwork.

I will think what to do with it a little more. In the meanwhile, I would appreciate if you can check if git version works for you.

Loading...