Bug#619275: Perl Policy change to document major version upgrade trigger

[Bill Allombert <Bill.Allombert@math.u-bordeaux1.fr>]

On Fri, Mar 25, 2011 at 08:31:51AM +0100, Salvatore Bonaccorso wrote:
> Hi Dominic
> 
> Only read trough yet (but not native english speaker):
> 
> On Tue, Mar 22, 2011 at 04:35:16PM +0000, Dominic Hargreaves wrote:
> > Signed-off-by: Dominic Hargreaves <dom@earth.li>
> > ---
> >  perl-policy.sgml |   20 ++++++++++++++++++++
> >  1 files changed, 20 insertions(+), 0 deletions(-)
> > 
> > diff --git a/perl-policy.sgml b/perl-policy.sgml
> > index b9f3277..47cf9f6 100644
> > --- a/perl-policy.sgml
> > +++ b/perl-policy.sgml
> > @@ -461,6 +461,26 @@ perl -MExtUtils::Embed -e ldopts
> >  	  package must depend upon it explicitly.
> >  	</p>
> >        </sect>
> > +
> > +      <sect id="perl_upgrades">
> > +        <heading>Perl Package Upgrades</heading>
> > +        <p>
> > +          Starting from <package>perl</package> 5.12.3-2, a dpkg trigger
> > +          named <var>perl-major-upgrade</var> will be triggered by the
> > +          postinst of the <package>perl</package> package during major
> > +          upgrades. Some examples of things which consitute a major upgrade
> 
> consitute -> constitute

Hello Salvatore,

Are you willing to second it ?

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here.