http://bugzilla.opensuse.org/show_bug.cgi?id=1086036 http://bugzilla.opensuse.org/show_bug.cgi?id=1086036#c1 --- Comment #1 from Dominique Leuenberger <dimstar@opensuse.org> --- pfft... yeah, this was being disabled as in earlier discussions this was clearly dubbed as 'useless for Tumbleweed, where we get the upstream translations will regular package updates anyway' - of course nobody took leap into account with this. And the package translation-update-upstream is an empty package (so also not exactly the same as used in SLE/Leap, which helped greatly in hiding this away) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1086036 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lnussel@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1086036 http://bugzilla.opensuse.org/show_bug.cgi?id=1086036#c4 --- Comment #4 from Stanislav Brabec <sbrabec@suse.com> --- Tumbleweed will always have an empty or nearly empty tarballs. It makes sense to run these script in the late Beta / RC stage. I spent last week on translations updates, so updates are on its way to SLE. I can submit them to Leap, but it needs the same translation-update-upsrteam for both. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1086036 http://bugzilla.opensuse.org/show_bug.cgi?id=1086036#c5 --- Comment #5 from Ludwig Nussel <lnussel@suse.com> --- leap pulls translation-update-upstream from SLE so as soon as it is checked in there it will get submitted to Leap. I guess the condition should be changed to check for sle_version instead. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1086036 http://bugzilla.opensuse.org/show_bug.cgi?id=1086036#c7 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #7 from Dominique Leuenberger <dimstar@opensuse.org> --- Discussed with sbrabec on IRC, the agreed path forward should be: * unconditionally enable t-u-u again in all packages * on Tumbleweed, translation-update and translation-update-upstream are placeholder packages without content (stale content was what lead to strange translations in the past, which triggered the disabling of for oS) * Leap and SLE being in sync, can share the t-u and t-u-u packages * For Leap there is the risk that some packages handled by t-u (post install updates) differ between SLE and Leap; those might need extra care -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1086036 http://bugzilla.opensuse.org/show_bug.cgi?id=1086036#c13 --- Comment #13 from Stanislav Brabec <sbrabec@suse.com> --- Just FYI: As SLE is in late RC phase and Leap still accept changes, and translation-update-upstream is a package that can be broken by any difference, I decided to to perform translation packages split now.

From now on, SLE 15 and Leap 15 translation packages will differ.

It keeps safe both products at cost of running all scripts twice from now on. But anyway, thanks for your effort. It helped to keep common translation package as long as possible. In future, I would like to provide a per-package OBS translation-update service that will prevent this type of problems completely. Maintenance of a centralized database of all translation updates and making updates currently takes me too much time. -- You are receiving this mail because: You are on the CC list for the bug.