On 26. 01. 23 4:51, Yaakov Selkowitz wrote:
On Tue, 2023-01-24 at 15:55 +0100, Miro Hrončok wrote:
Based on the current fail to build from source policy, the following
packages
should be retired from Fedora 38 approximately one week before branching.
5 weekly reminders are required, hence the retirement will happen
approximately in 2 weeks, i.e. around 2023-02-08.
Since this is unfortunately after the branching,
packages will be retired on rawhide and f38.
Policy:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
Why isn't automatic orphaning at the beginning of this countdown part of this
policy, so that others have the chance to take and fix the package? If
someone (other than the maintainer, who should already be well aware) were to
just now notice that one of these packages were about to be retired, there
isn't really enough time to go through the BZ route to get it orphaned first.
That is a good question.
The original idea is that FTBFS packages are orphaned when the maintainers
don't respond to the FTBFS bugzillas. But many do set the bugzillas to ASSIGNED
to avoid the orphaning or sometimes the FTBFS bugzillas are closed in mistake
or not opened at all.
I suppose orphaning the packages first would make perfect sense, but the devil
is in the details. I suppose packagers might feel bad if suddenly "their"
packages are orphaned without any reminder or warning of some sort. So we would
need to modify the policy from:
1. warn
2. warn
3. warn
4. warn
5. warn
6. retire
To something like:
1. warn
2. warn
3. warn
4. orphan
5. warn
6. warn
7. warn
8. retire
And make the process much longer. And we would need to figure out what to do if
the package is taken (unorphaned) in between 4. and 8. without being fixed.
I am deliberately avoiding the option to modify the policy to:
1. warn
2. warn
3. warn
4. warn
5. warn
6. orphan
7. wait
8. wait
9. wait
10. wait
11. wait
12. retire via the orphan policy
Because folks will take the packages (and not fix them) between 6. and 12. --
it is often done by the previous maintainers (I don't really understand why) or
by new maintainers who take the package without realizing they have been
orphaned due to FTBFS.
free42 brouhaha
gtkhash nonamedotc
kguitar davidcornette
kjots kde-sig, thunderbirdtr
kmplayer moceap, rdieter
libmobi avsej
xml-security-c bruno, kloczek
PRs have been posted for these.
Thanks. Since this is all done by a human you can just give me a definitive lit
of package you want to maintain instead of letting them be retired and I can
assign them to you and let you merge the PRs instead of retiring them. That
offer stands for anybody.
However, note that I would very much prefer if you followed the nonresponsive
maintainer policy -- that way other packages might become available to
responsive maintainers.
--
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://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, report it: https://pagure.io/fedora-infrastructure/new_issue
