Eric Blake wrote:
> I've now applied the patches, with tweaks as discussed on 1/2.
In GNU gettext, I now see this message when using the top-level GNUmakefile:
/bin/bash: rsyncable: command not found
The reason is that GNU gettext imports the relevant files directly (via
'gnulib-tool --copy-file
On 1/3/19 8:44 AM, Eric Blake wrote:
> And I botched something in _sc_search_regexp. Will push the followup
> patch as soon as I diagnose the issue.
>
D'oh, I killed an important backslash:
+++ b/top/maint.mk
@@ -314,7 +314,7 @@ define _sc_search_regexp
: Check for the construct;
On 1/2/19 2:14 PM, Eric Blake wrote:
> On 12/20/18 7:06 AM, Roman Bolshakov wrote:
>> On Thu, Dec 13, 2018 at 06:34:51PM +0300, Roman Bolshakov wrote:
>>> Hello,
>>>
>>> There was an issue with syntax-check on FreeBSD reported a few years
>>> ago:
>>> https://www.redhat.com/archives/libvir-list/201
On 12/20/18 7:06 AM, Roman Bolshakov wrote:
> On Thu, Dec 13, 2018 at 06:34:51PM +0300, Roman Bolshakov wrote:
>> Hello,
>>
>> There was an issue with syntax-check on FreeBSD reported a few years
>> ago:
>> https://www.redhat.com/archives/libvir-list/2015-August/msg00758.html
>> http://lists.gnu.or
On Thu, Dec 13, 2018 at 06:34:51PM +0300, Roman Bolshakov wrote:
> Hello,
>
> There was an issue with syntax-check on FreeBSD reported a few years
> ago:
> https://www.redhat.com/archives/libvir-list/2015-August/msg00758.html
> http://lists.gnu.org/archive/html/bug-gnulib/2015-08/msg00019.html
>
Hello,
There was an issue with syntax-check on FreeBSD reported a few years
ago:
https://www.redhat.com/archives/libvir-list/2015-August/msg00758.html
http://lists.gnu.org/archive/html/bug-gnulib/2015-08/msg00019.html
The patch series attempts to resolve the issue on gnulib side. With
related cha
