On Thu, Nov 14, 2019 at 3:17 PM Miro Hrončok <mhroncok(a)redhat.com> wrote:
On 06. 11. 19 8:29, Miro Hrončok wrote:
> M2.
>
> For traditional packages, it was consistent and easy to find package
> dependencies in Fedora. For a proven packager, Fedora Packaging Committee member
> or generally for anybody doing a System Wide Change, being able to run queries
> like:
>
> $ repoquery --repo=rawhide --whatrequires 'libpython3.8.so.1.0()(64bit)'
>
> is trivial. Arguably, there are some quirks already (for example it doesn't
> properly work with boolean (rich?) deps).
>
> Witch modules, I still don't remember how to do this, but I know it requires
> more than 1 easy repoquery over rawhide.
This is also currently complicated by the fact that when Fedora N branches, the
modules are not there on Fedora N+1 until they are rebuilt.
Until they are *successfully* rebuilt, specifically. We do a
mass-rebuild for Fedora N+1 when Fedora N branches from Rawhide. If a
module (such as scala, right now) fails to build successfully at the
Branched mass-rebuild, it doesn't appear in the Rawhide composes. This
*should* be a quick way to notice things are not working, but scala
has been broken for a while now.