On 14.10.20 19:32, Kevin Fenzi wrote:
> We now allow scls if:
>
> * They only need to be used at build time (ie, the rpms produced do not
> require users to install/enable any scls)
> * They are approved by the epel steering comittee.
>
> So far we have only enabled devtoolset. (so for
On Tue, Oct 13, 2020 at 12:14:24PM +0200, Leon Fauster wrote:
> Am 13.10.20 um 10:12 schrieb Christopher Engelhard:
> > On 12.10.20 10:49, Leon Fauster wrote:
> > > Not sure but IIRC EPEL should not depend on software collections ...?
> >
> > Can someone confirm that? If the package can't depend
On 13.10.20 12:14, Leon Fauster wrote:
> My recall was this
>
> https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/DBAQB3V35TXPNUV4UKKHXUC52BENZJUQ/
OK, thanks, that clears that up. So I'll go ahead and retire the EPEL7
package. Maybe I can put an updated
Am 13.10.20 um 10:12 schrieb Christopher Engelhard:
On 12.10.20 10:49, Leon Fauster wrote:
Not sure but IIRC EPEL should not depend on software collections ...?
Can someone confirm that? If the package can't depend on php7.2+, then
the question of how to deal with EPEL7 is moot.
My recall
On 12.10.20 10:49, Leon Fauster wrote:
> Not sure but IIRC EPEL should not depend on software collections ...?
Can someone confirm that? If the package can't depend on php7.2+, then
the question of how to deal with EPEL7 is moot.
Christopher
___
On 12.10.20 12:09, Petr Pisar wrote:
> RHEL releases a minor version every six months. And as I remember, EPEL8
> allows breaking upgrades at each new RHEL release. Thus technically, it's
> possible to rebase the package every year without getting into conflict with
> packaging guidelines. On the
Am 11.10.20 um 23:29 schrieb 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
On Sun, Oct 11, 2020 at 02:18:26PM +0200, Christopher Engelhard wrote:
> 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
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
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
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
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
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
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
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
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
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
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
18 matches
Mail list logo
