I have installed dnscrypt-proxy to look into its documentation. I were using unbound+dnssec-trigger and wanted it to continue. But after a reboot my configuration were broken and VPN redirection did not work. I have found that happened because dnscrypt-proxy has a custom way to auto-enable itself on installation. I do not think this is allowed by packaging guidelines. Reproducible: Always Steps to Reproduce: 1. dnf install unbound dnssec-trigger 2. dnf enable --now dnssec-triggerd 3. dnf install dnscrypt-proxy 4. reboot Actual Results: my explicitly configured unbound has failed to startup, because there is different service listening on the same port already. I have never chosen to replace that by dnscrypt-proxy. Expected Results: The service is enabled only manually, by usual configuration via systemctl: systemctl enable --now dnscrypt-proxy Fedora allows auto-enabled services only when they do not modify other services. That does not happen directly, but by listening on common domain port on 127.0.0.1 it effectively does. If it used alternative localhost address it might be okay. But it must not as it is now. This service has not a FESCo ticket required to be enabled by default: https://src.fedoraproject.org/rpms/fedora-release/blob/rawhide/f/90-default.preset I do not think it passes guidelines: https://docs.fedoraproject.org/en-US/packaging-guidelines/DefaultServices/#_enabling_services_by_default It also does not use systemd macros, which I think it should use: https://docs.fedoraproject.org/en-US/packaging-guidelines/Scriptlets/#_systemd
Yup, this needs to be fixed. This package was recently orphaned and I picked it up, will try and get this sorted out on the next update (hopefully) soon.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39.
FEDORA-2023-fd8de8b367 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-fd8de8b367
FEDORA-2023-0a1ef0ef74 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-0a1ef0ef74
FEDORA-2023-6c6700154a has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-6c6700154a
FEDORA-2023-fd8de8b367 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-fd8de8b367` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-fd8de8b367 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-6c6700154a has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-6c6700154a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-6c6700154a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-0a1ef0ef74 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-0a1ef0ef74` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-0a1ef0ef74 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-fd8de8b367 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-6c6700154a has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-0a1ef0ef74 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.