Bug#1111141: systemctl ends in assertion failed on armhf

[Luca Boccassi]

On Fri, 15 Aug 2025 at 11:51, Marc Haber
<mh+debian-packages at zugschlus.de> wrote:
>
> Hi Luca,
>
> On Fri, Aug 15, 2025 at 10:50:14AM +0100, Luca Boccassi wrote:
> >Control: tags -1 forwarded https://github.com/systemd/systemd/pull/38587
> >
> >On Fri, 15 Aug 2025 07:35:28 +0200 Marc Haber
> ><mh+debian-packages at zugschlus.de> wrote:
> >> Package: systemd
> >> Version: 258~rc2-2
> >> Severity: serious
> >>
> >> Hi,
> >>
> >> on my only Banana Pi with unstable, after updating to current
> >unstable,
> >> all systemctl calls end up with a failed assertion:
> >
> >Any chance you could please help test the following on your hardware?
> >The only arm porterbox we have runs on arm64 with a 64bit kernel so
> >can't reproduce it there, and I can't see any other native 32bit
> >porterbox either, and I don't have any hardware
>
> systemd takes about a day to build on that hardware, and I'd rather not
> cross-build to debug in this hardware-related matter, and I will be
> traveling to FrOSCon in an hour. It is unlikely that I will have results
> before wednesday next week.
>
> And, the Banana Pis are on the way out, I actually contemplated to
> decommission the only Banana Pi unstable system that I have left quicker
> than intended.
>
> I apologize but I'll probably be out of the debugging loop for a few
> days. I have just started the build though.

Ok, in case it helps, 'ninja -C build systemctl' will only build that
binary, so should take a fraction of the time, even though that might
still be slow