Skip to content
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

Closed
mkoeppe opened this issue Apr 17, 2020 · 37 comments
Closed

Modify giac upstream tarball to remove non-portable filenames #29521

mkoeppe opened this issue Apr 17, 2020 · 37 comments

Comments

@mkoeppe
Copy link
Contributor

mkoeppe commented Apr 17, 2020

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:

$ find . -name "*:*"
./doc/pari/Programming_in_GP:_control_statements.html
./doc/pari/Programming_in_GP:_other_specific_functions.html
./doc/pari/cont_Programming_in_GP:_other_specific_functions.html
./doc/pari/cont_Programming_in_GP:_control_statements.html

(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

@mkoeppe mkoeppe added this to the sage-9.1 milestone Apr 17, 2020
@mkoeppe

This comment has been minimized.

@mkoeppe

This comment has been minimized.

@mkoeppe mkoeppe changed the title Upgrade giac to 1.5.0-87 Upgrade giac to 1.5.0-87 and fix non-portable filenames Apr 17, 2020
@dimpase
Copy link
Member

dimpase commented Apr 17, 2020

Upstream: Not yet reported upstream; Will do shortly.

@kiwifb
Copy link
Member

kiwifb commented Apr 17, 2020

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.

@dimpase
Copy link
Member

dimpase commented Apr 18, 2020

@dimpase
Copy link
Member

dimpase commented Apr 18, 2020

Changed upstream from Not yet reported upstream; Will do shortly. to Reported upstream. No feedback yet.

@sagetrac-parisse
Copy link
Mannequin

sagetrac-parisse mannequin commented Apr 18, 2020

comment:7

This is a problem that should be reported to PARI:
https://pari.math.u-bordeaux.fr/dochtml/html-stable.tgz

@kiwifb
Copy link
Member

kiwifb commented Apr 18, 2020

comment:8

Replying to @sagetrac-parisse:

This is a problem that should be reported to PARI:
https://pari.math.u-bordeaux.fr/dochtml/html-stable.tgz

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.

@sagetrac-parisse
Copy link
Mannequin

sagetrac-parisse mannequin commented Apr 18, 2020

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.

@kiwifb
Copy link
Member

kiwifb commented Apr 18, 2020

comment:10

xcas is the fltk application, right? I am not sure we ever build it in sage as we would have to make sure there is a proper fltk install and that it is detected properly. So, not shipping those won't hurt I guess.

@frederichan-IMJPRG
Copy link

comment:11

Yes xcas is never built by the spkg because we put in spkg-install:
sdh_configure --disable-gui
I did this long ago to prevent the configure script to find a bad version of fltk that might be installed on the system.

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Apr 18, 2020

comment:12

OK sounds like our just spkg-src needs to delete more stuff.

@dimpase
Copy link
Member

dimpase commented Apr 18, 2020

comment:13

Replying to @sagetrac-parisse:

This is a problem that should be reported to PARI:
https://pari.math.u-bordeaux.fr/dochtml/html-stable.tgz

apparently it's already fixed, for the upcoming release, i.e.
https://pari.math.u-bordeaux.fr/dochtml/html.tgz
I see no : in filenames.

For html-stable, I see


-rw-r--r-- 1 dimpase dimpase   26979 Jul 19  2016  Programming_in_GP:_control_statements.html
-rw-r--r-- 1 dimpase dimpase   39993 Dec  1  2018  Programming_in_GP__control_statements.html
-rw-r--r-- 1 dimpase dimpase   46872 Jul 19  2016  Programming_in_GP:_other_specific_functions.html
-rw-r--r-- 1 dimpase dimpase   78935 Dec  1  2018  Programming_in_GP__other_specific_functions.html

so these files with : are just leftovers, by looking at dates...

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Apr 18, 2020

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

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Apr 23, 2020

comment:16

Would someone who knows about the spkg-src be willing to update it?

@kiwifb
Copy link
Member

kiwifb commented Apr 23, 2020

comment:17

Replying to @mkoeppe:

Would someone who knows about the spkg-src be willing to update it?

I'll admit that I don't really want to touch it. I would probably have wanted to do the whole thing slightly differently.

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Apr 23, 2020

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Apr 23, 2020

Commit: 31d2b93

@mkoeppe

This comment has been minimized.

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Apr 23, 2020

New commits:

036dbbabuild/pkgs/giac/spkg-src: Remove files with nonportable names and other unneeded files
31d2b93build/pkgs/giac/spkg-src: Make the script work on macOS too

@mkoeppe mkoeppe changed the title Upgrade giac to 1.5.0-87 and fix non-portable filenames Modify giac upstream tarball to remove non-portable filenames Apr 23, 2020
@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Apr 23, 2020

Changed commit from 31d2b93 to 84df0e5

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Apr 23, 2020

Branch pushed to git repo; I updated commit sha1. New commits:

84df0e5build/pkgs/giac: New upstream tarball

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Apr 23, 2020

Changed upstream from Reported upstream. No feedback yet. to Fixed upstream, in a later stable release.

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Apr 23, 2020

Author: Matthias Koeppe

@kiwifb
Copy link
Member

kiwifb commented Apr 23, 2020

Reviewer: François Bissey

@kiwifb
Copy link
Member

kiwifb commented Apr 23, 2020

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.

@dimpase
Copy link
Member

dimpase commented Apr 23, 2020

comment:23

does this work? I would worry about - in the patch level.

@dimpase
Copy link
Member

dimpase commented Apr 23, 2020

Changed reviewer from François Bissey to none

@dimpase
Copy link
Member

dimpase commented Apr 23, 2020

Reviewer: François Bissey, Dima Pasechnik

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Apr 23, 2020

comment:25

Attachment: giac-1.5.0.63-p0.tar.bz2.gz

Branch pushed to git repo; I updated commit sha1. New commits:

081b1d2Fixup
a9b4666fixup

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Apr 23, 2020

Changed commit from 84df0e5 to a9b4666

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Apr 23, 2020

comment:26

This one works for me.

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Apr 23, 2020

comment:27

Using -p0 because that becomes part of the tarball name.

@dimpase
Copy link
Member

dimpase commented Apr 23, 2020

comment:28

afk now, but OK.

@kiwifb
Copy link
Member

kiwifb commented Apr 23, 2020

comment:29

I checked the bit I was worried about (whether some stuff in doc/Makefile.am could lead to a breakage) and I am definitely OK with this.

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Apr 23, 2020

comment:30

Thanks!

@vbraun
Copy link
Member

vbraun commented Apr 24, 2020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants