Bug 1387108 - Build HDFS providers in VFS2.1
Summary: Build HDFS providers in VFS2.1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: apache-commons-vfs
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: gil cattaneo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1387110
TreeView+ depends on / blocked
 
Reported: 2016-10-20 07:06 UTC by Christopher Tubbs
Modified: 2017-07-31 18:44 UTC (History)
3 users (show)

Fixed In Version: apache-commons-vfs-2.1-7.fc25
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-19 21:03:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Christopher Tubbs 2016-10-20 07:06:58 UTC
Description of problem:

HDFS providers are disabled in Fedora's build of apache-commons-vfs 2.1, because Hadoop was "retired". I've taken ownership of the hadoop package, and it has been unretired. The HDFS providers in upstream VFS2.1 no longer need to be disabled.

Comment 1 gil cattaneo 2016-10-28 07:42:09 UTC
submitted as update @ https://bodhi.fedoraproject.org/updates/FEDORA-2016-a2800f7739

Comment 2 Fedora Update System 2016-10-31 10:21:29 UTC
apache-commons-vfs-2.1-7.fc25 has been pushed to the Fedora 25 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-2016-a2800f7739

Comment 3 Fedora Update System 2016-11-03 18:22:10 UTC
apache-commons-vfs-2.1-7.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.

Comment 4 Fedora Update System 2016-11-19 21:03:27 UTC
apache-commons-vfs-2.1-7.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.


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