[prev in list] [next in list] [prev in thread] [next in thread]
List: pkgsrc-users
Subject: Re: CVS commit: pkgsrc/net/syncthing
From: Greg Troxel <gdt () lexort ! com>
Date: 2019-12-28 1:47:19
Message-ID: rmir20pi5lk.fsf () s1 ! lexort ! com
[Download RAW message or body]
Fr=C3=A9d=C3=A9ric Fauberteau <triaxx@NetBSD.org> writes:
> Le 2019-12-27 15:37, Greg Troxel a =C3=A9crit=C2=A0:
>> Fr=C3=A9d=C3=A9ric Fauberteau <triaxx@NetBSD.org> writes:
>>
>>>> I do not know if it's really related, but since I made the
>>>> upgrade, my
>>>> domU falls every ~4/5 day with syslogd complaining that no buffer
>>>> space available:
>>>> 2019-10-13T18:54:41.103713+00:00 www.triaxx.org syslogd 477 - -
>>>> recvfrom() unix `/var/run/log': No buffer space available
>>>> 2019-10-13T19:00:00.820144+00:00 www.triaxx.org syslogd 477 - - last
>>>> message repeated 3142 times
>>>
>>> It seems to be https://github.com/syncthing/syncthing/issues/6081,
>>> fixed in 1.3.2.
>>
>> Given that this is a pretty serious bug, that the update is almost
>> micro, and that syncthing is a leafy package, I am inclined to have
>> 1.3.2 updated now so it's in the branch. It seems better to maybe have
>> to pullup a fix to that, compared to having what feels like broken
>> syncthing for a quarter.
>>
>> So if that sounds ok to you, please go ahead and commit the update.
>
> It runs correctly for me on my server and my laptopp for 2 days. But I
> do not use Android app and I cannot ensure this release breaks
> nothing.
OK. I will update my tree to 1.3.2 and test with android and if it's
ok as I'm 99.9% sure it will be, commit the update. Let me know if you
think that's not a good plan.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic