Saw this while installing :
/var/tmp/rpm-tmp.5awcsv: line 8: รท: command not found
warning: %post(etcd-3.5.0-2.fc34.x86_64) scriptlet failed, exit status 127
@tyrbiter@akumar Thanks for testing. etcd moved some folders around and my script to detect binaries did not work for some reason. Would you mind testing the update FEDORA-2021-02c3c8d8bf ?
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 etcd-3.5.0-1.fc34, 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.
sudo systemctl restart etcd gives an error, the daemon will no longer start after this update
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.
Saw this while installing : /var/tmp/rpm-tmp.5awcsv: line 8: รท: command not found warning: %post(etcd-3.5.0-2.fc34.x86_64) scriptlet failed, exit status 127
Service does not start.
This update can be pushed to stable now if the maintainer wishes
Still nothing about fixing the daemon fails to start problem.
This update has been obsoleted by etcd-3.5.0-4.fc34.
@tyrbiter @akumar Thanks for testing. etcd moved some folders around and my script to detect binaries did not work for some reason. Would you mind testing the update FEDORA-2021-02c3c8d8bf ?
I can confirm that the rpm in FEDORA-2021-02c3c8d8bf has fixed the problem I was seeing on both my Fedora 34 systems.