On Sun, Nov 19, 2017 at 05:01:27PM +0200, Niko Tyni wrote: > On Sun, Nov 19, 2017 at 02:38:40PM +0100, Aurelien Jarno wrote: > > > Now that we have glibc 2.26 in experimental, can I ask about the status > > of this issue? Do we have to add Breaks: against the affected perl > > packages? > > Thanks for the reminder. > > I looked a bit at "fixing" libasync-interrupt-perl, noted that it uses > SIG_SIZE for other things too and decided I don't want to spend my time > on that. > > My plan is to use the attached workaround, which should keep the ABI > regardless of the glibc version. It should probably go to sid soon. > > I don't think Breaks are needed. The issue only happens if the current > perl gets built with the new glibc. Assuming we upload the workaround > to sid before glibc 2.26, I think it should be fine.
Hello, Nothing too much to add, but this sounds like a good idea. Thanks for taking care of this! Cheers, Dominic.