On Mon, Jul 29, 2019, 16:40 Miro Hrončok <mhroncok@xxxxxxxxxx> wrote:
On 29. 07. 19 16:35, Hans de Goede wrote:
> Hi,
>
> On 29-07-19 12:37, Miro Hrončok wrote:
>> The following packages are orphaned and will be retired when they
>> are orphaned for six weeks, unless someone adopts them. If you know for sure
>> that the package should be retired, please do so now with a proper reason:
>> https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
>>
>> Note: If you received this mail directly you (co)maintain one of the affected
>> packages or a package that depends on one. Please adopt the affected package or
>> retire your depending package to avoid broken dependencies, otherwise your
>> package will be retired when the affected package gets retired.
>>
>> See the full report: https://churchyard.fedorapeople.org/orphans-2019-07-28.txt
>> Grep it for your FAS username and follow the dependencies.
>
> I'm confused, a whole bunch of the packages being orphaned here seem to be
> due to jpackage-utils / javapackages-tools I thought that these had been
> picked-up by some SIG until the whole discussion about main-repo packages
> (build)requiring on modular ones was done?
Nope, not those. Those are **new** problematic packages. The SIG can take them
and then take more and more. Until it cracks.
The Stewardship SIG is already "maintaining" over 200 Java packages (for now). I've been working on dropping optional features and modules to reduce the number of required packages - before we determine which of these 500 orphans are actually needed for stuff to continue to work.
And, as Miro pointed out, we just *can't* adopt everything. There are 1.5 people submitting packaging changes, and ~3 people doing PR reviews. Nobody should expect 2-3 people to maintain 800 packages, where almost none of us had prior experience with Java packaging.
On top of that, most of these packages haven't been touched in years, so they're pretty broken in many cases (they've been orphaned because of several non-responsive maintainer procedures, after all).
As far as I can tell, that leaves 2-3 active Java maintainers in fedora (primarily pushing things to modules), and 2-3 active Stewardship SIG members, trying to play catch-up and FTBFS whack-a-mole in non-modular branches.
That said, any help people can offer (be it PR submissions, reviews, or maintenance of "ursine" packages as member of the SIG) is of course welcome, until the whole modular-non-modular mess is resolved somehow.
Fabio
--
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
_______________________________________________ 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
