What happens when a system package gets updated ?

[Emmanuel Charpentier]

I got mugged by a system’s (i.e. Debian testing) upgrade of libflint, going from 2.5.2 to 2.5.3. In Debian, libflint was libflint-2.5.2, with no “version independent” symlink libflint (nor even libflint-2.5). sage was linked “hard” against libflint-2.5.2.

Therefore, Sage crashed at start for lack of ibflint-2.5.2. Attempting to run configure again apparently succeeded but make failed to find the new library.

Workaround (compilation in progress) ./configure --with-system-flint=no ; make, which seems to involve a lot of other recompilations (including singular and arb…).

What is the recommended way to cope with such surprises ?

​

[Emmanuel Charpentier]

Well... that failed also : `sage` still searched for `libflint 2.5.2`.

Back to `make distclean && ./configure && make`, I guess...

[Dima Pasechnik]

such upgrades are not different from what comes with a Sage package update - rebuild everything that depends on it.

I don't know why you decided to build Sage's flint instead.

​

--
You received this message because you are subscribed to the Google Groups "sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/ccce2412-46a9-4e63-87b2-6d49252cdd1fo%40googlegroups.com.

[Dima Pasechnik]

On Mon, 31 Aug 2020, 07:58 Emmanuel Charpentier, <emanuel.c...@gmail.com> wrote:

I got mugged by a system’s (i.e. Debian testing) upgrade of libflint, going from 2.5.2 to 2.5.3. In Debian, libflint was libflint-2.5.2, with no “version independent” symlink libflint (nor even libflint-2.5). sage was linked “hard” against libflint-2.5.2.

this looks like a bug in Debian

Therefore, Sage crashed at start for lack of ibflint-2.5.2. Attempting to run configure again apparently succeeded but make failed to find the new library.

Workaround (compilation in progress) ./configure --with-system-flint=no ; make, which seems to involve a lot of other recompilations (including singular and arb…).

What is the recommended way to cope with such surprises ?

​

--

[Michael Orlitzky]

On 2020-08-31 02:58, Emmanuel Charpentier wrote:
>
> What is the recommended way to cope with such surprises ?
>

You just have to rebuild sage; it's a pitfall inherent to any software
not installed with your system's package manager. The package manager
knows to upgrade flint's "reverse dependencies" at the same time
(whenever the flint upgrade introduces backwards-incompatibilities), but
a git checkout of sage isn't so fortunate.