On Fri, Sep 24, 2021 at 10:58 AM Miro Hrončok <mhroncok@xxxxxxxxxx> wrote:
> > Should it query for removed packages instead of components?
> >
> > It seem that when python-foo is retired, the script will attempt to remove
> > python-foo instead of python3-foo (and python3-foo-docs etc.).
> >
> > PS That's why I mentioned both options when answering your "how to find out
> > what has been retired" question. The solution is to stop using the source repos
> > (and src arch).
>
> Another idea: The script currently needs fedora-packager (for the pkgname
> command). If you use --qf=%{NAME} in the repoquery, it won't.
Yes, I've already created a small PR on those dependencies (another is
using `dnf repoquery` instead of `repoquery` that drops depencendy on
dnf-utils package).
And I agree that the script should use packages instead of source
packages - currently the results are really wild - a lot of packages
is suggested for removal without being actually retired.
But still I'd rather have this as part of distribution - a package
similar to fedora-obsolete-packages which would allow me to remove all
retired packages simply by installing it.
Oh there is already this proposal -
https://fedoraproject.org/wiki/Changes/Fedora-Retired-Packages
Marek Blaha
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
