Your message dated Tue, 17 Dec 2019 06:47:09 +0100
with message-id <[email protected]>
and subject line Re: Bug#946588: thunderbird's dowgrade prevention is being
triggered after upgrade from stretch
has caused the Debian Bug report #946588,
regarding thunderbird's dowgrade prevention is being triggered after upgrade
from stretch
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.)
--
946588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946588
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: thunderbird
Version: 1:68.2.2-1~deb10u1
Severity: important
The current package of thunderbird in stretch (68.2.2-1~deb9u1) reports a
bigger version number than the current package in buster (68.2.2-1~deb10u1) due
to the inclusion of the build timestamp. The version reported by stretch is
68.2.2_20191116203149/20191116203149 and buster
68.2.2_20191116193034/20191116193034.
This information is then used by thunderbird to fill the compatibility.ini in
the profile and after an upgrade from stretch to buster leads to thunderbird
prompting to either quit or create a new profile because it detects that an
older version of thunderbird is trying to open a profile last used by a newer
version. I believe
using the same profile should be safe, as the underlying upstream version is
the same at the moment and should probably never be newer in oldstable than
stable.
As a workaround it's possible to start thunderbird with the parameter "--allow-
downgrade" or manually delete the line starting with "LastVersion=" in the
compatibility.ini in the profile but less savy users may use access to the data
in their old profiles (the data is still there but a regular user will probably
not be able to access it without further instructions).
-- System Information:
Debian Release: 10.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages thunderbird depends on:
ii debianutils 4.8.6.1
ii fontconfig 2.13.1-2
ii libatk1.0-0 2.30.0-2
ii libc6 2.28-10
ii libcairo-gobject2 1.16.0-4
ii libcairo2 1.16.0-4
ii libdbus-1-3 1.12.16-1
ii libdbus-glib-1-2 0.110-4
ii libevent-2.1-6 2.1.8-stable-4
ii libffi6 3.2.1-9
ii libfontconfig1 2.13.1-2
ii libfreetype6 2.9.1-3+deb10u1
ii libgcc1 1:8.3.0-6
ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1
ii libglib2.0-0 2.58.3-2+deb10u2
ii libgtk-3-0 3.24.5-1
ii libgtk2.0-0 2.24.32-3
ii libjsoncpp1 1.7.4-3
ii libpango-1.0-0 1.42.4-7~deb10u1
ii libstartup-notification0 0.12-6
ii libstdc++6 8.3.0-6
ii libvpx5 1.7.0-3+deb10u1
ii libx11-6 2:1.6.7-1
ii libx11-xcb1 2:1.6.7-1
ii libxcb-shm0 1.13.1-2
ii libxcb1 1.13.1-2
ii libxext6 2:1.3.3-1+b2
ii libxrender1 1:0.9.10-1
ii libxt6 1:1.1.5-1+b3
ii psmisc 23.2-1
ii x11-utils 7.7+4
ii zlib1g 1:1.2.11.dfsg-1
Versions of packages thunderbird recommends:
ii hunspell-de-de [hunspell-dictionary] 20161207-7
ii hunspell-en-us [hunspell-dictionary] 1:2018.04.16-1
ii lightning 1:68.2.2-1~deb10u1
Versions of packages thunderbird suggests:
ii apparmor 2.13.2-10
ii fonts-lyx 2.3.2-1
ii libgssapi-krb5-2 1.17-3
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:68.3.0-2~deb10u1
Control: tags -1 fixed 1:68.3.0-2~deb9u1
Hello Jens, hello Robert,
the BTS should have noticed that these reports are fixed within the
upload version 1:68.3.0-2~deb10u1 for buster.
And as well for stretch by version 1:68.3.0-2~deb9u1.
So this email will close your reports now.
On Wed, Dec 11, 2019 at 12:33:14PM +0100, Jens Holzkämper wrote:
> Package: thunderbird
> Version: 1:68.2.2-1~deb10u1
> Severity: important
>
>
> The current package of thunderbird in stretch (68.2.2-1~deb9u1) reports a
> bigger version number than the current package in buster (68.2.2-1~deb10u1)
> due
> to the inclusion of the build timestamp. The version reported by stretch is
> 68.2.2_20191116203149/20191116203149 and buster
> 68.2.2_20191116193034/20191116193034.
>
> This information is then used by thunderbird to fill the compatibility.ini in
> the profile and after an upgrade from stretch to buster leads to thunderbird
> prompting to either quit or create a new profile because it detects that an
> older version of thunderbird is trying to open a profile last used by a newer
> version. I believe
> using the same profile should be safe, as the underlying upstream version is
> the same at the moment and should probably never be newer in oldstable than
> stable.
>
> As a workaround it's possible to start thunderbird with the parameter
> "--allow-
> downgrade" or manually delete the line starting with "LastVersion=" in the
> compatibility.ini in the profile but less savy users may use access to the
> data
> in their old profiles (the data is still there but a regular user will
> probably
> not be able to access it without further instructions).
Regards
Carsten
--- End Message ---
