Bug#1068174: yosys: Please package the latest upstream release

[Scott Ashcroft]

On Sun, 2025-03-16 at 17:34 +0100, Daniel Gröber wrote:
> Hi Steffen, Scott,

Hi.

> Nah. I'm too much of a perfectionist for that. I'd sooner switch to HTML
> output than have no docs in Debian at all (maybe we should enable those
> anyway?).

The HTML docs seem to use pip to pull in some python modules (including
one which has been forked by the yosys team) so are probably a lot more
work than getting the pdfs building.

> Now on to hard mode: autpkgtest. It seems debian/yosys-testsuite has lost
> it's precision. It runs through sucessfully but doesn't actually do
> anything. Upstream seems to have made some high-concept makefile changes
> that are breaking:
> 
>     # makefile-tests/ is a dummy string, not a directory
>     .PHONY: makefile-tests
>     makefile-tests: $(MK_TEST_DIRS:%=makefile-tests/%)
>     # this target actually emits .mk files
>     %.mk:
>         +cd $(dir $*) && bash run-test.sh
>     # this one spawns submake on each
>     makefile-tests/%: %/run-test.mk $(TARGETS) $(EXTRA_TARGETS)
>         $(MAKE) -C $* -f run-test.mk
>         + at echo "...passed tests in $*"
>     
>     test: makefile-tests abcopt-tests seed-tests
> 
> Haven't got the spoons remaining to figure that out today. Given a working
> sbuild setup autopkgtest is easy (if obscure) to run if you want to give
> this a shot. To re-use the binary .debs you already have:
> 
>     autopkgtest -B -s . -- schroot chroot:unstable-amd64-sbuild
> 
> -s is to get a shell on test failure so fail it intentially if you want to
> explore in the test environment.

OK. That should be fixed by b3e5bef48763537e8c992150e8363ac4112d4636
from https://salsa.debian.org/sashcroft/yosys

I say should because I couldn't figure out how to force schroot to use
my yosys binary packages and stop installing the old ones from
unstable.
In the end I just forced a test to fail, installed my stuff, and reran
the tests.

Cheers,
Scott