https://bugzilla.redhat.com/show_bug.cgi?id=2263999
--- Comment #16 from Ben Beasley <code(a)musicinmybrain.net> ---
Unfortunately, I think there’s more than that, including arched packages with
noarch binary packages like python-dask, which build on every architecture, and
packages that have indirect dependencies on python-pandas via noarch packages.
I started with “fedrq wrsrc python-pandas.” (Usually wrsrc -s is nicer, but I
wanted to make sure to capture packages that only had runtime dependencies on
pandas.) The first entry is R-reticulate,
https://src.fedoraproject.org/rpms/R-reticulate/blob/rawhide/f/R-reticula....
It has no BuildArch/ExcludeArch/ExclusiveArch, so it’s a normal arched package
that builds everywhere, and it’s therefore affected. It has its own tree of
dependent packages: both R-rsconnect and R-sessioninfo depend on it.
/→ R-rsconnect → ???
R-reticulate <
\→ R-sessioninfo → ???
R-rsconnect and R-sessioninfo are noarch, so they are OK, but what if an arched
package depends on pandas indirectly *via* R-rsconnect? R-pkgdown depends on
R-rsconnect, but it is also noarch. R-devtools and R-lobstr depend on
R-pkgdown: R-devtools is noarch, but R-lobstr is not, so it is potentially
impacted. And the arched package R-dplyr depends on it. I’m using asterisks
below to mark noarch packages.
/→ *R-devtools* → ???
/→ *R-rsconnect* → *R-pkgdown* <
/ \→ R-lobstr → R-dplyr → ???
R-reticulate <
\→ R-sessioninfo → ???
Filling this out a little further in the same way:
/→ R-RMariaDB \ /→ *R-BiocFileCache* → *R-biomaRt*
/→
*R-DBItest*<→ R-RPostgres >→ *R-dbplyr* <
/→ <B> *R-devtools* → <
\→ R-odbc ----/ \→ (R-dplyr; see <A>)
/ \→
R-profvis → *R-ggplot2* → (15 dependent packages) → ???
/→ *R-rsconnect* → *R-pkgdown* <
/ \→ R-lobstr → <A> R-dplyr → (18
dependent packages) → ???
R-reticulate < /→ (*R-devtoools*; see <B>)
\ /→ R-pkgcache
\→ R-sessioninfo < /→ (*R-devtoools*; see <B>)
\→ *R-rcmdcheck* <
\→ *R-reprex* \→ *R-rhub* →
(*R-devtoools*; see <B>)
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.
--
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...