Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.rc > #365126 > unrolled thread

Bug#1072594: This was not a failure caused by po4a, but a misconfiguration in goobox

Started byMartin Quinson <Martin.Quinson@ens-rennes.fr>
First post2024-06-13 00:40 +0200
Last post2024-06-13 11:40 +0200
Articles 4 — 3 participants

Back to article view | Back to linux.debian.bugs.rc

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#1072594: This was not a failure caused by po4a, but a misconfiguration in goobox Martin Quinson <Martin.Quinson@ens-rennes.fr> - 2024-06-13 00:40 +0200
    Bug#1072643: Po4a needs to announce stricter parsing of config files Santiago Vila <sanvila@debian.org> - 2024-06-13 11:40 +0200
      Processed: Re: Po4a needs to announce stricter parsing of config  files "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-06-13 11:40 +0200
    Bug#1072643: Po4a needs to announce stricter parsing of config files Santiago Vila <sanvila@debian.org> - 2024-06-13 11:40 +0200

#365126 — Bug#1072594: This was not a failure caused by po4a, but a misconfiguration in goobox

FromMartin Quinson <Martin.Quinson@ens-rennes.fr>
Date2024-06-13 00:40 +0200
SubjectBug#1072594: This was not a failure caused by po4a, but a misconfiguration in goobox
Message-ID<IOENj-2twT-19@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

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.

Thanks for reporting,
Mt

[toc] | [next] | [standalone]


#365139 — Bug#1072643: Po4a needs to announce stricter parsing of config files

FromSantiago Vila <sanvila@debian.org>
Date2024-06-13 11:40 +0200
SubjectBug#1072643: Po4a needs to announce stricter parsing of config files
Message-ID<IOP62-2CuB-5@gated-at.bofh.it>
In reply to#365126
severity 1072643 normal
reopen 1072643
thanks

Note: The commands from Helge did not work, I'm reopening as "normal".

Thanks.

[toc] | [prev] | [next] | [standalone]


#365141 — Processed: Re: Po4a needs to announce stricter parsing of config files

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2024-06-13 11:40 +0200
SubjectProcessed: Re: Po4a needs to announce stricter parsing of config files
Message-ID<IOP62-2CuB-9@gated-at.bofh.it>
In reply to#365139
Processing commands for control@bugs.debian.org:

> severity 1072643 normal
Bug #1072643 {Done: Martin Quinson <Martin.Quinson@ens-rennes.fr>} [po4a] Regression: po4a fails on valid non-utf8 file
Severity set to 'normal' from 'serious'
> reopen 1072643
Bug #1072643 {Done: Martin Quinson <Martin.Quinson@ens-rennes.fr>} [po4a] Regression: po4a fails on valid non-utf8 file
Bug reopened
Ignoring request to alter fixed versions of bug #1072643 to the same values previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1072643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072643
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]


#365140 — Bug#1072643: Po4a needs to announce stricter parsing of config files

FromSantiago Vila <sanvila@debian.org>
Date2024-06-13 11:40 +0200
SubjectBug#1072643: Po4a needs to announce stricter parsing of config files
Message-ID<IOP61-2CuB-1@gated-at.bofh.it>
In reply to#365126
Hello Martin.

Please disregard the severity aspect of this bug. The RC status
was just an artifact of a FTBFS bug being reassigned to another
package. I agree that it would have been better to downgrade at
the same time of doing the reassign.

Everything we ask (Helge and I) is that this is documented a little
bit better. Let me tell you a somewhat personal story: I have never
used NEWS.Debian before, but recently I did a potentially breaking
change in base-files (the way /etc/profile.d/*.sh snippets are read)
and I was suggested to use a NEWS.Debian for that, which I did,
after checking that it would help.

In this case, I fixed one of the affected packages myself,
because it was orphaned and anybody could fix it without
asking for permission:

https://tracker.debian.org/news/1535648/accepted-apt-build-01250-source-into-unstable/

For the fix, I recoded some files to UTF-8. However, in the previous message
you said that it was not really necessary. So, at this point, I still don't
know what is the exact nature of the behaviour change that makes some
packages to FTBFS, so I believe I would be one of those who would have benefited
from having a NEWS.Debian file.

Thanks.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.bugs.rc


csiph-web