-
-
Notifications
You must be signed in to change notification settings - Fork 526
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
Modify giac upstream tarball to remove non-portable filenames #29521
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Upstream: Not yet reported upstream; Will do shortly. |
comment:5
Would be nice to do this. There are a few trivial doctests impacted by this. But I'll wait to know what upstream intend to do about the naming before going ahead. |
comment:6
please see https://xcas.univ-grenoble-alpes.fr/forum/viewtopic.php?f=3&t=2513 |
Changed upstream from Not yet reported upstream; Will do shortly. to Reported upstream. No feedback yet. |
comment:7
This is a problem that should be reported to PARI: |
comment:8
Replying to @sagetrac-parisse:
Thanks for that . Which now begs the question, should we install pari's html doc with giac? We already have the documentation which comes with pari, in pdf if I am not mistaken. |
comment:9
The HTML doc is intended to be used from Xcas (Help, Manuals, PARI-GP), I don't think you will need it to run giac inside sage. |
comment:10
|
comment:11
Yes xcas is never built by the spkg because we put in spkg-install: |
comment:12
OK sounds like our just |
comment:13
Replying to @sagetrac-parisse:
apparently it's already fixed, for the upcoming release, i.e. For
so these files with |
comment:14
A decision needs to be made whether for 9.1, we want to do the update to to 1.5.0-87 or just clean up the tarball of 1.5.0-63 |
comment:16
Would someone who knows about the spkg-src be willing to update it? |
comment:17
Replying to @mkoeppe:
I'll admit that I don't really want to touch it. I would probably have wanted to do the whole thing slightly differently. |
Commit: |
This comment has been minimized.
This comment has been minimized.
Branch pushed to git repo; I updated commit sha1. New commits:
|
Changed upstream from Reported upstream. No feedback yet. to Fixed upstream, in a later stable release. |
Author: Matthias Koeppe |
Reviewer: François Bissey |
comment:22
LGTM. I didn't even know you could use that syntax for tar under linux, looks much better now. Have to check a couple of things before switching it to positive. |
comment:23
does this work? I would worry about |
Changed reviewer from François Bissey to none |
Reviewer: François Bissey, Dima Pasechnik |
comment:25
Attachment: giac-1.5.0.63-p0.tar.bz2.gz Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:26
This one works for me. |
comment:27
Using |
comment:28
afk now, but OK. |
comment:29
I checked the bit I was worried about (whether some stuff in |
comment:30
Thanks! |
Changed branch from u/mkoeppe/upgrade_giac_to_1_5_0_87_and_fix_non_portable_filenames to |
http://www-fourier.ujf-grenoble.fr/~parisse/debian/dists/stable/main/source/
When preparing the reduced tarball with
spkg-src
,we should rename the non-portable file names with a colon in them:
(problematic at least on Windows - as reported in #28549.)
Previous updates:
Follow-up: #29552 (Upgrade giac to 1.5.0-87) ... for Sage 9.2
Upstream: Fixed upstream, in a later stable release.
CC: @antonio-rojas @dimpase @frederichan-IMJPRG @sagetrac-parisse @slel @infinity0 @saraedum @tobihan @timokau @kiwifb
Component: packages: standard
Author: Matthias Koeppe
Branch/Commit:
a9b4666
Reviewer: François Bissey, Dima Pasechnik
Issue created by migration from https://trac.sagemath.org/ticket/29521
The text was updated successfully, but these errors were encountered: