Re: [sage-devel] Re: System upgrades breaking sage frequently

On Wednesday, 3 August 2022 at 23:41:02 UTC-7 isu...@gmail.com wrote: > Can you try in a couple of hours and report back? > Yes, this time it looks like the instructions led to a successful build! Nice. -- You received this message because you are subscribed to the Google Groups "sage-devel

Re: [sage-devel] Re: System upgrades breaking sage frequently

Hi Nils, We need to rebuild primecount for the latest primesieve version. That's why an older primesieve version was used. I've opened a PR at https://github.com/conda-forge/primecount-feedstock/pull/7 Can you try in a couple of hours and report back? Isuru On Wed, Aug 3, 2022 at 11:44 PM Nils B

Re: [sage-devel] Re: System upgrades breaking sage frequently

Hi Isuru, I followed https://doc.sagemath.org/html/en/installation/conda.html#sec-installation-conda-develop except that for my bash, the long compound "configure" invocation didn't work (is that even correct bash symtax? my shell is pretty vanilla, so I'd be surprised if my shell rejects syn

Re: [sage-devel] Re: System upgrades breaking sage frequently

Hi Nils, Can you give me the commands that you did to get the primesive/conda error? I'd like to fix that. Isuru On Wed, Jul 27, 2022 at 4:52 AM Samuel Lelièvre wrote: > 2022-07-27 00:27 UTC, Matthias Koeppe: > > > > Only packages for which we have "spkg-configure.m4" scripts > > can be taken

Re: [sage-devel] Re: System upgrades breaking sage frequently

2022-07-27 00:27 UTC, Matthias Koeppe: > > Only packages for which we have "spkg-configure.m4" scripts > can be taken from the system More and more packages have such scripts. Many thanks to people who authored and reviewed the corresponding tickets: https://trac.sagemath.org/query?order=id&desc=

Re: [sage-devel] Re: System upgrades breaking sage frequently

On Tuesday, July 26, 2022 at 5:34:07 PM UTC-7 Nils Bruin wrote: > Things like not having to issue "sage -b" after making a little edit will > be nice to have eventually, > This feature (editable installs) is actually orthogonal to the decision on the conda install method. You can activate it u

Re: [sage-devel] Re: System upgrades breaking sage frequently

On Tuesday, 26 July 2022 at 17:27:11 UTC-7 Matthias Koeppe wrote: > Sort of. This is another way to build Sage with conda. It is described in > the 2nd of the 3 sections on the same page, > https://doc.sagemath.org/html/en/installation/conda.html#using-conda-to-provide-system-packages-for-the-sa

Re: [sage-devel] Re: System upgrades breaking sage frequently

On Tuesday, July 26, 2022 at 5:12:47 PM UTC-7 Nils Bruin wrote: > On Tuesday, 26 July 2022 at 15:58:18 UTC-7 Matthias Koeppe wrote: > >> >> Whether the method described in section >> https://doc.sagemath.org/html/en/installation/conda.html#using-conda-to-provide-all-dependencies-for-the-sage-li

Re: [sage-devel] Re: System upgrades breaking sage frequently

On Tuesday, 26 July 2022 at 15:58:18 UTC-7 Matthias Koeppe wrote: > > Whether the method described in section > https://doc.sagemath.org/html/en/installation/conda.html#using-conda-to-provide-all-dependencies-for-the-sage-library-experimental > > works always depends on the conda package mainta

Re: [sage-devel] Re: System upgrades breaking sage frequently

On Tuesday, July 26, 2022 at 2:08:32 PM UTC-7 Nils Bruin wrote: > > configure: error: > > Given --with-system-primesieve=force, but no system package could be > used. > That's an error. Please install the indicated package to continue. > (To override this error, use ./configure --wi

Re: [sage-devel] Re: System upgrades breaking sage frequently

Yup, rerunning "mamba env update -n sage-build -f src/environment.yml" installed eclib and now "./configure ..." produces one less error: configure: error: Given --with-system-primesieve=force, but no system package could be used. That's an error. Please install the indicated package

Re: [sage-devel] Re: System upgrades breaking sage frequently

On Tuesday, July 26, 2022 at 6:47:47 AM UTC-7 wst...@gmail.com wrote: > For CoCalc, [...] we run a 1-2 > pages long "./configure ..." command before I even do "make". At the > top it starts with > > --with-system-python3=no \ > --with-system-r=no \ > --with-system-primecount=no \ > --with-sy

Re: [sage-devel] Re: System upgrades breaking sage frequently

For CoCalc, where we have a bunch of different specific versions of Sage pre-installed that all stay stable over *years*, we run a 1-2 pages long "./configure ..." command before I even do "make". At the top it starts with --with-system-python3=no \ --with-system-r=no \ --with-system-primecount=no

Re: [sage-devel] Re: System upgrades breaking sage frequently

2022-07-26 07:13:30 UTC, Dima Pasechnik: this says that conda is behind Sage in regard of versions of eclib and primesieve/count - eclib upgrade in Conda now done: https://github.com/conda-forge/eclib-feedstock/pull/36 - primesieve and primecount seem up to date -- You received this message

Re: [sage-devel] Re: System upgrades breaking sage frequently

On Tue, 26 Jul 2022 at 08:13, Dima Pasechnik wrote: > > On Tue, Jul 26, 2022 at 8:24 AM Nils Bruin wrote: > > > > On Monday, 25 July 2022 at 12:53:08 UTC-7 Matthias Koeppe wrote: > >> > >> Have you tried the existing instructions that I pointed you to? > > > > > > I have now. I'm stuck on running

Re: [sage-devel] Re: System upgrades breaking sage frequently

On Tue, Jul 26, 2022 at 8:24 AM Nils Bruin wrote: > > On Monday, 25 July 2022 at 12:53:08 UTC-7 Matthias Koeppe wrote: >> >> Have you tried the existing instructions that I pointed you to? > > > I have now. I'm stuck on running configure. > > * the ./configure command suggested doesn't work in my

[sage-devel] Re: System upgrades breaking sage frequently

On Monday, 25 July 2022 at 12:53:08 UTC-7 Matthias Koeppe wrote: > Have you tried the existing instructions that I pointed you to? > I have now. I'm stuck on running configure. * the ./configure command suggested doesn't work in my bash. I'm getting: bash: unexpected EOF while looking for matc

[sage-devel] Re: System upgrades breaking sage frequently

On Monday, July 25, 2022 at 7:09:00 PM UTC-7 Nils Bruin wrote: > On Monday, 25 July 2022 at 18:55:54 UTC-7 Matthias Koeppe wrote: > >> >> https://doc.sagemath.org/html/en/installation/conda.html#sec-installation-conda-develop >> links to a different section, namely "Using conda to provide all >>

[sage-devel] Re: System upgrades breaking sage frequently

On Monday, July 25, 2022 at 6:39:35 PM UTC-7 Nils Bruin wrote: > I've not been able to find the version-specific rpm's at all (if I do "dnf > search flint" these things do not show up). [...] as far as I can tell, > /usr/lib64/libflint.so.17 is really owned by flint-2.9.0-1.fc36.x86_64 and > n

[sage-devel] Re: System upgrades breaking sage frequently

On Monday, 25 July 2022 at 18:55:54 UTC-7 Matthias Koeppe wrote: > > https://doc.sagemath.org/html/en/installation/conda.html#sec-installation-conda-develop > links to a different section, namely "Using conda to provide all > dependencies for the Sage library (experimental)" > Read that > Ah, OK

[sage-devel] Re: System upgrades breaking sage frequently

https://doc.sagemath.org/html/en/installation/conda.html#sec-installation-conda-develop links to a different section, namely "Using conda to provide all dependencies for the Sage library (experimental)" Read that On Monday, July 25, 2022 at 6:46:55 PM UTC-7 Nils Bruin wrote: > On Monday, 25 July

[sage-devel] Re: System upgrades breaking sage frequently

On Monday, 25 July 2022 at 12:53:08 UTC-7 Matthias Koeppe wrote: > On Monday, July 25, 2022 at 12:44:20 PM UTC-7 Nils Bruin wrote: > >> Can we get sage-on-conda modified so that it works nicely with git-trac, >> so that a sage-conda container can be used for development? I would be very >> inter

[sage-devel] Re: System upgrades breaking sage frequently

On Monday, 25 July 2022 at 12:57:06 UTC-7 Matthias Koeppe wrote: > On Monday, July 25, 2022 at 12:44:20 PM UTC-7 Nils Bruin wrote: > >> As long as fedora doesn't allow two different version of flint to be >> installed at the same time >> > > It does allow two different versions of the shared libr

[sage-devel] Re: System upgrades breaking sage frequently

On Monday, July 25, 2022 at 12:44:20 PM UTC-7 Nils Bruin wrote: > I think build-from-source using these kinds of system resources should > actually *not* be a recommended install method: > The installation guide (https://doc.sagemath.org/html/en/installation/index.html) only recommends it to

[sage-devel] Re: System upgrades breaking sage frequently

On Monday, July 25, 2022 at 12:44:20 PM UTC-7 Nils Bruin wrote: > As long as fedora doesn't allow two different version of flint to be > installed at the same time > It does allow two different versions of the shared library package to be installed. Please see https://trac.sagemath.org/ticket/

[sage-devel] Re: System upgrades breaking sage frequently

On Monday, July 25, 2022 at 12:44:20 PM UTC-7 Nils Bruin wrote: > Can we get sage-on-conda modified so that it works nicely with git-trac, > so that a sage-conda container can be used for development? I would be very > interested in a guide to that. > Have you tried the existing instructions th

[sage-devel] Re: System upgrades breaking sage frequently

On Thursday, 21 July 2022 at 11:52:42 UTC-7 Nils Bruin wrote: > On Thursday, 21 July 2022 at 11:31:35 UTC-7 Matthias Koeppe wrote: > >> >> You really just need to stop your distribution from automatically >> uninstalling the old shared library packages when you do upgrades. Both the >> old versi

Re: [sage-devel] Re: System upgrades breaking sage frequently

On Sat, 23 Jul 2022, 20:31 Emmanuel Charpentier, < emanuel.charpent...@gmail.com> wrote: > FWIW, the very same mishap just happened to me > > on Debian.testing. > > What I fail to understand is why Sake was linked to a *specif

[sage-devel] Re: System upgrades breaking sage frequently

FWIW, the very same mishap just happened to me on Debian.testing. What I fail to understand is why Sake was linked to a *specific* version of libflint.so, rather than to the *generic* version… ​ Le mercredi 20 juillet 202

Re: [sage-devel] Re: System upgrades breaking sage frequently

remix for WSL. This corresponds to Fedora 36, and I have installed Sagemath (9.6) with "dnf install sagemath." 　 Tomoaki Sato (cxn00...@nifty.ne.jp) > > From: Matthias Koeppe > Reply-To: sage-devel@googlegroups.com > To: sage-devel > Subject: [sage-devel] Re: Syste

[sage-devel] Re: System upgrades breaking sage frequently

On Thursday, July 21, 2022 at 11:52:42 AM UTC-7 Nils Bruin wrote: > Conda looks like it has potential too, > I'd say that's an understatement > It's presently unclear to me [...] whether a "production" conda build > could co-exist with a "development" conda build: is "conda activate" > somet

[sage-devel] Re: System upgrades breaking sage frequently

On Thursday, July 21, 2022 at 11:52:42 AM UTC-7 Nils Bruin wrote: > somehow register those packages *are* dependencies ... I guess that could > be done by building a placeholder package (rpm or deb) that declares all > the specific dependencies. And to "declare" these, one could install that >

[sage-devel] Re: System upgrades breaking sage frequently

I have opened https://trac.sagemath.org/ticket/34207 with the goal of adding documentation on best practices. Help welcome On Thursday, July 21, 2022 at 11:31:35 AM UTC-7 Matthias Koeppe wrote: > On Thursday, July 21, 2022 at 11:14:13 AM UTC-7 Nils Bruin wrote: > >> On Wednesday, 20 July 2022 a

[sage-devel] Re: System upgrades breaking sage frequently

On Thursday, 21 July 2022 at 11:31:35 UTC-7 Matthias Koeppe wrote: > > You really just need to stop your distribution from automatically > uninstalling the old shared library packages when you do upgrades. Both the > old version (needed for your from-source installation of Sage) and the new > v

[sage-devel] Re: System upgrades breaking sage frequently

On Thursday, July 21, 2022 at 11:14:13 AM UTC-7 Nils Bruin wrote: > On Wednesday, 20 July 2022 at 23:33:09 UTC-7 Antonio Rojas wrote: > >> >> They are not, that's exactly the point of library soversions. The >> soversion, if correctly used, is bumped when a release contains some ABI >> incompati

[sage-devel] Re: System upgrades breaking sage frequently

On Wednesday, 20 July 2022 at 23:33:09 UTC-7 Antonio Rojas wrote: > > They are not, that's exactly the point of library soversions. The > soversion, if correctly used, is bumped when a release contains some ABI > incompatible change that requires a rebuild of consumers. So you can't just > link

[sage-devel] Re: System upgrades breaking sage frequently

El jueves, 21 de julio de 2022 a las 7:32:59 UTC+2, Nils Bruin escribió: > In that case, shouldn't sagemath be linking to libflint.so instead of > libflint.so.16 then? That's the thing that seems to be available between > the different versions. Are they not ABI compatible? (or at least in one

[sage-devel] Re: System upgrades breaking sage frequently

On Wednesday, 20 July 2022 at 15:09:56 UTC-7 Matthias Koeppe wrote: > On Wednesday, July 20, 2022 at 3:05:44 PM UTC-7 Nils Bruin wrote: > >> I'm pretty sure that if a package has been "dnf install"-ed, then it's >> considered desired, and not just there as a prerequisite. >> > > Yes, but you like

[sage-devel] Re: System upgrades breaking sage frequently

On Wednesday, July 20, 2022 at 3:05:44 PM UTC-7 Nils Bruin wrote: > I'm pretty sure that if a package has been "dnf install"-ed, then it's > considered desired, and not just there as a prerequisite. > Yes, but you likely did "dnf install libflint-devel". The shared library package, in some vers

[sage-devel] Re: System upgrades breaking sage frequently

I'm pretty sure that if a package has been "dnf install"-ed, then it's considered desired, and not just there as a prerequisite. So preventing libraries from being removed should be as simple as including the requisite package in the recommended "dnf install ..." as written at: https://doc.sage

[sage-devel] Re: System upgrades breaking sage frequently

On Wednesday, July 20, 2022 at 1:55:52 PM UTC-7 Matthias Koeppe wrote: > On Wednesday, July 20, 2022 at 1:42:58 PM UTC-7 Nils Bruin wrote: > >> I've noticed that after a modest upgrade (just "dnf update"), with some >> regularity sage breaks. In the most recent edition, "libflint.so" couldn't >>

[sage-devel] Re: System upgrades breaking sage frequently

On Wednesday, July 20, 2022 at 1:42:58 PM UTC-7 Nils Bruin wrote: > I've noticed that after a modest upgrade (just "dnf update"), with some > regularity sage breaks. In the most recent edition, "libflint.so" couldn't > be found. > > I guess there is some prerequisite that sage was relying on to