Description of problem: I am doing simple SRPM build. After start, there are unreled the changes to postinit snapshot: INFO: rolled back to postinit snapshot However later, the content of this snapshot is updated: Start: dnf update Dependencies resolved. ================================================================================ Package Arch Version Repository Size ================================================================================ Upgrading: ca-certificates noarch 2014.2.2-2.fc22 local 426 k ... snip ... After this, the postinit snapshot should be updated as well, otherwise it is updated every other time. Or alternatively, the old snapshod should be dropped and created new one, to avoid possible update issues. Version-Release number of selected component (if applicable): $ rpm -q mock mock-1.2.3-1.fc21.noarch How reproducible: Steps to Reproduce: 1. mock ruby-2.2.0-0.1.r48879.fc22.src.rpm 2. wait until some updates lands in the repository, possibly few days 3. mock -r ruby ruby-2.2.0-0.1.r48879.fc22.src.rpm Actual results: The build root is updated, but the snapshot is not Expected results: The snapshod should be either updated or recreated Additional info:
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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.
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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.
I still think this would be useful.
Should be resolved via: https://github.com/rpm-software-management/mock/issues/68 Please reopen if you happen to see this error again.
Uhhhh, sorry. Wrong bug id.
I would not regret if this was really fixed ;)
This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component.
https://github.com/rpm-software-management/mock/pull/594
Fixed upstream, nightly builds (if anyone wanted to test) are in 'dnf copr enable @mock/mock'.
FEDORA-2020-afe3cb8dbc has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-afe3cb8dbc
FEDORA-2020-54d3e6d1c1 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-54d3e6d1c1
FEDORA-EPEL-2020-646d5f7450 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-646d5f7450
FEDORA-EPEL-2020-77cf1cc1a9 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-77cf1cc1a9
FEDORA-2020-afe3cb8dbc has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-afe3cb8dbc` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-afe3cb8dbc See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-646d5f7450 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-646d5f7450 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-77cf1cc1a9 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-77cf1cc1a9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-54d3e6d1c1 has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-54d3e6d1c1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-54d3e6d1c1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-afe3cb8dbc has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-54d3e6d1c1 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2020-e8977f0629 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-e8977f0629 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-3361ef3fc2 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-3361ef3fc2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-e8977f0629 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2020-3361ef3fc2 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report.