openSUSE Contrib November 2011

contrib@lists.opensuse.org

5 participants
27 discussions

[Bug 731832] [chromium] Unstable alpha/beta snapshots submitted to Stable repo

by bugzilla_noreply＠novell.com

https://bugzilla.novell.com/show_bug.cgi?id=731832 https://bugzilla.novell.com/show_bug.cgi?id=731832#c6 Markus K <kamikazow(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|kamikazow(a)web.de | --- Comment #6 from Markus K <kamikazow(a)web.de> 2011-11-23 16:43:46 UTC --- (In reply to comment #5) > The problem is there is no such thing as stable branch of Chromium. Google > release engineering is crap, because you can't tell if the release is a feature > release or bugfix release. Well, the stable branch in always latest major version number -2. So currently 15 is stable, 16 is beta, 17 is alpha. > Markus, do you have some trick how to decide which version is "stable" enough > for Factory? That would help greatly. Well, after looking at Arch's PKGBUILD [1] it's actually very easy. The tarball of the latest Chromium has exactly the same version number as Google Chrome. The latest stable version can either be automatically found out by parsing the XML file http://commondatastorage.googleapis.com/chromium-browser-official and then looking for the newest "LastModified" of major-2 (probably not worth the effort writing a parser) or by simply grabbing the newest version number from http://googlechromereleases.blogspot.com/search/label/Stable%20updates and manually modifying the specfile every few weeks. In specfile syntax the tarball can be acquired via http://commondatastorage.googleapis.com/chromium-browser-official/chromium-… So as of today, the specfile would specify "Version: 15.0.874.121" And the latest stable version is http://commondatastorage.googleapis.com/chromium-browser-official/chromium-… [1] https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=… -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- To unsubscribe, e-mail: opensuse-contrib+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-contrib+owner(a)opensuse.org

10 years, 7 months

[Bug 731832] [chromium] Unstable alpha/beta snapshots submitted to Stable repo

by bugzilla_noreply＠novell.com

https://bugzilla.novell.com/show_bug.cgi?id=731832 https://bugzilla.novell.com/show_bug.cgi?id=731832#c5 Pavol Rusnak <prusnak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |prusnak(a)suse.com InfoProvider| |kamikazow(a)web.de --- Comment #5 from Pavol Rusnak <prusnak(a)suse.com> 2011-11-23 15:49:58 CET --- The problem is there is no such thing as stable branch of Chromium. Google release engineering is crap, because you can't tell if the release is a feature release or bugfix release. (They just increase the third number on every successful build and increase the major version when the dice falls on six, the rest is always set to 0). We knew it long time before pushing Chromium to Factory. I don't know who declared 15.0.874.0 version as stable but I know it was not Google for sure. Markus, do you have some trick how to decide which version is "stable" enough for Factory? That would help greatly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- To unsubscribe, e-mail: opensuse-contrib+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-contrib+owner(a)opensuse.org

10 years, 7 months

[Bug 731832] [chromium] Unstable alpha/beta snapshots submitted to Stable repo

by bugzilla_noreply＠novell.com

https://bugzilla.novell.com/show_bug.cgi?id=731832 https://bugzilla.novell.com/show_bug.cgi?id=731832#c4 --- Comment #4 from Stephan Kulow <coolo(a)suse.com> 2011-11-23 10:05:02 CET --- No, you will have to face the problem yourself :) As far as openSUSE repos are concerned, it's perfectly reasonable to e.g. provide both stable and unstable chromium builds. Having development versions of browsers is rather unusual, there I must agree with Markus. But Markus is free to package chromium-stable and leave the unstable branch to Raymond, I won't stand in the way (maintenance team might, they don't like too many security problems with too many browsers). I for one would prefer a stable branch too, but I'm not in a position to demand anything from Raymond - there are no such rules for openSUSE releases. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- To unsubscribe, e-mail: opensuse-contrib+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-contrib+owner(a)opensuse.org

10 years, 7 months

[Bug 731832] [chromium] Unstable alpha/beta snapshots submitted to Stable repo

by bugzilla_noreply＠novell.com

https://bugzilla.novell.com/show_bug.cgi?id=731832 https://bugzilla.novell.com/show_bug.cgi?id=731832#c3 --- Comment #3 from Raymond Wooninck <rwooninck(a)opensuse.org> 2011-11-23 08:38:34 UTC --- (In reply to comment #2) > I know. This is why until very recently Chromium simply crashed when visiting a > site with saved passwords. > Until a few days ago the latest Chromium update couldn't be installed because > of a package conflict with libv8. >From which location are you taking your chromium packages ? At least not from opensUSE_12.1 nor from openSUSE_Factory. If this was your issue, why didn't you report this as a bug ? I have the feeling here that you have a mixture of repo's from where you get Chromium and from where you get libv8. > The simple truth is: Chromium is now in the stable repository and has to obey > the rules that come with it. Fine, then I guess the only person here that can set the rules are the project manager. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- To unsubscribe, e-mail: opensuse-contrib+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-contrib+owner(a)opensuse.org

10 years, 7 months

[Bug 731832] [chromium] Unstable alpha/beta snapshots submitted to Stable repo

by bugzilla_noreply＠novell.com

https://bugzilla.novell.com/show_bug.cgi?id=731832 https://bugzilla.novell.com/show_bug.cgi?id=731832#c2 --- Comment #2 from Markus K <kamikazow(a)web.de> 2011-11-22 12:21:45 UTC --- (In reply to comment #1) > You are mixing two different products here. Chrome is a proprietary product of > Google and is not opensource. The opensource variant of Chrome is Chromium. I'm not mixing anything. I know the difference between the two. You seem to not know the difference between Factory (where you can dump alphas/betas) and Stable (where you can't). > Therefore openSUSE can only ship the Chromium product and not Chrome. I know. However there is no rule demanding that openSUSE must ship unstable snapshots. Google Chrome releases are based on a stable branch of Chromium. By your logic if Firefox was a proprietary product, the only choice left would be shipping Minefield (=Trunk nightlies) instead of a package based off the stable branch. > openSUSE always had the Chromium package in the Contrib repo's for some time > already which was always based on the latest snapshots. I know. This is why until very recently Chromium simply crashed when visiting a site with saved passwords. Until a few days ago the latest Chromium update couldn't be installed because of a package conflict with libv8. > There is nobody stopping you from downloading Google Chrome and use the > absolutely stable version. Nobody is stopping the Chromium maintainer to package Chromoium from the stable branch. > However as indicated Chromium has been living like > this inside the openSUSE repo's for the last 1.5 year and this is the first bug > report about it not being an outdated but stable release. What does it matter if I now file the first bug report. 1.5 years ago Chromium wasn't in the main Stable repo but in officially unsupported Contrib. The simple truth is: Chromium is now in the stable repository and has to obey the rules that come with it. Another simple truth is that among the popular distributions shipping Chromium, openSUSE is the only one releasing ALPHA versions as regular packages. Debian has 15.x in sid: http://packages.qa.debian.org/c/chromium-browser.html Same with Arch: https://www.archlinux.org/packages/extra/i686/chromium/ Ubuntu also ships 15.x: http://www.ubuntuupdates.org/ppa/chromium_stable_channel SRWare Iron is also based on 15.x: https://www.srware.net/en/software_srware_iron_download.php -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- To unsubscribe, e-mail: opensuse-contrib+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-contrib+owner(a)opensuse.org

10 years, 7 months

[Bug 731832] [chromium] Unstable alpha/beta snapshots submitted to Stable repo

by bugzilla_noreply＠novell.com

https://bugzilla.novell.com/show_bug.cgi?id=731832 https://bugzilla.novell.com/show_bug.cgi?id=731832#c1 Raymond Wooninck <rwooninck(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rwooninck(a)opensuse.org --- Comment #1 from Raymond Wooninck <rwooninck(a)opensuse.org> 2011-11-22 09:02:26 UTC --- You are mixing two different products here. Chrome is a proprietary product of Google and is not opensource. The opensource variant of Chrome is Chromium. Therefore openSUSE can only ship the Chromium product and not Chrome. I know that Chrome is following certain release cycles and there are indications what is stable and what is not. However these seem not valid for Chromium as that it is constantly mentioned Google Chrome. openSUSE always had the Chromium package in the Contrib repo's for some time already which was always based on the latest snapshots. Very frequent updates were provided and this will continue also now that Chromium 17.0.xxx is in openSUSE 12.1 and openSUSE Factory. There is nobody stopping you from downloading Google Chrome and use the absolutely stable version. However as indicated Chromium has been living like this inside the openSUSE repo's for the last 1.5 year and this is the first bug report about it not being an outdated but stable release. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- To unsubscribe, e-mail: opensuse-contrib+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-contrib+owner(a)opensuse.org

10 years, 7 months

[Bug 731832] [chromium] Unstable alpha/beta snapshots submitted to Stable repo

by bugzilla_noreply＠novell.com

https://bugzilla.novell.com/show_bug.cgi?id=731832 https://bugzilla.novell.com/show_bug.cgi?id=731832#c zj jia <zjjia(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia(a)suse.com AssignedTo|bnc-team-screening(a)forge.pr |opensuse-contrib(a)opensuse.o |ovo.novell.com |rg -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- To unsubscribe, e-mail: opensuse-contrib+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-contrib+owner(a)opensuse.org

10 years, 7 months

[Bug 731295] Chromium 17.0.922.0 (=?UTF-8?Q?Build=20de=20d=C3=A9veloppement=200=20Linux?=) crash with some javascript

by bugzilla_noreply＠novell.com

https://bugzilla.novell.com/show_bug.cgi?id=731295 https://bugzilla.novell.com/show_bug.cgi?id=731295#c6 --- Comment #6 from Bernhard Wiedemann <bwiedemann(a)suse.com> 2011-11-20 21:00:07 CET --- This is an autogenerated message for OBS integration: This bug (731295) was mentioned in https://build.opensuse.org/request/show/92753 12.1 / chromium -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- To unsubscribe, e-mail: opensuse-contrib+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-contrib+owner(a)opensuse.org

10 years, 7 months

[Bug 731295] Chromium 17.0.922.0 (=?UTF-8?Q?Build=20de=20d=C3=A9veloppement=200=20Linux?=) crash with some javascript

by bugzilla_noreply＠novell.com

https://bugzilla.novell.com/show_bug.cgi?id=731295 https://bugzilla.novell.com/show_bug.cgi?id=731295#c5 --- Comment #5 from Ben Kevan <ben.kevan(a)bio-rad.com> 2011-11-19 16:59:57 UTC --- Raymond, Yes, we're not supposed to use Contrib anymore. I think 11.4 even has a mis-match in the V8 versions since network:/chromium went 17.0.9xx.0. What really needs to be done is the following: Creation of network:/chromium/openSUSE_12.1 (the .spec looks just fine). Push new chromium to update/openSUSE_12.1 (this because the current build that's released with openSUSE 12.1 is broken with a major site (i.e., youtube.com). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- To unsubscribe, e-mail: opensuse-contrib+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-contrib+owner(a)opensuse.org

10 years, 7 months

[Bug 731295] Chromium 17.0.922.0 (=?UTF-8?Q?Build=20de=20d=C3=A9veloppement=200=20Linux?=) crash with some javascript

by bugzilla_noreply＠novell.com

https://bugzilla.novell.com/show_bug.cgi?id=731295 https://bugzilla.novell.com/show_bug.cgi?id=731295#c4 --- Comment #4 from Raymond Wooninck <rwooninck(a)opensuse.org> 2011-11-19 16:40:04 UTC --- Hi Ben, I am taking my packages directly from network:chromium which is the official development repo for Chromium. Both contrib_11.3 and contrib_11.4 are linked to this repo and should follow automatically the updates. For 12.1 I am not sure how to continue here. I have to talk to coolo to see how and what with regards to the update process.I have added the repo openSUSE_12.1 to network:chromium and I know that a couple of messages went already around indicating to people that they should use the network:chromium repo instead of the contrib ones. For 11.3 and 11.4 we just kept it this way for compatibility reasons. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. -- To unsubscribe, e-mail: opensuse-contrib+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-contrib+owner(a)opensuse.org

10 years, 7 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

openSUSE Contrib November 2011