On Fri, 2012-12-21 at 16:59 -0400, David Prévot wrote:
> Hi Abou, Paul,
> 
> Le 21/12/2012 15:13, Paul Gevers a écrit :
> 
> > Reading through bug 684437 [1] I think you misunderstood the last remark
> > by David Prévot, where he proposed to create a 2.6.0-7 with all the
> > translations, but creating a debdiff without the translations.
> 
> Confirmed (and ACK about all your other remarks Paul, thanks), sorry if
> my previous message were not clear enough.

I've planned to upload it in 2 steps in order to keep the debdiff as
small as possible and as clear for RT as possible.

The plan is: 
* 2.6.0-7 with translation support, but no translations. So that RT can
look deeply on debdiff and see minor changes.
  1) fpc-2.6.0/debian/changelog: Short description of the changes
  2) fpc-2.6.0/debian/control: Automatically generated file from
fpc-2.6.0/debian/control.in (see below for changes in this file)
  3) fpc-2.6.0/debian/control.in: Updated build dependency and
descriptions
  3.1) fpc requires now po-debconf to build in order to allow
translating debconf screens
  3.2) Updated description fields fixing bad English and rephrasing in
order to make text clearer.
  4) fpc-2.6.0/debian/copyright.in: Fixed typo preventing correct update
of upstream release sources. This file is used to automatically generate
fpc-2.6.0/debian/copyright upon build process.
  5) fpc-2.6.0/debian/fp-compiler.templates.in: Updated description
fields fixing bad English and rephrasing in order to make text clearer.
  6) fpc-2.6.0/debian/po/POTFILES.in: Added file required by po-debconf
  7) fpc-2.6.0/debian/po/templates.pot: Added file required by
po-debconf

  As you can see, the modifications are limited to description text
update and fixes, increasing quality of the package without any
potential risk on the package or other packages stability.

* 2.6.0-8 only translation files.

* 2.6.0-9 some other small and nice to have features with very little
risk.

Cheers,

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to