Carlos Henrique Lima Melara <[email protected]> writes: > Hi, > > On Wed, Nov 05, 2025 at 09:24:00AM -0500, Nicholas D Steeves wrote: >> >> I just wanted to update this bug so that there's a record that at >> least one team member cares about Syncthing for Debian. > > I can say there are 2 team members :-) I do use syncthing regularly but > was using trixie while setting up my new notebook. Now the notebook is > ready with testing and I was surprised to not have syncthing there.
Yay! >> The plan at >> this point should definitely be to import a newer upstream release, >> and I've spent a number of hours trying to work through the BD churn, >> but I wasn't able to get a recent 1.x series of Syncthing to build due >> to what seemed to be Azure-related things. It's also the case that my >> Golang knowledge is aspirational and limited. > > The problem was the bump in quic-go library that made it stop working, I > was able to find the patch to fix it [1] and applied. Yes, that's what broke 1.29.5, but it's also a problem that we're 15 releases behind upstream. If you take a look at the debian/experimental git branch then you'll see what I mean about the Azure and Windows-specific stuff that I'm talking about. > I plan to upload and maybe add myself as uploader (after this upload) > if that's ok to other uploaders. I'm confident that everyone involved would appreciate this! If you're confident that it would save time and effort to jump debian/experimental forward to 2.0.11, please go ahead and do so! (It's currently at a WIP 2.0.5) Also, feel free to drop the 0010-disable-azure-imports.patch experiment if that's the wrong direction, and please also delete the current changelog entries related to it if you do so. >> That's why I haven't set myself as an Uploader, and this package will >> need help from other team members to get back to good state. > > At least it will get back to testing for now :-) > Thank you! Nicholas
signature.asc
Description: PGP signature
