jelly1

I intentionally hold back major Python versions till I can dedicate a lot of time to get everything rebuild and compatible. A lot of big Python programs (ML, scientific) usually need work to get compatible requiring ~ 1-2 weeks of time to get this all done :)

With Cockpit Client this is not even required it will do the SSH magic for you.

https://flathub.org/apps/org.cockpit_project.CockpitClient

Cockpit Developer here, the webserver is written in C and the old bridge (the one "API" which communicates with JavaScript through the webserver with system API's such as systemd, podman, dbus, etc.).

The new bridge is written in Python and when time comes we want to rewrite our webserver into some modern.

I guess,.. but this FOSDEM we hacked on more Rust based tooling :-)

https://github.com/archlinux/rebuilder https://github.com/archlinux/signstar

Smallest country in Europe has the highest percentage of employees working form home

More and more people I know have become partly vegetarian and it seems that the meat replacements are also becoming more popular. But I can't say much about the scale of things.

Why doesn't this link to the original article https://www.nytimes.com/2019/07/01/opinion/slack-chat-hacker... instead of this shady businessinsider.com website?

In the future, Arch also wants to make their iso also reproducible :-). But first the packages have to be reproducible.

We work together with a few Debian developers involved with reproducible builds in the reproducible-builds project, so yes a lot of work is shared which is awesome :)

Well I didn't mean to claim it's 100% reproducible in the title. But we finally started working towards reproducible builds, we still need a way for users to easily reproduce builds, publish the results somewhere. And test with more differences, luckily Debian has done a lot of effort in this regard!