Bug 601989
Summary: | Creating new fuse-encfs filesystem fails with 'boost::filesystem::filesystem_error' | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | andrew | ||||
Component: | fuse-encfs | Assignee: | Till Maas <opensource> | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | el5 | CC: | jhcaiced, jokajak, josh.kayse, lemenkov, ole.d, opensource | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2012-08-21 18:36:49 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
andrew
2010-06-09 00:43:20 UTC
Created attachment 489967 [details]
Spec for fuse-encfs-1.7.4 ported from Fedora 13 spec
I'm attaching a spec file I've created for latest encfs-1.7.4 ported and updated from Fedora 13 to EPEL. It uses boost141 from EPEL instead of RHEL boost, as the latter is not supported by encfs.
I've tested build on i386 and x86_64 - it builds cleanly with mock and works on CentOS 5.5.
As current encfs in EPEL simply does not work I think a major upgrade is reasonable and complies with update policy.
I would tend to agree that we should update to 1.7.4 as it resolves some additional security relevant bugs. Unfortunately encfs requires boost >= 1.34 and we have only 1.33.1 in EL-5. Has anybody tried to patch encfs to allow building against boost-1.33.1? (In reply to comment #3) > Unfortunately encfs requires boost >= 1.34 and we have only 1.33.1 in EL-5. > > Has anybody tried to patch encfs to allow building against boost-1.33.1? As written in comment 1 there is boost141 in EPEL which provides a newer version of boost. Is this not enough? Since encfs is broken now for two years in EPEL 5, please respond whether you are still intending to maintain it and orphan it, if not. Also please consider this to be the first message regarding the nonresponsive package mainater procedure: https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers I hope you simply missed the possibility to use boos141 and can prepare an update soon. (In reply to comment #4) > (In reply to comment #3) > > Unfortunately encfs requires boost >= 1.34 and we have only 1.33.1 in EL-5. > > > > Has anybody tried to patch encfs to allow building against boost-1.33.1? > > As written in comment 1 there is boost141 in EPEL which provides a newer > version of boost. Is this not enough? Since encfs is broken now for two > years in EPEL 5, please respond whether you are still intending to maintain > it and orphan it, if not. Also please consider this to be the first message > regarding the nonresponsive package mainater procedure: > https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers > > I hope you simply missed the possibility to use boos141 and can prepare an > update soon. I don't use encfs anymore so feel free to take it over. fuse-encfs-1.7.4-7.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/fuse-encfs-1.7.4-7.el5 Package fuse-encfs-1.7.4-7.el5: * should fix your issue, * was pushed to the Fedora EPEL 5 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing fuse-encfs-1.7.4-7.el5' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-6382/fuse-encfs-1.7.4-7.el5 then log in and leave karma (feedback). fuse-encfs-1.7.4-7.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report. |