Package Details: chromium-dev 126.0.6423.2-1

Git Clone URL: https://aur.archlinux.org/chromium-dev.git (read-only, click to copy)
Package Base: chromium-dev
Description: The open-source project behind Google Chrome (Dev Channel)
Upstream URL: http://www.chromium.org
Keywords: browser web
Licenses: BSD
Submitter: None
Maintainer: sl1pkn07
Last Packager: sl1pkn07
Votes: 160
Popularity: 0.27
First Submitted: 2010-05-17 09:04 (UTC)
Last Updated: 2024-04-21 19:18 (UTC)

Required by (0)

Sources (13)

Latest Comments

« First ‹ Previous 1 .. 137 138 139 140 141 142 143 144 145 146 147 .. 152 Next › Last »

<deleted-account> commented on 2010-10-02 18:16 (UTC)

mutantmonkey, bison is in base-devel group, thus it should not be included in makedepends. base-devel is a requirement to compile anything on arch.

mutantmonkey commented on 2010-10-02 16:41 (UTC)

Please add bison to makedepends, I wasn't able to build without installing it.

<deleted-account> commented on 2010-09-29 14:43 (UTC)

@jpaechnatz: Looks like http://code.google.com/p/chromium/issues/detail?id=57275, except I use -Duse_system_ssl=0. It seems you build somehow gets hooked up with the system nss in spite of that.

obbala commented on 2010-09-29 07:42 (UTC)

Since 7.0.517.8 I wasn't able to compile a newer version...caused by similar failures like: CXX(target) out/Release/obj.target/net/net/spdy/spdy_http_stream.o net/socket/ssl_client_socket_nss.cc: In Funktion »int net::<unnamed>::MapNSPRError(PRErrorCode)«: net/socket/ssl_client_socket_nss.cc:212:10: Fehler: »SSL_ERROR_WEAK_SERVER_KEY« wurde in diesem Gültigkeitsbereich nicht definiert make: *** [out/Release/obj.target/net/net/socket/ssl_client_socket_nss.o] Fehler 1 make: *** Warte auf noch nicht beendete Prozesse... Breche ab ... Do I miss a package? I already checked for nss/nspr, but they are current (maybe to new?) Thanks.

terminalmage commented on 2010-09-25 01:57 (UTC)

New official release: 7.0.517.13

Det commented on 2010-09-23 18:05 (UTC)

Well, at least the "google devs is lazy" and "only one excuse for not updating" parts made my day :).

terminalmage commented on 2010-09-22 22:54 (UTC)

Again, sl1pkn07, if you want a newer version than the latest official dev release, download the tarball (http://aur.archlinux.org/packages/chromium-dev/chromium-dev.tar.gz), unpack, modify the release number in the PKGBUILD, and run makepkg. It's not that hard. But, don't expect every tarball to build because, as baghera said, the tarballs are auto-generated and aren't guaranteed to build.

<deleted-account> commented on 2010-09-22 18:37 (UTC)

@ sl1pkn07 You should look a bit more closer at the link you provided. There are _at least_ two tarballs a day. Those are _not_ all official release, they're official tarballs generated by a buildbot. Sometimes those tarballs are broken and won't compile, while official releases tracked on the blog brings code in a consistent state. Google devs are not lazy updating the blog.

sl1pkn07 commented on 2010-09-22 18:29 (UTC)

you no look the link address? http://build.chromium.org/buildbot/>official</chromium-7.0.530.0.tar.bz2 the google devs is lazy for updating the blog (of course, working in the program) last post in dev channel: "Thursday, September 16, 2010 | 17:52" the #malix post is only one excuse for not updating this package if i have want a new version, download from the SVN... o wait: http://build.chromium.org/buildbot/official/chromium-7.0.517.8.log greetings

« First ‹ Previous 1 .. 137 138 139 140 141 142 143 144 145 146 147 .. 152 Next › Last »