Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2052524

Summary:	rubygem-sinatra el8 rpm should keep the epoch number
Product:	Red Hat Satellite	Reporter:	Lukas Pramuk <lpramuk>
Component:	Packaging	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Lukas Pramuk <lpramuk>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.11.0	CC:	pcreech
Target Milestone:	6.11.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-07-05 14:32:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lukas Pramuk 2022-02-09 13:50:29 UTC

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

Comment 2 Lukas Pramuk 2022-02-16 11:46:05 UTC

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

Comment 6 errata-xmlrpc 2022-07-05 14:32:53 UTC

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