-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Thanks for your reply,
On 06/09/16 15:52, Bill Allombert wrote: > On Thu, Sep 01, 2016 at 09:29:28PM +0100, Jerome BENOIT wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA512 >> >> Hi, thanks for your reply. >> >> On 01/09/16 20:29, Bill Allombert wrote: >>> On Sun, Aug 21, 2016 at 02:37:11PM +0100, Jerome Benoit wrote: >>>> Source: pari >>>> Severity: wishlist >>>> >>>> Dear Maintainer, >>>> >>>> it appears that the current sage[math] (version 7.3) cannot build >>>> against PARI 2.7, >>>> while is might against PARI 2.8.0.alpha . >>> >>> As far as I understand SAGE use some unspecified GIT snapshot of PARI >>> and not an official release. >> >> There was a (long) discussion on the Debain Sage list about this >> mater, and it almost end up here. >> The latest stable version of Sage builds against PARI 2.8.0[.alpha] >> and the consensus among the Debian Sage Team is to stick to Sage >> version depending on official version of PARI. The point was made >> clear >> along the discussion. In short, we do not plan to use some unspecified >> GIT snapshot of PARI, but PARI 2.8. >> Can you package the version 2.8.0.alpha in experimental ? If you do >> not have time, I would be glad to >> open such an experimental branch. This will certainly save some energy. > > I discussed with upstream and having PARI 2.8.0 in experimental > is a bad idea. It is better to wait for PARI 2.9.0 to be released. Thanks for your asking. > > 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. 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). > 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. Thanks, Jerome > > Cheers, > - -- Jerome BENOIT | calculus+at-rezozer^dot*net https://qa.debian.org/developer.php?login=calcu...@rezozer.net AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36 C68B -----BEGIN PGP SIGNATURE----- iQQcBAEBCgAGBQJXzt4iAAoJED+SGaZ/NsaLvF8gAMQkFh9SNHXT/uA+rNfc56DV EWNhx9E2qidIaVXe+d5TLKygvVqGb4GKvbVIDqT8Zjep4gtBLe80FkZGVqBPiF3b kKrm5vD3vz86lu6FbJPflOeyimeh3+0u931DseoyI8LpQh8jy0Zh4fjnLBcaXx9o zAvrh9T2s+qGdMsrwYchPXVj2+s0ZBeyJLjq6u/QLLPRvDaaqNjZ40CiaoIBNIIK qkAyi64Ztdv6+5U0hRVg7/tQew2fBVaZdOLvo3wWmVgA3eSIvgE9Qy7Vbovb1Yod sk5yABhVinyxYJ6hCye6Q1Dv2II5fJhdQ3MXt9sXeeTvgslXH0eApVd7OFh5xRdN +V1B2mpVSj9HqeCmhkRFk56sHh4q8seVDRWWZAAc9eTp+MpUG4vt7cfYy7GsiilT WhnBGsAI2yN17LIw59O74jEOQlwwhP1Q2qh6cw8IV2dknxr+4zIJGH9PsCKWiSfc Qt9ulHFSNq9PIf/gyIK8IhmvgJXptGdDW+PJ/+ATsa9Ycw9nAJ8t2CDnDyzXbKZn P1rpQvhPWCcmywL4KgHLOX/7hAAcl6b0JFP+WoCAAyhbDA3WMBO1BkMCCDRK5xvT rI8JbZ7lsWNZDgskXmwvJrMnRRPuh5YE4dwoKIrgAZjGLwd4KjgHCQaQ1dQdzqxJ DIsyGTnlhodli7khSdZ8gBr8D7VQjisYXhDnatK+dL+hMq4BqmBi8hUEz4UjBbuK i2/sJN3UTCFynzUlk6AMTa5aFY7CeqetCkJjEDHCqTiIDVa5h0F3HlNGj3x3/w9F vUR9JV0kmP8Phcs2a0czVP9OfruE6LgoKPBvyG08nkQpdzn0+pf8SWpB3h5VIBCS AmnAnvp6TIuZgsXe28jWDN5TpLKiEh/N8Z7X3aiFe63xJDlhG8gNugqP36OwEmDr CugRHcoD5CCzSV2JjjEXwIy1Bv7gCsXg+aADxFlQJttMb2apn+6TBSJyVtkHutJm nBX/4VS7+m86FvUSKydUW5Qx3XFMUhLsL2mHxS2dWjMtPjX5FAzwuCVIP43b1Shk ADBLB9baVB39vfY+uKY+Xgkpt/7RPnmaeXxdrOFGE7TnAIOumYy+znkUZ/2a39C3 0dslf4gJ8CAbTt9NpE+DL83FWecNuRW/jlxtjgHRneBfa9GcwhVQB+iRQawhZs+w LqJ5lbalp60vXvGgn7jJMS35b4t5K4rj/LKiNQ6E1nuo2r2jwYL+ZdiBC2CiqWcb CmeOYAwkEuPrSG7CYZUQDLUfvvkLbpOMXfp57gYsl7vTqtp/M7tpUPAj91P7Y9KF tnYo8ZEKgB2hFloyksouLfqKYwcc1kDtZa4JB1wV3+MS9mWOzxVjvfzaJhAgcB4= =pC/z -----END PGP SIGNATURE-----