=== asac_ is now known as asac [01:09] * BUGabundo $ mv /home/BUGabundo /media/bed ; operation time out === ripps is now known as ripps|sleep [15:15] asac, i've committed (yesterday) something that should help you building chromium on arm out of the box [15:15] asac, i backed off the gyp/make patch for now, it's not ready [16:08] fta: is that already in todays daily i can grab? [16:09] let me check where it failed exactly ... didnt feel like it was in v8 [16:09] * asac boots the other system [16:09] bbi 30 minutes [16:13] on arm, it should fail in v8 snapshot, and in nacl (native client) [16:13] so i disabled those for you [16:23] ur right [16:23] great [16:23] now need to grab latest daily? [16:28] ok spinning daily from 3 minutes ago :) [16:28] great [16:29] so make isnt ready? ... too many bugs or just for one day work too much? [16:41] i'd say it's close, but needs at least two fixes. i Cced you yesterday [16:43] btw, are you on lucid already? [16:43] wonder if i should go and upgrade at least the main desktop [16:43] thing [16:44] no, still karmic [16:46] ok guess i can do some housecleaning and go for dinner etc. while this thing builds [16:50] lol [17:05] but maybe it just works :) [17:05] lets hoppe= [17:05] building v8/custom stuff atm [17:05] ok gone for a bit [18:31] ... still spinning [18:32] guess that means its promissing :) [18:32] somewhere in the middle of webkit HTML stuff ... probably takes 12+ hy [18:34] didn't you say that we'll have a xen/arm builder soon? [18:35] asac, ^^, what will it be? arm on i686 h/w? or just arm on arm h/w? [18:35] asac: hi... is chromium only available in the ppa? [18:35] and not in the ubuntu repos? [18:36] nice job getting chromium going on arm [18:36] mac_v, yes [18:37] ah.. ok.. but why is it so? [18:37] mac_v, talk to asac or fta about that [18:40] there's no upstream release for linux for one, and there's 33.000 source files / 600MB to review for licenses [18:40] but technically, it's good enough imho [18:40] fta, i'm running it as my default browser [18:41] great [18:41] ah.. right no upstream release.. ok [18:41] lucid will be chromium :) [18:41] ;p [18:41] asac, what? [18:42] asac: will it atleast be in the universe? ;p [18:42] ... for mobile at least :) [18:42] mac_v: yes... we are getting it in the archive (probably by bribing archive admins or something like that) [18:42] lol ;) [18:42] asac, i think i should add thumb too for arm [18:43] heh , i tried it long back , but i missed mouse gestures.. so came back to ff :) [18:43] fta: its default for toolchains that support it [18:43] so no need to add it [18:43] basically we do everything in toolchain [18:43] easier than adding stuff that is release specific [18:43] thought you said it will be, but it's not there yet [18:43] its in lucid [18:43] oh [18:43] only thing that isnt in is the implicit-it legacy flag [18:43] that will come soon [18:44] ok [18:44] but we need xulrunner build now, so i added it [18:44] hopefull thum also makes firefox snappier on arm [18:44] so in worst case we can keep using firefox in mobile UNE [18:44] arm UNE to be specific [18:45] ok uploaded xul with that flag ... lets hope thats enough [18:47] hmm gwibber seems to be dying all the time [18:47] when did that start again ?>( [18:47] did someone push an update to -proposed or for webkit or something? [18:47] no idea, it's stable here [18:49] so, arm ppa anytime soon? [18:50] only for native ppas for now still [18:50] we are working on improving tools so folks without arm hardware can build/run/test arm stuff [18:50] maybe by alpha-2 they are mature enough [18:51] the ppa support is basically blocked on lack of xen support for arm afaik [18:51] http://wiki.xensource.com/xenwiki/XenARM ? [18:52] yes. i think there is work going on that is promissing [18:52] but i'm not sure it's arm on arm or arm on i686 [18:52] it says Xen on ARM VMM [18:53] i would think its arm in xen vm on i386 [18:53] fta: is there another ppa , other than this? > https://edge.launchpad.net/~chromium-daily/+archive/ppa , something more stable ;) or is this fairly stable? [18:53] which is probably what we want anyway for virtual builders [18:53] unless we want to do a 100 builder farm :) [18:53] anyway ... first hardware must become available for normal users [18:53] once that is achieved i dont think it will take long to make this more ubiquous in all ways [18:55] CachedScript.cpp :2~) [18:55] not sure if that is at least 30% :) [18:55] CrossOriginAccessControl.cpp now :) [18:56] fta: i think we need to put full copyright info for all the licenses listed in copyright in the file [18:57] or reference them from common [18:57] just fyi [18:58] yes, but even before that, i wanted all the chromium files clarified. for 3rd party, i just wanted to steal from our system packages [18:58] good idea [18:59] wonder if its a good idea to do parallel building for arm :) [19:00] well ... as long as its a remote porter machine its probably ok [19:00] poing is that this machine only has 512k mem :) [19:00] so swapping to death [19:01] hmm ... otoh its not that big atm [19:01] 99m [19:01] for each xcc1plus [19:02] funny how google experiments stuff on users in releases: http://codereview.chromium.org/434110 [19:02] hehe ... good that we dont have any releases yet o nlinux:) [19:02] 0.5% of users will participate :) [19:03] guess that means: without being asked [19:03] i was planning to do some [19:04] to do some? [19:04] experiments? [19:04] how do you get feedback? [19:05] no, releases [19:05] based on their 3 channels, somehow [19:06] hmm [19:06] thought they do not publish all the info to replay those channels yet [19:06] has that changed?= [19:06] they don't, so i'm trying to auto-guess [19:10] asac: shall i schedule Bug #386900 , for Lucid? [19:10] Launchpad bug 386900 in network-manager ""Auto eth0" in notifications is confusing" [Wishlist,Confirmed] https://launchpad.net/bugs/386900 [19:13] mac_v: good question :) ... patches welcome i guess. i think dan is not entirely negative on this nowadays - so there is a chance :) [19:13] ;) [19:15] so nspluginwrapper process seems to be now called /proc/self/exe with .32 rc8 kernel:/ [19:15] for a moment i was shocked to see "exe" in top [19:17] oh i think thats because chromium does odd stuff [19:26] fta: armin76 said chromium will fail after 5h :) ... some file being built with sse2 unconditionally or something [19:26] also just fyi :) [19:30] i have a patch for that [19:31] if it's the same place, it should work [19:33] fta: link? [19:34] it's in bzr [19:34] link? :) [19:35] http://bazaar.launchpad.net/~chromium-team/chromium-browser/chromium-browser.head/annotate/head:/debian/patches/drop_sse2.patch [19:35] it's trivial [19:36] i've been using it since early May [19:37] fta: i don't have the build logs, but i remember it was not a build-time issue [19:37] err [19:37] it was a buildtime issue, thats what i mean [19:37] it tried to compile a file with sse2 on its name [19:37] hm, so it may be different then [19:38] then fix it, i don't have access to arm h/w [19:38] i will check that out now :) [19:39] but lets see ... maybe its really fixed and i win the bet we had in #ubuntu-arm :) [19:39] doubtful [19:39] unfortunately armin76 also said that my 512m are going to be good enough :( [19:39] if you don't hit that you're going to hit a segfault :) [19:39] i dont think having -j2 as its now makes that better :( [19:40] armin76: on what? [19:40] can't remember that one [19:40] i tried a lot of things, and that was last week [19:40] i don't remember anymore :) [19:52] fta: i guess ffox source for >3.5 are good enough to do a full build (with mozclient) ... e.g. we do not strip stuff as we did in 3.0? [19:52] at least from size i would think its identical to full moz central (- binonly) [19:53] yes [19:54] xul still building on lucid armel at least now :) [19:54] but xpcom .... so it can still fail on assembler i would guess [21:07] asac, it's not easy, i can just identify new branches, and releases in those branches. but i don't have enough information to assign those releases to a channel [21:13] asac, for ex, in november: http://paste.ubuntu.com/330578/ [21:15] right and they have the right dependency revisions documented for those? [21:16] so that gives me 7 branches, resp with their tips at 3.0.195.36, 4.0.223.17, 4.0.229.2, 4.0.237.2, 4.0.245.2, 4.0.249.19, 4.0.250.2 [21:16] c still building :) [21:16] i guess alsmost 4h? hmm [21:16] not sure [21:17] whats their latest "official" windows release? [21:17] stable [21:17] i jmean [21:17] mean [21:17] http://googlechromereleases.blogspot.com/ [21:18] hm, that's just the dev channel of chrome and chrome frame [21:18] what did you expect? [21:18] 3 branches, stable, beta and dev [21:18] heh ok. [21:19] it's probably 3.0.195.36, 4.0.223.17 and 4.0.249.19 [21:19] but i can't tell for sure [21:22] * asac spins all-in-one-ffox :) [21:22] like chronologically, they made 4.0.250.1 then 4.0.249.3, then 4.0.250.2, then 4.0.249.{4..19} [21:22] big chunk approach :) === ripps|sleep is now known as ripps [21:44] i wonder if there's a seed file somewhere i can use [21:47] fta: do you know whats the status of chromium gtk theming is? [21:47] fta: from what i understood on the mail threads that existed they did not publish the seed files for releases in the past [21:47] i'm not sure they want to do it [21:48] but either already started to do that or will be at some point [21:48] fta: hmm ... didnt they have an effort at some point? [21:48] to use system theme? [21:49] use gtk theme ;) [21:49] found it [21:49] isnt really that bad [21:49] thought a bit tunable ;) [21:49] mac_v: did you checkout chromium theming? [21:49] i am sure there is potential for beautification ;) [21:51] c is building "webkit/extensions/..../v8 [21:51] asac: when did they add theming to chromium? [21:51] mac_v: its there for a while ... you can click on "Use GTK+ Theme" [21:52] in tools -> something... [21:52] oh... cool.. [21:52] tools -> options -> personal stuff [21:52] * mac_v checks [21:52] crazy name ;) [21:52] for a tab [21:52] maybe in the apt source file installed with chrome.. [21:52] ;) [21:52] "Personal Stuff" ;) [21:52] everything is stuff [21:52] Tools Stuff, Option Stuff ;) [21:52] anyone has chrome installed? [21:53] no [22:07] asac: ah... there it is... will have to tweak chromium out ;) [22:11] just when i thought i was done with theming and stuff for a while... they pull be back it ;p [22:11] in* [22:11] *pull me back in! [22:12] oh great... i think i got to hit the sack [22:13] mac_v: thx!! enjoy [22:13] c still building [22:13] svn20091128r33239/build-tree/src/chrome/browser/automation/automation_provider.cc:2221: [22:22] preview: 4.0.223.16 (Windows Beta Channel), 4.0.249.12 (Mac Dev channel), 4.0.249.11 (Windows & Linux Dev channel) (2009-11-23; 5 days ago) [22:22] Stable release 3.0.195.33 (2009-11-12; 16 days ago) [22:23] hmm, wikipedia seems to know more than i do ;) [22:25] so 195 is stable, 233 beta and 249 dev, pff [22:26] s/243/223/ [22:26] it's probably 3.0.195.36, 4.0.223.17 and 4.0.249.19 [22:27] bingo [22:27] fta: hmm , the default chromium home page is still "9.04" :) [22:27] ? [22:27] where? [22:28] for me its google ;) [22:28] not sure if i set that somewhere [22:28] fta: fresh install directs to > http://start.ubuntu.com/9.04/ [22:28] and new tab is ... newtab [22:28] options shows that ^ [22:28] maybe system integration of some kind? [22:28] chromium has the ubuntu start page??? how come? [22:29] it didn't do anything for that to happen [22:29] oh , or did that gather info from firefox o.0 [22:29] -it+i [22:29] oh, yes, b-m imports [22:29] ah.. nvm crazy me then .... lalala [22:36] if i do a chromium/stable ppa with 3.0.195.*, i wonder if users will use it.. it's old [22:39] i would start with the chromium/testing for now ;) [22:39] i would think that 3. was not really great for linux [22:43] stable & beta are just for windows [22:44] beta recently moved to 4.0.223.16 from 3.0.195.27 [22:50] well. but you are talking about trying to do the same for ubuntu ;) [22:50] so i say: go for testing/beta atm ... once 4.x gets to stable also start doing it for stable [22:51] if its not possible because they dont publish the seeds for those branches then we need to do someting about it ;) [22:53] asac, http://identi.ca/notice/15708021 [22:58] replied ;) [22:58] http://identi.ca/conversation/15708021#notice-15711128 [23:00] E: firefox-3.5: menu-icon-not-in-xpm-format /usr/share/pixmaps/firefox-3.5.png [23:00] E: firefox-3.5: embedded-zlib ./usr/lib/firefox-3.5.6pre/libxul.so [23:00] hehe [23:00] seems lintian doesnt like us including zlib [23:13] c still building ;) [23:13] svn20091128r33239/build-tree/src/chrome/browser/fav_icon_helper.cc [23:21] asac, <50% [23:22] and just of the build part, excluding the tests and the rest of the packaging [23:23] yeah [23:23] is there a flag i can set to not run the tests ;)? [23:28] yes [23:28] WANT_TESTS=0 [23:28] ok willl check that [23:28] next time .. :-P [23:29] you're building on your phone or what? [23:29] * micahg likes the green for the dailies :) [23:30] fta, where can I grab a stable chrome release for sid / squeeze? [23:30] fta, e.g not a daily, but something a bit more stable [23:30] no stable release available [23:30] only dailies [23:31] because upstream does not do any stable releases for chrome/linux yet. read backlog (last few hours) [23:31] that was discussed extensively there ;) [23:31] av`: ^^ [23:31] ah damnit [23:31] but you can install the daily packages in debian sid afaik [23:31] so I need to hope that the dailies I gonna grab will be stable enough [23:31] dailies are good usually [23:32] haven't seen many complain about it here ;) [23:32] I saw fta talking about a chrome-unstable release [23:32] some days ago, but don't know where to grab it :) [23:32] gonna search a bit [23:39] av`: dailies _are_ chromium-unstable basically [23:40] the official chrome is available on net somewhere -> search ;) [23:40] thats named chrome-unstable [23:40] but is basically our dailies (fta?) [23:43] yep, google-chrome-unstable is provided by google (no source) but it's not more stable that our dailies. both are from trunk [23:43] -that+than [23:44] the daily is more popular [23:44] chromium-browser 22602 1.68% 4911 10997 6690 4 [23:44] google-chrome-unstable 18666 1.39% 4535 8225 5887 19 [23:44] yep [23:44] ok, perfect, gonna have a look at the dailies then [23:44] http://launchpad.net/~chromium-daily [23:44] ;) [23:44] ok firefox all-in-one seems to work [23:44] thanks :) [23:44] some minor cleanups and that should be good [23:45] so it means more build cycles?? [23:45] if we keep xulrunner, yes. [23:46] i don't mind, but obviously, some do [23:47] !builderstatus [23:51] !builderstatus [23:51] lol