On 05. 08. 19 12:07, Hans de Goede wrote:
Hi all,
On 05-08-19 11:52, 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 report at
https://churchyard.fedorapeople.org/orphans-2019-08-05.txt
> Grep ti for your FAS username and follow the dependency chain.
Miro, thank you for generating these reports.
In the extended version:
https://churchyard.fedorapeople.org/orphans-2019-08-05.txt
I see that javapackages-tools is still on the list (because it depends on gradle)
and that in turn brings problems for lot of other packages.
So I wonder what the plan forward is. I've been looking at my own packages
which depend on javapackages-tools and they really only need 2 things:
1) javapackages-filesystem
2) %jpackage_script macro (and it deps)
Looking at:
https://fedoraproject.org/wiki/Packaging:Java this is pretty much
the minimum set of what packages need to follow the guidelines. It seems that
javapackages-tools contains way more then this and I'm wondering if it would
be a good idea to do a javapackages-tools-minimal as a separate package and
move the 2 items from above there. Then over time we can move java-packages
in the base package set to use javapackages-tools-minimal and eventually drop
the full javapackages-tools from the base package set.
In the mean time I guess we need to fix the gradle problem to fix all these
broken dependency chains for F31, I guess ideally by dropping the gradle dep if
possible...
Miro, it seems that the full report is still not picking up all the
additional
problems caused by javapackage-tools also being the sole provider of\
javapackages-filesystem ?
Unfortunately, I won't be able to fix this any time soon.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok