On Thu, May 08, 2025 at 04:32:09AM +0200, Theo Buehler wrote:
> On Wed, May 07, 2025 at 07:38:29PM -0400, Daniel Dickman wrote:
> > numpy 1.x in the tree is a blocker for updating quite a few ports.
> > 
> > The main blocker for the update used to be boost. But now that we have 
> > boost 1.87 I think it's a good time to update numpy to the 2.x series. The 
> > diff below gets us to 2.0.2.
> > 
> > I have fixes for these which are all fairly straightforward and I can 
> > commit once numpy is at the 2.x series:
> >  astro/py-erfa (update 2.0.1.1 -> 2.0.1.3)
> >  graphics/py-matplotlib (remove hardcoded upper bound on numpy < 2)
> >  math/py-cvxpy (update 1.2.1 -> 1.6.2)
> >  math/py-numexpr (update 2.8.4 -> 2.10.2)
> >  math/py-scikit-learn (update 1.4.1post1 -> 1.5.2)
> >  math/py-scs (update 2.1.1-2 -> 3.2.6)
> >  math/py-tables (upstream wants numpy 2.x, but we patch it. undo our local 
> > patch)
> 
> Would you mind sharing a diff including these fixes? When running a bulk,
> every build failure costs some time triaging, and while most of these are
> nearly leaf ports, py-matplotlib has more than a dozen reverse deps.
> 
> Like for math/py-tables, landry had to relax a build requirement in
> geo/py-rasterio (and maybe elsewhere?). This can also be removed.
> 
> > These I'd like to mark BROKEN until they can be fixed by someone with an 
> > interest:
> > - graphics/piglit (very old and stale)
> > - x11/qt6/pyside/shiboken (core vs _core include path update is needed?)
> 
> While I'm fine with this, I know that jsg used to use piglit for drm
> stress testing and jtt might want to look into pyside.

Yes, piglit continues to be useful for that.

The complication is they stopped the github mirror and don't do releases.

I'm not sure if gitlab has hash stable git archives.  The FDO instance
also has Anubis in front of it.
https://gitlab.freedesktop.org/mesa/piglit

Reply via email to