You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Git project recently announced a vulnerability in Git. The Git project doesn't declare what branches they consider as supported. All packagers can do is observe what branches get backports when a security issue is announced. In this case, the security fix was applied as far back as the 2.17 branch. That means Git 2.16 is now end of life upstream.
IUS previously shipped this branch as the git2u package, which was later renamed to git216. In approximately one month, all git216 (and git2u) packages will move to our archive repository and will no longer be maintained.
Users looking for an alternative have two other choices from IUS. We have the git222 package in our stable repos. We also have git224 in the testing repos, waiting for user feedback in the original request.
The text was updated successfully, but these errors were encountered:
The Git project recently announced a vulnerability in Git. The Git project doesn't declare what branches they consider as supported. All packagers can do is observe what branches get backports when a security issue is announced. In this case, the security fix was applied as far back as the 2.17 branch. That means Git 2.16 is now end of life upstream.
IUS previously shipped this branch as the git2u package, which was later renamed to git216. In approximately one month, all git216 (and git2u) packages will move to our archive repository and will no longer be maintained.
Users looking for an alternative have two other choices from IUS. We have the git222 package in our stable repos. We also have git224 in the testing repos, waiting for user feedback in the original request.
The text was updated successfully, but these errors were encountered: