[Pkg-shadow-devel] shadow.pot not updated

[Martin Quinson]

--72k7VsmfIboquFwl
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, May 24, 2005 at 07:35:36AM +0200, Christian Perrier wrote:
> Quoting Nicolas Fran=E7ois (nicolas.francois@centraliens.net):
> > Hello,
> >=20
> > The shadow.pot file in the shadow source package is not up-to-date (see
> > chpasswd usage).
>=20
> Yep, that's a problem I noticed. I have kept a locally built
> shadow.pot file and I msgmerge translations with it when I receive
> them.
>=20
> However, several translations currently need to be msgmerged with it=A0:
> which means that we later need to update all 1xx patches (and probably
> use this occasion to remove all changes to PO files in 327)
>=20
> This is what I suggest if someone can work on it.
>=20
> And then add a 100 patch which updates shadow.pot.

We may want to delay this to after the catchup to 4.0.9 since it will ease a
lot this mess. But that's just my opinion and I won't be able to help in
this area anyway. Much to few time, sorry. Damn non-sleepin'baby ,)

> > >From what I read in Makefile.in.in, it seems that it is the intent not=
 to
> > have it updated too often.
> > shadow.pot is updated by the 'dist' rule. Shall we call
> > 'make -C po update-po' explicitly in debian/rules?
>=20
> We really should make sure that shadow.pot we provide in the Debian
> source is up-to-date, sure.
>
> > How other packages are doing?

Make sure to read what the debconf package does in this area to limit the
number of commits by ignoring the ignorable changes to po files ;)

> > Shall we call make -C po update-po manually and update the right quilt
> > patches?
>=20
> I'm anyway not fond of quilt patches for upstream translation
> updates. This is transitory. As soon as we will have merged back with
> upstream, we will ONLY use upstream translations. There should be no
> more need to local patches. After all, upstream is with us right now
> and if we sometimes need "translation update" versions, we will just
> ask Tomaszand I'm pretty sure there won't be any problem.

Agreed, and thus my proposal to postpone all this.

> > Another question regarding POs:
> > if po/shadow.pot and po/$lang.po are patched by quilt, which file is
> > used by translators? Are they aware that they should apply the patches?
>=20
> That's currently a problem. Most translation updates come because
> shadow is referenced in what we call "level 4" for Debian Installer
> translations. Translators use the D-I i18n/l10n framework where PO
> files come from the various CVS/SVN by scripts setup by Dennis
> Stampfer.
>=20
> These scripts are currently puzzled by our move to quilt (they're run
> on gluck which is a woody machine without quilt). I'm trying
> to sort the issue with Dennis. I suggested him to just do=A0: "for i in
> `cat debian/patches/series`=A0; do cat $i - patch -p1=A0; done"

On IRC, we came to a much better solution, even if I can't find the logs
again, right now. You have to filter out the comments of the series file,
protect the patch name and actually pipe cat into patch ;)

> > (Maybe the recent update were caused by a call for translation by
> > Christian, who provided the right po)
>=20
> Yes, exactly.
>=20
> I don't intend to send another call for updates. I prefer waiting for
> us to achieve the resync with upstream and *then* send a general call
> for updates, sending PO files as they are in Tomasz CVS.

See, you agree to postpone the po mess sort out until after we catchup
upstream ;)

Bye, Mt.

--72k7VsmfIboquFwl
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFCktLWIiC/MeFF8zQRAtB7AKCAJxxHYkgQ71i9XbsJSjAvPGnKQQCgk6/k
fR6e1FRZJVjbzgFHiH/I1IE=
=wGVo
-----END PGP SIGNATURE-----

--72k7VsmfIboquFwl--