Daniel Markstedt

@aseering Thank you very much for your permission! I have prepared a PR here: https://github.com/Netatalk/netatalk/pull/1727 As a reminder to self: Test that the Linux arp cache fix doesn't confuse NetBSD.

For future consideration: util-linux has a mostly compatible reimplementation which has clearer attribution, and seeing active development. This could be an option for forking. https://github.com/util-linux/util-linux/blob/master/include/list.h

Interestingly, I found out the hard way today that macipgw code doesn't work correctly on aarch64 Linux. https://github.com/Netatalk/netatalk/issues/1735

The tests on both 2.x and 3.x have gotten unreliable on Linux specifically over the last few weeks, and I've not been able to figure out the root cause yet...

That's a good idea. TBH I've never used C at this level but it's a good learning experience. The odd thing, though, is that my main dev machine is affected...

It's worth noting that the tests are passing with 2.4.x code in the Arch job in our GitHub CI workflow: https://github.com/Netatalk/netatalk/actions/runs/10053455499/job/27786261358

I'd be very curious to see if the same issue happens if you get around to setting up the Meson build system in the same environment.

@VorpalBlade Random idea: What happens if you build the entire package with `-j1` (apart from taking a long long time)? With Meson, I was able to work around this by...

@VorpalBlade Would you have the opportunity to look at this again any time soon? Just a heads-up that we're working towards a netatalk4 release now, which will obsolete both netatalk2...

Closing this as won't-fix for now. Please reopen if you encounter the same issue with netatalk 4.0 or later!