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