-
-
Notifications
You must be signed in to change notification settings - Fork 491
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to gc 8.0.4 and libatomic 7.6.10 #26287
Comments
comment:1
the branch has a bit misleading name. |
This comment has been minimized.
This comment has been minimized.
comment:2
Note: gc 8.02 was released on 2018-12-23. |
Changed keywords from none to upgrade, gc, libatomic |
comment:3
there is also a newer 7.6 release there, namely 7.6.10. |
comment:4
Did you mean to put the ticket in needs_review? |
Changed branch from u/dimpase/packages/gc786 to u/slelievre/packages/gc786 |
New commits:
|
Changed keywords from upgrade, gc, libatomic to upgrade, gc, libatomic, days101 |
This comment has been minimized.
This comment has been minimized.
comment:9
I'm testing on Cygwin; don't anticipate any serious problems (though we need to do gc and libatomic for #27330). |
comment:10
Works for me. Could we move on ? Erik, what's the status on Windows ? |
comment:11
Ticket retargeted after milestone closed |
Changed branch from u/slelievre/packages/gc786 to u/mkoeppe/packages/gc786 |
This comment has been minimized.
This comment has been minimized.
Changed author from Dima Pasechnik to Dima Pasechnik, Samuel Lelièvre, Matthias Koeppe |
Reviewer: Isuru Fernando |
Changed branch from u/mkoeppe/packages/gc786 to |
Routine updates to the latest stable versions, to keep in lockstep with (some) distros.
Tarballs:
The
libatomic_ops
update is needed for #29327.CC: @antonio-rojas @embray @kiwifb @isuruf @slel
Component: packages: standard
Keywords: upgrade, gc, libatomic, days101
Author: Dima Pasechnik, Samuel Lelièvre, Matthias Koeppe
Branch/Commit:
c335ef8
Reviewer: Isuru Fernando
Issue created by migration from https://trac.sagemath.org/ticket/26287
The text was updated successfully, but these errors were encountered: