[EPEL-devel] Re: Fast-moving packages in EPEL

2020-10-11 Thread Christopher Engelhard
On 11.10.20 23:29, Nick Howitt wrote: > How do you intend to handle the switch to PHP7.3? Not sure yet - I wanted to make sure it even makes sense to keep nextcloud in EPEL7 first. But that's another reason it's probably risky to jump people from NC10 to NC18+ (NC13 was the last release to

[EPEL-devel] Fedora EPEL 6 updates-testing report

2020-10-11 Thread updates
The following Fedora EPEL 6 Security updates need testing: Age URL 9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-f853880b07 prosody-0.11.7-1.el6 The following builds have been pushed to Fedora EPEL 6 updates-testing kyotocabinet-1.2.78-1.el6 Details about builds:

[EPEL-devel] Fedora EPEL 7 updates-testing report

2020-10-11 Thread updates
The following Fedora EPEL 7 Security updates need testing: Age URL 12 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-98b234afda libuv-1.40.0-1.el7 9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-bd6a96cd24 python34-3.4.10-7.el7 9

[EPEL-devel] Fedora EPEL 8 updates-testing report

2020-10-11 Thread updates
The following Fedora EPEL 8 Security updates need testing: Age URL 9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-0f2bfced63 prosody-0.11.7-1.el8 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-b15161810d pdns-4.3.1-1.el8 The following builds have been

[EPEL-devel] Re: Fast-moving packages in EPEL

2020-10-11 Thread Nick Howitt
On 11/10/2020 18:22, Christopher Engelhard wrote: On 11.10.20 15:10, H wrote: I'd like it updated, and kept updated, for EPEL 7. Do you happen to have a system with the current 10.0.something EPEL7 package set up & would you be willing to - if I make an updated package - test the upgrade

[EPEL-devel] Re: Fast-moving packages in EPEL

2020-10-11 Thread Christopher Engelhard
On 11.10.20 15:10, H wrote: > I'd like it updated, and kept updated, for EPEL 7. Do you happen to have a system with the current 10.0.something EPEL7 package set up & would you be willing to - if I make an updated package - test the upgrade process? I could set up something myself, but I think

[EPEL-devel] Re: Fast-moving packages in EPEL

2020-10-11 Thread Kevin Fenzi
On Sun, Oct 11, 2020 at 07:47:22AM +0200, Christopher Engelhard wrote: > 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

[EPEL-devel] Re: Fast-moving packages in EPEL

2020-10-11 Thread Matthew Miller
On Sun, Oct 11, 2020 at 02:05:20PM +0200, Christopher Engelhard wrote: > I'm sort of hesitant to dive into learning how modularity works, though > ... although, maybe a good opportunity to learn. The spin-up is a little rougher than we'd hoped, but once you've got it set up it shouldn't be too

[EPEL-devel] Re: Fast-moving packages in EPEL

2020-10-11 Thread H
On October 11, 2020 7:57:45 AM EDT, Nicolas Chauvet wrote: >Le dim. 11 oct. 2020 à 07:47, Christopher Engelhard 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

[EPEL-devel] Re: Fast-moving packages in EPEL

2020-10-11 Thread Nick Howitt
The version check can be disabled in NC: diff -Naur -b nextcloud/lib/private/Updater.php nextcloud.njh/lib/private/Updater.php --- nextcloud/lib/private/Updater.php 2019-04-08 15:22:33.0 -0600 +++ nextcloud.tjr/lib/private/Updater.php 2019-05-20 12:48:46.007165729 -0600 @@ -188,14

[EPEL-devel] Re: Fast-moving packages in EPEL

2020-10-11 Thread Christopher Engelhard
One thing I forgot that makes things even worse: - upstream does not support updates across more than one major version, so anybody who actually has the old v10 installed will have their installation completely broken by ANY update at this point - for the same reason, trying to limit major

[EPEL-devel] Re: Fast-moving packages in EPEL

2020-10-11 Thread Christopher Engelhard
On 11.10.20 13:57, Nicolas Chauvet wrote: > 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

[EPEL-devel] Retiring blender for epel7

2020-10-11 Thread Nicolas Chauvet
Hi, Same as in nextcloud, I'm proposing to retire blender from epel7. The packaged version if still working is very old and unmaintained. (there are lots of unfixed CVE). Having a full featured and modern blender there looks out of reach. Thanks. -- - Nicolas (kwizart)

[EPEL-devel] Re: Fast-moving packages in EPEL

2020-10-11 Thread Nicolas Chauvet
Le dim. 11 oct. 2020 à 07:47, Christopher Engelhard 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

[EPEL-devel] Re: Proposing an EPEL packaging SIG

2020-10-11 Thread Christoph Karl
Hello Alexandre! On 11.09.20 20:52, Michel Alexandre Salim wrote: The rationale is that many Fedora packagers do not specifically care about EL, and with their long release cycles the maintenance burden is higher (e.g. upgrading to fix a security vulnerability might not be possible if the newer