Control: tags 819758 + pending
On Tue, 2016-05-24 at 00:56 +0100, Dominic Hargreaves wrote:
> On Mon, May 23, 2016 at 08:31:40PM +0100, Adam D. Barratt wrote:
> > Control: tags 819758 -moreinfo +confirmed
> >
> > [CC += the p-u bug]
> >
> > On Mon, 2016-05-23 at 11:35 +0200, gregor herrmann wrot
On Mon, May 23, 2016 at 08:31:40PM +0100, Adam D. Barratt wrote:
> Control: tags 819758 -moreinfo +confirmed
>
> [CC += the p-u bug]
>
> On Mon, 2016-05-23 at 11:35 +0200, gregor herrmann wrote:
> > On Mon, 23 May 2016 09:27:44 +0100, Dominic Hargreaves wrote:
> >
> > > On Mon, May 23, 2016 at 0
Control: tags 819758 -moreinfo +confirmed
[CC += the p-u bug]
On Mon, 2016-05-23 at 11:35 +0200, gregor herrmann wrote:
> On Mon, 23 May 2016 09:27:44 +0100, Dominic Hargreaves wrote:
>
> > On Mon, May 23, 2016 at 08:33:41AM +0200, gregor herrmann wrote:
> > > On Sun, 22 May 2016 21:40:43 +0100,
On Mon, 23 May 2016 09:27:44 +0100, Dominic Hargreaves wrote:
> On Mon, May 23, 2016 at 08:33:41AM +0200, gregor herrmann wrote:
> > On Sun, 22 May 2016 21:40:43 +0100, Dominic Hargreaves wrote:
> > > Not to my knowledge. I can publish the built packages for amd64
> > > somewhere temporarily and s
On Mon, May 23, 2016 at 08:33:41AM +0200, gregor herrmann wrote:
> On Sun, 22 May 2016 21:40:43 +0100, Dominic Hargreaves wrote:
>
> > > Has anyone else tested the
> > > package?
> > Not to my knowledge. I can publish the built packages for amd64
> > somewhere temporarily and see if anyone can tes
On Sun, 22 May 2016 21:40:43 +0100, Dominic Hargreaves wrote:
> > Has anyone else tested the
> > package?
> Not to my knowledge. I can publish the built packages for amd64
> somewhere temporarily and see if anyone can test them before they get
> as far as stable-proposed-updates.
I can install th
[CCing debian-perl]
On Sun, May 22, 2016 at 07:31:10PM +0100, Adam D. Barratt wrote:
> On Sat, 2016-05-21 at 14:43 +0100, Dominic Hargreaves wrote:
> > I wondered if you needed any more information in order to process this
> > request - since I am aware it's a large diff? Can we do anything
> > di
On Sat, 2016-05-21 at 14:43 +0100, Dominic Hargreaves wrote:
> I wondered if you needed any more information in order to process this
> request - since I am aware it's a large diff? Can we do anything
> different in order to make life easier as far as reviewing goes, or
> by providing more backgro
On Sat, Apr 30, 2016 at 08:21:44PM +0100, Dominic Hargreaves wrote:
> Release team: please consider #819758 as being a request for the attached
> patch (which includes the previously-submitted change); there is more
> rationale about the patches included in [1] - but the short version is
> that th
On Mon, Apr 25, 2016 at 10:31:18PM +0300, Niko Tyni wrote:
[test branch for perl 5.20.3 changes]
> Looks good. I like the separate merges.
>
> Grouping together
> fixes/5.20.3/preserve_record_separator.diff
> fixes/5.20.3/test_count_base_rs.diff
> more explicitly might be nice but that's just
On Mon, Apr 25, 2016 at 10:31:18PM +0300, Niko Tyni wrote:
> On Sun, Apr 24, 2016 at 06:25:03PM +0100, Dominic Hargreaves wrote:
>
> > I've applied these in branch dom/jessie-imports-from-5.20.3 on top of
> > the jessie branch (which now has the fix for #821848 applied). I used
> > two separate me
On Sun, Apr 24, 2016 at 06:25:03PM +0100, Dominic Hargreaves wrote:
> I've applied these in branch dom/jessie-imports-from-5.20.3 on top of
> the jessie branch (which now has the fix for #821848 applied). I used
> two separate merge commits (one for the functional stuff and one for the
> docs).
L
On Sun, Apr 24, 2016 at 03:42:19PM +0300, Niko Tyni wrote:
> On Sun, Apr 24, 2016 at 02:43:26PM +0300, Niko Tyni wrote:
>
> > I wonder if it would be useful to prefix the patch (file)names with
> > something else than the current 'debian/' or 'fixes/', perhaps '5.20.3/',
> > to highlight their ori
On Sun, Apr 24, 2016 at 02:43:26PM +0300, Niko Tyni wrote:
> I wonder if it would be useful to prefix the patch (file)names with
> something else than the current 'debian/' or 'fixes/', perhaps '5.20.3/',
> to highlight their origins? This might at least make 'perl -V' output
> a bit clearer.
Dom
On Sat, Apr 23, 2016 at 04:36:26PM +0100, Dominic Hargreaves wrote:
> Source: perl
> Version: 5.20.2-3+deb8u4
> I analysed the 165 commits in upstream's git repository between
> 5.20.2 and 5.20.3 and selected what I believe to be the 40-odd
> relevant patches (the others are either non-functional
Source: perl
Version: 5.20.2-3+deb8u4
As discussed with Niko in recent weeks, I believe we should be importing
all relevant patches from maint releases of perl into Debian stable.
This provides Debian stable users with many important bugfixes that have
been reviewed and tested upstream already.
T
16 matches
Mail list logo
