On 2024-10-31 03:55:40, 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?
Ideally sage would support both old and new versions at the same time, so that not everyone has to upgrade at the same instant. Of course this is not always possible and/or can be a huge waste of time. You can force the sage distribution to build a local copy of libbraiding by changing its spkg-configure.m4 to detect some feature that is only present in the new version of libbraiding. That will fix the sage-distro CI runners, but most linux distros, and now the meson CI, won't be using the sage distribution at all. There may be some unfixable breakage in that case if you are e.g. waiting for conda to update libbraiding and conda is waiting for sage. That same conda-esque breakage will happen elsewhere too and will require everyone to quickly update libbraiding and patch their sage packages which is why it's best avoided if it's not too hard. -- 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/ZyOW8AZqD7WCjhr1%40mertle.
