Search
1000 results for “gentoo”
-
Kolejny dzień, kolejna paczka #RustLang, która nie ufa dzielonym bibliotekom i zamiast tego używa swojej przypadkowej wersji #libwebp. A potem nagle trafia się CVE i z łaski swojej rozważa dopuszczenie możliwości statycznego wiązania z systemową biblioteką — tyle że było to półtora roku temu, i nic od tego czasu się nie ruszyło. A ja teraz się użeram z łataniem tego szajsu, bo coś się sypie użytkownikom #Gentoo, i jedyne co mi przychodzi do głowy to to, że włączona wersja libwebp kłóci się z systemową, której używa gtk4.
-
Sigh. Another day, another #RustLang packages that doesn't trust shared libraries and instead bundles random version of #libwebp. Then hits a CVE and starts considering graciously permitting people to maybe statically link to the system library — except that was 1.5 year ago and nothing happened since. And now I'm patching that crap because shit is falling apart for #Gentoo users, and my best guess is that vendored libwebp is conflicting somehow with shared libwebp that gtk4 links to.
-
-
I had the stupid idea to try to do some #AdventOfCode riddles in #TIBasic on my #TI92 calculator (once I'm done with Advent of Code 2023 in Lean). To do that I need some way to copy the input over to the calculator, but the official software from TI does not support Linux.
However, I am positively surprised to see that #Gentoo Linux has TILP2 - an open source #TI92 linking software - in its official repositories.
-
What a pleasant surprise, I thought I'd boot in to my new Gentoo install to see if I could repair the issue.
It booted straight to the desktop.
Very happy.
Now to work out why I can't get sound to work.
-
@peppe well fuck me, I left everything compiling while I eat dinner.
Come back to a black screen yet, the entire PC is still running. Completely unresponsive, nothing seems to be actually working.
So I had to hard reboot, and I am welcome with another black screen.
I have lost patience for today.
-
-
New on blog: "Poetry(-core), or the ultimate footgun"
"""
I've been complaining about the Poetry project a lot, in particular about its use (or more precisely, the use of poetry-core) as a build system. In fact, it pretty much became a synonym of a footgun for me — and whenever I'm about to package some project using poetry-core, or switching to it, I've learned to expect some predictable mistake. I suppose the time has come to note all these pitfalls in a single blog post.
"""https://blogs.gentoo.org/mgorny/2024/12/20/poetry-core-or-the-ultimate-footgun/
-
Did I mention that #Gentoo has now #time64 stages for #x86?
Well, we have #Docker images now as well:
$ docker run gentoo/stage3:i686-openrc python -c 'import datetime; print(datetime.datetime(2044, 1, 1).timestamp())'
Traceback (most recent call last):
File "<string>", line 1, in <module>
OverflowError: timestamp out of range for platform time_t
$ docker run gentoo/stage3:i686-ssemath-t64-openrc python -c 'import datetime; print(datetime.datetime(2044, 1, 1).timestamp())'
2335219200.0(there's only a "ssemath" variant, using "-mfpmath=sse" — the floating-point computations are done on 64-bit SSE registers rather than 80-bit x87 registers, giving more consistent results between 32-bit x86 and everything else)
-
A wspominałem, że mamy już w #Gentoo archiwa stage3 w wariancie #time64 dla #x86?
No to wspominam, że teraz mamy też obrazy Dockera:
$ docker run gentoo/stage3:i686-openrc python -c 'import datetime; print(datetime.datetime(2044, 1, 1).timestamp())'
Traceback (most recent call last):
File "<string>", line 1, in <module>
OverflowError: timestamp out of range for platform time_t
$ docker run gentoo/stage3:i686-ssemath-t64-openrc python -c 'import datetime; print(datetime.datetime(2044, 1, 1).timestamp())'
2335219200.0(robimy tylko wariant "ssemath", czyli z "-mfpmath=sse" — operacje zmiennoprzecinkowe wykonywane są przy pomocy 64-bitowych rejestrów SSE, a nie 80-bitowych x87, co daje mniejsze rozbieżności między 32-bitowych x86, a całą resztą architektur)
-
@kipjatkom в феди есть разработчик #CalculateLinux (дистрибутив на основе #Gentoo). Хоть у меня и ванильный Gentoo, но их бинарный репозиторий добавлен, за что большая благодарность :blobcatflower:
-
Ciekawostka: jeżeli różne programy sypią się z błędami typu:
(…): GLib-GIO-ERROR **: 20:46:27.286: Settings schema '…' does not contain a key named '…'
a macie pewność, że schematy skompilowane, i definitywnie zawierają taki klucz, to może okazać się, że z jakiegoś powodu w waszym katalogu domowym siedzi dodatkowy plik ze skompilowanymi schematami, i jest używany zamiast systemowego.
Czyli:
rm ~/.local/share/glib-2.0/schemas/gschemas.compiled
-
Ciekawostka: jeżeli różne programy sypią się z błędami typu:
(…): GLib-GIO-ERROR **: 20:46:27.286: Settings schema '…' does not contain a key named '…'
a macie pewność, że schematy skompilowane, i definitywnie zawierają taki klucz, to może okazać się, że z jakiegoś powodu w waszym katalogu domowym siedzi dodatkowy plik ze skompilowanymi schematami, i jest używany zamiast systemowego.
Czyli:
rm ~/.local/share/glib-2.0/schemas/gschemas.compiled
-
Ciekawostka: jeżeli różne programy sypią się z błędami typu:
(…): GLib-GIO-ERROR **: 20:46:27.286: Settings schema '…' does not contain a key named '…'
a macie pewność, że schematy skompilowane, i definitywnie zawierają taki klucz, to może okazać się, że z jakiegoś powodu w waszym katalogu domowym siedzi dodatkowy plik ze skompilowanymi schematami, i jest używany zamiast systemowego.
Czyli:
rm ~/.local/share/glib-2.0/schemas/gschemas.compiled
-
Ciekawostka: jeżeli różne programy sypią się z błędami typu:
(…): GLib-GIO-ERROR **: 20:46:27.286: Settings schema '…' does not contain a key named '…'
a macie pewność, że schematy skompilowane, i definitywnie zawierają taki klucz, to może okazać się, że z jakiegoś powodu w waszym katalogu domowym siedzi dodatkowy plik ze skompilowanymi schematami, i jest używany zamiast systemowego.
Czyli:
rm ~/.local/share/glib-2.0/schemas/gschemas.compiled
-
Fun fact: if random applications are crashing with errors like:
(…): GLib-GIO-ERROR **: 20:46:27.286: Settings schema '…' does not contain a key named '…'
and you've already verified that you've compiled the schemas, and that the schema contains the listed key, then it may mean that for some reason you have another compiled schema file in your home directory, and it's taking precedence.
In other words:
rm ~/.local/share/glib-2.0/schemas/gschemas.compiled
-
Fun fact: if random applications are crashing with errors like:
(…): GLib-GIO-ERROR **: 20:46:27.286: Settings schema '…' does not contain a key named '…'
and you've already verified that you've compiled the schemas, and that the schema contains the listed key, then it may mean that for some reason you have another compiled schema file in your home directory, and it's taking precedence.
In other words:
rm ~/.local/share/glib-2.0/schemas/gschemas.compiled
-
Fun fact: if random applications are crashing with errors like:
(…): GLib-GIO-ERROR **: 20:46:27.286: Settings schema '…' does not contain a key named '…'
and you've already verified that you've compiled the schemas, and that the schema contains the listed key, then it may mean that for some reason you have another compiled schema file in your home directory, and it's taking precedence.
In other words:
rm ~/.local/share/glib-2.0/schemas/gschemas.compiled
-
Fun fact: if random applications are crashing with errors like:
(…): GLib-GIO-ERROR **: 20:46:27.286: Settings schema '…' does not contain a key named '…'
and you've already verified that you've compiled the schemas, and that the schema contains the listed key, then it may mean that for some reason you have another compiled schema file in your home directory, and it's taking precedence.
In other words:
rm ~/.local/share/glib-2.0/schemas/gschemas.compiled
-
Yesterday was one of the very few times I managed to lock myself out of my #Gentoo system.
This time I didn't understand the severity of a warning after a systemd update.
With an older #SailfishOS SDK I had to set systemd.unified_cgroup_hierarchy=false on the kernel command-line to get the build docker image working. The updated systemd no longer supports this, and refused to launch...
Good that I have a #SystemRescue CD for such situations... IT took less than 15 minutes to fix it.