Notices by Natanael Copa (ncopa@fosstodon.org), page 3

The not so good:

We got a bug report that was something like: "why don't you backport security fixes for some of the packages in community?"

us: "ok, which package is it?"

them: "I won't tell you. Its your job to know and its your job to fix".

And we had to deal with a violation of the Code of Conduct. Not fun at all.

Would have been so much nicer if we could get help find a solution for the problem instead of demanding complaints.

Don't be that person.

Fortunately, most people are nice

More of the good:

I took the time to register an account at kde bug tracker (I was surprised I didn't already have one! - or I just forgot the email address I used last time) - and file a bug. Within hours the fix was pointed to me and we could properly solve it.

I had the privilege to report back that the fix indeed works.

Feels good! Open Source can be very nice

This week I have experienced both the good and the bad with working with open source.

The good: Today I asked in gcc IRC channel about build failure of cross compiler. They were able the help me in the right direction and I found out it must be a bug in busybox awk. Feels so good to find that out, after banging my head into this for a couple of days. Ask for help early!

(still don't know exactly how busybox awk is broken 😨 )

Got a SiFive HiFive Premiere P550 dev board today. Thank you riscv.org!

#RISCV

@danct12
I replaced the fan with heatsink on my Banana Pi BPI-F3 to reduce noise. From my measurements of the CPU temp it seems to work better than the fan.

I just pushed linux-lts 6.12 to #AlpineLinux edge and this will be the kernel for Alpine 3.21.

@navi probably a good idea to avoid typedefs.

Linux kernel code style guide explains why
https://www.kernel.org/doc/html/v6.11/process/coding-style.html#typedefs

@dalias I git bisected it to this:
https://git.busybox.net/busybox/commit/libbb/dump.c?h=1_37_stable&id=e2287f99fe6f21fd6435ad04340170ad4ba5f6b3

The place where it fails in kernel build is here:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/firmware/efi/libstub/Makefile.zboot?h=v6.6#n9

I have sent a patch for a testcase that reproduces it to busybox mailing list

@sertonix or we could rename the standard iso to «netinst» or similar

I know I shouldn’t laugh but I can’t help it.

https://www.reddit.com/r/AlpineLinux/comments/1fyio9d/alpine_dont_install_and_deleted_windows/?utm_source=share&utm_medium=ios_app&utm_name=ioscss&utm_content=2&utm_term=1

I’m open to ideas how to prevent it happening again.

#AlpineLinuxAteMyWindows

I am trying to balance "don't break things" vs "move forward" in #AlpineLinux. Right now it feels like everything is broken, but at least we are moving forward(?).

@atomicthumbs
Congrats! you discovered the PID 1 zombie problem in Docker.

It is the responsibility of PID 1 to reap zombies. (see NOTES under wait(2). https://man7.org/linux/man-pages/man2/wait.2.html#NOTES)

You solve this with `--init`
https://docs.docker.com/reference/cli/docker/container/run/#init

@lanodan @domi @resingm

Unit tests, yes.

I had a struggle to get local ipv6 working in docker in github actions. I got it working eventually, but it would have been so much easier if it was enabled and just worked by default.

@weirdtreething @domi @resingm

Imagine how helpful it would be for you to be able to test it in CI, even if you cannot test it locally!

@feld @resingm

Aha! That explains.

So the real blame is on the DDoS hackers.

@resingm How can ISP adopt IPv6 if the open source software they rely on does not work with IPv6? And how can the open source software verify that things work on IPv6 if they cannot test it in CI?

The low IPv6 adoption is on GitHub.

@domi @resingm

But how do you switch to IPv6-first if you can't test it in your CI/CD pipeline?

My point is that we need GitHub users demand IPv6.

@resingm what I think is worse is that there is no ipv6 in the GitHub CI infra. GitHub host a big part of the worlds open source project but it is incredibly difficult for those to run test suites to verify that the ipv6 actually works. So it is no surprise that GitHub open source projects seldom test the ipv6 functionality.

@sertonix @postmarketOS also, we use OpenRC not because it is great but because we started with it decades ago and no good alternatives that officially supports musl has popped up since then.

@sertonix @postmarketOS yes. I don’t think we want support more than one init system. We don’t mind anyone packaging other init systems but you are pretty much on your own if you do.