Running fedora is such a delight. I can wait till they have it fixed. Much better than *its release day, lets see what happens"
I don’t mind the delay much, but I’m so tried of waiting for Syncthing 2. All my other nodes are at the v2, for a very long time. Months, I don’t even remember. The older version works, but it constantly shows some issues which aren’t there. I expect the migration to 2.0 would resolve the issues. It’s there in the Fedora 44, but the 43 does not have it for some reason. I’m waiting. Otherwise it’s good.
You could also consider just running the binary given that alternative fits your usecase? Single-user and trusting the syncthing-team, but they seem (my opinion, no affiliation, fellow user only) highly trustworthy. The binary auto-updates and you don’t have to wait for the distro package maintainers to update the repos. Might be an acceptable tradeoff in the case of syncthing, or maybe not - just raising as an alternative for you to consider.
Oh wow, I was not aware of this option! I think I’d wait for fiesta to upgrade, since it’s weeks anyway. But in general, that’s very useful to have it updating itself not supervised! A potential attack surface, but I guess for most casual users that’s not a real threat. Thanks for letting me (and I hope someone else too) know!
Waiting for the system package to get updated is always preferable, but if you really can’t wait, there’s always the option of using docker or flatpak or some other distribution method that is uncoupled from your distro, as that’s exactly the sort of situation they’re useful for. I try not to use them by default (and I think projects that recommend and use them AS the default or only distribution method are doing everyone a disservice), but sometimes you have to fend for yourself.
There’s also the option of compiling from source, which I think a lot of people think is less standardized, scarier and slower than it really is. This isn’t Windows (and it shouldn’t be) so it usually isn’t a nightmare. The further away we get away from compiling our own applications from source, the less healthy the whole open source ecosystem gets. We really need people compiling software regularly and creating the incentive to actually have a sane, responsible, user-friendly build process, because the closer we get to only ever using provided binaries, the closer we get to being effectively closed-source with decorative source code. The source code is there for a reason, it should be demystified so we don’t develop a learned helplessness about it.
Hey, thanks for an interesting point of view! I mostly never compile from source, unless that’s some AUR package and it compiles everything on its own. I truly wants to try Gentoo some day (been postponing that for about two decades), but I always see my hardware as unworthy, of being too underpowered to compile everything I need. If I’d asked you to elaborate a bit, what would your suggestion be? Should I try Gentoo with compiling things for myself?
I want to get a used MacBook Air M1 as a secondary laptop (I’m eyeing one with some minor hardware issues, so it’d be somewhat affordable for a toy to play with). I thought of it, and I think I’d like to install Gentoo on it. I think this is the way, but perhaps you have some comments to that, or some advice.
Also, I remember when I used macOS, I used Mac ports, as brew has idiotic design when you have more than one user, which I had. Mac ports was compiling some things, I remember. But I think that’s different to what you say. More relevant thing, I think, would be, say, compiling a browser. I thought of attempting to compile a custom simplified Firefox on that imaginable (for now) MacBook Air machine, as I’m being irritated with so many features I don’t actually need. Say, the whole set of AI things, plus I really dislike options. Say, if I’m to use vertical tabs, I don’t need anything related to horizontal tabs, like at all. At this point I have no idea whether that’s trivial to remove things I never need and recompile, or whether that’s a separate hobby (if not a job) on its own, to catch up with the upstream.
That’s my whole point, you don’t need a whole distro to compile things. You can always compile things, that’s how distros get their packaged stuff in the first place. Compiling is the great equalizer. It compiles with whatever libraries your system already has. It doesn’t care what distro you have or what versions of things you’re using, as long as they work. And they usually do. Unless there’s some fundamental and likely recent incompatibility that hasn’t been upstreamed yet, which is rare.
Syncthing is written in go, which has its own library and compiling ecosystem and is relatively standardized and straightforward to compile. They walk you through the process here it should work on essentially every platform, even (and often especially) the weird non-standard ones that no other packaging format supports.