https://bugzilla.novell.com/show_bug.cgi?id=353229 Summary: While updating purge translation-update Product: openSUSE 11.0 Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: ke@novell.com QAContact: jsrain@novell.com CC: gekker@novell.com, lmichnovic@novell.com, robin.listas@telefonica.net Found By: --- As part of bug 350693 we release "translation overrides" translation-update for 10.3. Package names are translation-update and as sub-packages translation-update-de, translation-update-es, translation-update-fi, translation-update-ja, and translation-update-pt_BR. In the past, we did something similar for SLE10 and SLE10 SP1 (more to come). At update time we must make sure to remove these packages. To make this happen, I'll add empty packages for 11.0 (and, if wanted for SLE11). Now we must find a way, that translation-update and the sub-package will always be available on the installation media (and in the patterns?). See Ladislav's comment in bug 350693#c2 : Date: Thu, 6 Dec 2007 15:15:53 +0100 From: Ladislav Michnovič Subject: Re: [opensuse-translation] translation-update 2007/12/6, Carlos E. R. <>:
The Thursday 2007-12-06 at 10:46 +0100, Karl Eichwalder wrote:
For LCN it would be harder, because the translations are distributed in various packages.
This could be done using the overload strategy with the shadow directory for the .mo files. We did those things for SLED10. The package name is translation-update.
The tough part is to get rid of the package if you update from 10.3 to 11.0.
Ouch.
It has to be an optional package, with a warning to the user; and then try to remind whoever does that in Yast development to remove the package on upgrade... not a clean solution, it can backfire.
I have an idea how to solve it. Create this package within Suse and do a proper numbering. For example 10.3.x.y, which shows, that it is connected to openSUSE Linux 10.3. Release translation updates as often as needed, but when next SuSE release comes, renumber it to 11.0.x.y and make this package empty. This package will come within installation media and it would be without any files, only README for some information. If somebody will do an update, YaST, zypper, rpm can handle this and will erase all files which was installed on the system by that package in previous version. One thing is needed, to make some dependency on some basic package or Pattern which will ensure, that this package will be always installed. Ask YaST2 maintainers for details. Regards Ladislav. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.