Re: [stewardship-sig] Stewardship SIG: Initial report and plans for the future

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 29. 03. 19 22:25, Fabio Valentini wrote:
Hi everybody,

It looks like the first round of orphans has been taken in by our SIG - this
seemed to be a good time to do inventory and think about how to proceed.

Still missing:

stewardship-sig: apache-logging-parent, woodstox-core, apache-commons-csv, log4j, tagsoup, jeromq, maven-file-management

I've requested tagsoup in https://pagure.io/releng/issue/8251

Status Report
-------------

First of all, I've written a small script [0] that produces a simple HTML page
of the current status of the stewardship-SIG packager group. Pull Requests to
improve the report are welcome.

The current status is available at [1]. I will try to update that page
regularly.

Nice!

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.

I always go with (only use one repo if you want only that kind of info:

 $ dnf repoquery --repo=rawhide --repo=rawhide-source --whatrequires xxx

Alternatively, this gives source packages that require on runtime:

 $ dnf repoquery --repo=rawhide --source --whatrequires xxx

(You need fedora-repos-rawhide installed.)

Pagure Project
--------------

Since I'm already talking about Pull Requests, I've created a pagure project [4]
for our group, where we can have a ticketing system (for example, where change
of ownership for packages or retirement of leaf packages can be tracked), and
a collection of shared scripts and tools which can automate some of our
recurring tasks. The three scripts I mentioned will be moved there, as well.

First ticket: https://www.pagure.io/stewardship-sig/issue/1

[0]: https://github.com/decathorpe/miscripts/blob/master/stewardship-sig-report.py
[1]: https://decathorpe.fedorapeople.org/stewardship-sig.html
[2]: https://github.com/decathorpe/miscripts/blob/master/whatrequires.sh
[3]: https://github.com/decathorpe/miscripts/blob/master/whatbuildrequires.sh
[4]: https://www.pagure.io/stewardship-sig

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux