Quoting Ian Jackson (ijackson@chiark.greenend.org.uk):
> Christian PERRIER writes ("Re: Exploring the possibility of an l10n upload of xfonts-traditional to fix pending po-debconf l10n bugs (and debconf templates changes)"):
> > - pick the PO files *as they are* in my final summary in the review
> > bug report
>
> I assume you mean #660965. You have CC'd 658416 which is a
> content-free bug report which I closed and which has now been
> archived.
Sure. This is what I meant with "my final summary in the review bug report"
> Thinking about this: you appear to be saying that the updated
> translations from #661479, #661718, etc. etc., are all in your tarball
> in #660965. In which case we should (a) put a note in the bottom of
> the other reports (b) merge or close them all ?
>
That could be done but I usually leave this aside because not every
maintainer wants to do things the same way..:-)
As, anyway, all other reports are closed by the upload, there is
indeed no real problem in having the translations files in two places.
Properly closing the individual translation bug reports can of course
be a hassle for maintainers, which is why I include a changelog
excerpt in the final summary, too.
> Given the workflow here I think it would make more sense to close the
> per-language reports. That would probably avoid the possibility that
> an updated translation would be attached to one of these reports but
> dropped in favour of the one in your tarball.
I wouldn't do that for all packages where I'm doing a review (because
having all translation bug reports is kind of a red flag in my l10n
survey scripts....showing that the said package has abunch of pending
updates for several loanguages) but I
usually adapt myself to whatever the maintainer thinks.
To summarize all this, I'm not hardly insisting on NMUing the package
(because I really fear doing something you wouldn't agree with...). My
main concern is having these translations incorporated at some not too
far point in the future so that I can move my radar to another
"target"...:-)
Attachment:
signature.asc
Description: Digital signature