https://bugzilla.redhat.com/show_bug.cgi?id=2263999
--- Comment #19 from Sandro <gui1ty(a)penguinpee.nl> ---
Created attachment 2017692
-->
https://bugzilla.redhat.com/attachment.cgi?id=2017692&action=edit
Leaf status dependency tree of python-pandas
Now that I've been doing a bit more digging and poking, I hopefully have a more
complete picture of the state of affairs.
(In reply to Ben Beasley from comment #16)
Ok, now that I’ve drawn part of a scary graph that seems like it’s
going to
consume most of the R ecosystem, I’ll point out that Pandas is only a test
dependency for R-reticulate, and we should be able to cut off this entire
tree at the root by conditionalizing the BuildRequires there on architecture
and skipping some or all tests on i686. But the above is still a good
example of how each directly-dependent package needs to be considered
individually, and how indirectly-dependent packages are important too.
Regarding above, I've learned that packages, for which only the source package
dependents on the package being investigated, this is an indicator that no
further examination of (child) dependencies is required.
To make that more concrete:
`fedrq wrsrc python-pandas` lists `R-reticulate`, however, `fedrq subpkgs
R-reticulate | fedrq pkgs -F requires | grep pandas` will return no results.
Thus, python-pandas is indeed only a BR for R-reticulate and we don't need to
examine the sub tree rooted at R-reticulate.
With that and some other lessons learned, I know have a complete[1] tree (to
the points where we can stop investigating). It's a rather large tree (see
attachment). Summing up the results, we have:
- 34 leaf package already excluding i686
- 33 leaf packages not yet excluding i686
- of those, only two are arched packages (or depending on arched packages)
- python3-spyking-circus.noarch (depends on python3-statsmodels.x86_64)
- python3-contextualbandits.x86_64
- 47 packages that BR python-pandas
- of those, we only need to consider packages that have arched sub packages
- python-elephant
- python-astropy
- pyproj
- cantera
- python-mne
- root
- arbor
- rpy
- R-reticulate
- pyproj
- python-fastavro
- python-rapidfuzz
- python-dask
[1] While I believe the tree is complete, it does contain duplicates, which I
didn't filter. E.g.: arbor BRs python3-pandas, yet arbor also BRs
python3-seaborn, which itself has a runtime requirement on python3-pandas. Thus
arbor is listed twice.
--
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...