Description of problem: rubygem-sinatra el8 rpm doesn't have an epoch number. The rpm should continue to have the epoch defined (keeping the epoch 1:) as it's not a really good packaging practice to lose epoch from newer rpm builds Version-Release number of selected component (if applicable): 7.0.0 Snap8 rubygem-sinatra-2.1.0-2.el8sat.noarch How reproducible: deterministic Steps to Reproduce: 1. # rpm -q --provides -p rubygem-sinatra-2.1.0-2.el8sat.noarch.rpm rubygem(sinatra) = 2.1.0 rubygem(sinatra) = 2.1.0-1 rubygem-sinatra = 2.1.0-2.el8sat < epoch 1 missing Actual results: epoch missing Expected results: keeping epoch 1 consistently with past rhel and future fedoras rpms Additional info: # rpm -q --provides -p rubygem-sinatra-1.4.7-3.el7sat.noarch.rpm rubygem(sinatra) = 1.4.7 rubygem-sinatra = 1:1.4.7-3.el7sat # rpm -q --provides -p rubygem-sinatra-2.1.0-1.fc35.noarch.rpm rubygem(sinatra) = 2.1.0 rubygem-sinatra = 1:2.1.0-1.fc35
VERIFIED. @Satellite 7.0.0 Snap9 rubygem-sinatra-2.1.0-3.el8sat.noarch # rpm -q --provides rubygem-sinatra rubygem(sinatra) = 2.1.0 rubygem(sinatra) = 2.1.0 rubygem-sinatra = 1:2.1.0-3.el8sat >>> epoch is now present and set to 1
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: Satellite 6.11 Release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:5498