A NethServer system is constituted by RPMs that come mainly from CentOS, EPEL and NethServer mirrors. Updates are announced by each project on its specific channel:
- NethServer https://github.com/NethServer/dev/issues?q=is%3Aissue+is%3Aclosed
- CentOS https://lists.centos.org/mailman/listinfo/centos-announce
- EPEL https://email@example.com/
A NethServer machine fetches:
- NethServer updates from an URL like:
- CentOS updates from an URL like:
- EPEL updates from an URL like:
$releasever is currently
All those packages updates improve the original system release by pushing it forward, like rolling continuously.
When CentOS produces a new minor version like 7.5.1804 they publish a new “minimal” ISO image. The NethServer developers add a small RPM set on that image together with a kickstart file. The resulting image is the NethServer ISO, with installer, server-manager and other stuff.
When NethServer 7.5.1804 is released, any existing 7.4.1708 installation can be upgraded seamlessly, because both CentOS and NethServer ensure compatibility between minor releases.
Locking to a specific distribution release¶
It is possible to lock to a specific distribution release, like
explained in the “Software center” section of the administrator’s manual.
The implementation is provided by the
nethserver-base package and is based
on the following elements: