Mozilla Thunderbird version 60.3.1 (Default) registry not incremented, remains at 60.3.0
Categories
(Thunderbird :: Installer, defect)
Tracking
(thunderbird_esr6067+ fixed, thunderbird67 fixed, thunderbird68 fixed)
People
(Reporter: richard.dong, Assigned: rjl)
References
Details
Attachments
(2 files, 1 obsolete file)
|
16.89 KB,
image/png
|
Details | |
|
1.59 KB,
patch
|
Paenglab
:
review+
jorgk-bmo
:
approval-comm-beta+
jorgk-bmo
:
approval-comm-esr60+
|
Details | Diff | Splinter Review |
| Reporter | ||
Updated•7 years ago
|
Comment 2•7 years ago
|
||
Comment 4•7 years ago
|
||
Comment 5•7 years ago
|
||
Comment 6•7 years ago
|
||
Comment 7•7 years ago
|
||
| Reporter | ||
Comment 8•6 years ago
|
||
This was resolved for versions 60.4.0 through 60.5.1, however I'm seeing the issue arise again on the latest 60.5.2.
Installing 60.5.2 will have 60.5.1 appear as the Data value for the (Default) key under:
HKEY_LOCAL_MACHINE\SOFTWARE\Mozilla\Mozilla Thunderbird(Default)
OR:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Mozilla\Mozilla Thunderbird(Default)
Comment 9•6 years ago
|
||
Yes, sorry, the release manager here. We shipped TB 60.5.2 base on Mozilla 60.5.1 since I didn't know that they were doing a 60.5.2 as well :-(
Will be OK again for TB 60.6.
Rob, can we tweak the build system so it uses the TB version and not the Mozilla version?
| Assignee | ||
Comment 10•6 years ago
|
||
(In reply to Jorg K (GMT+1) from comment #9)
Yes, sorry, the release manager here. We shipped TB 60.5.2 base on Mozilla 60.5.1 since I didn't know that they were doing a 60.5.2 as well :-(
Will be OK again for TB 60.6.
Rob, can we tweak the build system so it uses the TB version and not the Mozilla version?
I'll take a look and see what I can do.
Speaking to Florent in comment 3, information platform.ini should all refer to Firefox/Gecko versions and Mercurial changesets. It is entirely possible that the Milestone field in platform.ini does not match the Thunderbird version. Currently, bug 1507754 is open and documents that the SourceRepository field in platform.ini incorrectly refers to a comm- repository rather than a mozilla- one.
In contrast, most of the information in application.ini refers to Thunderbird. The exception is the [Gecko] section, which will refer to the Gecko platform version on which a particular build is based.
| Assignee | ||
Comment 11•6 years ago
|
||
| Assignee | ||
Comment 12•6 years ago
|
||
With respect to the version numbers found in the Windows Registry, it is working as designed.
This is taken from a registry dump after a clean install of 60.5.2. The same information is in the screenshot in attachment 9047254 [details].
[Software\\Wow6432Node\\Mozilla\\Mozilla Thunderbird]
@="60.5.1"
"CurrentVersion"="60.5.2 (en-US)"`
This is the NSIS installer code that writes the above.
StrCpy $0 "Software\Mozilla\${BrandFullNameInternal}"
${WriteRegStr2} $TmpVal "$0" "" "${GREVersion}" 0
${WriteRegStr2} $TmpVal "$0" "CurrentVersion" "${AppVersion} (${AB_CD})" 0
The @ key (Default) is set to the Gecko Runtime version, ${GREVersion}. In this case it's 60.5.1.
Then the CurrentVersion key is set to the application version, ${AppVersion}, or 60.5.2 (en-US) in this case.
So, it's correct in that the NSIS code very clearly is using ${GREVersion} as the value for the key in question. It's not a case of the Gecko version accidentally getting used instead of the Thunderbird version, which was my original suspicion.
The keys could probably be named more appropriately, and if you're trying to ascertain the currently installed Thunderbird version by interrogating the registry, there isn't a nice simple version number that you can get. The closest is the CurrentVersion key, but it has a l10n tag appended to it which means parsing out the version number somehow.
Without knowing the use case, I would probably change the Default key to match the Thunderbird version, then add a GeckoVer key for the Gecko version. I'll defer to Wayne to make that decision.
Comment 13•6 years ago
|
||
Sorry I don't really have experience here, so I'll defer to Jorg and others.
Comment 14•6 years ago
|
||
Yes, Rob, we can certainly change/fix the installer. Richard Marti has been working on installers. He or I would be happy to try out a try build if you don't have access to a Windows machine.
| Assignee | ||
Comment 15•6 years ago
|
||
This seems to do the right thing when run under Wine (also tested on Windows 10 x64).
I did not test a signed installer (Bug 1458385 may be causing issues here), and I did not test running the updater.
I suspect the updater will not be a problem since this is shared code.
Comment 16•6 years ago
|
||
| Assignee | ||
Comment 17•6 years ago
|
||
Removed extra newline
| Assignee | ||
Updated•6 years ago
|
Comment 18•6 years ago
|
||
Comment 20•6 years ago
|
||
Comment 21•6 years ago
|
||
Pushed by mozilla@jorgk.com:
https://hg.mozilla.org/comm-central/rev/205c80a11ab9
Use TB version as default version in Win registry. r=Paenglab
Updated•6 years ago
|
Comment 22•6 years ago
|
||
TB 67 beta 2:
https://hg.mozilla.org/releases/comm-beta/rev/daee3654255f6c952510ab43e043d30f9e15eb7c
Comment 23•6 years ago
|
||
TB 60.7 ESR (or earlier, like TB 60.6.2):
https://hg.mozilla.org/releases/comm-esr60/rev/7787632227e0da0b59c1ee1a946ce1d048b9199f
Description
•