Re: [cross-project-issues-dev] EGit 4.9.1 and 4.9.2 Have Problems Clonin

[Matthias Sohn <matthias.sohn@xxxxxxxxx>]

Thomas found out that the repo http://git.eclipse.org/gitroot/jdt/eclipse.jdt.core.git has two tags that differ only by case:

refs/tags/Cheetah
refs/tags/cheetah

which seems to cause this issue on case-insensitive filesystems.

Creating multiple refs only differing in case isn't fully portable, on case-insensitive filesystems

this may lead to problems.

In eclipse.jdt.core.git rename or delete one of those tags, this should fix the problem for this repository.

There is probably room to improve the current behaviour of jgit. Though I think the fact that this problem

is caused by two refs which only differ in case reduces the severity of the issue considerably.

This problem is tracked in https://bugs.eclipse.org/bugs/show_bug.cgi?id=528497

-Matthias 

On Wed, Dec 13, 2017 at 6:02 PM, Matthias Sohn <matthias.sohn@xxxxxxxxx> wrote:

yes, I found the commit which introduced the issue and started debugging the problem to see how to fix this.

-Matthias

On Wed, Dec 13, 2017 at 5:37 PM, Frederic Gurr <frederic.gurr@eclipse-foundation.org> wrote:

Hi,

I guess Matthias Sohn is already investigating, but we should find out
quickly if this requires yet another respin, so the process (ask PMC and
the Planning Council) can be started.

Regards,

Fred


--
Frederic Gurr

Release Engineer
Eclipse Foundation

On 13.12.2017 06:43, Ed Merks wrote:
> Hi,
>
> I'm concerned that EGit 4.9.1 and 4.9.2 consistently fail to produce a
> well-formed clone for some Eclipse repositories, e.g., for
> http://git.eclipse.org/gitroot/jdt/eclipse.jdt.core.git Oomph's Git
> Clone task fails like this:
>
> java.lang.Exception: org.eclipse.jgit.api.errors.RefNotFoundException:
> Ref refs/remotes/origin/master can not be resolved
>   at
> org.eclipse.oomph.setup.git.impl.GitCloneTaskImpl.perform(GitCloneTaskImpl.java:892)
>   at
> org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.doPerformNeededSetupTasks(SetupTaskPerformer.java:3324)
>   at
> org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.access$1(SetupTaskPerformer.java:3267)
>   at
> org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil$1.run(SetupTaskPerformer.java:4494)
>   at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240)
>   at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267)
>   at
> org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil.performNeededSetupTasks(SetupTaskPerformer.java:4488)
>   at
> org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil.access$0(SetupTaskPerformer.java:4486)
>   at
> org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performNeededSetupTasks(SetupTaskPerformer.java:3258)
>   at
> org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performTriggeredSetupTasks(SetupTaskPerformer.java:3233)
>   at
> org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.perform(SetupTaskPerformer.java:3133)
>   at
> org.eclipse.oomph.setup.ui.wizards.ProgressPage$9.run(ProgressPage.java:575)
>   at
> org.eclipse.oomph.setup.ui.wizards.ProgressPage$11$1.run(ProgressPage.java:701)
>   at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> Caused by: org.eclipse.jgit.api.errors.RefNotFoundException: Ref
> refs/remotes/origin/master can not be resolved
>   at
> org.eclipse.jgit.api.CreateBranchCommand.getStartPointObjectId(CreateBranchCommand.java:283)
>   at
> org.eclipse.jgit.api.CreateBranchCommand.call(CreateBranchCommand.java:136)
>   at
> org.eclipse.oomph.setup.git.impl.GitCloneTaskImpl.createBranch(GitCloneTaskImpl.java:1232)
>   at
> org.eclipse.oomph.setup.git.impl.GitCloneTaskImpl.perform(GitCloneTaskImpl.java:824)
>   at
> org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.doPerformNeededSetupTasks(SetupTaskPerformer.java:3324)
>   at
> org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.access$1(SetupTaskPerformer.java:3267)
>   at
> org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil$1.run(SetupTaskPerformer.java:4494)
>   at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240)
>   at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267)
>   at
> org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil.performNeededSetupTasks(SetupTaskPerformer.java:4488)
>   at
> org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil.access$0(SetupTaskPerformer.java:4486)
>   at
> org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performNeededSetupTasks(SetupTaskPerformer.java:3258)
>   at
> org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performTriggeredSetupTasks(SetupTaskPerformer.java:3233)
>   at
> org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.perform(SetupTaskPerformer.java:3133)
>   at
> org.eclipse.oomph.setup.ui.wizards.ProgressPage$9.run(ProgressPage.java:575)
>   at
> org.eclipse.oomph.setup.ui.wizards.ProgressPage$11$1.run(ProgressPage.java:701)
>   ... 1 more
>
> Even if I do it manually in the IDE, it produces this result.
>
>
>

> I.e., there are no Remote Tracking branches for some repositories. So
> the one repo above works, but the other (for JDT Core) always produces
> this ill-formed result.
>
> I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=528497 to
> track the issue.
>
> I'm concerned that we will release Oxygen with a serious JGit problem.
>
> Regards,
> Ed
>
>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev