jira-importer opened a new issue, #1197:
URL: https://github.com/apache/maven-scm/issues/1197

   **[Michael 
Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)**
 opened 
**[SCM-973](https://issues.apache.org/jira/browse/SCM-973?redirect=false)** and 
commented
   
   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.
   
   
   ---
   
   **Affects:** 1.12.0
   
   **Remote Links:**
   - [GitHub Pull Request #133
   ](https://github.com/apache/maven-scm/pull/133)
   
   **Backported to:** 
[1.12.1](https://github.com/apache/maven-scm/milestone/31?closed=1)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to