Re: Looking for a volunteer to automate the orphaned packages process
On Thu, 2023-10-19 at 18:43 +0200, Frantisek Zatloukal wrote:
> On Thu, Oct 19, 2023 at 6:24 PM Adam Williamson
> wrote:
>
> > I'm not sure I have time to take this, but glancing over it, I have a
> > suggestion on how to further automate the release stuff.
> >
> > You can use Bodhi release date to determine the extant EPEL releases
> > and the current Branched release. If you query
> > https://bodhi.fedoraproject.org/releases/ with content-type JSON, you
> > get a bunch of data on releases (paginated, so either handle the pages
> > or use https://bodhi.fedoraproject.org/releases/?rows_per_page=500
> > instead).
> >
> > To get all current EPEL releases you'd do something like this:
> >
> > epels = {int(rel['version']) for rel in releases if
> > rel['state'] == 'current' and rel['id_prefix'] ==
> > 'FEDORA-EPEL'}
> >
> > To find current Branched, you can do something like this:
> >
> > devrels = {int(rel['version']) for rel in releases if
> >rel['state'] == 'pending' and rel['id_prefix'] == 'FEDORA'}
> > if len(devrels) > 1:
> > branched = min(devrels)
> > else:
> > branched = None
> >
> > that logic should be safe as long as we don't change the release
> > process. There is always one "pending" Fedora release - Rawhide. If
> > there's more than one, there will be two, and the other one will be
> > Branched.
> >
>
> Or, the "lazier" to implement alternative for this would be
> https://packager-dashboard.fedoraproject.org/api/v1/releases :)
how/where is that data sourced?
if it's from fedfind, it ultimately relies on me manually updating a
JSON file, which isn't awesome. if it's from bodhi, great. :D
fedfind unfortunately can't use bodhi data because of the problem that
releases are marked stable too early in bodhi, but that shouldn't be a
problem for this script's use case.
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
https://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Looking for a volunteer to automate the orphaned packages process
On Thu, Oct 19, 2023 at 6:24 PM Adam Williamson
wrote:
> I'm not sure I have time to take this, but glancing over it, I have a
> suggestion on how to further automate the release stuff.
>
> You can use Bodhi release date to determine the extant EPEL releases
> and the current Branched release. If you query
> https://bodhi.fedoraproject.org/releases/ with content-type JSON, you
> get a bunch of data on releases (paginated, so either handle the pages
> or use https://bodhi.fedoraproject.org/releases/?rows_per_page=500
> instead).
>
> To get all current EPEL releases you'd do something like this:
>
> epels = {int(rel['version']) for rel in releases if
> rel['state'] == 'current' and rel['id_prefix'] ==
> 'FEDORA-EPEL'}
>
> To find current Branched, you can do something like this:
>
> devrels = {int(rel['version']) for rel in releases if
>rel['state'] == 'pending' and rel['id_prefix'] == 'FEDORA'}
> if len(devrels) > 1:
> branched = min(devrels)
> else:
> branched = None
>
> that logic should be safe as long as we don't change the release
> process. There is always one "pending" Fedora release - Rawhide. If
> there's more than one, there will be two, and the other one will be
> Branched.
>
Or, the "lazier" to implement alternative for this would be
https://packager-dashboard.fedoraproject.org/api/v1/releases :)
--
Best regards / S pozdravem,
František Zatloukal
Senior Quality Engineer
Red Hat
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Looking for a volunteer to automate the orphaned packages process
On Thu, 2023-10-19 at 11:06 +0200, Miro Hrončok wrote:
> Hello folks,
>
> you might know I run a script that generates
>
> https://churchyard.fedorapeople.org/orphans.txt
> https://churchyard.fedorapeople.org/orphans.json
>
> The script is located at
> https://pagure.io/releng/blob/main/f/scripts/find_unblocked_orphans.py
>
> I try to monitor the output and whenever it is stuck, I restart it.
>
> Every 2 weeks I try to save a copy of the generated file and send it to the
> devel list, devel announce list and the affected maintainers.
>
> Every branching, the script needs (trivial) changes.
>
> When I see packages orphaned for 6+ weeks, I retire them.
>
>
> I took this task a coupe years back because I was not satisfied with the
> status
> quo at that time (packages orphaned for year+ lingering in the distro).
>
> The task is semi-automated but not fully. After almost 5 years, I think it's
> time to pass this to somebody else. Preferably to somebody who would enjoy
> automating it entirely.
>
> I can provide all the details about the operation if you want to become the
> reaper's apprentice.
>
> Please do let me know. I believe this process is essential for the health of
> Fedora but I'd like to be relieved of this task.
I'm not sure I have time to take this, but glancing over it, I have a
suggestion on how to further automate the release stuff.
You can use Bodhi release date to determine the extant EPEL releases
and the current Branched release. If you query
https://bodhi.fedoraproject.org/releases/ with content-type JSON, you
get a bunch of data on releases (paginated, so either handle the pages
or use https://bodhi.fedoraproject.org/releases/?rows_per_page=500
instead).
To get all current EPEL releases you'd do something like this:
epels = {int(rel['version']) for rel in releases if
rel['state'] == 'current' and rel['id_prefix'] == 'FEDORA-EPEL'}
To find current Branched, you can do something like this:
devrels = {int(rel['version']) for rel in releases if
rel['state'] == 'pending' and rel['id_prefix'] == 'FEDORA'}
if len(devrels) > 1:
branched = min(devrels)
else:
branched = None
that logic should be safe as long as we don't change the release
process. There is always one "pending" Fedora release - Rawhide. If
there's more than one, there will be two, and the other one will be
Branched.
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
https://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Looking for a volunteer to automate the orphaned packages process
On Thu, Oct 19, 2023 at 11:06 AM Miro Hrončok wrote: > > Hello folks, > > you might know I run a script that generates > > https://churchyard.fedorapeople.org/orphans.txt > https://churchyard.fedorapeople.org/orphans.json > > The script is located at > https://pagure.io/releng/blob/main/f/scripts/find_unblocked_orphans.py > > I try to monitor the output and whenever it is stuck, I restart it. > > Every 2 weeks I try to save a copy of the generated file and send it to the > devel list, devel announce list and the affected maintainers. > > Every branching, the script needs (trivial) changes. > > When I see packages orphaned for 6+ weeks, I retire them. > > > I took this task a coupe years back because I was not satisfied with the > status > quo at that time (packages orphaned for year+ lingering in the distro). > > The task is semi-automated but not fully. After almost 5 years, I think it's > time to pass this to somebody else. Preferably to somebody who would enjoy > automating it entirely. > > I can provide all the details about the operation if you want to become the > reaper's apprentice. > > Please do let me know. I believe this process is essential for the health of > Fedora but I'd like to be relieved of this task. I think it might be possible to migrate this task to be a releng toddler? In that case there wouldn't even need to be a "volunteer" to run it, exactly :) For example, the recent implementation of the "SIG Policy" (which does some repoqueries and then modifies dist-git settings) isn't *that* different (it's just much less long-running), and it works fine as a toddler. Fabio ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Looking for a volunteer to automate the orphaned packages process
On Thu, 2023-10-19 at 11:06 +0200, Miro Hrončok wrote: > Hello folks, > > you might know I run a script that generates > > https://churchyard.fedorapeople.org/orphans.txt > https://churchyard.fedorapeople.org/orphans.json > > The script is located at > https://pagure.io/releng/blob/main/f/scripts/find_unblocked_orphans.py > > I try to monitor the output and whenever it is stuck, I restart it. > > Every 2 weeks I try to save a copy of the generated file and send it > to the > devel list, devel announce list and the affected maintainers. > > Every branching, the script needs (trivial) changes. > > When I see packages orphaned for 6+ weeks, I retire them. > > > I took this task a coupe years back because I was not satisfied with > the status > quo at that time (packages orphaned for year+ lingering in the > distro). > > The task is semi-automated but not fully. After almost 5 years, I > think it's > time to pass this to somebody else. Preferably to somebody who would > enjoy > automating it entirely. > > I can provide all the details about the operation if you want to > become the > reaper's apprentice. > yeah, as already mention, I think sometimes is reaped too much, but the results, at the end of the day, are good, we have a better Fedora. I know the balance is extremely difficult and needs lots of work. I have some commits to improve find_unblocked_orphans.py (not yet completely finished ) , the feature that I'd like implement is query more than one repo , will be useful to query el + epel for example and some optimizations IIRC. > Please do let me know. I believe this process is essential for the > health of > Fedora but I'd like to be relieved of this task. > > -- > Miro Hrončok > -- > Phone: +420777974800 > IRC: mhroncok > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue -- Sérgio M. B. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Looking for a volunteer to automate the orphaned packages process
2023-10-19T09:06:53Z Miro Hrončok : you might know I run a script that generates https://churchyard.fedorapeople.org/orphans.txt https://churchyard.fedorapeople.org/orphans.json The script is located at https://pagure.io/releng/blob/main/f/scripts/find_unblocked_orphans.py I try to monitor the output and whenever it is stuck, I restart it. Every 2 weeks I try to save a copy of the generated file and send it to the devel list, devel announce list and the affected maintainers. Every branching, the script needs (trivial) changes. When I see packages orphaned for 6+ weeks, I retire them. I took this task a coupe years back because I was not satisfied with the status quo at that time (packages orphaned for year+ lingering in the distro). The task is semi-automated but not fully. After almost 5 years, I think it's time to pass this to somebody else. Preferably to somebody who would enjoy automating it entirely. I can provide all the details about the operation if you want to become the reaper's apprentice. Please do let me know. I believe this process is essential for the health of Fedora but I'd like to be relieved of this task. Hi Miro, Thanks for all of your work on the orphaned package process and related processes up until now. I agree that making sure that packages in the distro are maintained is crucial. This task interests me and is similar to previous work I've done in the Go ecosystem, but I'm not sure I'm up for additional responsibilities right now, at least not before EOY. Best, Maxwell -- Maxwell G (@gotmax23) Pronouns: He/They ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Looking for a volunteer to automate the orphaned packages process
On 19-10-2023 11:06, Miro Hrončok wrote: I can provide all the details about the operation if you want to become the reaper's apprentice. A reaper by the name of Churchyard! ⚰️ ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
