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.

Update: Clarification:

After getting some replies to my original message, wondering where I got the info #syncthing 2 is incompatible with the old clients, I did a quick search.

The release logs

https://github.com/syncthing/syncthing/releases/tag/v2.0.10

don't state any connection incompatibilities, and the forum posts

https://forum.syncthing.net/t/syncthing-version-2-interoperability-with-version-1/24830
https://forum.syncthing.net/t/syncthing-2-0-compatibility-with-older-st-clients/24792

say there are none either.

So apparently I completely misinterpreted the warning which appears when trying to update via the web interface.

Sorry for the confusion I caused.

@uvok
Thanks for this warning. I'll be very careful with my next -Syu!
@uvok
Having said that, I just realised I already had Syncthing 2 both on my archlinux and on my phone working seamlessly with the same configuration I had with 1.x
@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.
@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.
@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.
@uvok @fabiscafe I also obtain nginx, node.js, bird, and tailscale from their APT repositories.
@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.
@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.
@uvok In that case, please give the wiki a read:
https://wiki.archlinux.org/title/Frequently_asked_questions
Frequently asked questions - ArchWiki

@fabiscafe @uvok Syncthing v1.30.0 is still available for download:

https://github.com/syncthing/syncthing/releases/tag/v1.30.0

Release v1.30.0 · syncthing/syncthing

Syncthing 2 is coming Syncthing version 1.x will soon be replaced by Syncthing version 2.x. Version 2 brings a new database format and various cleanups, but remains protocol compatible with Syncthi...

GitHub
@uvok where did you get the info that it's incompatible?
@bitpirate I probably misunderstood the warning in the web interface
@uvok Hmm, I still need to do the upgrade but I thought it was compatible version 1 and 2 communicating tk eachother?
@maruno hm, I think I misunderstood the huge red box with a warning in the web interface

@uvok From the release notes:
"Version 2 brings a new database format and various cleanups, but remains
*protocol compatible* with Syncthing 1" (emphasis mine)

Also Archlinux is a rolling release distro. Updates following the lastest upstream is exactly what it says on the tin. They might provide a `-old` package in the AUR or even in the repo, but especially for an update that does automatic migrations and is protocol compatible with the previous version, I would not expect even that.

@uvok which part of “bleeding edge” do you find hard to comprehend?