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 sympow to 2.023.6 (for GCC 10 support) #3360
Comments
comment:1
The latest release is 1.023 at http://magma.maths.usyd.edu.au/~watkins/sympow.tar.bz2 Cheers, Michael |
This comment has been minimized.
This comment has been minimized.
Changed keywords from none to upgrade, sympow |
comment:7
Didn't realise there was a newer version. Considering sympow's code, an upgrade can only be an improvement. |
comment:8
See also #25099 "Add DESTDIR support for sympow". |
comment:9
sympow 1.023 segfaults (in Debian) on some inputs that used to work with 1.018
|
comment:10
This is essentially a known bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863919. I submitted a patch for it on salsa: https://salsa.debian.org/science-team/sympow/merge_requests/1. |
comment:12
In an effort to update the sympow package in nix, I contacted the debian maintainer (Jerome Benoit). He told me that he really did receive their tarball in a private email (how did you guys manage to find that file on his homepage?). He also told me that "the upstream author is responsive (and he did not have a GIT because the code was written before the GIT revolution)". Debian adds sage's patches and some more[1], as for example the bug fix saraedum mentions. It seems like Debian effectively became the new upstream of this package. I asked the maintainer if he had considered making it official and forking it, which he declined. [1] https://salsa.debian.org/science-team/sympow/tree/master/debian/patches |
comment:13
Replying to @timokau:
In my case: I wrote a private email to the sympow author and he told me about the URL.
I was in correspondence with the sympow author about the recent segfault patch. Afterwards I proposed to move the project to github and basically take over maintenance but I have not heard back for a while since then. |
comment:14
Is the URL still valid ? |
comment:15
sympow still seems to be hosted at that URL. Its just not advertised anywhere. But there are still all those semi-mandatory patches flying around that should probably be upstreamed. Having the project in some public version control would be great. |
comment:16
My notes about the url at |
comment:17
I am on my way to fork sympow on gitlab. My concern will be only the unix part (read not the mathematical part) in view to harmonize related patches and integration in unix systems. |
comment:18
Great! Thank you for doing that. |
comment:128
|
comment:129
on what machine |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:131
Tests run at https://github.com/mkoeppe/sage/actions/runs/187726088 |
comment:132
Builds correctly on all platforms. |
comment:133
Fedora 32 x86_64 for the record |
comment:134
Replying to @vbraun:
Thanks. Works fine on both |
comment:135
Still doesn't work. My build log has a
thats not in yours; Build race with pari/gp? Seems like this would explain the |
comment:136
Yes, seems like we may need to add pari as a dependency |
Changed branch from u/mkoeppe/sympow-2.23.2 to |
Fork now maintained by the debian sympow maintainer (gh-jgmbenoit).
https://gitlab.com/rezozer/forks/sympow
Upstream URL: see checksums.ini
See also:
Upstream: Reported upstream. No feedback yet.
CC: @slel @timokau @saraedum @isuruf @antonio-rojas @orlitzky @embray @dimpase @tscrim
Component: packages: standard
Keywords: upgrade, sympow
Author: Timo Kaufmann, Matthias Koeppe
Branch/Commit:
2e3dd4d
Reviewer: Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/3360
The text was updated successfully, but these errors were encountered: