Your message dated Fri, 13 Nov 2020 09:55:40 +0100
with message-id <5784664.boacyM5Ppe@thyrus>
and subject line Re: [Pkg-kde-extras] Bug#971879: Bug#971879: Bug#971879:
gthumb: "charset=Ascii" appears before the comment of the image
has caused the Debian Bug report #971879,
regarding "charset=Ascii" appears before the comment of the image
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
971879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971879
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gthumb
Version: 3:3.8.0-2.1+b2
Severity: normal
When viewing a JPEG image, "charset=Ascii" appears before the comment.
See attached screenshot. This is a regression.
Note that there is no issue when using the exiftool utility,
i.e. this is specific to gthumb.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500,
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.8.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gthumb depends on:
ii gsettings-desktop-schemas 3.38.0-2
ii gthumb-data 3:3.8.0-2.1
ii libbrasero-media3-1 3.12.2-6
ii libc6 2.31-2
ii libcairo2 1.16.0-4
ii libclutter-1.0-0 1.26.4+dfsg-1
ii libclutter-gtk-1.0-0 1.8.4-4
ii libexiv2-27 0.27.3-3
ii libgcc-s1 10.2.0-13
ii libgdk-pixbuf2.0-0 2.40.0+dfsg-5
ii libgl1-mesa-dri 20.1.9-1
ii libglib2.0-0 2.66.0-2
ii libgstreamer-plugins-base1.0-0 1.18.0-2
ii libgstreamer1.0-0 1.18.0-3
ii libgtk-3-0 3.24.23-2
ii libjpeg62-turbo 1:2.0.5-1.1
ii libjson-glib-1.0-0 1.6.0-1
ii liblcms2-2 2.9-4+b1
ii libpango-1.0-0 1.46.2-1
ii libpangocairo-1.0-0 1.46.2-1
ii libpng16-16 1.6.37-3
ii libraw20 0.20.0-4
ii librsvg2-2 2.50.1+dfsg-1
ii libsecret-1-0 0.20.3-1
ii libsoup2.4-1 2.72.0-2
ii libstdc++6 10.2.0-13
ii libtiff5 4.1.0+git191117-2
ii libwebkit2gtk-4.0-37 2.30.1-1
ii libwebp6 0.6.1-2+b1
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages gthumb recommends:
ii libgphoto2-6 2.5.25-3
ii libgphoto2-port12 2.5.25-3
gthumb suggests no packages.
-- no debconf information
--
Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
In data venerdì 13 novembre 2020 02:41:44 CET, Vincent Lefevre ha scritto:
> I'm reopening the bug because it also affects nomacs (though much
> less seriously since a better metadata is used by nomacs),
I'm closing this bug again, for the same reasons already explained in
my previous messages. Unless the upstream situation changes, there is
nothing actionable on the Debian side of exiv2, and thus it is
pointless to have this bug open.
> and this
> time, this is a bug introduced on the Debian side: nomacs ships with
> exiv2 0.27.2, and it is Debian's choice to link with exiv2 0.27.3.
>
> Before upgrading to the incompatible version exiv2 0.27.3, this
> should have been discussed with the nomacs maintainers.
Considering the security track of exiv2 [1], shipping an embedded copy
of exiv2 is rather bad idea, and it should not be even considered.
[1] https://security-tracker.debian.org/tracker/source-package/exiv2
--
Pino Toscano
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
