ISSUE during DNF update: Running scriptlet: djvulibre-libs-3.5.27-27.fc33.x86_64 /usr/lib/tmpfiles.d/wesnothd.conf:1: Path '@FIFO_DIR@' not absolute. --- INFO about the system: $ rpm -qa | grep -e wesnoth-ser -e djvul wesnoth-server-1.15.14-1.fc33.x86_64 djvulibre-libs-3.5.27-28.fc33.x86_64 $ rpm -qf /usr/lib/tmpfiles.d/wesnothd.conf wesnoth-server-1.15.14-1.fc33.x86_64 $ cat /usr/lib/tmpfiles.d/wesnothd.conf d @FIFO_DIR@ 0700 nobody users - --- If this is not 'wesnoth-server' issue, please switch the BZ to 'djvulibre' pkg.
It actually appears to be a systemd issue, as @FIFO_DIR@ is a valid value.
Alright, providing Systemd packages versions: $ rpm -qa | grep -i systemd systemd-246.14-1.fc33.x86_64 systemd-libs-246.14-1.fc33.i686 systemd-libs-246.14-1.fc33.x86_64 rpm-plugin-systemd-inhibit-4.16.1.3-1.fc33.x86_64 python-systemd-doc-234-14.fc33.x86_64 systemd-networkd-246.14-1.fc33.x86_64 systemd-pam-246.14-1.fc33.x86_64 systemd-container-246.14-1.fc33.x86_64 systemd-rpm-macros-246.14-1.fc33.noarch python3-systemd-234-14.fc33.x86_64 systemd-udev-246.14-1.fc33.x86_64 libreport-plugin-systemd-journal-2.15.2-2.fc33.x86_64 --- NOTE: system appears completely up-to-date at this moment.
Syntax with @VARNAME@ is for replacing configuration values during build. systemd-tmpfiles does not support such syntax… It looks like the value didn't get replaced properly during build. Still an issue with wesnoth-server-1.15.14-1.fc34.x86_64.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Still no change in wesnoth-server-1.16.0-1.fc35.x86_64.rpm.
Still happening with wesnoth-server-1.17.5-1.fc36.x86_64
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
I still see that message on F38.
Yep, someone's dropped the ball on this one. Still a problem, but one I ignore when I see it.
Sorry about that, I spent a long time trying to find the "right" way to fix this, and it fell off my radar. Pushing an update with an inelegant but effective fix.
FEDORA-2023-87a5151216 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-87a5151216
FEDORA-2023-c6561c4409 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-c6561c4409` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-c6561c4409 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-87a5151216 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-87a5151216` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-87a5151216 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-c6561c4409 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2023-87a5151216 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.