Bug 1349684 - E117: Unknown function: netrw#NetrwBrowseX when running GBrowse
Summary: E117: Unknown function: netrw#NetrwBrowseX when running GBrowse
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: vim-fugitive
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Vít Ondruch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-24 01:27 UTC by Brad Hubbard
Modified: 2016-07-05 04:59 UTC (History)
1 user (show)

Fixed In Version: vim-fugitive-2.2-5.fc24
Clone Of:
Environment:
Last Closed: 2016-07-05 04:59:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Brad Hubbard 2016-06-24 01:27:32 UTC
Description of problem:
:GBrowse produces "E117: Unknown function: netrw#NetrwBrowseX"

per https://github.com/tpope/vim-fugitive/issues/594

Version-Release number of selected component (if applicable):
vim-fugitive-2.2-4.fc24.noarch

How reproducible:
100%

Comment 2 Fedora Update System 2016-06-24 09:28:03 UTC
vim-fugitive-2.2-5.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-234c478696

Comment 3 Vít Ondruch 2016-06-24 09:28:26 UTC
Thx for the patch.

Comment 4 Brad Hubbard 2016-06-24 09:29:52 UTC
(In reply to Vít Ondruch from comment #3)
> Thx for the patch.

No, thank you.

Comment 5 Fedora Update System 2016-06-25 00:31:18 UTC
vim-fugitive-2.2-5.fc24 has been pushed to the Fedora 24 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-234c478696

Comment 6 Fedora Update System 2016-07-05 04:59:39 UTC
vim-fugitive-2.2-5.fc24 has been pushed to the Fedora 24 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.