Open Bug 1490598 Opened 2 years ago Updated 6 days ago
Language packs on addons
.thunderbird .net not updated for Thunderbird 60/68
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0 Build ID: 20180830143136 Steps to reproduce: I tried to install Deutsch Language Pack. Actual results: It does not work (install button deactivated) as the Language Pack is only compatible with 52.0 and not the most recent 60.0 Release. Expected results: The Deutsch Language Pack should be available for 60.0, too (which was released more than a month ago).
This affects all language packs by Mozilla on addons.thunderbird.net. The German one can be found at https://addons.thunderbird.net/en-US/thunderbird/addon/deutsch-de-language-pack-thund/ Andreas, do you know whom to talk to to upload the new language packs. Franz, for now you can download the language packs from http://ftp.mozilla.org/pub/thunderbird/releases/60.0/win64/xpi/ de.xpi is German. Right-click and save the links.
Status: UNCONFIRMED → NEW
Component: de / German → Add-Ons: General
Ever confirmed: true
Product: Mozilla Localizations → Thunderbird
Summary: Thunderbird-60.0: Deutsch Language Pack not compatible → Language packs on addons.thunderbird.net not updated for Thunderbird 60
Sebastian: Thx for the reply. I tried to get it working with the linked de.xpi. Still all in English. Tried it.xpi, same issue. They get copied to default_profile/extensions and renamed (looks like in firefox) but apparently not used. It is a different issue, I think. Do you know if it is already reported? How can I debug this issue?
You still need to manually activate the language pack: 1. Go to Thunderbird's Options. 2. Go to "Advanced" > "General" 3. Open the "Config Editor" and confirm the warning. 4. Right-click the list and choose "New" > "String". 5. Use as name intl.locale.requested and set the value to de 6. Close Thunderbird and launch it again.
Thank you very much! That did the trick. And sorry for the dumb questions. Never had to use the advanced config editor before.
This is a little weird. I've fixed the issue preventing web extensions from uploading to addons.thunderbird.net, but they can't be approved right now because addons-server tries to sign them, and we don't have a working signing server nor do I think we can even have one. I don't know if I can just disable signing in the code or if that will produce language packs that won't enable by default or what.
I got this to upload by disabling signing, but addons-server only recognizes web extensions as compatible with Firefox by default, so you have to manually force compatibility for Thunderbird on the versions page (https://addons.thunderbird.net/en-US/developers/addon/deutsch-de-language-pack-thund/versions/2468594) otherwise it won't be installable for Thunderbird and in fact the page will break because it tries to redirect you to AMO, since the addon is only compatible with Firefox, creating a circular redirect.
Also, all the versions have a buildid string in them, which seems less than ideal. "Version 60.0buildid20180731173940" is what is displayed after upload, rather than Version 60.0.
Thx Andrei! The language pack is available now and auto update from 52 to 60 worked. Unfortunately the GUI is still in English. I have to manually set intl.locale.requested in the advanced config editor.
Is it normal to have to manually enable these? I don't really know how they're supposed to work.
Before the 60.0 switch it usually was enough to install and enable the language pack addon.
So for Firefox, there is some releng magic that creates and uploads the language packs from automation, hence the 60.0buildid20180731173940 version number. We may have to do something like this as well. ni? rjl to figure this out. It would also be great if on addons.thunderbird.net we could assume that WebExtensions are (only) compatible with Thunderbird by default.
Flags: needinfo?(philipp) → needinfo?(rob)
(In reply to Philipp Kewisch [:Fallen] [:📆] from comment #11) > It would also be great if on addons.thunderbird.net we could assume that > WebExtensions are (only) compatible with Thunderbird by default. If we do this, it does mean that you will be able to upload any Firefox web extension, it will be auto approved and available for download/install, but probably won't work. Maybe that's not a big deal, but it is a regression from legacy extensions, because Web Extensions don't have any application compatibility information beyond "gecko". I dunno if this is intentional, if we're supposed to be guessing the application compatibility based on the permissions and chrome_resources used by the extension, but it seems like it'd be a lot easier if we could just require addiong Thunderbird to the application list for all TB Web Extensions manifests. Maybe that goes against the design intention though, I don't really understand how this was supposed to work.
I took a real quick look, and there are some taskcluster tasks defined for Firefox that deal with signing and uploading langpack addons: release-sign-and-push-langpacks release-beetmover-signed-langpacks release-beetmover-signed-langpacks-checksums Those would need to be ported over to Thunderbird. Additionally, new scopes will need to be created within Taskcluster to support uploading to addons.thunderbird.net.
Counting up some of what I am guessing are the most used languages, I get 600,000 users. We failed to track this for release. So we need to prioritize fixing this. Rob, how long might this take and can it go to the top of your list?
I don't have a good sense of how long this will take unfortunately. A lot depends on ATN and what it's capabilities are, and at the moment it's a black box for me. I'll try to pull together what needs to be done. I'll likely need input/help from :sancus. In the short-term, can we set up a knowledgebase article or wiki page with the alternate install instructions described earlier in this bug to grab the XPI from the ftp site and install that way? (See comment 1 and comment 3) I realize it's not ideal, but we can at least get people going that way.
(In reply to Wayne Mery (:wsmwk) from comment #15) > Counting up some of what I am guessing are the most used languages, I get > 600,000 users. Wayne, can you please clarify this. What are these language packs used for? Everyone can download a localised version of TB with the language pack already installed. In TB 60 it's quite cumbersome to activate an installed language pack or switch between them. Somehow I'm missing the urgency of this.
I'm not an intl user, so I have no clue to answer either question of what and urgency. But there are two bug reporters who can be asked, plus whoever is in SUMO such as https://support.mozilla.org/en-US/questions/1240358 Perhaps there is a lot of overlap, or many users don't care. Cut 600k in half and it still a high percentage of users, so this at least deserves a strong assessment by us.
Even if we fix this, those 600.000 users will then run into bug 1437480. They'll need to set pref "intl.locale.requested". Exposing this in the UI has only arrived in TB 63 in bug 1481852 which we can't backport.
The language packs are often used for: - portable version of TB - Linux distros if they do not provide langpack as a package in their repository - if someone installs English version of TB and consider installing different version not-safe or too difficult - or if they simply do not know it is possible (usually other sw allows to switch languages seamlessly compared to TB).
(In reply to Rob Lemley [:rjl] from comment #16) > I don't have a good sense of how long this will take unfortunately. A lot > depends on ATN and what it's capabilities are, and at the moment it's a > black box for me. Firefox has a job that does this for AMO, so you should be able to copy a lot from there. Essentially there is a user that does the upload via the API, and the secret is stored with the others. Hope it helps!
> Firefox has a job that does this for AMO, Back to Rob :)
I will see what I can come up with.
There is work being done on the Firefox langpack addons process in bug 1566298, so this is an opportune time to get these working on Thunderbird, uploading to addons.thunderbird.net. First pass at porting the Taskcluster kind files from Firefox.
Comment on attachment 9078323 [details] [diff] [review] tb_langpack_ATN_taskcluster.patch Note: This reflects the more-recent work I'm doing here -- however it does not yet work (I need to get autograph support for a new signing user that can sign addons, AND I need to modify the AMO submission user to be @mozilla.com -- you may want to chat with me before implementing :-)
Assignee: rob → nobody
You need to log in before you can comment on or make changes to this bug.