On Tue, Jun 07, 2016 at 02:33:15AM +0100, Adam D. Barratt wrote:
> On Tue, 2016-06-07 at 00:46 +0100, Dominic Hargreaves wrote:
> > On Mon, Jun 06, 2016 at 08:54:23PM +0100, Dominic Hargreaves wrote:
> [...]
> > > In hindsight, it's obvious that Debian's testing of this update wasn't
> > > sufficie
On Tue, 2016-06-07 at 00:46 +0100, Dominic Hargreaves wrote:
> On Mon, Jun 06, 2016 at 08:54:23PM +0100, Dominic Hargreaves wrote:
[...]
> > In hindsight, it's obvious that Debian's testing of this update wasn't
> > sufficient either. Such breaking changes in perl stable updates are,
> > I believe,
On Mon, Jun 06, 2016 at 08:54:23PM +0100, Dominic Hargreaves wrote:
> Thanks Niko for analysis. The sequence of events went like this:
>
> 1) a commit (which fixed a segfault, but broke compatibility) was
>committed to the upstream development branch
> 2) upstream testing detected the issue in
3 matches
Mail list logo