mastodon.uno è uno dei tanti server Mastodon indipendenti che puoi usare per partecipare al fediverso.
Mastodon.Uno è la principale comunità mastodon italiana. Con 77.000 iscritti è il più grande nodo Mastodon italiano: anima ambientalista a supporto della privacy e del mondo Open Source.

Statistiche del server:

6,4K
utenti attivi

#gentoo

20 post17 partecipanti3 post oggi

#Gentoo is also going "full #PEP517" now, or to be more precise, we are going to rip out the legacy code paths that used `setup.py install`. However, that doesn't mean that PEP517 support is a solved problem.

1. There are still packages that require `setup.py install`, and either outright reject or ignore PEP517. And I'm not talking of dead packages but actively maintained projects. #Fail2Ban is a particularly notorious example (the way I see it, it's going to stop working sooner or later).

2. Some packages that do work with PEP517 builds, still require some hacks to install correctly. Sometimes it means moving files around, sometimes installing some files manually, sometimes patching stuff.

3. There are many packages that use the legacy setuptools backend to workaround their broken PEP517 port. Fortunately, these are at least easy to fix, provided you can convince upstream that actually altering sys.path is the correct solution.

4. Finally, we have removed a fair bunch of "hopeless" packages.

PSA: reminder that on 2025-05-01, #Gentoo is switching the default to #Python 3.13.

We are also removing the support for Python 3.10 and #PyPy 3.10 targets. Unlike the previous times, the upgrade to PyPy 3.11 now requires switching target flags.

We also do expect CPython 3.14 betas to land mid-May, and we will start adding relevant targets soon afterwards, as time permits.

public-inbox.gentoo.org/gentoo
gentoo.org/support/news-items/

public-inbox.gentoo.org[gentoo-dev] [Python] The big plans for May: Python 3.13 by default, Python 3.10 + PyPy 3.10 gone, Python 3.14 incoming

So, if you noticed half a dozen different #RustLang compilers being installed on your #Gentoo system… that's because the eclass pins the compiler to the newest version supported at the time the package was built. So if you built a package when Rust 1.82.0 was the newest version in Gentoo, the package will keep requiring this version until you rebuild it. Move 5 versions forward, and you have random packages pinning half a dozen Rust toolchain versions. Awesome.

So what you can do? There's a half-broken 'rust-rebuild' set that will rebuild too many packages (installing all Rust compilers). What you can do instead is, for each old compiler version:

1. Determine which package are pinning to it (e.g. via `emerge -cv =rust-1.82.0*`).
2. Check these packages for `RUST_MAX_VER` (optional, but avoids rebuilding stuff that will pin to this version anyway).
3. Rebuild these packages.
4. Try removing the compiler again (`emerge -cv =rust-1.82.0*`).
5. Repeat for every other version till you are left with just the newest.

Yeah, Rust is great. Truly love it. [keyboard melted by acid]

#dailyreport #gentoo #wayland #security #linux #secops
I wrote article about simple sandboxing in Wayland. It is
when we run application under another user.
For security this isolate applications from most user
resources.

I configured two tmux servers - one inside Wayland Sway
and other at console for long running proceses.

I run process with command:

sudo --preserve-env=WAYLAND_DISPLAY,XDG_RUNTIME_DIR -u ff firefox

Still think that Xfce4 window manager is the best one.

Yeah, so if you felt that requiring nightly #RustLang compiler to work is not bad enough, we now have packages that call `cargo build` recursively. Like, you build the package and one of the crates calls `cargo build` via `build.rs`. Good news is, is that mostly works.

By "mostly", I mean we need to unpack the package first, process Cargo.lock, unpack the crates and then process Cargo.lock from the crates. But who would care about details like that, or that packages are effectively silently fetching more packages behind your back?

Memory safety is all that matters! Stable dependencies? Supply chain #security? Transparency? Meh, stuff for weaklings!

Ritorno a scrivere qui dopo molto tempo, Come state? :)

Giravo attorno a voler fare un post qui da giorni, credo che lo userò come "diario" delle cose che sto studiando preparandomi per lpic-1

Stamattina ho deciso di imparare di più sulla configurazione dei sistemi dedicando un SSD che non usavo ad una installazione di Gentoo. È una bella giornata

Installing binary packages using the #portage package manager feels like watching paint dry, compared to other package managers. I can count multiple seconds per package, even when said package is empty (e.g. a virtual).

I've always wondered why that is. It *feels* wrong, and nobody has managed to explain it to me.

A few days ago, while waiting multiple hours for 1500 packages to install into a clean root, it finally bothered me enough to dig into it.

M'he adonat que el meu #Gentoo del PC té encara llibreries de 32 bits 😲
Estic seguint els passos per a eliminar-les del sistema, només vull 64 bits.
A veure si me'n surto... ara tinc a gcc compilant-se ell mateix.

@cJ @jk In my point of view, #Gentoo is relatively stable over a couple of months regarding features. Granted, over a period of several years I had to adopt for different paths (distfiles was moved to /var/something, e.g.), now we have more /etc/*.d config directories, …). But certain things are very stable (if you want: still openrc, alsa, …)
There's even lilo in portage!

It's rather programs like firefox that break behaviour / configs (and there isn't a simple way to configure it, anyway).

Ha risposto nella discussione

@jk

It may be personal but I see it with a much different perspective.

I'm *immensely grateful* that it's possible to have a machine with so many millions of SLOC running pretty much exactly how I want, respecting my freedom, with me contributing so little in return.

I'm also grateful that I can get to learn and know what's inside, and via the stream of updates and breakages, essentially be getting free continuous learning and also staying updated.

I'm purposely running #gentoo on my main machine, playing that Tamagotchi game very much.
When I want to "get things done without surprises", I use a "stable" "supply chain", trading off my own risk against reduced functionality, increased cost.

The good thing with "Linux" is that in no case you lose your freedom.

Oops! Bloody hell....some #rust fanboy/fangirl messed with some core system package and messed up and dish out half-arsed version , which essentially failed ....heck

Damnit! I have nothing against the new surge of Rust ...but for fuck's sake ....stop spoiling

#linuxadmin #rust #dracut #gentoo #opensource #operatingsystem

Context:

reddit.com/r/Gentoo/comments/1