Bug 1197364 - [RFE:EPEL] Request to add python-astropy to EPEL 7
Summary: [RFE:EPEL] Request to add python-astropy to EPEL 7
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: python-astropy
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1229615
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-28 18:52 UTC by Bryce Nordgren
Modified: 2015-09-19 22:40 UTC (History)
2 users (show)

Fixed In Version: python-astropy-1.0.3-4.el7.1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-19 22:40:22 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Bryce Nordgren 2015-02-28 18:52:08 UTC
Would you consider producing an EPEL 7 build of Astropy? 

Either way, thanks for the time you invested in packaging this software for Fedora! Much appreciated!

Comment 1 Sergio Pascual 2015-03-12 14:44:11 UTC
I have mixed feelings about this. 

On one hand, astropy 1.0 is a LTS release, with two years of bugfixes. 

On the other hand, RHEL has ~10 years of support. 

So either releases after 1.0 are backwards compatible and can be updated or EPEL7 will have an outdated and useless version of astropy for 8 years.

So, unless epel provides a way to update packages I'm not interested.

Perhaps a copr is a good solution if the dependecnies (erfa, cfitsio, etc) are the same in epel7 and in astropy


Of course, if you are already a maintainer, we can maintain an epel7 branch

Comment 2 Orion Poplawski 2015-05-13 20:16:06 UTC
I think it's worth a try.  I've requested a branch in pkgdb.

Comment 3 Sergio Pascual 2015-05-21 09:21:54 UTC
Orion, do I need to do something to move this forward? 

In the pkgdb page I can see "Fedora EPEL 7 Awaiting Review", but, who is supposed to review this?

Comment 4 Orion Poplawski 2015-05-21 16:55:29 UTC
You.  But since you didn't respond in a week, the request was processed anyway :).

I'm now hitting:

DEBUG util.py:388:  Error: No Package found for wcslib-devel >= 4.25

could you update wcslib in epel7?  Thanks!

Comment 5 Orion Poplawski 2015-06-25 15:57:32 UTC
Sergio - On EPEL7 I had to not apply the python-astropy-system-six.patch patch.  EPEL7 has python-six 1.3.0 which is not new enough, and I got:

+ /usr/bin/python2 setup.py build --offline
Traceback (most recent call last):
  File "setup.py", line 18, in <module>
    import astropy
  File "/builddir/build/BUILD/astropy-1.0.3/astropy/__init__.py", line 76, in <module>
    from . import config as _config
  File "/builddir/build/BUILD/astropy-1.0.3/astropy/config/__init__.py", line 12, in <module>
    from .configuration import *
  File "/builddir/build/BUILD/astropy-1.0.3/astropy/config/configuration.py", line 28, in <module>
    from ..utils.exceptions import AstropyWarning, AstropyDeprecationWarning
  File "/builddir/build/BUILD/astropy-1.0.3/astropy/utils/__init__.py", line 18, in <module>
    from .misc import *
  File "/builddir/build/BUILD/astropy-1.0.3/astropy/utils/misc.py", line 24, in <module>
    from ..extern.six.moves import urllib
ImportError: cannot import name urllib

This may be temporary as it appears that python-six-1.9.0 will be coming to RHEL7.2: https://bugzilla.redhat.com/show_bug.cgi?id=1185409

Now I'm getting some failing tests which I need to look at.

Comment 6 Orion Poplawski 2015-06-29 22:09:43 UTC
Okay, test issues fixed and reported here: https://github.com/astropy/astropy/pull/3900


Note You need to log in before you can comment on or make changes to this bug.