On Tue, Sep 30, 2025 at 9:50 AM Marc Culler <[email protected]> wrote:

> I was able to build sagelib by replacing sage/local/include/boost (as
> installed by the boost spkg) with a copy of that same directory from
> boost-1.89.0.
>
> So, moving on to the next build failure, I was unable to download
> sage_numerical_backends_coin.  It is no surprise that the file is not on
> any Sage mirror.  But it seems that the upstream url is also incorrect:
>
> raise FileNotMirroredError('tarball does not exist on mirror network and
> neither at the upstream URL')
> sage_bootstrap.tarball.FileNotMirroredError: tarball does not exist on
> mirror network and neither at the upstream URL
> Exception ignored in: <http.client.HTTPResponse object at 0x1092bdff0>
> Traceback (most recent call last):
>   File
> "/private/var/tmp/sage-10.8-current/local/lib/python3.13/http/client.py",
> line 432, in close
>     super().close() # set "closed" flag
>   File
> "/private/var/tmp/sage-10.8-current/local/lib/python3.13/http/client.py",
> line 445, in flush
>     self.fp.flush()
> ValueError: I/O operation on closed file.
> ************************************************************************
> Error downloading tarball of sage_numerical_backends_coin
>

sage_numerical_backends_* have been broken for more than a year.
Help needed.
They rely on outdated setup mechanics. As well sage_numerical_backends_coin
relies on the  cbc spkg, which also needs an update,
but on the other hand it's buggy.

cbc is just a relatively efficient LP/ILP solver, but currently we are
spoiled for choice.
E.g. there is HiGHS, an actively maintained MILP/LP solver, hooked up on
scipy
https://scipy.github.io/devdocs/reference/generated/scipy.optimize.milp.html

Dima

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion visit 
https://groups.google.com/d/msgid/sage-release/CAAWYfq3_dGwX%3Dt-SReFDCFeCr%3DdcrKnx3Bi_WqFRB5S%3DxMC%2B4Q%40mail.gmail.com.

Reply via email to