Let's cc arches when ready.
My opinion is I don't think this should block glibc-2.26-stabilization. Ace-1.920.0-r1 ( current stable ) shouldn't be expected to have problems with C bindings or RPC support, because it used the CPAN default configuration of *not* compiling those features in. ( And the absence of these features was additionally concealed by the lack of running tests ) -r2 made these problems more visible because I 1) Enabled C eXtensions 2) Enabled RPC support 3) Added basic assurance tests that #1 and #2 were doing as advertised. But suffice to say, I doubt anything in tree uses the RPC mechanisms that are broken by the GLIBC migration, because if it did, it would have been broken since forever, and anything on CPAN that uses those features would have been broken since forever.
(In reply to Kent Fredric (IRC: kent\n) from comment #1) > My opinion is I don't think this should block glibc-2.26-stabilization. > > Ace-1.920.0-r1 ( current stable ) shouldn't be expected to have problems > with C bindings or RPC support, because it used the CPAN default > configuration of *not* compiling those features in. ( And the absence of > these features was additionally concealed by the lack of running tests ) OK sounds good.
Arches, please stabilize: =dev-perl/Ace-1.920.0-r3 For: amd64 x86 Thanks.
x86 stable
amd64 stable