On Thursday 31 October 2024 at 03:55:41 UTC-7 mmarco wrote: I recently released a new version of libbraiding that exposes new functionality, in order to use those new functions from Sage (see #38887).
However, the CI tests fail because they use the old version (taken from the system, instead of installing the new spkg). Which is the right way to proceed in this case? Should I somehow force the containers to build the new spkg? Would this be caught by changing the version requirement? Then the old version provided by the system wouldn't satisfy sage's version requirement any more, so wouldn't that push sage to install its own? -- 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+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/sage-devel/df829e62-29bd-41ac-a500-7edb4a986e22n%40googlegroups.com.
