[Pkg-shadow-devel] How to process with bug reports

[Christian Perrier]

/me back from 2 days away....

Quoting Nicolas Fran=E7ois (nicolas.francois@centraliens.net):
> Hi,
>=20
> I'm having a look at some bug reports.
>=20
> #263805:
>  * I could reproduce it with shadow 4.0.3-29, but not with the current
>    version nor 4.0.3-29.1
>=20
>    Can I close it with a mail to 263805-done, or should it be logged in
>    the debian changelog?

You can close it with -done, for sure. Better ask for an advice here
but I will trust you blindly.

>=20
>=20
> Some bugs (e.g. #249611) can be fixed safely.
> (I'm putting in this category bugs dealing with program strings and
> documentation)
> Do we plan to fix them for Sarge?

That one we can, probably. We need to make the same change in all
translations which can be done for sure.

Please tag it as [SARGE FIX] by retitling it.


> Do I commit fixes in the sarge branch?

Commit the fixes in the sarge branch but you must commit fixes in po/
as well....which is a bit tricky:

-preventively replace "--login" by "--user" in all PO files for that
string only (a carefully crafted sed command is recommended)

-regenerate the POT file and merge all PO files with it

-test that previouly complete PO files are still complete



> Do I commit fixes in the sid branch?

Yes, but given that all "upstream" changes are in debian/patches you
have to patch the translation patches....and add a patch for the usage
line patch

>=20
>=20
> Note: Tomasz, you may want to apply the patch proposed in
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D249611
> to in your CVS.

We still need to find a way to be sure that Tomasz takes Debian
reported bugs into account and propagates the fixes to upstream sources.