Bug 1491982 - please update/maintain pass in EPEL
Summary: please update/maintain pass in EPEL
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: pass
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christophe Fergeau
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1492134
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-09-15 08:25 UTC by marcindulak
Modified: 2018-10-05 13:54 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-10-05 13:54:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description marcindulak 2017-09-15 08:25:08 UTC
Description of problem:

The versions available in EPEL are really old compared to Fedora, e.g.:

pass-1.5-2.el7.noarch


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 marcindulak 2017-09-15 08:41:40 UTC
Oh, I see the build is limited by the version of tree:

$ rpmbuild --rebuild pass-1.7.1-2.fc26.src.rpm
tree >= 1.7.0 is needed by pass-1.7.1-2.el7.centos.noarch

and RHEL 7.4 is still shipping tree-1.6.0-10.el7.x86_64

Is there a way to get a more recent tree in RHEL7?

Comment 2 Carl George 🤠 2017-09-15 13:21:19 UTC
Create a bug under the RHEL 7 product and tree component and ask them.  They have been much more pragmatic with version rebases during RHEL 7 than they have in the past.  Once you create that you can mark it as a blocker for this bug.

Comment 3 marcindulak 2017-09-15 14:47:08 UTC
I've made an attempt to build the latest tree + pass based on Fedora 26 SRPMS, but the pass tests are failing. Could someone verify this is really the case, maybe more dependencies on RHEL need to be updated in order to build the latest pass?

Comment 4 Carl George 🤠 2018-10-05 13:54:10 UTC
I see the request to rebase tree was declined.  If they change their mind I can re-open this.


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