Bug#931401: syncthing: incorrect warning please upgrade to v0.14.14 or newer

[Joaquín Aguirrezabalaga]

Package: syncthing
Version: 1.1.4~ds1-1
Severity: normal

Dear Maintainer,

Since version 1.1.4~ds1-1 of syncthing I am seeing this warning on both
the syncthing web page as in the journal logs, syncing between clients
with this new version:

WARNING: Not sending symlinks to old client CLIENTID - please upgrade to v0.14.14 or newer

I see this when the client CLIENTID has 1.1.4~ds1-1 version installed.

I am not sure if this is just a harmless warning or if the behaviour for
symlinks is really being affected.

My suspicion is that the 1.1.4~ds1-1 has its version not correctly set
at build time.

On a machine with 1.1.4~ds1-1 I get:

$ syncthing --version
syncthing unknown-dev "Erbium Earthworm" (go1.11.6 linux-amd64) unknown@unknown 1970-01-01 00:00:00 UTC

whereas in a maching with 1.0.0~ds1-1+b11 I get:

$ syncthing --version
syncthing v1.0.0-ds1 "Erbium Earthworm" (go1.11.6 linux-amd64) debian@debian 2019-06-08 10:15:59 UTC [noupgrade]

Thanks

Joaquín


-- System Information:
Debian Release: 10.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages syncthing depends on:
ii libc6 2.28-10

syncthing recommends no packages.

syncthing suggests no packages.

-- no debconf information

[BenWiederhake.GitHub]

Hello,

I also have this issue. It prevents me from syncing symlinks. :/

It seems that d/rules is trying to inject a clever version string, and
it fails for some reason.

Cheers,
Ben

[benm...@benmorris.org.uk]

It appears that this version string also breaks the GTK client (from the
syncthing-gtk package). The first run wizard shows the error
"Syncthing-GTK needs Syncthing daemon 0.14.50 or newer, but only v0.0
were found", and refuses to proceed without downloading a binary of the
daemon from GitHub.

[dirdi]

Package: syncthing
Version: 1.1.4~ds1-4
Followup-For: Bug #931401

Just want to confirm Joaquín's assumption that the package was built
with a wrong version string:

$ strings /usr/bin/syncthing | grep unknown-dev
_eval_args_additionalsalarm clockalloc_spaceaudio/basicaudit-*.logauthoritiesbad addressbad messagebad timedivbad verb '%broken pipebytes fieldcall of nilcgocall nilcircledast;clobberfreecomplement;connectionscontentionscontextmenucreated by crossorigincurlywedge;customtype=delete filedoubleStarsdynamicAddrempty fieldeqslantgtr;expected :=file existsfinal tokenfloat32nan2float64nan2float64nan3folderLabelformenctypegccheckmarkglobalBytesglobalFilesgtreqqless;gui-addresshash error:http-serverhttps_proxyi/o timeoutignorePermsignoreStatsinSyncBytesinSyncFilesindex-blockinuse_spaceis disabledisCandidatejournal-numld [x + %d]lessapprox;lesseqqgtr;linux-amd64listenLocallmoustache;local errorlocal.protolongVersionlongmapsto;lost mcachemSpanManualmapstodown;mapstoleft;memdb@flushmethodargs(nLeftarrow;nanosecondsneedDeletesnewestFirstnil contextnleftarrow;not reachednot startednsubseteqq;nsupseteqq;oldestFirston write topanic-*.logparse errorpermissionsplaceholderprecapprox;prevVersionrange_closeraw-controlreceiveonlyreflect.SetrescanIntvsretry-afterrightarrow;rmoustache;runtime: P runtime: p save configscheddetailsendreceivesetnonblockshort writesqsubseteq;sqsupseteq;stack faultstack tracestat after:subsetneqq;succapprox;supsetneqq;syncDir: %vtable@buildterms_closetime: file tls: alert(tracealloc(traffic updtrashcan@%punknown-devunreachableunsubscribeupuparrows;valid untilvarepsilon;varnothing;weak hasherzero header~syncthing~ addresses: (sensitive) PRIVATE KEY [recovered] allocCount found at *( gcscandone m->gsignal= minTrigger= nDataRoots= nSpanRoots= pages/byte

Did one figure out a workaround?

Btw: The bug was reported upstream, too: https://forum.syncthing.net/t/odd-not-sending-symlinks-to-old-client-messages-on-debian/14254
But was closed since this is clearly a debian specific issue.

-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing'), (50, 'unstable')

Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores)

Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages syncthing depends on:

ii libc6 2.29-10