Hi Chris,
Le 2025-01-08 15:54, Chris Hofstaedtler a écrit :
My experience is that if you don't have strong ties with people "on
the
inside" (or write 'provocative' email like I just did) you will mostly
be
ignored, plain and simple. The "normal" processes leads to dead ends
unfortunately.
Indeed. To me it seems like this is how all contribution-driven
projects work though: if you're not in a position to do something
yourself, the only thing left to do is either make yourself heard
loudly, repeatedly, in public, or discreetly find someone who can
help you directly.
I think that the fact that the project expect newcomer to follow a lot
of specific rules for each interaction (ITP, ITS, RFS, ... even
bugreporting is 'special') made me feel that it wasn't "the ordinary
contribution-driven project" and I expected a more formal follow-up;
like a balance between the energy I need to put to interact with the
project, "the project" puts energy to respond if I followed all the
rules.
Problem is that "the project" doesn't exist, only it's the volunteers
and their free time.
Anyway, that's an (interesting) social problem, but the technical one is
bellow...
[...]
> Segmentation fault (core dumped)
that's new to me.
I never tried to build it on aarch64, only amd64 :-/
This might very well be a compiler bug on aarch64, who knows.
I'm totally out of my comfort zone now ^^
So, I suppose i have to search for an old rpi3 somewhere at home and
get
back to work...
Can't promise to find an amd64 box that I trust enough to build
something for NEW anytime soon. If you can get it to build on
aarch64 that would be awesome.
I quickly rent an Ampere A1 (arm64) based VM in the cloud;
installed bookworm as the OS, installed sbuild from bookworm-backports;
and no problem to build the packages in an brand new arm64 unstable
chroot...
I'm lost.
What kind of hardware are you using ?
Chris
br,
Sébastien
