Epel repo doesn’t have minor version (7.7.1908), only major release (7), so now it is pointing to the latest 7 version (7.9.2009) and that is causing the problem with dependencies.
Recently I upgraded two servers from 7.6.1810 to 7.9.2009 following @davidep’s advice:
But before proceeding, you might want to update nextcloud 17 to 18 then to 19 as updates skipping major releases are not supported.
# update to nextcloud 18.0.4
yum install http://packages.nethserver.org/nethserver/7.8.2003/updates/x86_64/Packages/nethserver-nextcloud-1.10.1-1.ns7.noarch.rpm
#update to nextcloud 19.0.3
yum install http://packages.nethserver.org/nethserver/7.8.2003/updates/x86_64/Packages/nethserver-nextcloud-1.14.2-1.ns7.noarch.rpm
If it warns about dependency problems like before (from epel repo), try disabling epel repo at runtime (i.e. yum --disablerepo=epel update yourpackages ).
After that, you could proceed with:
# Upgrades across multiple versions is not a tested procedure.
yum install -y http://mirror.nethserver.org/nethserver/nethserver-release-7.rpm
signal-event software-repos-save
yum update
If doing the updates remotely (ssh…) it is advisable to use a screen/tmux session (for instance, to prevent errors produced in case of dropped connection causing unfinished yum transactions.)