Hi,

Quoting Reinhard Tartler (2024-08-11 17:25:00)
> while looking at
> https://ci.debian.net/packages/r/reform-setup-wizard/unstable/arm64/50343230/ 
> I
> noticed that your package is using podman to run an autopkgtest:
> 
> https://sources.debian.org/src/reform-setup-wizard/1.0-7/debian/tests/control/#L1-L20
> 
> that's awesome!
> 
> However, the test above fails with:
> 
> 
> 120s + rm wayvnc.conf swayvnc.sh
> 120s + podman rmi -f swayvnc
> 120s Error: could not find "netavark" in one of [/usr/local/libexec/podman 
> /usr/local/lib/podman /usr/libexec/podman /usr/lib/podman].  To resolve this 
> error, set the helper_binaries_dir key in the `[engine]` section of 
> containers.conf to the directory containing your helper binaries.
> 
> 
> Please don't fail on this podman invocation or depend on the 'netavark' 
> package
> which is required for rootful podman. For rootless podman, you'll need to
> depend on the 'passt' package for getting networking setup.

thank you for having look at my silly little package! How did you come across
this failure? I hope this did not block anything for you? Thanks for filing
this bug!

I'm a complete podman-noop, so I'm happy that you are chiming in. Pulling in
the netavark package is easy but I wonder if this is a new behaviour? If you
look at other CI results on arm64, then it did succeed in the past and I why
that is if the test is missing a dependency:

https://ci.debian.net/packages/r/reform-setup-wizard/unstable/arm64/

I'm actually not so sure whether I want to keep having this autopkgtest in the
first place. The functionality of this package should maybe rather get checked
by openqa.debian.net because trying to find buttons on screenshots is very
fragile and there is a nasty big-endian bug hidden in my code which shows on
s390x.

Of course even better than scanning screenshots would be to use something like
dogtail but alas, automating interaction with gtk applications seems to be
non-functional under wayland because of intentional wayland design choices...

Anyways, I'll be helpful for any input you can give.

Thanks!

cheers, josch

Attachment: signature.asc
Description: signature

Reply via email to