Uploaded image for project: 'Maven SCM'
  1. Maven SCM
  2. SCM-973

GitCheckInCommandNoBranchTest fails with Git 2.34.0+

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

      Tests running on FreeBSD and Windows 10 gives me:

      ----------------------------------------------------------------------
      Provider message
      ----------------------------------------------------------------------
      The git-push command failed.
      ----------------------------------------------------------------------
      ----------------------------------------------------------------------
      Command output
      ----------------------------------------------------------------------
      remote: fatal: bad object refs/empty.txt
      fatal: bad object refs/empty.txt
      To file:///var/mosipov/Projekte/maven-scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/target/git_copy/
       ! [remote rejected] master -> master (missing necessary objects)
      error: Fehler beim Versenden einiger Referenzen nach 'file:///var/mosipov/Projekte/maven-scm/maven-scm-providers/maven-scm-providers-git/maven-scm-provider-gitexe/target/git_copy/'
      
      ----------------------------------------------------------------------
      

      The reason is in Git 2.34.0:

       * The ref iteration code used to optionally allow dangling refs to be
         shown, which has been tightened up.
      

      Source: https://github.com/git/git/blob/2ae0a9cb8298185a94e5998086f380a355dd8907/Documentation/RelNotes/2.34.0.txt#L68-L69

      We simply need to replace those broken refs with .gitkeep to retain dirs.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            michael-o Michael Osipov
            michael-o Michael Osipov
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment