Upstream has released git 2.13.3 on July 12: https://raw.githubusercontent.com/git/git/master/Documentation/RelNotes/2.13.3.txt It fixes several bugs. I was thinking about shipping this update, but tmb beat me to building it. However, it doesn't appear it has been assigned to QA yet. Assigning the bug to Thomas just to make sure it's ready to go. Updated packages in core/updates_testing: ---------------------------------------- git-2.13.3-1.mga6 git-arch-2.13.3-1.mga6 git-core-2.13.3-1.mga6 git-core-oldies-2.13.3-1.mga6 git-cvs-2.13.3-1.mga6 git-email-2.13.3-1.mga6 git-prompt-2.13.3-1.mga6 git-svn-2.13.3-1.mga6 gitk-2.13.3-1.mga6 gitweb-2.13.3-1.mga6 libgit-devel-2.13.3-1.mga6 perl-Git-2.13.3-1.mga6 perl-Git-SVN-2.13.3-1.mga6 from git-2.13.3-1.mga6.src.rpm
BTW, if/when it does get assigned to QA, I have a MGA6-64-OK already. I've been running this git version with issue for several days already.
Yeah, I wanted to test it a little before assigning to QA. assigning now, adding the OK according to comment 1, and advisory: subject: git 2.13.3 maintenance release src: 6: core: - git-2.13.3-1.mga6 description: | This update provides the git 2.13.3 maintenance release adding more fixes for SHA-1 collision detection, various bugs and regressions. For more info see the referenced relnotes. references: - https://bugs.mageia.org/show_bug.cgi?id=21406 -https://raw.githubusercontent.com/git/git/master/Documentation/RelNotes/2.13.3.txt
Assignee: tmb => qa-bugsWhiteboard: (none) => mga6-64-ok advisory
Keywords: (none) => validated_updateWhiteboard: mga6-64-ok advisory => mga6-64-ok advisory mga-6-32-okCC: (none) => nathan95, sysadmin-bugs
Whiteboard: mga6-64-ok advisory mga-6-32-ok => mga6-64-ok advisory mga6-32-ok
An update for this issue has been pushed to the Mageia Updates repository. http://advisories.mageia.org/MGAA-2017-0053.html
Resolution: (none) => FIXEDStatus: NEW => RESOLVED