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?
>
>
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,
On 2017-10-24 15:34, Dominic Hargreaves wrote:
> On Sun, Oct 22, 2017 at 08:57:59PM +0300, Niko Tyni wrote:
> > On Sat, Sep 16, 2017 at 10:27:26AM +0300, Niko Tyni wrote:
> > > Package: perl
> > > Version: 5.26.0-8
> > > Severity: normal
> > > X-Debbugs-Cc: d...@debian.org, vor...@debian.org,
> >
On Sun, Oct 22, 2017 at 08:57:59PM +0300, Niko Tyni wrote:
> On Sat, Sep 16, 2017 at 10:27:26AM +0300, Niko Tyni wrote:
> > Package: perl
> > Version: 5.26.0-8
> > Severity: normal
> > X-Debbugs-Cc: d...@debian.org, vor...@debian.org, gl...@packages.debian.org
> >
> > As seen in
> >
On Sat, Sep 16, 2017 at 10:27:26AM +0300, Niko Tyni wrote:
> Package: perl
> Version: 5.26.0-8
> Severity: normal
> X-Debbugs-Cc: d...@debian.org, vor...@debian.org, gl...@packages.debian.org
>
> As seen in
> https://bugs.launchpad.net/ubuntu/+source/libanyevent-perl/+bug/1717367
> an upstream
Package: perl
Version: 5.26.0-8
Severity: normal
X-Debbugs-Cc: d...@debian.org, vor...@debian.org, gl...@packages.debian.org
As seen in
https://bugs.launchpad.net/ubuntu/+source/libanyevent-perl/+bug/1717367
an upstream change in glibc 2.26, presumably
6 matches
Mail list logo
