Sebastian Krzyszkowiak @dos@librem.one

Same thing in static form 😺 #librem5

Me: Is a photo taken with a phone a representation of what its camera saw or what its software believed to be there? 😼
Dyzio:

#catsofmastodon #shotonlibrem5 #darktable late #caturday #mobile #photography

@gamingonlinux I even see *developers* having that expectation when presented with complex systems.

@ptrc potrójna ściana ognia

@aeva It's true! Just browse itch.io and you'll quickly stumble upon them all 😁

@mcc @passcod Not exactly; it only updates remote-tracking branches, and there are no remote-tracking tags to update. So after `git fetch origin main` you would have it in `origin/main`, not in `main`.

I rarely use pull in git myself, I usually fetch and then decide what to do (merge, rebase or do nothing if not needed). Fetching tags has some special logic meant to make things simpler, but this sure can make things confusing too, especially when 99% of what you explicitly fetch are branches 🤪

@mcc @passcod You can specify the local ref to write to by using `:` notation, just like with git push. In general fetch doesn't touch local refs unless told to (though tags are a bit special, but not in this specific case).

@passcod @mcc Fetching branches works the exact same way.

@xethos @frameworkcomputer Looks like it's just a regular modem module not unlike the one on the M.2 card that's used with the Librem 5 though? Nothing open about it except the PCB that it's soldered to.

@aeva @mcc @azonenberg @astraleureka Phew, I just fixed a code like that a few days ago that I left there with a TODO a few months earlier - except it's 18 seconds these days 😂

@nanook @janvlug @mistersixt crimson is based on bookworm, but all the PureOS-specific changes need to be updated too and we're not done yet, so things remain broken meanwhile.

@nanook @janvlug @mistersixt We're talking about crimson, not bookworm.

@nanook @janvlug @mistersixt You must have a pretty low threshold of "flawless" then. Even hiding the splashscreen on app launch is broken right now, it always waits for the timeout to pass. Epiphany crashes on launch. No way to copy things from terminal. File diaglos aren't adaptive. Typing with OSK is broken whenever GTK4 shows a completion popup. And those are just the immediately visible ones, there are many more under the hood.

@primalmotion @mistersixt @janvlug Don't get me wrong, I'd probably install it myself too just to play with it early if I wasn't working on it :) I just need to make it clear that "everything still works as expected" isn't very close to truth when I can easily identify several annoying regressions just by using it for 5 minutes and I *know* that there are many more hidden a bit deeper because I've seen what was done there and even introduced some regressions myself :)

@nanook @janvlug @mistersixt https://master.pureos.net/depcheck/pureos/crimson/binary/arm64/1

And there was some cheating too - several vital packages got their patches dropped instead of rebased to get the images into buildable and testable state faster.

It's just not ready yet. If you use it regardless, you're 100% on your own.

@mistersixt @janvlug Crimson isn't even ready for developers yet, let alone users. There are many regressions over byzantium, many broken dependencies and many non-installable packages there. It was just barely cleaned up enough for images to build last week, and plenty of work is still needed to put it into shape. You can run it if you want, sure, but expect problems and don't expect any support.