Re: Translation status robot not working?

[Camaleón <noelamac@gmail.com>]

El 2024-06-30 a las 22:53 +0200, Holger Wansing escribió:

> Hi,
> 
> Am 30. Juni 2024 17:36:32 MESZ schrieb "Camaleón" <noelamac@gmail.com>:
> >El 2024-06-30 a las 11:33 +0200, Holger Wansing escribió:
> >Well, I'm a bit «tired» (read it «softly, in the right meaning) of 
> >translating po-debconf templates that are not being updated/uploaded, 
> >for instance:
> >
> >****
> >slm¹
> >lyksom-server
> >kwartz-client
> >zoph
> >nodm
> >unattended-upgrades
> >minissdpd
> >watchdog
> >nbd
> >gitolite3
> >****
> 
> Well, looking at above packages shows, that this is in most cases not an issue 
> with the status page / webpage:
> 
> slm: bugreport closed, translation is included in unstable. But is not shown
> as done in status page.

Yup, already moticed the syntax to the maintainer.
 
> lyksom-server: there is no such package in the Debian archive. Apparently it
> has been removed from the archive shortly.

I misspelled it.

«lyskom-server» is still at BTS:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017458

> kwartz-client: bugreport closed, translation is included in unstable. But is 
> not shown as done in status page.

(...)

> >Not sure why these templates are not showing in the stats page as
> > «fully translated (100%)», not sure what I am missing here (?) because 
> >BTS is done but files are not reaching unstable repository¹ or not 
> >properly synced.
> 
> 'Your biggest problem' are bugreports, which are still open, which means they
> are not processed by the package maintainer.

Mostly, yes.

> And that in turn means, that your translation did not reached unstable, so
> the status page cannot "show it as fully translated", as you say above.
> (Those status show, what is currently in unstable !)
> 
> For this issue Helge already stated about some maintainers acting not
> optimal regarding translation update reports ... 
> Sadly!

Time is scarce, I do understand, but having a bug report with patch 
available opened for... 2 years? looks a bit overhelming :-)
> 
> 
> Thus, it leaves slm and kwartz-client as being not correctly shown on the
> status page.
> For slm I already mentioned in another mail, that there are fatal errors
> in the l10n material, which might be the reason for the processing being
> stopped for slm.
> 
> For kwartz-client however I see no reason why that should no be shown
> correctly on the status page ... :-(

Me neither :-(

Greetings

-- 
Camaleón