Broken CI/CD

[George Sapkin]

A package for which any subpackage that has executables in default
paths like /usr/bin, /usr/sbin, etc., with all of those executables
not passing the generic version checks, you need to add a
test-version.sh script at the same level as the package Makefile. In
that script you need to add a custom version check for each subpackage
of that package passed via $PKG_NAME, or skip the version check by
e.g. exit 0. The "untested package" guard is there so the checks fail
when a new subpackage is introduced.

I hope this explains the python3 example from before. Alternatively I
can add these test scripts for both packages.

George

On Tue, May 26, 2026 at 8:03 PM Philip Prindeville
<philipp_subx at redfish-solutions.com> wrote:
>
> Sorry, how do these work?  This seems to be something recent and I might have missed the hullabaloo about it.
>
> Seems there are three actions.
>
> exit 0
>
> $PKG_NAME -h 2>&1 | grep -F "$PKG_VERSION"
>
> echo "Untested package: $1" >&2; exit 1
>
> For strongswan and its many subpackages, which result is appropriate for which?
>
> I'm guessing the last one matches "*"... but for the first two?
>
>
>
> > On May 25, 2026, at 2:31 PM, George Sapkin <george at sapk.in> wrote:
> >
> > bind-ddns-confgen and strongswan-gencerts fail the generic version
> > checks so they need an override. You can check how it's done in
> > packages with test-version.sh, for example the one in
> > lang/python/python3/test-version.sh.
> >
> > libreswan-iptables doesn't install in snapshot either and needs to be fixed:
> >
> > root at OpenWrt:~# apk add libreswan-iptables
> > ERROR: unable to select packages:
> >  firewall4-2025.03.17~b6e51575-r2:
> >    conflicts: firewall-2025.10.03~3a65fde5-r2[uci-firewall=2025.03.17~b6e51575-r2]
> >    satisfies: world[firewall4]
> >  firewall-2025.10.03~3a65fde5-r2:
> >    conflicts: firewall4-2025.03.17~b6e51575-r2[uci-firewall=2025.10.03~3a65fde5-r2]
> >    satisfies: libreswan-iptables-4.12-r4[firewall]
> >  libreswan-4.12-r4:
> >    conflicts: libreswan-iptables-4.12-r4[openswan=4.12-r4]
> >    satisfies: libreswan-iptables-4.12-r4[libreswan]
> >  libreswan-iptables-4.12-r4:
> >    conflicts: libreswan-4.12-r4[openswan=4.12-r4]
> >    satisfies: world[libreswan-iptables]
> >
> >
> > George
> >
> >
> > On Mon, May 25, 2026 at 9:19 PM Philip Prindeville via openwrt-devel
> > <openwrt-devel at lists.openwrt.org> wrote:
> >>
> >> The sender domain has a DMARC Reject/Quarantine policy which disallows
> >> sending mailing list messages using the original "From" header.
> >>
> >> To mitigate this problem, the original message has been wrapped
> >> automatically by the mailing list software.
> >>
> >>
> >> ---------- Forwarded message ----------
> >> From: Philip Prindeville <philipp_subx at redfish-solutions.com>
> >> To: openwrt-devel <openwrt-devel at lists.openwrt.org>
> >> Cc:
> >> Bcc:
> >> Date: Mon, 25 May 2026 12:16:19 -0600
> >> Subject: Broken CI/CD
> >> Looking at the pipeline, on multiple PR's, the same architectures are failing (though not always in the same way).
> >>
> >> Anyone looking at this?
> >>
> >> https://github.com/openwrt/packages/actions/runs/26407817081/job/77748639498?pr=29556
> >> https://github.com/openwrt/packages/actions/runs/26361111256/job/77753564125?pr=29313
> >> https://github.com/openwrt/packages/actions/runs/26382281948/job/77675629013?pr=29547
> >>
> >>
> >> _______________________________________________
> >> openwrt-devel mailing list
> >> openwrt-devel at lists.openwrt.org
> >> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>
>