Sebastian Krzyszkowiak @dos@librem.one

It appeared so unrelated that when I eventually ended up with a known-good upstream version that now seemingly turned bad and realized that the trees I used differed just by that one commit, the first thing I checked was whether I used the same compiler toolchain as CI did. And yet... 😂

Me plenty of hours ago: "There's a regression in a forked project's version that introduced one new downstream commit and about 5000 commits from upstream. That one commit looks obviously unrelated, so I have to bisect these 5000."

...guess which commit it turned out to be 😜

@TheEvilSkeleton As far as I can see the Firefox implementation is being actively worked on, so it should be just a matter of time.

@newbyte I don't follow... What would "fast charging A to C cable" even mean? The only way an A to C cable can differentiate is by whether it carries USB 2.0/3.0 signals or not.

@tomgwynplaine Ryszard Petru

@pojntfx Reminds me of late Openmoko's stuff (Paroli)

@brettm Let's say 96% 😜

(I should report that I guess)

@pluszysta Niemieckiego uczyłem się w szkole, a i tak łatwiej mi wchodzą do głowy piosenki po fińsku gdzie nie mam nawet najmniejszej intuicji jeśli chodzi o rozumienie znaczenia.

@hailey What's calling lvscan in initrd?

But anyway - my point was that a Debian system is expected to have recommended packages installed and it's not being tested for cases where they're not.

Doesn't mean you can't report these things and get them improved, but you're sure going to stumble upon more issues like that this way.

@hailey That's why lvm2 package recommends the package that makes it work.

In general, packages "depend" on things they absolutely need, and "recommend" things they need to ensure full functionality. There are weaker dependencies in Debian as well, called "suggestions", and these aren't being installed by default.

"The Recommends field should list packages that would be found together with this one in all but unusual installations."
https://www.debian.org/doc/debian-policy/ch-relationships.html#binary-dependencies-depends-recommends-suggests-enhances-pre-depends

@hailey It's there so system admin can make conscious case-by-case decisions without being limited by hard deps - so you can pull mdadm without a mail server, for example. Or so someone else can get rid of thin-provisioning-tools when they don't need them activated at boot 😉 But if you just blindly disable all recommendations you sure are going to have more such experiences as the one you went through today.

@hailey It's called "Debian without --no-install-recommends" 😁

(seriously though, it's kinda expected to break with that option; it's not a supported configuration)

@wolnoscwkieszeni Udzielam to ja się od 2008 gdy kupiłem sobie Openmoko Neo Freerunnera 😂

@wolnoscwkieszeni Nazwy to się akurat właśnie pozbywają 😄

A telefonów niby jak na lekarstwo, a i tak leżą w magazynie. Jak się nie będzie kupować więcej to więcej się nie wyprodukuje 😉

@wolnoscwkieszeni To trzeba budować, kupować i wspierać, bo w portowanie GNU/Linuksa na telefony Androidowe bawimy się od dobrych piętnastu lat i jest jak jest, a faktyczny progres nastąpił dopiero z tymi dwoma 😁

@wolnoscwkieszeni Ja używam Librem 5.

@wolnoscwkieszeni Używam wyłącznie PureOSa i nie narzekam. Mobian też niczego sobie. Razem z pmOS to chyba taka "święta trójca" właśnie.

@wolnoscwkieszeni A tu to przesada w drugą stronę. Z jednej strony odnosi się tylko do PinePhone, który nie jest przesadnie wystrzałowym sprzętem, a z drugiej połowa tej listy to projekty okołojednoosobowe ;)