From: Leo Famulari <leo@famulari.name>
To: Julien Lepiller <julien@lepiller.eu>
Cc: "Simen Endsjø" <simendsjo@gmail.com>,
52275-done@debbugs.gnu.org, guix-patches@gnu.org
Subject: bug#52275: [PATCH] gnu: syncthing: Update to 1.18.4.
Date: Mon, 6 Dec 2021 12:14:23 -0500 [thread overview]
Message-ID: <Ya5E73brr++tGJoe@jasmine.lan> (raw)
In-Reply-To: <647D76CD-1605-4B54-BF79-BFF85C14AD50@lepiller.eu>
I pushed 4e282bc934488b1c9ab9e97c838efe058da9e0bd, which updates
Syncthing to 1.18.4 and builds it with Go 1.17. I did this because
Syncthing assumes that one is building with Go 1.17, based on the
changes in Syncthing 1.18.2.
I'll test the update of the Go 1.17 series shortly and hopefully put Go
1.17 into use across all packages this week.
On Mon, Dec 06, 2021 at 06:47:31AM -0500, Julien Lepiller wrote:
> I've actually been running 1.18.4 for some time noo, without issues. Just skipping the tests makes it work, so why not? If this is a problem, I think 1.18.1 is better unless there is an important bug in it.
>
> Le 6 décembre 2021 03:15:51 GMT-05:00, "Simen Endsjø" <simendsjo@gmail.com> a écrit :
> >
> >"Leo Famulari" <leo@famulari.name> writes:
> >
> >> On Sun, Dec 5, 2021, at 03:54, Simen Endsjø wrote:
> >>> Great! As 1.16.1 is broken due to this bug:
> >>> https://github.com/syncthing/syncthing/issues/7685
> >>
> >> Broken somewhat... It works quite well in general :) The CLI is rather new and untested compared to the GUI / web API.
> >
> >I'm trying to run it from a server, and would like to avoid exposing a
> >web API.
> >
> >>> I updated the patch to 1.18.1, but should we rather use 1.17.0 you
> >>> think?
> >>
> >> Can you clarify why we might choose Syncthing 1.17.0 if we could use 1.18.1? Or did you mean Go 1.17?
> >
> >1.17.0 doesn't include any later patch versions, and might be more
> >stabel. Haven't looked at the issues closed 1.18.2-4, so it might be a
> >non-issue. I have very simple use, I just need something other than
> >1.16.1 as I cannot add devices with that version.
> >
> >
> >
next prev parent reply other threads:[~2021-12-06 17:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-04 11:51 [bug#52275] [PATCH] gnu: syncthing: Update to 1.18.4 Simen Endsjø
2021-12-04 11:51 ` simendsjo
2021-12-05 5:44 ` Leo Famulari
2021-12-05 5:59 ` Leo Famulari
2021-12-05 8:54 ` Simen Endsjø
2021-12-05 19:34 ` Leo Famulari
2021-12-06 8:15 ` Simen Endsjø
2021-12-06 11:47 ` Julien Lepiller
2021-12-06 17:14 ` Leo Famulari [this message]
2021-12-04 12:18 ` Julien Lepiller
2021-12-05 8:52 ` Simen Endsjø
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Ya5E73brr++tGJoe@jasmine.lan \
--to=leo@famulari.name \
--cc=52275-done@debbugs.gnu.org \
--cc=guix-patches@gnu.org \
--cc=julien@lepiller.eu \
--cc=simendsjo@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).