Remaining fix is introduced to head at r299238 (almost just after
my previous post) and stable/10 is rolled back to 5.25 at r299236
for now.
Moreover, 5.27 is introduced to head at r299736. This version is
confirmed OK for me.
So both head and stable/10 are OK now.
Thanks, Xin!
Regards.
On
Broken pipe problem alone is fixed on head by r299234. (MFC after 3days)
*Confirmed on stable/10. As this is the first related update
after r298192(MFC'ed one), the effect should be the same.
But another problem Akinori mentioned is not yet fixed.
*On upstream bugtracker, it's already
Thanks for your investigation.
I left comment about this on bugzilla
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209211
and related thread in The FreeBSD Forums.
https://forums.freebsd.org/threads/55989/#post-319345
Regards.
On Sat, 07 May 2016 15:32:11 +0900
"Akinori MUSHA"
This looks like a bug in file 5.26. I've just filed an issue on the
tracker of file(1):
http://bugs.gw.com/view.php?id=543
File 5.26 turned out to have some other nasty bugs like the following,
so I'd recommend you avoid it.
http://bugs.gw.com/view.php?id=540
Fortunately the
This looks like a bug in file 5.26. I've just filed an issue on the
tracker of file(1):
http://bugs.gw.com/view.php?id=543
File 5.26 turned out to have some other nasty bugs like the following,
so I'd recommend you avoid it.
http://bugs.gw.com/view.php?id=540
Fortunately the
On Mon May 2 15:44:19 UTC 2016 Tomoaki AOKI wrote:
> Hi.
>
> Today I encountered this problem on stable/10 and could determine the
> problematic commit is r298920, "Update file to 5.26".
>
> This commit is MFC of r298192, and reverting it fixes the issue on
> head, too.
>
> What I did (for
Hi.
Today I encountered this problem on stable/10 and could determine the
problematic commit is r298920, "Update file to 5.26".
This commit is MFC of r298192, and reverting it fixes the issue on
head, too.
What I did (for stable/10) is...
1) Running at r298836: No problem.
2) Update to
https://lists.freebsd.org/pipermail/freebsd-ports/2016-April/102983.html
reported a "Broken pipe" problem with portupgrade on 11.0-CURRENT on amd64.
FYI: I had the/a "Broken pipe" portupgrade problem on powerpc64 under
11.0-CURRENT -r298518 on 2016-Apr-23 updating from /usr/ports -r413230 to
