Bug 1398962

Summary: rpm fuse-encfs is missing for el6
Product: [Fedora] Fedora EPEL Reporter: arnaud056 <arnaud056>
Component: fuse-encfsAssignee: Michel Lind <michel>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: el6CC: michel, vascom2
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: fuse-encfs-1.7.4-25.el6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-12 17:18:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description arnaud056 2016-11-27 16:37:05 UTC
Description of problem:
the rpm fuse-encfs for el6 is missing into the repo

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


How reproducible:
yum --enablerepo=epel install fuse-encfs

Steps to Reproduce:
1.
2.
3.

Actual results:
no package fuse-encfs can't be found

Expected results:

as fuse-encfs is still present into the repo for RHEL7, please rebuild it for RHEL6.
Thanks


Additional info:
rpm is still present here: http://mirrors.sohu.com/fedora-epel/6/x86_64/

Comment 1 Vasiliy Glazov 2016-11-28 07:31:14 UTC
EL6 has very old packages or not have required dependencies (for example perl-libintl) to build current version of fuse-encfs.

Only old version can be builded. You can try this build http://koji.fedoraproject.org/koji/taskinfo?taskID=16654075

But I am not sure that we can push it to repos because fuse-encfs not supported for EPEL 6 now https://admin.fedoraproject.org/pkgdb/package/rpms/fuse-encfs/

Comment 2 arnaud056 2016-11-28 19:51:15 UTC
Hi Vasily,
I'm not sure to have understand right your answer:
EPEL6 still exists. fuse-encfs still exists too (for EPEL7). Then what is the necessity to remove it from the repos EPEL6, event if it is not the last release (newer releases are not possible because of missing dependencies, I understand this) ?

Thanks for your link. Following it I found the rpm https://kojipkgs.fedoraproject.org//work/tasks/4076/16654076/fuse-encfs-1.7.4-24.el6.x86_64.rpm (previously I only had found 1.7.4-1 - see initial message).

It is for me an additional reason (it is already built! Nothing to do!) to push it back into the repo.

Question in the opposite direction: what is/are the reason(s) to take the last present release away (in the past the rpm was present) from the repo?

Thanks.
Arnaud

Comment 3 Vasiliy Glazov 2016-11-29 03:08:05 UTC
It was done before I am taked maintaining of this package.

I will try push it to the repo again.

Comment 4 Carlos Maiolino 2016-11-30 12:44:54 UTC
*** Bug 1398960 has been marked as a duplicate of this bug. ***

Comment 5 Vasiliy Glazov 2017-01-23 06:23:58 UTC
Package unretired.
Now I wait when it will be unblocked in koji https://pagure.io/releng/issue/6596

Comment 6 Fedora Update System 2017-01-27 04:19:28 UTC
fuse-encfs-1.7.4-25.el6 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-d85acd2a5a

Comment 7 Fedora Update System 2017-01-29 01:18:41 UTC
fuse-encfs-1.7.4-25.el6 has been pushed to the Fedora EPEL 6 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-d85acd2a5a

Comment 8 arnaud056 2017-01-29 07:08:08 UTC
Thanks Valisily for the job!

How / when will the rpm be moved into the regular repository?

Comment 9 Vasiliy Glazov 2017-01-29 07:13:20 UTC
It will be moved to updates repo after two weeks or earlier if carma count up to 3.

Comment 10 Fedora Update System 2017-02-12 17:18:38 UTC
fuse-encfs-1.7.4-25.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.