rpmautospec-rpm-macros-0.2.3-1.fc35 suffers from a locale bug: (1) Get a rpmautospec-driven dist-git repository: $ fedpkg clone -a ravada Cloning into 'ravada'... remote: Enumerating objects: 357, done. remote: Counting objects: 100% (357/357), done. remote: Compressing objects: 100% (350/350), done. remote: Total 357 (delta 159), reused 0 (delta 0), pack-reused 0 Receiving objects: 100% (357/357), 947.11 KiB | 1.59 MiB/s, done. Resolving deltas: 100% (159/159), done. $ cd ravada (2) Create a source package in cs_CZ.UTF-8 locale: $ LC_ALL=cs_CZ.UTF-8 fedpkg srpm Downloading ravada-1.0.3.tar.gz ######################################################################## 100.0% chyba: špatný datum v %changelog: Ne čec 25 2021 Robert-André Mauchin <zebob.m> 1.0.3-1 Zapsáno: /home/test/fedora/ravada/ravada-1.0.3-1.fc35.src.rpm It reported a bad date in %changelog, but created the RPM package nevertheless. (3) The changelog in the SRPM package is empty: $ rpm -q --changelog -p ravada-1.0.3-1.fc35.src.rpm Compare to creating the package in en_US.UTF-8 locale: $ LC_ALL=en_US.UTF-8 fedpkg srpm error: %changelog not in descending chronological order setting SOURCE_DATE_EPOCH=1627171200 Wrote: /home/test/fedora/ravada/ravada-1.0.3-1.fc35.src.rpm $ rpm -q --changelog -p ravada-1.0.3-1.fc35.src.rpm | head * Sun Jul 25 2021 Robert-André Mauchin <zebob.m> 1.0.3-1 - Update to 1.0.3 Close: rhbz#1973849 * Fri Jul 23 2021 Fedora Release Engineering <releng> - 1.0.1-3 - Rebuilt for https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild * Mon May 24 2021 Jitka Plesnikova <jplesnik> - 1.0.1-2 - Perl 5.34 re-rebuild updated packages
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle. Changing version to 35.
FEDORA-2022-1e8145fb45 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-1e8145fb45
FEDORA-2022-e050aa1e6d has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-e050aa1e6d
FEDORA-2022-0c44eb0df4 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-0c44eb0df4
FEDORA-2022-1e8145fb45 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-1e8145fb45` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-1e8145fb45 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-0c44eb0df4 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-0c44eb0df4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-0c44eb0df4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-e050aa1e6d has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-e050aa1e6d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-e050aa1e6d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-e050aa1e6d has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-1e8145fb45 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-0c44eb0df4 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.