Bug 1179092 - EPEL7 package request - tsocks
Summary: EPEL7 package request - tsocks
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: tsocks
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: 2015-01-06 08:04 UTC by Ben Konrath
Modified: 2024-07-08 22:07 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-07-08 22:07:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ben Konrath 2015-01-06 08:04:56 UTC
It would be nice to see this package in the EPEL 7 repository.

Here is some information about EPEL:

https://fedoraproject.org/wiki/Getting_a_Fedora_package_in_EPEL
https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies

I managed to get tsocks-1.8-0.14.beta5.fc21.src.rpm to work on EL7 so it should be easy to submit the build.

Here are the instructions I used to build this package locally in case anybody is interested:

* Download the src rpm

http://dl.fedoraproject.org/pub/fedora/linux/development/21/source/SRPMS/t/tsocks-1.8-0.14.beta5.fc21.src.rpm

* Install the build dependencies:

sudo yum-builddep tsocks-1.8-0.14.beta5.fc21.src.rpm

* Run the build:

rpmbuild --rebuild tsocks-1.8-0.14.beta5.fc21.src.rpm

* Install the rpms:

sudo yum localinstall ~/rpmbuild/RPMS/x86_64/*.rpm

Thanks, Ben

Comment 1 markusN 2015-01-20 11:40:10 UTC
You can recompile the EL6 SRPM with "mock" (yum install mock) to prepare a clean EL7 package:

# fetch SRPM
wget http://dl.fedoraproject.org/pub/fedora/linux/development/21/source/SRPMS/t/tsocks-1.8-0.14.beta5.fc21.src.rpm

# mock to EL7
mock -r epel-7-x86_64 --rebuild tsocks-1.8-0.14.beta5.fc21.src.rpm

# see created S/RPMs:
ls -la /var/lib/mock/epel-7-x86_64/result

# install
sudo yum localinstall /var/lib/mock/epel-7-x86_64/result/tsocks-1.8-0.14.beta5.el7.centos.x86_64.rpm

Installed:
  tsocks.x86_64 0:1.8-0.14.beta5.el7.centos

Tested on Scientific Linux 7, works fine.

It would be great to see this package in EPEL7.

Comment 2 markusN 2015-01-24 20:16:14 UTC
Created now as (inofficial) repo here:

https://copr.fedoraproject.org/coprs/neteler/tsocks/

su
wget -O /etc/yum.repos.d/tsocks-epel-7.repo https://copr.fedoraproject.org/coprs/neteler/tsocks/repo/epel-7/neteler-tsocks-epel-7.repo
yum update
yum install tsocks

Comment 3 Ben Konrath 2015-01-25 09:53:40 UTC
markusN: Great initiative on getting an el7 package for tsocks that you share with other. You can also become the tsocks maintainer for the el7 branch directly in epel when maintainers don't respond to el7 requests. This would be a better solution in the long run because it makes it easier for users to install tsock with just the epel repo enabled (i.e. users wouldn't have to enable another repo to get tsocks).

Here's the documentation that explains the process:

If it is unclear if the Fedora maintainer of the package intends to participate in EPEL then the proposed EPEL maintainer should file a bug against the package and ask about their plans for EPEL in general and the package at hand. If there is no answer within seven days the proposed EPEL maintainer is free to request the EPEL branch and become the EPEL Maintainer (CC the Fedora maintainer here as well). Please note on your CVS request the number of the bug you filed. If the Fedora maintainer decides not to be active in EPEL they should be added to the CC list for all bugs so that collaboration can happen where a bug effects Fedora and EPEL. 

https://fedoraproject.org/wiki/Getting_a_Fedora_package_in_EPEL

Comment 4 Fedora Admin user for bugzilla script actions 2021-04-23 00:36:36 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 5 Troy Dawson 2024-07-08 22:07:54 UTC
EPEL 7 entered end-of-life (EOL) status on 2024-06-30.\n\nEPEL 7 is no longer maintained, which means that it\nwill not receive any further security or bug fix updates.\n 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.