ah |

… expose these kinds of deps really nicely in their packaging metadata, if they just knew about them.

Hence, if the lack of dep metadata is the main big con of dlopen() deps, let's see if we can do something about it!

here's my proposal about this:

It's a very simple approach. All it does is insert an ELF "note" into generated binaries that declare these deps. This information can then be consumed by package managers, initrd generators and other tools.

Given recent online discussions I feel the need to share: My opinion on Code of Conducts is that they should not be needed, but if you are anti-CoC then you are the problem and the reason they exist.

Every internet of shit, phone, tablet, and other sorts of device manufacturers should be required to push/post a root unlock firmware for their devices before they can stop supporting them. There's too goddamn much ewaste from everything already. If they're going to abandon their devices, at least make it easy for people to unlock them and do whatever else they want with them.

“a compiler is when the dependency hell happens on the developer's computer, and an interpreter is when the dependency hell happens on the deployment target” - ohAitch

My number one wish from the fallout of the xz backdoor is that it kills autoconf/configure/autohell. That shit is illegible and watching for compile failure is a shitty way to test for features

💚 Stay strong xz maintainer(s). We're with you.💚

Everyone said get a Brother printer so I bought a 3-in-1 scanner and printer. There seems to be something wrong with it though. I plugged it into a Linux laptop, opened a document, pressed print, selected the printer, and it printed. Then I opened simple-scan, pressed scan, and it scanned.

This isn't how printers and scanners are supposed to work. Where do I install the drivers that don't work properly etc? This was no fun. I demand a refund.

@agrantler @bagder from my debian involvement I can attest to that users do expect people to have time machines!

The 2024 schedule is now available!

Don't miss out and make sure to get your tickets now!

Been offline and according to my ISP there was an "upgrade" of the Metropolitan area network (MAN). This caused BB2 to again put me behind #CGNAT (always these unannounced things happening when I'm away from home). As a nice surprise when this was addressed I noticed they started giving out native #IPv6 (finally!) via #DHCPv6, except their router is silently dropping all traffic that needs forwarding (so actually worse than nothing).... Why are all ISPs so incompetent?

@bagder this sounds like something which should have a name that ends with law. Stenbergs law maybe? :-)

Similar experience: pointing out where the bug is, being asked to submit PR to fix off-by-one (adding -1), being asked to sign CLA for something which is obviously not copyrightable work:
"Our repository settings doesn't allow us to merge otherwise" <-- then go fix those settings!

@mjg59 If I've learned anything from my decades of professional experience helping build products with yocto it is that the "correct" way to use yocto is to download the vendor built image, mount it, copy binaries inside. "What's patches? What's bitbake? Btw can you fix my broken manual cross compiler setup so I can build and statically link GPLed Qt into my proprietary application?"

@janne thanks!

Actually u-boot v2024.01 (final) is now in unstable (and should migrate to testing in >= 4 days)....

I can't help but think about the boot DING sound when I read about controlling "boot volume" via nvram tools, before next second remember what your actually talking about... Any chance someone has figured out how to disable the boot sound on M1?

#debian experimental now has u-boot-asahi. This together with already available m1n1 and asahi-fwextract you can now run update-m1n1 command and have all the bootloader parts from official debian repos. (Missing kernel and dtbs.)

BEWARE: This is a pure mainline u-boot, missing Asahi tree functionality like: M2 keyboard, multi-(Linux/BSD) booting and some USB parts.

A quick note that the new year started with asahi-audio being accepted inte the #Debian archive and swiftly updated to latest version. This means testing/unstable now has a complete userspace #Asahi audio stack! Still lacking an Asahi kernel in the official archive though, so check out for usable third parties (while we wait for mainlining of kernel parts)!

Another precondition for the #asahi audio stack in #debian on it’s way to unstable with lsp-plugins 1.2.14-1 upload.