Alexander von Gluck

This happens every time weave is deployed.

If I ```ipset destroy weave-kube-test```, it just gets recreated by the weave pod every time it attempts to start.

Seeing folks hacking in a sleep 1 before the ipset destroy call: https://github.com/replicatedhq/kURL/pull/717/commits/877767c3abf7f498574f9b2e4199e208683a4dca It's kind of messy, but maybe something that needs added until the race condition can be figured...

The solution listed above immediately fixed the issue for me

``` $ pkg-config --cflags openssl -I/packages/openssl-1.1.1k-1/.self/develop/headers $ pkg-config --libs openssl -L/packages/openssl-1.1.1k-1/.self/develop/lib -lssl -lcrypto ```

Hi! yeah, i'm one of the developers of the Haiku operating system (MIT Licensed). Recently got a MacBook Pro for work and wanted to see if I could improve the...

Master errors out during build vs during run.. same error: ``` $ /usr/local/bin/acbuild begin . begin: mkdir .acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci/rootfs/.acbuild/currentaci: file name too long ```

ah! The '.' after the begin seemed to be the cause. Removing the '.' results in a working image!

To give a bit more information i'd like to work on porting renpy to Haiku (which has pygame), but will need to port and package pygame_sdl2 which is a fork...

llvmpipe OpenGL rendering works fine on Haiku (mesa 21.3), as does SDL2. So pygame_sdl2 is going to be around for the long haul? If so I guess I need to...