Bug 1480900 - Opening git project from a `git worktree` directory fails
Summary: Opening git project from a `git worktree` directory fails
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: eclipse-jgit
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mat Booth
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-12 18:33 UTC by Christopher Tubbs
Modified: 2021-04-08 10:08 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-04-08 10:08:12 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Eclipse Project 477475 0 None None None 2017-08-12 18:33:02 UTC

Description Christopher Tubbs 2017-08-12 18:33:02 UTC 
Description of problem:
I attempted to import an existing Maven project into Eclipse from a `git worktree` location, and got an error with the git Auto-share feature.

Version-Release number of selected component (if applicable):
eclipse-jgit-4.8.0-2.fc26.noarch

How reproducible:
Always

Steps to Reproduce:
1. git clone some-project && cd some-project
2. git worktree add ../tmp some-branch
3. Open Eclipse and import existing project form ../tmp

Actual results:
Error message about failing to Auto-share git project

Expected results:
Git feature active in Eclispe, tracking git changes

Additional info:
This appears to be a known upstream bug with eclipse-jgit https://bugs.eclipse.org/bugs/show_bug.cgi?id=477475
Comment 1 Fedora Admin user for bugzilla script actions 2021-03-24 00:21:21 UTC 
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
Comment 2 Alexander Kurtakov 2021-04-08 10:08:12 UTC 
This bug is from F26 and so many things changed since then but upstream hasn't acted on this one. It will be part of fedora when upstream supports it so no point in this bug.
Note You need to log in before you can comment on or make changes to this bug.