Package: fwbuilder
Version: 5.3.7-3
Severity: normal

Dear Maintainer,

   * What led up to the situation?

     We have UTF8 characters in the fwbuilder database file.
     Trying to load an old revision of the database
     results in error "Error parsing XML from file [...] Input is not proper 
UTF-8 [...]"

   * What was the outcome of this action?

     it is not possible to load older revisions at all if they contain UTF8.

Using the fwbuilder debug-switch shows that when choosing an old revision,
fwbuilder calls co -pREVISION and gets the data from stdin.
It then writes the data to a temporary file where all non-ascii characters
are converted to latin1.

Looking at the source code this seems intentional:

https://github.com/fwbuilder/fwbuilder/blob/master/src/libgui/RCS.cpp#L780

I'm curious why this is happening. Shouldn't the data be written without
conversion?

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.17.0-3-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fwbuilder depends on:
ii  fwbuilder-common     5.3.7-3
ii  libc6                2.27-6
ii  libgcc1              1:8.2.0-5
ii  libgl1               1.1.0-1
ii  libqt5core5a         5.11.1+dfsg-7
ii  libqt5gui5           5.11.1+dfsg-7
ii  libqt5network5       5.11.1+dfsg-7
ii  libqt5printsupport5  5.11.1+dfsg-7
ii  libqt5widgets5       5.11.1+dfsg-7
ii  libsnmp30            5.7.3+dfsg-3
ii  libssl1.1            1.1.1~~pre9-1
ii  libstdc++6           8.2.0-5
ii  libxml2              2.9.4+dfsg1-7+b1
ii  libxslt1.1           1.1.32-2
ii  zlib1g               1:1.2.11.dfsg-1

Versions of packages fwbuilder recommends:
ii  fwbuilder-doc  5.3.7-3
ii  rcs            5.9.4-4

fwbuilder suggests no packages.

-- no debconf information

Reply via email to