reopen 1072643 severity 1072643 important found 1072643 0.72 thanks Hello Martin, Am Thu, Jun 13, 2024 at 12:26:53AM +0200 schrieb Martin Quinson: > I think that the fix applied to #1072594 (recoding the input file from latin-1 > to UTF-8) was not necessary. Changing the config of po4a to correctly specify > the used encoding would have worked. > > I tried to improve the error messages upstream to help future users to debug > such issues, but in any case, this does not justify a RC bug against po4a, > thus > closing.
I'm not arguing the severity (I left it intentionally to you after closing), but there still is a bug. I leave this to you and Santiago, but making several pages suddenly FTBFS is IMHO at least serious. For several years (probably something like 10 years) this worked without problem, now it fails (and with a very strange message). If the previous po4a was buggy, i.e. allowed broken config files, then a warning or NOTE during updates would be mandated, but switching this (inadverently, probably) to a strange or even fatal error message is not sufficient. Here is the statement from Santiago: From: Santiago Vila <sanv...@debian.org> To: 1072...@bugs.debian.org, Helge Kreutzmann <deb...@helgefjell.de> Subject: Regression: po4a fails on valid non-utf8 file Date: Wed, 5 Jun 2024 19:03:48 +0200 (Adding this note to the cloned bug) Note: If you take a look at the FTBFS bugs I reported yesterday: https://people.debian.org/~sanvila/build-logs/202406/?C=M;O=A you can see that several of them are also a consequence of this change in po4a. So, I fully support that this kind of behaviour change deserves at least an entry in NEWS.Debian. Thanks. So no, this bug is not closed. Greetings Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: PGP signature
