https://bugzilla.redhat.com/show_bug.cgi?id=2263999
--- Comment #21 from Sandro <gui1ty(a)penguinpee.nl> ---
Given that noarch packages will no longer be built on i686, I went ahead and
submitted PRs where needed. That means I only had to look into arched packages
directly or indirectly depending on pandas. Here's the current status:
### Packages with runtime dependency on pandas
- python-contextualbandits:
https://src.fedoraproject.org/rpms/python-contextualbandits/pull-request/3
### Packages with buildtime dependency on pandas
- arbor: already excludes i686
- cantera: already excludes i686
- pyproj:
https://src.fedoraproject.org/rpms/pyproj/pull-request/5
- python-mne: already excludes i686
- python-astropy:
https://src.fedoraproject.org/rpms/python-astropy/pull-request/10
- python-ephyviewer: already excludes i686
- python-fastavro: already excludes i686
- python-google-cloud-monitoring: no arched subpackages
- python-imbalanced-learn: no arched subpackages
- python-jsonpickle: no arched subpackages
- python-lsp-server: no arched subpackages
- python-mplcursors: no arched subpackages
- python-param: no arched subpackages
- python-plotly: no arched subpackages
- python-probeinterface: no arched subpackages
- python-pytest-arraydiff: no arched subpackages
- python-pytest-harvest: no arched subpackages
- python-pytest-steps: no arched subpackages
- python-rapidfuzz:
https://src.fedoraproject.org/rpms/python-rapidfuzz/pull-request/6
- python-sklearn-genetic-opt: no arched subpackages
- python-tabulate: no arched subpackages
- root:
https://src.fedoraproject.org/rpms/root/pull-request/5
- rpy:
https://src.fedoraproject.org/rpms/rpy/pull-request/1
- R-reticulate:
https://src.fedoraproject.org/rpms/R-reticulate/pull-request/1
- snakemake: no arched subpackages
- stats-collect: no arched subpackages
- BRed by wult, but that package is `ExclusiveArch x86_64`
### Non-trivial packages
- python-dask
- python-statsmodels
I hope I've got this right this time ...
Regarding the last category, non-trivial packages, those have circular
dependencies and/or multiple packages depending on them. I plan on treating
them the same way as pandas. In other words, determine the dependency tree for
those packages and take it from there. In fact, I've already ran the analysis.
The trees are much smaller than the tree for pandas. And the fact that noarch
is no longer affected by i686 builds should reduce the work required as well.
Packages listed in the pandas dependency tree, but not mentioned here, depend
in some way on the two non-trivial packages and will be dealt with when those
packages get sorted out.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2263999
Report this comment as SPAM:
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=rep...