[Bug 731832] New: [chromium] Unstable alpha/beta snapshots submitted to Stable repo
https://bugzilla.novell.com/show_bug.cgi?id=731832 https://bugzilla.novell.com/show_bug.cgi?id=731832#c0 Summary: [chromium] Unstable alpha/beta snapshots submitted to Stable repo Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: All URL: https://www.srware.net/en/software_srware_iron_downloa d.php OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: kamikazow@web.de QAContact: qa@suse.de Found By: --- Blocker: --- As I write this, the latest Chromium version in the main openSUSE repo is 17.x which currently is in alpha state. The stable version of Chrome is 15.x. Alpha/beta versions are for Factory, not Stable repos. Serious bugs can hit Chromium any day. Chromium version in Stable should follow Google Chrome 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#c
zj jia
https://bugzilla.novell.com/show_bug.cgi?id=731832
https://bugzilla.novell.com/show_bug.cgi?id=731832#c1
Raymond Wooninck
https://bugzilla.novell.com/show_bug.cgi?id=731832
https://bugzilla.novell.com/show_bug.cgi?id=731832#c2
--- Comment #2 from Markus K
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#c3
--- Comment #3 from Raymond Wooninck
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 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
https://bugzilla.novell.com/show_bug.cgi?id=731832
https://bugzilla.novell.com/show_bug.cgi?id=731832#c5
Pavol Rusnak
https://bugzilla.novell.com/show_bug.cgi?id=731832
https://bugzilla.novell.com/show_bug.cgi?id=731832#c6
Markus K
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#c7
Cristian Rodríguez
https://bugzilla.novell.com/show_bug.cgi?id=731832
https://bugzilla.novell.com/show_bug.cgi?id=731832#c8
Raymond Wooninck
participants (1)
-
bugzilla_noreply@novell.com