Le dim. 11 oct. 2020 à 07:47, Christopher Engelhard <ce(a)lcts.de> a écrit :
Hi,
the nextcloud server package is currently stuck at ancient version 10
(current is 20) in EPEL7 (It's not (yet) available EPEL8 repos).
I'd like to fix that, but
- upstream releases a new version roughly every 4 months
- they support them only for roughly 1 year (officially it's "at least 8
months")
- nextcloud receives A LOT of bug- and CVE-fixes, and there is no way
I'll be able to backport all of those, so staying on an older version
after upstream stopped support is not really an option.
So, should this still be in EPEL even though it would receive major
version updates or is it better to retire it from EPEL?
I suspect that EPEL users would probably prefer to run it from
upstream's containers anyways, so retiring might make more sense, but
I'm open either way.
I'm fine with retiring it.
But on the alternatives , you can have modules (or application
streams) for both epel and fedora.
It would be a good way forward. so it won't enforce nextcloud version
with a given fedora and or epel and would allow to update nextcloud at
users own pace.
But as epel7 is concerned, I'm good for retirement.