Closed strogdon closed 8 months ago
Yes, it is likely that an upgrade in fplll
should trigger a rebuild of fpylll
. Unfortunately, I am not sure the latest update of fplll
changed the library soname and consequently the subslot. This is tricky when something that is only a header changes for example. But I think here the soname should have been changed since something has been removed. I'll check.
Yes, 5.4.0, which was removed a month ago and 5.4.2 have the same subslot. So, no automatic trigger. And checking fplll
they did not increase the right thing to take into account the symbol removal. No way to figure out that things will break.
On vanilla I have the failure
Rebuilding Sage's
fpylll
resolved the issue. So something changed. The same doctest failed on s-o-g and rebuilding the s-o-gfpylll
resolved things. Shouldfpylll
have been rebuilt automatically? I believe I can understand the vanilla issue since other system libs could be linked intofpylll
. But I don't know about s-o-g? This is with9.7.rc1
and I haven't tested since9.7.beta8
.