@mks_h <--- @GTK probably has better things to do than https://xkcd.com/386/ ... It gets tiresome after so many years.
fosdem leadership: "people are saying that we are giving the coinscam fascist guy a keynote because he is sponsoring us, but this is a vicious lie--we are giving him the keynote because we just really like what he has to say!"
Nuntio vobis magnus gaudium, habemus Microsoft 3rd Party UEFI CA-trusted systemd-boot published in Debian unstable! It took many years of work to get here, and special thanks to Ansgar from FTP team and Philipp from DSA for the infra work!
$ sbverify --list systemd-bootx64.efi.signed
image signature issuers:
- /CN=Debian Secure Boot CA
image signature certificates:
- subject: /CN=Debian Secure Boot Signer 2024 - 20425036 - systemd-boot
https://ftp.debian.org/debian/pool/main/s/systemd-boot-efi-amd64-signed/
(arm64 too)
Remembering and thanking Steve Langasek https://discourse.ubuntu.com/t/remembering-and-thanking-steve-langasek/52665
Just received a "login from new location" warning mail stating the ip as my ipv6 address. Even though I got native #ipv6 setup for my home network last year, this still makes me feel like 2025 is finally the year for ipv6 taking off (from my personal perspective). Only took 20 more years than I expected.
Maybe I'm late, but I just noticed my ISP #bredband2 now offers me native #ipv6 via dhcpv6, including prefix delegation. Now have ipv6 enabled my local network. Can't find any info online about this change which has been requested for many years already. Why not announcement one might wonder.
@hrw can we while at it also stop talking about gdisk now that (c)fdisk has GPT support (since many years)?
@dusnm @ariadne @BrodieOnLinux I think company backing of Linux is great, but lets remember the companies are backing Linux because they have to and because it makes them money very much despite GPLv2. If a viable MIT licensed alternative shows up to be used in place of Linux, companies will dump Linux in a heartbeat (which I find very unfortunate, copyleft ftw).
@b0rk_reruns there's no need for 644, just use chmod u=rw,go=r foobar.txt ... You can even do relative changes like chmod u+r foobar.txt ... No need to mess your brain up with manually thinking of bits.
I'm old enough to have lived through the struggles of everything being proprietary and free software fighting its way up which made me an avis supporter, but in my experience younger people came in to the game when Open Source was already well established and thus take its existance for granted without ever thinking much about it. Companies also encouraging the workflow of building on top of and never contributing made this natural for them... Atleast thats how I see it.
@juliank "The implication graph building allows us to implement an apt why command, [...]" 🎉👏🥳
@mjg59 @neverpanic @TonyYarusso isn't that just one of the fundamental flaws of apparmour though? IIRC paths instead of inodes being the main reason apparmour was rejected from mainline for multiple years.
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.
@agrantler @bagder from my debian involvement I can attest to that users do expect people to have time machines!
Been offline and according to my ISP bredband2.com 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: https://github.com/dgraph-io/badger/pull/1205
"Our repository settings doesn't allow us to merge otherwise" <-- then go fix those settings!
"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?"