-
-
Notifications
You must be signed in to change notification settings - Fork 522
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 pynac to support gcc-11 #31694
Comments
comment:1
There are still several pynac bug tickets that may not be hard to fix, so I think I will be posting quite a few more pynac patches in the next few months, so let's wait on this. But it would be good to make an upgrade before the 9.4 release. |
comment:2
Aren't you preparing your patches using git? I'd recommend to create pull requests to the pynac repo to make it more transparent. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:7
I am going to cut a new release of pynac with all da patchez |
Commit: |
Branch: u/dimpase/packages/pynac/0.7.28 |
Author: Dima Pasechnik |
New commits:
|
comment:9
Thank you Dima! :) |
comment:10
yah, thanks a lot! |
comment:11
Dave, I've merged all your pynac patches into master, e.g. while the log is clear they are yours, I'm still the author. If you like you can do a PR on github to change the author of these commits. |
comment:12
GH Actions run please |
comment:13
Replying to @mkoeppe:
running at https://github.com/sagemath/sagetrac-mirror/actions/runs/972993967 |
comment:14
Replying to @dimpase:
Thanks, Dima, that's great! I am not concerned about the "author", so nothing needs to be done, as far as I'm concerned. Copying these patches to the pynac repository has been on my to-do list for a long time, but I never got around to it, so thanks for doing this! In the future, I'll try to save you (and the distro managers) some trouble by making the appropriate PRs. |
comment:15
Replying to @DaveWitteMorris:
I guess you actually might have a git repo with these patches applied (at least this is how I typically do package patching), so it could have been a breeze to convert these into PRs. Anyway, it's done now. |
comment:16
One can set the author name and email as different from the committer's: $ git commit --author="Author Name <[email protected]>" This can be used to amend the last commit done: $ git commit --amend --author="Author Name <[email protected]>" --no-edit Reference:
|
comment:17
Replying to @dimpase:
gentoo failed bc system eclib wanted #31443
|
comment:18
Replying to @dimpase:
looks like that everything (modulo the usual GH actions suspects, e.g. broken conda on some platforms) is working. |
comment:19
Broken on |
comment:56
Dima, could you please make a release without PR 378, so that we can get this blocker ticket done? Just focused on what this ticket says - add support for gcc 11, consolidate existing patches; no breaking/removing of other platform support. |
comment:57
I volunteer to make the next pynac releases. |
comment:58
Replying to @mkoeppe:
let's just drop gcc 4.x. It would minimise the disruption, and it's overdue anyway. |
comment:59
As I said on #32074, I am +1 on this proposal to drop support for gcc 4.x. That should solve the immediate problem. |
comment:60
Or even better/quicker, just add |
comment:61
It's important to keep tickets focused. In particular for a blocker ticket like this one, which creates an urgency to get it in. The urgent need to add support for gcc 11 is entirely unconnected to a decision to drop support for the gcc 4 versions used in some of our supported distributions. It is poor practice to connect these two issues arbitrarily. |
comment:62
our resources are limited;
|
comment:63
It's important to keep tickets focused -- that includes avoiding to give unsolicited advice to other developers regarding time management. |
Changed branch from u/dimpase/packages/pynac/0.7.28 to u/mkoeppe/packages/pynac/0.7.28 |
Changed author from Dima Pasechnik to Dima Pasechnik, Matthias Koeppe |
New commits:
|
Reviewer: Matthias Koeppe, ... |
comment:67
tests run on https://github.com/sagemath/sagetrac-mirror/actions/runs/986545913 |
comment:68
lgtm |
Changed reviewer from Matthias Koeppe, ... to Matthias Koeppe, Dima Pasechnik |
comment:69
Thanks! |
Changed branch from u/mkoeppe/packages/pynac/0.7.28 to |
comment:71
I don't see this branch in the current develop branch, what's up? |
Changed commit from |
(from #31786)
pynac fails to compile with gcc-11 (headers porting) pynac/pynac#375
... and ideally to consolidate the various patches added in #31679, #31645 etc.... as also requested in https://groups.google.com/g/sage-packaging/c/_vxPV7aKNjQ/m/b2-EdWP1BgAJ
When making a new release, also care should be taken to use a recent version of libtool that supports macOS Big Sur (see #31920).
CC: @dimpase @DaveWitteMorris @kiwifb @antonio-rojas
Component: packages: standard
Author: Dima Pasechnik, Matthias Koeppe
Branch:
c9c50e3
Reviewer: Matthias Koeppe, Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/31694
The text was updated successfully, but these errors were encountered: