Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Log-Dispatch CPAN distribution.

Report information
The Basics
Id: 106823
Status: resolved
Priority: 0/
Queue: Log-Dispatch
People
Owner: Nobody in particular
Requestors: emmanuel [...] seyman.fr
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: 2.50

History Show all quoted text
  Wed Sep 02 08:20:58 2015 emmanuel [...] seyman.fr - Ticket created
Subject: perl-Log-Dispatch >= 2.47 causes other modules to fail
Date: Wed, 2 Sep 2015 14:20:40 +0200
To: bug-Log-Dispatch [...] rt.cpan.org
From: Emmanuel Seyman <emmanuel [...] seyman.fr>
The Fedora Perl group realized that a number of modules fail to build since we upgraded Log-Dispatch to 2.48 (actually, we've established that the problems started occuring with 2.47). Since the update, Log-Dispatch-Config, MooseX-LogDispatch and MooseX-LazyLogDispatch all fail to build. I don't know if this is an issue of their tests being wrong (I'll happily file bugs against the appropriate distributions if need be) or if this should have been fixed by ether's patch in #106605. FYI, Fedora's tracking bug is: https://bugzilla.redhat.com/show_bug.cgi?id=1258940
  Wed Sep 02 15:24:24 2015 SREZIC [...] cpan.org - Correspondence added
On 2015-09-02 08:20:58, emmanuel@seyman.fr wrote: Show quoted text
> > The Fedora Perl group realized that a number of modules fail to build > since we > upgraded Log-Dispatch to 2.48 (actually, we've established that the > problems > started occuring with 2.47). > > Since the update, Log-Dispatch-Config, MooseX-LogDispatch and > MooseX-LazyLogDispatch all fail to build. I don't know if this is an > issue of > their tests being wrong (I'll happily file bugs against the > appropriate > distributions if need be) or if this should have been fixed by ether's > patch in > #106605. > > FYI, Fedora's tracking bug is: > https://bugzilla.redhat.com/show_bug.cgi?id=1258940
Version 2.50 is supposed to fix this problem according to the Changes file. See https://metacpan.org/source/DROLSKY/Log-Dispatch-2.50/Changes#L5
  Wed Sep 02 15:24:25 2015 The RT System itself - Status changed from 'new' to 'open'
  Wed Sep 02 15:26:58 2015 DROLSKY [...] cpan.org - Status changed from 'open' to 'resolved'
  Wed Sep 02 15:26:59 2015 DROLSKY [...] cpan.org - Fixed in 2.50 added
  Wed Sep 02 15:27:20 2015 DROLSKY [...] cpan.org - Correspondence added
On Wed Sep 02 15:24:24 2015, SREZIC wrote: Show quoted text
> On 2015-09-02 08:20:58, emmanuel@seyman.fr wrote:
> > > > The Fedora Perl group realized that a number of modules fail to build > > since we > > upgraded Log-Dispatch to 2.48 (actually, we've established that the > > problems > > started occuring with 2.47). > > > > Since the update, Log-Dispatch-Config, MooseX-LogDispatch and > > MooseX-LazyLogDispatch all fail to build. I don't know if this is an > > issue of > > their tests being wrong (I'll happily file bugs against the > > appropriate > > distributions if need be) or if this should have been fixed by > > ether's > > patch in > > #106605. > > > > FYI, Fedora's tracking bug is: > > https://bugzilla.redhat.com/show_bug.cgi?id=1258940
> > Version 2.50 is supposed to fix this problem according to the Changes > file. See > https://metacpan.org/source/DROLSKY/Log-Dispatch-2.50/Changes#L5
Yes, it does fix the problem. I tested the modules in question, and they all passed their tests.