runit-services (0.8.2) unstable; urgency=medium

    During the Trixie development cycle, the path where elogind is installed changed
    in a non backward compatible way and the elogind service in this package was updated
    accordingly.
    In order to avoid issues related to elogind failure (see #1069075, #1095025), the
    elogind's run file in /etc/sv/elogind/, if any, is being forced-upgraded to a version
    with the right path. A backup of the run file is available as /etc/sv/elogind/run.pkgbk.
    If you have local changes in elogind's run file you can merge changes manually; otherwise
    the backup file can be removed.

 -- Lorenzo Puliti <plorenzo@disroot.org>  Mon, 10 Feb 2025 13:58:26 +0100

runit-services (0.8.0) unstable; urgency=medium

    Before version (0.7.0) the dhclient service was automatically enabled at package
    installation; however the service interacts badly with other network services such
    as network-manager, wicd, connman and the like, causing disruption on network setup.
    For this reason, since version (0.7.0) the dhclient service is shipped as disabled
    by default.
    This change is effective on new installations but for installations upgrading from old
    versions of the package, the dhclient service remains enabled.
    Unless dhclient was enabld as explicit choice of the sysadmin, (and no other service
    is used to configure the network) it's recommended to permanently disable it with

    # update-service --remove dhclient

    to avoid network issues.
    Note that there are networks hooks to invoke dhclient as oneshot during network
    setup (for example during system boot), and disabling the dhclient runit service does
    not affect such hooks.

 -- Lorenzo Puliti <plorenzo@disroot.org>  Wed, 20 Nov 2024 17:31:49 +0100