![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/4271bdc6-5114-4749-a5a9-afbc82a99c78.png)
They’re too busy compiling the 15678th generation of their systems
They’re too busy compiling the 15678th generation of their systems
There truly is something for everyone! :D
That’s really interesting!
The good news is it sounds like this issue is being taken into account.
Is there a part in that page that says so? I wasn’t able to find it
I wouldn’t be surprised if they added a YEAR2 though. T-SQL has a datetime2, after all.
Ok I wasn’t expecting that, it sounds like a meme, but it’s actually real lol
Yes 2 bytes is absolutely fine for me in fact (waiting for this comment to age like milk in my cryo pod), but then if YEAR will just stay the same forever, will it become a relic of the past? If so, why YEAR in the first place, who would actually make use of it?
Puce Screen of Panic
That’s class
You can keep all the lines of those who didn’t accept to the change with the original license, it will end up as a bad mix, but it’s doable if the licenses are compatible
It’s like Minecraft, but 2D
DivestOS on my tablet
Cool, there are supported tablets now?
Oh I thought that was only Artix, what does CachyOS use?
Non c’è scelta, se l’ultimo italiano dovesse lasciarci, allora anche questa informazione dovrà lasciare l’umanità
Rememeber, whenever you break one spaghetto you break one heart 💔
If the client (which encrypts the data in for an E2EE service) is open source and has also been audited by third parties than there’s little reason to do so
Here’s hoping that the bus and the truck don’t look our way 🥂
Seconded, @iso@lemy.lol is a great dude :)
Sure thing!
Edit: looks like it worked by pinning to community first, which removed it from local pins, and then also removing the community pin
You may not understand, but we do.
Questo segreto rimarrà custodito gelosamente dalla stirpe italica. ◉‿◉
And better error messages than “bro, you got a syntax error on this line”
Is that so? From the issue I read there was no way around it because the two images are fundamentally incompatible once you layer that package, you had to remove the layered package, it seemed from the discussion that they might have “fixed” the base image at some point as a pull request was opened on Pagure. I waited a bit for it to go upstream, but nothing happened for a long time and just went thorugh with the manual intervention, and actually, now that I check it again, the maintainer siosm commented that they can’t accept the PR
Doesn’t Bazzite have the base image modified to have the codecs included already? I think that’s probably why you didn’t experience any disruption there
- Full hardware accelerated codec support for H264 decoding.
link: https://github.com/ublue-os/bazzite/?tab=readme-ov-file#about--features
Could be, it looks pretty unknown for now though