Bug 963000 - Home page version should match package NVR
Summary: Home page version should match package NVR
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 4.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 4.4
Assignee: Simon Green
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-14 23:31 UTC by Jeff Fearn 🐞
Modified: 2018-12-09 06:29 UTC (History)
6 users (show)

Fixed In Version: 4.4.0009
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-04 00:45:47 UTC
Embargoed:


Attachments (Terms of Use)

Description Jeff Fearn 🐞 2013-05-14 23:31:01 UTC
Description of problem:
Currently the rh-bugzilla package NVR does not match the version on the home page.

e.g. 'version 4.2.5-8.4' != 4.2-20130220.2

Version-Release number of selected component (if applicable):
All

How reproducible:
Always

Steps to Reproduce:
1. Look at home page to get version
2. compare to RPM NVR

  
Actual results:
They don't match

Expected results:
They should match

Additional info:
Bumping the epoch will allow lower NVRs to override higher NVRs.

Comment 2 Simon Green 2013-07-10 08:19:52 UTC
(In reply to Jeff Fearn from comment #0)
> Expected results:
> They should match

Does that mean the homepage should show 4.4-20130610-1, or the RPM should be 4.4-5.1 (for example)? I'm assuming the first from the title of the bug, but want to confirm first.

Comment 3 Simon Green 2013-09-17 00:20:57 UTC
(In reply to Simon Green from comment #2)
> Does that mean the homepage should show 4.4-20130610-1, or the RPM should be
> 4.4-5.1 (for example)? I'm assuming the first from the title of the bug, but
> want to confirm first.

The RPM should contain the version number. This has been requested by Marco, and we will implement it as part of sprint9. (rh-bugzilla-4.4.0009-X.noarch.rpm)

Comment 5 Simon Green 2013-10-04 00:45:47 UTC
This change is now live. If there are any issues, do not reopen this bug.
Instead, you should create a new bug and reference this bug.

  -- simon


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