On Mon, Nov 4, 2013 at 4:09 PM, Yamaban
On Mon, 4 Nov 2013 21:52, Jan Ritzerfeld
wrote: Am Montag, 4. November 2013, 15:18:48 schrieb Raymond Wooninck:
[...] can you try the chromium package (the 30.0.xxx one), to see if this one works with the old libicu libs ? I have adjusted the build to utilize the internal libicu again for 12.2 and 12.3.
[snip]
and I will submit it as a Maintenance update.
Now you some kind of lost me since I am relatively new to this: Why do we need a maintenance update here?
1. a "Maintenance update" lands in the "distro update" repo, instead of just the network:chromium repo. and is thus available for all via "zypper patch".
2. the hole happening (around libicu) gets more and better documentation than otherwise, including corresponding bnc entries, and can now be found and handled when other software hits the same bug(s)
3. the security team can do an evalution about the reach and level of the problem the old libicu bears, e.g. what packages are hit by this, does this open exploidable holes, etc.
does this overview help to answer your question? Anybody else, please correct me if I got things wrong here, as I'm just human, and not omnipotent, nor all-knowing.
- Yamaban.
A little more clarification: OBS has 3 rings of repositories: Distribution level such as 12.2 or 12.3 is the most formal Devel level is less formal, but expected to be kept usable Home level is the wild west and there are no generic guidelines openSUSE does formal releases at the distribution level every 8 months and supports them for 18 months. If bugs are found in the released products, it is normal practice to get an update into the updates repository to fix the problem. The devel repositories are lesser repositories and there is no update life expectancy associated with them. Certainly fixing a bug in the distro only in a devel repo would be considered bad form. Greg Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org