uvok cheetahNov 9
Urgh. Fuck.
#ArchLinux already switched to #syncthing version 2, which is incompatible with synthing 1.
WTF-
I would expect either a syncthing2 package, or at least a syncthing1 fallback.
That's *not* good package management.
Show threadFabian【ファビアン】🏳️‍🌈Nov 9
@uvok We dont do versioned packages unless required. This is expected. Best case is to open an issue. But given that v2 is available for 2 month now and v1 isnt available even on the syncthing page, I dont really see the need for it.
Show threaduvok cheetah
@fabiscafe "It's available for 2 months" is not a good argument, I think.
I also use Debian on one of my servers, and Debian system packages still use syncthing 1.x.
I would expect interoperability to work out of the box.
Nov 9 at 11:44amWeb
Show threadMarekNov 9
@uvok @fabiscafe Syncthing is one of the things I get from the official Syncthing APT repository (since Debian packages it too slowly). It can also be activated via extrepo.
Show threadMarekNov 9
@uvok @fabiscafe I also obtain nginx, node.js, bird, and tailscale from their APT repositories.
Show threadMarekNov 9
@uvok @fabiscafe Alternatively, maybe downgrade or something like that on Arch?
But yes, that's annoying, of course. Although I think Denian's packaging model is to blame here.
Show threadFabian【ファビアン】🏳️‍🌈Nov 9
@mark22k @uvok You cant blame a stable distro to keep its version, nor a rolling distro to go for the latest stable. All of this is expected behavior.
Show threadFabian【ファビアン】🏳️‍🌈Nov 9
@uvok In that case, please give the wiki a read:
https://wiki.archlinux.org/title/Frequently_asked_questions
Frequently asked questions - ArchWiki