[Debian-science-sagemath] Bug#835027: pari: please provide PARI 2.8.0[.alpha] in experimental

[Jerome BENOIT]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512



On 06/09/16 17:22, Ximin Luo wrote:
> Jerome BENOIT:
>> On 06/09/16 15:52, Bill Allombert wrote:
>>> PARI 2.8.1 will be released in about one month and will be
>>> API/ABI incompatible with 2.8.0. Then PARI 2.9.0 will be
>>> released. We should focus on PARI 2.9.0 and not be distracted
>>> with 2.8.0.
>> 
> 
> It's not usual for FOSS projects to make API/ABI changes across minor
> versions. And *especially* not to keep installation paths the same
> whilst doing so. What's the rationale for upstream to do this?
> 
>> Can you consider PARI 2.8.1 for experimental ? Do you plan to bring
>> PARI 2.9.0 to Debian before the big freeze ?
>> 
>> 
>>> Making valid Debian packages for PARI 2.8.0 is difficult, even
>>> in experimental. First the PARI library is not versionned the
>>> same way in stable and unstable release, so the packaging need to
>>> be adjusted to take that into account (something pari-sage does
>>> not do).
> 
> Could you explain what is meant by "not versioned the same way"? It
> seems that these two lists are identical:
> 
> https://packages.debian.org/jessie/amd64/libpari-dev/filelist
> (2.7.2) https://packages.debian.org/sid/amd64/libpari-dev/filelist
> (2.7.6)
> 
> and the versions (2.7.2, 2.7.6) seem very similar to me...
> 
>>> Secondly, such experimental packages must not interfer with the
>>> packages for PARI 2.7.6, so different package names and filepath
>>> needs to be used. pari-sage does not do that either.
>> 
>>> And then you have to change Sage to use the new names and new
>>> paths.
>> 
>>> You should just bundle pari 2.8.0 in the Sage tarball in the
>>> meantime. This would be far less disruptive. Then when PARI 2.9.0
>>> is released, you can move to that.
>> 
>> It is not tenable because then a full bunch a library must be
>> packaged against pari-sage. Please note that pari-sage is rather an
>> ad hoc package to step forward. We strongly wish to work with the
>> stable PARI material.
>> 
> 
> I think what Jerome means here is that we have other packages like
> cysignals that we need to build against pari-2.8.0. This makes it
> hard to "just bundle pari 2.8 with sage". Or if this isn't what you
> meant, could you clarify?

I exactly means this: it is not just cysignals, but also, according to
the Debian Sage page, at least eclib, lcalc. The list might be longer
because any mathematical software built against PARI can be potentially
used with Sage[Math].

> 
> I think, the best situation for now is just for us (debian sagemath)
> to package pari at version 2.8 and put it in our sid-sage APT repo.
> This would unblock our progress for the other items. We are nowhere
> near making a "proper Debian package" for sage yet, so we don't need
> to worry about co-installation and paths at this time. The important
> thing is to *unblock* other items so we can work on those.

I am agree. 

> 
> By the time that we are ready to upload Sage 7.3 (or 7.4), hopefully
> they will have upgraded to pari 2.9. Or if not, *then* we can think
> about how to solve this issue with 2.8 being an old unsupported
> version.

For unblocking (stepping forward) it is fine, but the sooner we can work with
a effective packaged version of PARI is the the better.

Thanks,
Jerome

> 
> X
> 

- -- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calculus@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B
-----BEGIN PGP SIGNATURE-----

iQQcBAEBCgAGBQJXzxOCAAoJED+SGaZ/NsaLs5sgAIYfqil3Kq5Xhq/DW8znD403
oee4RkNjz2eRiB6UyVNyxuc/kbWIIhBkvguMF9jde7Yjv+inuted3iJTqQXyQUS/
2DvNoUgDshvuHr0ErOw7M1T7EGmzeYhhQl1IOB3buBAwdyeE+PGo4k2gOLlQEZV0
nD5wnWbWIjW89+ofjonvZChI4R2BsLgPELxGc1xo2idvTfQtcW/GHOTk+Pex66Pj
RduJv668zTL6qENoZbt9TqGvuYnjxX3cln9my3giRkxm9UmKlb4ufNDepKRXhF0B
Ioad4HiYi14wy//7NJf4D8MS9W/ZL9cHRKRyBTV6GJhmzGYNPVp2X0PfSTQ87HNt
pvxQ4ytbfi5JQMIOcJbgrh8x/ZSq7xMB1xKjL+C9L6J7VthelMtKAyNn3QGgWNtx
Cf/lbiJQIvk3sdO3Ny9ld0R1SYTMksRaB8hE3zK+atPRlGzPz+BWY99M/ub3CrWJ
PgFlpkNZ8gcN0bx3+7B7Yzh3HgYVkwyKoyMghITs3dpiWPJLlHW/zNWYGA6wWacy
E7n1vgmv5Qm5Fupmq68gssI9fqKlLhDgLW5oZDiWXfgrt3zQ126qnOssGZDDy8Z7
B27GrgTDVOP7rQeVYCc1drJxUsYiRXpYd69BL+jx1/0kfh790apbSI8mgAamvCw9
bHmgs43279ubLbhYSMmOT+gv8r8w8pRznoQ/Q+MVWgDYzo1BgV6LNDzfjyJ2aYFL
mfzzk5oGpayOMWKeppL85AJqvkL5CLwGObXJHcljWfd5juFaUWXT36DGUnl6BJ/5
mWD9iSuUJNO9iSMHhAgoH0zvKypLf58WiOBF0m28bDIEV5Sqz8QosgLsdsQ6j9LM
kkp1spcfCRkF7tBfHv37K91oTuXNEQUn1fPyje4aqvWPQ1WkIhk1y5xrQuEkE6DC
4KozQIpGQdDYlnguw3jk9XzNKuLcnwz4Inw+spjSSbpqAEDg4tcXkS0ahdvOY8qL
v3/gDeeIWmO05KjwFmjZbBNoD6tuqPCIp70RJHDI/UjJL2UGscpHj9/Pjt3Mal1b
aLAkxoeeytduVWf/v7NrfIg1Ap6JodWTvfLXZQWNMjb56brDcIcDQ1PVVUjtq7Ve
5PdEIX3CG6nl//khVJPyQdrLwuXE15Sd5qIIX/oGECeu1HfceGHZe5gigzuPn92B
E3HNlZlS+rqxZ7rVLLBRB5ArUGYFXnQbttWrY6nWO3hGWdzLpqc3AfUQxr8mnmYk
SfbyPtPWO6s8Qo+UWiNVbGLpSia/XIypLe+LJTWRQmBfSn7uedeX9BuzTZOsuF2u
nf8Qn9dAJkXBGOmLmQKDCQ3+wLzDjm5cZNtBaL73WgFMvM3yYCbkaVcMIcbB+CE=
=fzKz
-----END PGP SIGNATURE-----