[opensuse-packaging] Re: [opensuse-factory] Extended Chromium builds for openSUSE !
Am Mittwoch, 30. Oktober 2013, 22:44:27 schrieb ich:
[...] For me (oS 12.3), at least chromium-beta crashes whenever it tries to autofill. That is, it even crashes in its own settings. This is caused by a very old bug in libicu 49.1[0][1] that is fixed in 49.1.2, thus not affecting Factory. However, 12.3 and 12.2 have this 18 months old icu. I branched icu of 12.3 and updated it to 49.2.1 in https://build.opensuse.org/package/show/home:jritzerfeld:branches:openSUSE :12.3:Update/icu.openSUSE_12.3_Update Can anyone else confirm that this problem really exists and libicu 49.1.2 fixes the problem? [...] [0] https://code.google.com/p/chromium/issues/detail?id=122499 [1] http://bugs.icu-project.org/trac/ticket/9283
I filed a bug report: https://bugzilla.novell.com/show_bug.cgi?id=848553 and prepared maintenance updates for 12.2 and 12.3. According to http://en.opensuse.org/Portal:Maintenance I set its state to NEEDINFO maintenance... Is it still true that I now have to wait for a positive review by the Maintenance Team *before* I create a request for starting a maintenance incident? Gruß Jan -- A system tends to grow in terms of complexity rather than of simplification, until the resulting unreliability is intolerable. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Saturday 02 November 2013 13:35:37 Jan Ritzerfeld wrote:
I filed a bug report: https://bugzilla.novell.com/show_bug.cgi?id=848553 and prepared maintenance updates for 12.2 and 12.3. According to http://en.opensuse.org/Portal:Maintenance I set its state to NEEDINFO maintenance... Is it still true that I now have to wait for a positive review by the Maintenance Team *before* I create a request for starting a maintenance incident?
Hi Jan, No, just submit the update as a maintenance request or as a normal request to 12.2:Update and 12.3:Update. Mention the Submit Request numbers in the bug report and then the Maintenance team will take it from there. They would validate if they can/will accept the update, build it separately, etc. Regards Raymond -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Am Samstag, 2. November 2013, 16:09:59 schrieb Raymond Wooninck:
[...] No, just submit the update as a maintenance request or as a normal request to 12.2:Update and 12.3:Update.
Okay. I completely reworked the update and now only need one patch: https://build.opensuse.org/project/show/home:jritzerfeld:branches:OBS_Mainta...
Mention the Submit Request numbers in the bug report and then the Maintenance team will take it from there. They would validate if they can/will accept the update, build it separately, etc.
I will do this. Thanks, Raymond! However, since this problem is triggered by network:chromium using the system libicu instead of its "own" it maybe easier to fix it there? I do not know whether this is possible in this case as it was with libxml (bnc#825157). libicu of oS 13.1 should be recent enough to use it while 12.2, 12.3, and Tumbleweed use a too old version of libicu49. Gruß Jan -- Government can't change the course of the ship, it merely adjusts the compass. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Am Sonntag, 3. November 2013, 16:15:17 schrieben ich:
[...] However, since this problem is triggered by network:chromium using the system libicu instead of its "own" it maybe easier to fix it there? [...]
I forgot to mention that the chromium provided by standard oS 12.3 works fine because it uses its own libicui8n while it seems to use the other libicu libraries of the system. Thus, I would like to avoid breaking other stuff by updating libicu in 12.2 and 12.3. Gruß Jan -- Habit is stronger than reason. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Sunday 03 November 2013 16:25:29 Jan Ritzerfeld wrote:
I forgot to mention that the chromium provided by standard oS 12.3 works fine because it uses its own libicui8n while it seems to use the other libicu libraries of the system. Thus, I would like to avoid breaking other stuff by updating libicu in 12.2 and 12.3.
Hi Jan, 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. Please let me know if this one works and I will submit it as a Maintenance update. Regards Raymond -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
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.
Okay. What I did is: * Fresh 12.3 installation * Installed all available updates (without adding any additional repos) * Installed 1-click http://software.opensuse.org/ymp/network:chromium/openSUSE_12.3/chromium.ymp?base=openSUSE%3A12.3&query=chromium * "rpm -qi chromium" says chromium-30.0.1599.114-565.1.x86_64 * "ldd /usr/lib64/chromium/chromium | grep libicui18n" yields in no output * Opened chromium settings => *no* crash Then I: * installed chromium-beta from the same repository and * opened chromium settings => crash
Please let me know if this one works
Works fine. Many thanks again, Raymond! I will put these findings into my bug report.
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? Gruß Jan -- Only God can make a random selection. (Even though the computer randomly chose this message) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Mon, 4 Nov 2013 21:52, Jan Ritzerfeld <suse@...> 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. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Mon, Nov 4, 2013 at 4:09 PM, Yamaban <foerster@lisas.de> wrote:
On Mon, 4 Nov 2013 21:52, Jan Ritzerfeld <suse@...> 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
On Monday 04 November 2013 16:21:15 Greg Freemyer wrote:
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.
Furthermore regular updates are provided for packages with Security fixes, (And this included Chromium). Raymond -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Am Montag, 4. November 2013, 22:09:21 schrieb Yamaban:
On Mon, 4 Nov 2013 21:52, Jan Ritzerfeld <suse@...> wrote: [...]
Now you some kind of lost me since I am relatively new to this: Why do we need a maintenance update here? [...]
does this overview help to answer your question? [...]
Yes, indeed. Thanks, Yamaban! The first paragraph was totally new for me. The second and third seem obvious, after reading them. :) Just out of curiosity, how is such a maintenance update prepared technically? "osc maintained chromium" does not list network:chromium... Gruß Jan -- If you're not confused yet, you haven't been paying attention. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (4)
-
Greg Freemyer -
Jan Ritzerfeld -
Raymond Wooninck -
Yamaban