unable to install the updated package (4.0.0-3.fc42) on fedora silverblue 42.
rpm-ostree upgrade gave the following error:
error: While applying overrides for pkg ddclient: Could not find user 'ddclient' in passwd file
I tried to uninstall the old version (4.0.0-1.fc42) first and then install the new version (4.0.0-3.fc42). It still gave the the same error. However, I can install the package inside a fedora 42 container.
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.
I tried with two versions of rpm-ostree: 2025.8-1.fc42 from fedora/42/x86_64/testing/silverblue and 2025.7-2.fc42 from fedora/42/x86_64/silverblue. Both produced the same error as before.
The bug was caused by rpm-ostree and sysusers. And ddclient just happened to implement migration to sysusers between 4.0.0-1 and 4.0.0-3.
It may be fixed in the next release of rpm-ostree.
BZ#2354194 ddclient failed: [file /etc/ddclient/ddclient.conf]> cannot open file: No such file or directory
The update as I see in the source code is going to break users that have already installed their configuration file under /etc/ddclient. So the fix will be a breaking change for many.
At this time I think it makes more sense to migrate files found at the old location to the new location in a script. It's frustrating that one notice the service has failed only after you lose track of your IP which can be super inconvenient for remote locations.
P.S. or link the configuration from the old location to the new location when one at the old location exists
Possibly more users might be like that but there might be many that noticed the issue and mitigated it. There is no reason to sacrifice any of these. One compatibility upgrade issue doesn't mean another one needs to be introduced when a relatively simple post-install on-liner can fix the issue for both.
Yeah it's unfortunate that this update got tied up with the rpm-ostree bug and then I got busy the past couple months.
Patches are welcome. :-) Also, if any of you are Fedora packagers and are interested in taking over maintainership, you're more than welcome. I don't actually use ddclient anymore.
This update has been submitted for testing by swt2c.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
unable to install the updated package (4.0.0-3.fc42) on fedora silverblue 42.
rpm-ostree upgradegave the following error:I tried to uninstall the old version (4.0.0-1.fc42) first and then install the new version (4.0.0-3.fc42). It still gave the the same error. However, I can install the package inside a fedora 42 container.
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.
This update can be pushed to stable now if the maintainer wishes
@vitamin can you try again with the latest version of rpm-ostree? This has supposedly been fixed in rpm-ostree-2025.7-1.fc42.
I tried with two versions of rpm-ostree: 2025.8-1.fc42 from
fedora/42/x86_64/testing/silverblueand 2025.7-2.fc42 fromfedora/42/x86_64/silverblue. Both produced the same error as before.Fixes the issue for me
@vitamin can you please file a bug against rpm-ostree for that issue?
This update has been submitted for stable by swt2c.
The bug has been filed:
https://bugzilla.redhat.com/show_bug.cgi?id=2359764
https://github.com/coreos/rpm-ostree/issues/5365
The bug was caused by rpm-ostree and sysusers. And ddclient just happened to implement migration to sysusers between 4.0.0-1 and 4.0.0-3. It may be fixed in the next release of rpm-ostree.
The update as I see in the source code is going to break users that have already installed their configuration file under
/etc/ddclient. So the fix will be a breaking change for many.At this time I think it makes more sense to migrate files found at the old location to the new location in a script. It's frustrating that one notice the service has failed only after you lose track of your IP which can be super inconvenient for remote locations.
P.S. or link the configuration from the old location to the new location when one at the old location exists
Far more users would have configuration at /etc/ddclient.conf and wouldn't know that the recent update to 4.0 broke that, IMO.
Possibly more users might be like that but there might be many that noticed the issue and mitigated it. There is no reason to sacrifice any of these. One compatibility upgrade issue doesn't mean another one needs to be introduced when a relatively simple post-install on-liner can fix the issue for both.
But if nobody is going to do this, I'm ok to just let it roll. Sad that small things like that reduce distro perceived trustworthiness.
Yeah it's unfortunate that this update got tied up with the rpm-ostree bug and then I got busy the past couple months.
Patches are welcome. :-) Also, if any of you are Fedora packagers and are interested in taking over maintainership, you're more than welcome. I don't actually use ddclient anymore.
This update has been unpushed.