[Pkg-electronics-devel] Bug#1152532: Bug#1152532: nextpnr: unbuildable in sid

[Gianfranco Costamagna]

Hello!



>You'd need all the changes in himbaechel/uarch/gatemate (18 commits 
>IIRC), plus their dependencies in common parts, to get something that 
>has a chance of actually working.
>
>If an Ubuntu release is close enough that you need a working version 
>right now, we could possibly make a 0.11.1+gitXXXX intermediate version, 
>but generally speaking, upstream changes so much between versions that 
>using tagged versions is the better choice.

the release is 6 months away, but I'm trying to rebuild against new boost, 
and having something that doesn't build is preventing decruft of old library...
but no hurry at all, indeed

>Uploading prjpeppercorn 1.14 was a mistake (and I held back for a few 
>months back when 1.13 came out for the same reason) -- but I wonder why 
>Ubuntu picked it up if it breaks the Build-Depends of nextpnr.

I guess it was auto-syncd, or don't know

>Unrelated: can Ubuntu deal with Build-Depends-Arch: on the arch:all 
>packages from the same source? There are two WIP branches on Salsa[1], 
>and one of them is a horrible hack that might or might not work on 
>Ubuntu (but it saves a few days of autobuilder time on each upload, so...).

I guess not, sadly. We usually do a build with some nocheck/stage1 profile enabled, then we upload
a new version that takes it from the previous built package.

In 2026 bootstrapping packages is still a nightmare

G.