Am 21.09.18 um 17:28 schrieb Carsten Schoenert: > >> So IMHO the thunderbird-l10n-$(lang) packages should recommend the >> corresponding lightning-l10n-$(lang) package, >> since thunderbird recommends lightning. > Only a small amount of users is able to really understand what > Recommends and Suggests means. And the real problem is more the really > depending package here. But we have no way to detect the correct > circumstances and needs by dpkg here. So we need to solve this problem > in a different way than using Recommends. My idea was that when lightning was installed alongside thunderbird because of the recommend (i.e. the user did not call apt with "--without-recommends"), the lightning-l10n package should be installed, too. (at least it would have saved me some time finding this. I first tried to debug this locally before I went to the bugtracker ;-) ) This would mean, that in a default debian-setup in most cases one of two cases would happen: - don't install recommends: only installing thunderbird-l10n-XX would not install lighting, so no problem (thunderbird is installed via depends) - install recommends: lightning is installed via recommends, as well as the language-pack, so also no problem
The current state (lighting-l10n missing) would require some manual intervention. >> (I used to only "apt install thunderbird-l10n-de", which pulled in >> thunderbird and lightning by depends/recommends, and >> just now wondered where my calendar is ;-) ) >> >> Even better would be to detect the missing lightning-l10n-pack and >> either let lightning fallback to english or, if that is somehow >> not possible, notify the user. > Unfortunately all this is impossible. We have no way to interact here > with Thunderbird and control the behavior of the Thunderbird binary then. I suspected something like that... However I still find it somewhat strange, that there is no indication inside thunderbird that something is not alright, I would either expect it to simply fallback to english, or to show an error somewhere. (In my case, coming from software-development myself, even a rather cryptic "l10n-error: could not open calendar-de/something" would have helped ;-) But if I understand you right, thats because the debian-packaging deviates from the way mozilla is distibuting this? (Would this problem also arise with thirdparty extensions, i.e. extensions not normally bundled with thunderbird?) > We could have detect this all earlier if user would test also packages > from experimental. :) > ;-)
