On Wed, 4 Apr 2018, 20:26 Adam Williamson, <adamwill@fedoraproject.org> wrote:

On Wed, 2018-04-04 at 11:15 +0100, James Hogarth wrote:
> On 4 April 2018 at 11:01, David Sommerseth <dazo@eurephia.org> wrote:
> > On 03/04/18 21:00, Christian Glombek wrote:
> > > I should probably add that the actual updater program has not been shipped in the rpms thus far. Although I'm not sure how this affects major updates, it is leading to problems elsewhere (i.e. people have to uninstall some apps on v13 and re-install them on v13.0.1 for them to work again).
> > >
> > > And how many people actually still run NC v10?
> >
> > I have two servers with NC v10 via EPEL 7 ... and getting increasingly concerned.
> >
>
> EPEL can't be updated

I think I used to just update it anyway. No-one shot me. :P
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org

Haha... you of all people know what steps I took and lengths I went through to safely update our owncloud users in EPEL when I took over maintenance from you ,)

The reason I said it can't be updated is that EL7 ships with PHP5.4 which has been dropped from support by both owncloud and nextcloud upstream... and they have no intention of changing that with SCL, RemiRepo and IUS as options for their users on their packages. 

But of course we can't use any of those for EPEL packages as per our own policies so it literally can't be updated... there's no choice but to retire it.