https://bugzilla.novell.com/show_bug.cgi?id=731832 https://bugzilla.novell.com/show_bug.cgi?id=731832#c zj jia <zjjia@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |zjjia@suse.com AssignedTo|bnc-team-screening@forge.pr |opensuse-contrib@opensuse.o |ovo.novell.com |rg -- 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.

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@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 on the CC list for the bug.

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@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 on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=731832 https://bugzilla.novell.com/show_bug.cgi?id=731832#c6 Markus K <kamikazow@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|kamikazow@web.de | --- Comment #6 from Markus K <kamikazow@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-%{version}.tar.bz2 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... [1] https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=p... -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=731832 https://bugzilla.novell.com/show_bug.cgi?id=731832#c8 Raymond Wooninck <rwooninck@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |WONTFIX --- Comment #8 from Raymond Wooninck <rwooninck@opensuse.org> 2011-11-25 18:23:09 UTC --- I will close this bugreport as a wontfix. The reason for this is that after the above discussion, I checked the Chromium release management and it is stated there that Chromium does not have any releases and that every distribution is free to select which package to provide to their users. Based on this I raised the question which chromium version should be provided to the openSUSE users in the opensuse-Packaging and opensuse-project mailinglists. Also we have to take into account that bringing the version of Chromium down to 15.0.894, would be impossible as that would cause issues with opening of the profiles, etc as that they were created with a newer version. The outcome of the discussion on the mailinglist was that everybody prefers to have the latest version available for openSUSE. I can very well understand your point, however I do not have the time to keep two versions of Chromium alive. However I would welcome any help that I can get and if you want you could take the maintenance of the Stable version of Chromium. I would gladly provide you with the necessary scripts, etc to do so. Regards Raymond -- 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.