Description of problem: Use of the %{?dist} tag is mandatory in Fedora. shim doesn't use it. Version-Release number of selected component (if applicable): 15-8 Steps to Reproduce: $ repoquery --repo=rawhide-source shim Actual results: shim-0:15-8.src Expected results: shim-0:15-8.fc32.src Additional info: https://docs.fedoraproject.org/en-US/packaging-guidelines/DistTag/
I have found: https://src.fedoraproject.org/rpms/shim-signed/c/63d4aeebfb95fc5e6bf8b1fd749cb10dde8f2e31?branch=f27 "Remove the dist tag so people don't complain about what it says." What does that mean?
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32.
Any progress on this?
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle. Changing version to 34.
This is still a problem even in Fedora rawhide: $ koji latest-build rawhide shim Build Tag Built by ---------------------------------------- -------------------- ---------------- shim-15-8 f35 pjones
It's still missing in the most recent updates: https://koji.fedoraproject.org/koji/packageinfo?packageID=14502
This is expected, is to allow the same shim build to be tagged for different Fedora releases, i.e: $ koji latest-build f32 shim Build Tag Built by ---------------------------------------- -------------------- ---------------- shim-15-8 f32 pjones $ koji latest-build f33 shim Build Tag Built by ---------------------------------------- -------------------- ---------------- shim-15-8 f33 pjones
Even builds with %{dist} can be tagged to mutliple releases. I don't understand the reasoning here, care to elaborate?
(In reply to Miro Hrončok from comment #9) > Even builds with %{dist} can be tagged to mutliple releases. I don't > understand the reasoning here, care to elaborate? Yes, but it's confusing for users to have a fcX build on a fcY release.
> Yes, but it's confusing for users to have a fcX build on a fcY release. Does this apply to all packages in Fedora or just shim?
For Covscan, as well as other build-oriented services, it would mainly help if build IDs were unique across Fedora/CentOS/RHEL instances of koji/brew. Using different dist-tags for each of those instances makes it easy to guarantee this requirement. If you cannot (or do not want to) use dist-tags, could you please satisfy this requirement by other means?
(In reply to Miro Hrončok from comment #13) > > Yes, but it's confusing for users to have a fcX build on a fcY release. > > Does this apply to all packages in Fedora or just shim? Are other packages built only once but tagged for different Fedora releases ? Anyways, you should discuss this with Peter, since he did the change and explained to me the rationale. I think that makes sense but I don't know how to address what Kamil asked in Comment 14.
This bug appears to have been reported against 'rawhide' during the Fedora 35 development cycle. Changing version to 35.
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.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. 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 '36'. 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. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 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.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. 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 '37'. 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. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 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.
This message is a reminder that Fedora Linux 38 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 38 on 2024-05-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 'version' of '38'. 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. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 38 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.
This message is a reminder that Fedora Linux 39 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26. 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 '39'. 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. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 39 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.
This is still valid for Fedora 40+.
This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-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 '40'. 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. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 40 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.
This is still valid for Fedora 41+ and the maitainer still hasn't responded :(
(In reply to Miro Hrončok from comment #24) > This is still valid for Fedora 41+ and the maitainer still hasn't responded :( "Version:" should be changed from 41 to rawhide
This message is a reminder that Fedora Linux 41 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 41 on 2025-12-15. 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 '41'. 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. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 41 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.