Bug 1778831 - [RFE] : bump opentracker to newer release
Summary: [RFE] : bump opentracker to newer release
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: opentracker
Version: epel7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-02 15:29 UTC by Fabian Arrotin
Modified: 2024-07-09 15:40 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-07-09 15:40:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
new .patch that applies to upstream opentracker source (2.66 KB, application/mbox)
2019-12-03 06:58 UTC, Fabian Arrotin
no flags Details

Description Fabian Arrotin 2019-12-02 15:29:52 UTC
Based on http://erdgeist.org/gitweb/opentracker/, it seems that there were some commits (now in git, instead of cvs) and what I can see in both the epel7 branch and F31 branch is that it's still blocked on this snap_ver : 

%global snapver 20160728 (https://src.fedoraproject.org/rpms/opentracker/blob/epel7/f/opentracker.spec#_1)

Can this be bumped and so having a new build ?

Thanks

Comment 1 Fabian Arrotin 2019-12-03 06:56:29 UTC
FWIW, I just tested a scratch build : https://cbs.centos.org/koji/taskinfo?taskID=1057163

I just had to modify .spec (as building now from a git clone instead of cvs) and also newer .patch for the Makefile (previous one didn't work).
Attaching it here for ref

Comment 2 Fabian Arrotin 2019-12-03 06:58:23 UTC
Created attachment 1641561 [details]
new .patch that applies to upstream opentracker source

Comment 3 Fedora Admin user for bugzilla script actions 2023-08-02 00:07:18 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 4 Troy Dawson 2024-07-09 15:40:01 UTC
EPEL 7 entered end-of-life (EOL) status on 2024-06-30.  EPEL 7 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.


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