Description of problem: Currently EPEL 10 repository doesn't include the python-astropy package. It would be very useful if that package is included in the EPEL 10 repository.
I started poking at this, we have a number of deps to build first. Sergio - do you want to take this on? It might be nice to add @astro-sig to erfa which seems to be where I'm stuck at the moment. Not sure what version of astropy we can build for epel10 - I think perhaps we can do 7.X if we relax the numpy build dep.
(In reply to Orion Poplawski from comment #1) > I started poking at this, we have a number of deps to build first. Sergio - > do you want to take this on? It might be nice to add @astro-sig to erfa > which seems to be where I'm stuck at the moment. Not sure what version of > astropy we can build for epel10 - I think perhaps we can do 7.X if we relax > the numpy build dep. I have added erfa to @astro-sig and also I have added it to epel (although I'm confused with epel10 and epel10.0...). Im not very intereted in maintaning packages in epel, to be honest.
With 7.0.1: No matching package to install: 'python3dist(astropy-iers-data) >= 0.2025.1.31.12.41.4' No matching package to install: 'python3dist(pyerfa) >= 2.0.1.1' No matching package to install: 'python3dist(pytest-astropy) >= 0.10' No matching package to install: 'python3dist(pytest-astropy-header) >= 0.2.1' No matching package to install: 'python3dist(pytest-doctestplus) >= 0.12' Though honestly at this point I think we just using conda for stuff like this these days.
I would need this for my org and would be ready to help packaging the missing packages. I think the first to do is erfa which I saw Sergio tried to build but then deleted (?) in el10. I can then take a few on (pyerfa, pytest-astropy*, pytest-doctestplus*) for EPEL if you guys are fine with it! Sergio: EPEL from 10 (hope I don't write too many wrong details) will be forked at each minor. So you see 10.0, 10.1 etc albeit the branch is epel10. So no worries for that (of course when one needs to install it, one has to use proper repos)
Just wanted to share some progress I'm doing locally (we rebuild all internal/not yet upstream stuff with OBS at our org, but of course we'd prefer to upstream as much as possible so community can profit from packages): - erfa: builds with no problems whatsoever, so should be hopefully immediate to put to EPEL10 - pyerfa: the latest available (2.0.1.5) requires a newer Numpy than available (requires > 2, available in EPEL 1.26.4). For the time being I used 2.0.1.1 which is the last that is fine with that Numpy (and is also the Fedora40 one, which EPEL10 is based on). I am not sure there are plans to bump numpy or if we should pursue relaxing numpy requirement. As newer astropy don't require newer pyerfa, maybe we could stay at least for now on 2.0.1.1. - python-pytest-doctestplus and (dependency) python-pytest-remotedata can build in EPEL10 with no issues. - about the python3dist(pytest-astropy*) and python3dist(astropy-iers-data) mentioned above by Orion: it seems like is a circular dependency with astropy itself. So I guess you would first once do without tests and then add? I build finally astropy-iers-data (as needed below for 6.0.1). pytest-astropy-header builds with no problems, pytest-astropy has a few more deps which I did not build for the time being. - astropy itself if I disable tests (since they require the ones on line above) I can get 5.3.3 (started from this since it is Fedora 40 one, so assumed we should have all deps) built with no problems. Would be nice to have newer of course, but depends on dependencies mostly. - I tried then 7.0.1 and in that case I indeed get complaints: nothing provides requested (python3dist(numpy) < 3~~ with python3dist(numpy) >= 2). This comes from pyproject.toml in [build-system] requires. (while dependencies state >= 1.23.2) As reported by Orion above. - I tried then also 6.0.1 (what was in Fedora41) and that works fine (this requires astropy-iers-data also if you disable tests) So maybe we could go for 6.0.1 if we assume we cannot touch numpy? Or stay on 5.3.3 so we are in line with Fedora40 ? Or try to relax numpy requirement as Orion suggested above and see if all works? Hope this is of help! As stated before: if you could share the EPEL package maintainer status I'd gladly help to put this forward! Thanks! F.
FYI - This is the patch I'm using to relax the numpy build requirements for 7.0.1, which should be fine: diff -up astropy-7.0.1/pyproject.toml.deps astropy-7.0.1/pyproject.toml --- astropy-7.0.1/pyproject.toml.deps 2025-02-06 14:23:14.000000000 -0700 +++ astropy-7.0.1/pyproject.toml 2025-08-11 20:56:17.874054867 -0600 @@ -159,7 +159,7 @@ wcslint = "astropy.wcs.wcslint:main" requires = ["setuptools", "setuptools_scm>=6.2", "cython>=3.0.0, <4", - "numpy>=2.0.0, <3", + "numpy>=1.23.2, <3", "extension-helpers>=1,<2"] build-backend = "setuptools.build_meta" fedepell - I've added you to this package. Are you in the astro-sig? Joining that would get you access to more packages as well.
Thanks for the patch suggestion, will try asap locally and report! About astro-sig: I wanted to join but a few days ago I checked the link of the mailing list and was kinda dead :-o Is this the correct site to start from: https://fedoraproject.org/wiki/Category:Astronomy_SIG (and there https://lists.fedoraproject.org/mailman/listinfo/astronomy which leads to error) ?
(In reply to Orion Poplawski from comment #6) > FYI - This is the patch I'm using to relax the numpy build requirements for > 7.0.1, which should be fine: > diff -up astropy-7.0.1/pyproject.toml.deps astropy-7.0.1/pyproject.toml > --- astropy-7.0.1/pyproject.toml.deps 2025-02-06 14:23:14.000000000 -0700 With your patch I can build as well 7.0.1. I did a bit of testing (with our downstream packages using it) and seems fine, but will keep it of course under control. > fedepell - I've added you to this package. Are you in the astro-sig? > Joining that would get you access to more packages as well. Thanks for adding to python-astropy! Of course we should first add various deps before being able to submit this one to epel. Could you indicate in case who to ask / how to join astro-sig as the Fedora webpage seems outdated? Would be glad to contribute there since we use plenty of those packages Thanks!
Astro Sig Sponsors (https://accounts.fedoraproject.org/group/astro-sig/) mattia Mattia Verga sergiopr Sergio Pascual
Thanks Orion, was added to astro-sig, started packaging deps for EPEL10!
In case anyone following has time to test (and possibly +1) these are the first deps in the chain submitted: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-45b16043e4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-7a5b3cd96a Once these are through I will then go to next ones. Thanks!
@sergio.pasra : could we have also python-astropy-iers-data package in astro-sig as it is also a dependency? Thanks!
I'm using astropy since some time on our systems where I build all the dependencies with OBS first. Now slowly all dependencies should be also in EPEL and so I created this https://src.fedoraproject.org/rpms/python-astropy/pull-request/15 which basically just has Orion's relax of Numpy compared to Fedora42, which sounds good. Nevertheless I have a problem that is mocking me from some time: it is still complaining that python-astropy-iers-data is not there, albeit then Sergio did it I think (via packit) and to me it looks it should be available for various EPEL10_x (see: https://koji.fedoraproject.org/koji/packageinfo?packageID=40235) albeit it was probably done in a different way (not to EPEL10 but to specific branches) which maybe had some side effects (which I did not have on other dependencies where I did on EPEL10 and then it would move to 10_x as they spawn to life). @orion do you maybe have some hint on this or could reproduce? Is a pity we are a step from having maybe it in EPEL10 after quite some deps but still not!
(just for the record: I've had the doubt is the version matching, but also removing that doesn't help. So seems definitely it's how the dependent package was packed / updated seemingly)
Maybe I understood: it was built for 10_2 but never updated: https://bodhi.fedoraproject.org/updates/?packages=python-astropy-iers-data @sergio.pasra : could you maybe trigger an update also for 10.2?
This should possibly solve the problem: https://src.fedoraproject.org/rpms/python-astropy-iers-data/pull-request/79
@fedepell I have created the update https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-b2bece9328 and merged your PR
Thanks Sergio! I've checked the build and +1 it as it looks good! Let's see when it gets in stable if this solves the problem! Thanks!
With iers now in stable 10.2, I am able to do the scratch build locally! I've now kicked https://src.fedoraproject.org/rpms/python-astropy/pull-request/15# to do scratch build on Koji, but I'm hopeful that is now also there fixed and we should be ready! Please give a look to the MR (basically is only relaxing Numpy requirement as per Orion's suggestion and patch) and let's hope we have a first astropy in EL10 :) Thanks! F.
FEDORA-EPEL-2025-d302d6948c (python-astropy-7.0.1-2.el10_2) has been submitted as an update to Fedora EPEL 10.2. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-d302d6948c
Sergio - Could you add me and fedepell to pyerfa as admins or at least collaborators for epel* branches so we could request epel branches? Thanks!
FEDORA-EPEL-2025-d302d6948c has been pushed to the Fedora EPEL 10.2 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-d302d6948c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.