On Mon, Apr 1, 2019 at 11:09 AM Miro Hrončok <mhroncok(a)redhat.com> wrote:
> Dependency Checks
> -----------------
>
> Also, I've tried to run some repoqueries to determine which of our packages are
> leaf packages that could be retired eventually. However, running repoqueries on
> f29 against the rawhide repos crashed dnf for some reason ... so I can't
> automate that easily, yet.
>
> I've tried coming up with a repoquery call that lists all packages that
> (Build)Require some given argument package, which we could then use to prune the
> list of packages maintained by this SIG. Can somebody please sanity-check what I
> did here [2] and here [3]? It would be good if we had a "correct" version
of
> those dependency checks. PRs to fix/improve those scripts are very welcome.
The report lists apache-rat as leaf. That is in fact a leaf built package, but
the SRPM is not leaf, as apache-rat-plugin (a subpackage) is required.
I guess we need to check all subpackages to report something as leaf.
Also, some packages are not leafs, because they are only needed by siblings
(subpackages of the same SRPM), but those should be reported as leaf SRPMs.
FTR:
- I extended the leaf check for all built binary packages (it slightly
increases the run-time of the report generator script).
- I haven't implemented filtering out sibling-dependencies yet, though
- but it shouln't be too hard too add that in.
- The latest report at [0] already includes this change.
[0]:
https://decathorpe.fedorapeople.org/stewardship-sig.html
Fabio
> --
> Miro Hrončok
> --
> Phone: +420777974800
> IRC: mhroncok
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org