Tootfinder

Opt-in global Mastodon full text search. Join the index!

@Zer0Rank@social.linux.pizza
2025-07-30 06:52:20

If you haven't tried it yet, I definitely recommend checking Jujutsu Version Control System.
I literally heard about it two days ago, started reading through some tutorials, and already feel like this is something exciting and new in the VCS world. You can use it locally on any git repository you already have, since it uses git as the backend.
Anyone else in the team can keep on using git, and if you feel like it you can switch back to use git at any time.
`jj` feels in…

@stsquad@mastodon.org.uk
2025-08-15 16:06:14

Dear #lazyweb,
I think I've reached the limit of #matplotlib trying to graph the forks from a #git repository. What I want to to plot the slowly growing trunk and then show the relative sizes o…

A hand drawn sketch showing the fork diagram the author would like to generate. A slowly growing core cone representing the trunk with branches coming of showing the relative size of the fork.
@mgorny@social.treehouse.systems
2025-08-12 18:12:44

I was trying to package #FlexiBLAS for #Gentoo, and to be honest, it doesn't look that good.
The first red flag is lack of an open bug tracker. Apparently, there is the tracker on GitLab that's limited to "members of their group and selected external contributors", but it doesn't seem to be used much. So it's "send us an email", and wonder how many people sent us the same bug report before.
The git repository is currently at something tagged 3.4.80 that seems to be prerelease, and its build system is quite broken. Not exactly the best path to verify that the bugs you are hitting are still there.
Now, upstream seems to insist on either using vendored netlib #LAPACK, or statically linking to the system library (we don't install the static libraries). Apparently I can specify the shared libraries instead, but it doesn't work — and it's unclear to me whether it doesn't work because I'm using the shared libraries, or because it doesn't support my LAPACK version. If I build LAPACK without deprecated symbols, it refuses to load it at runtime because of missing symbols. And if I build it with deprecated symbols, it fails to find some symbols at CMake time.
Honestly, I feel like I've spent too much time on this project already, especially given that its future is entirely unclear to me — the current git is quite broken, I have no clue how many issues were reported already and whether my bug reports will receive any reply. It definitely doesn't fare well for a package that we might start to rely heavily on. We don't want a cathedral there.
mpi-magdeburg.mpg.de/projects/
gitlab.mpi-magdeburg.mpg.de/so