Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 962935 - confusing usage of epoch in spacewalk-backend package
Summary: confusing usage of epoch in spacewalk-backend package
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Server
Version: 560
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Jan Pazdziora
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: sat560-triage
TreeView+ depends on / blocked
 
Reported: 2013-05-14 19:27 UTC by Jan Hutař
Modified: 2013-05-15 05:51 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-15 05:51:16 UTC


Attachments (Terms of Use)

Description Jan Hutař 2013-05-14 19:27:30 UTC
Description of problem:
spacewalk-backend package "provides" numerous versioned provides like "rhns = 1:1.7.38-45.el6sat" (including epoch), but package itself do not have epoch set (to "1").


Version-Release number of selected component (if applicable):
spacewalk-backend-1.7.38-45.el6sat.noarch.rpm


How reproducible:
always


Steps to Reproduce:
$ rpm -qp --qf="%{EPOCH}\n" spacewalk-backend-1.7.38-45.el6sat.noarch.rpm
(none)
$ rpm -qp --provides spacewalk-backend-1.7.38-45.el6sat.noarch.rpm | grep '= [0-9]\+:'
rhns = 1:1.7.38-45.el6sat
rhns-common = 1:1.7.38-45.el6sat
spacewalk-backend-upload-server = 1:1.7.38-45.el6sat


Actual results:
See above. IMO package should either define "epoch = 1", or provide versioned provides without epoch specified. In case this is expected and wanted state, please close this bug.


Expected results:
Packages epoch ane epoch in versioned provide should match.

Comment 2 Jan Pazdziora 2013-05-15 05:51:16 UTC
(In reply to comment #0)
> Description of problem:
> spacewalk-backend package "provides" numerous versioned provides like "rhns
> = 1:1.7.38-45.el6sat" (including epoch), but package itself do not have
> epoch set (to "1").

That's exactly expected. The spacewalk* packages have replaced the rhns* packages. The spacewalk* packages versioning started from 0.1 while rhns* were at 5.2 or similar.

Thus, saying that spacewalk* in epoch 0 provides rhns* in epoch 1 is actually correct, and it ensures that upon upgrade, rhns* packages get removed.

> Actual results:
> See above. IMO package should either define "epoch = 1", or provide
> versioned provides without epoch specified. In case this is expected and
> wanted state, please close this bug.
> 
> Expected results:
> Packages epoch ane epoch in versioned provide should match.

No. spacewalk != rhns.


Note You need to log in before you can comment on or make changes to this bug.