with this update, socket and service units was not found. reverted to 2.0.44-2 and dnscrypt-proxy.service couldn't start because in /etc/systemd/system/dnscrypt-proxy.service, exec line wasn't specifying the absolute path for config file. error message was:
Dec 17 10:07:20 fedora.notebook dnscrypt-proxy[3361]: [2020-12-17 10:07:20] [FATAL] Unable to load the configuration file [dnscrypt-proxy.toml] -- Maybe use the -config command-line switch?
i uninstalled dnscrypt-proxy, removed /etc/systemd/system/dnscrypt-proxy.service and installed 2.0.44-2 again, everyhing is fine now.
This update can be pushed to stable now if the maintainer wishes
This update has been submitted for testing by eclipseo.
This update's test gating status has been changed to 'ignored'.
This update's test gating status has been changed to 'waiting'.
This update has obsoleted dnscrypt-proxy-2.0.44-4.fc33, and has inherited its bugs and notes.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
The systemd unit is broken as the .socket is stored as .socket.back and .service is removed, not even backuped (?)
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
and a file: /etc/systemd/system/dnscrypt-proxy.service, I had to remove, to be able to use dnscrypt-proxy-2.0.44-2.fc33 with my backed up files
with this update, socket and service units was not found. reverted to 2.0.44-2 and dnscrypt-proxy.service couldn't start because in
/etc/systemd/system/dnscrypt-proxy.service, exec line wasn't specifying the absolute path for config file. error message was:i uninstalled dnscrypt-proxy, removed
/etc/systemd/system/dnscrypt-proxy.serviceand installed 2.0.44-2 again, everyhing is fine now.This update can be pushed to stable now if the maintainer wishes
Ok I messed up the update because I wanted to revert to the official installation process. I'll try to see how to work this up.
This update has been unpushed.