[00:02] <micahg> asac: don't we have to keep xulrunner for the other apps built on it?
[00:04] <asac> but as daily?
[00:04] <fta> sure, but no need to do dailies for those
[00:06] <micahg> asac: well, probably not, the only thing I can think of is if people want to test other apps with the daily
[00:09] <asac> question is: can we add xulrunner to universe without feeling too bad because we already know it will be abandoned security wise soonish?
[00:10] <micahg> asac: well, it should get at least 6 months after release
[00:10] <asac> thats the old world ;)
[00:10] <asac> i am not sure what will happen, but the idea is to even stop doing that
[00:10] <asac> :)
[00:10] <micahg> asac: I thought it was still in debate
[00:10] <asac> not sure if mozilla abandoned the idea
[00:11] <micahg> iirc, there was no resolution either way
[00:11] <micahg> but, I think we have to at least throw something in there for the other apps
[00:11] <micahg> what other choice do we have?
[00:12] <micahg> otherwise, we can provide the -dev packages in ff and let them know they might break?
[00:12] <asac_> reconnect
[00:12] <asac_> 01:11 < micahg> iirc, there was no resolution either way
[00:12] <asac_> 01:12 -!- asac_ [n=asac@e177168032.adsl.alicedsl.de] has joined #ubuntu-mozillateam
[00:13] <micahg> (06:11:31 PM) micahg: but, I think we have to at least throw something in there for the other apps
[00:13] <micahg> (06:11:46 PM) micahg: what other choice do we have?
[00:13] <micahg> (06:12:20 PM) micahg: otherwise, we can provide the -dev packages in ff and let them know they might break?
[00:13] <asac_> -> its just a huge axe hanging above us, so imo we need to plan as if they will do it ;) (for now)
[00:13] <asac_> other apps get removed ;)
[00:13] <micahg> ok, then, if we can get clearance for major changes in the depending apps, we can try to bump them to be compliant during the release cycle
[00:13] <asac_> or migrated to webkit
[00:13] <asac_> at best
[00:15] <asac_> well. the major/minor session basically had the input from release team etc. that we should try to get rid of it ...
[00:15] <asac_> one idea would be to provide a trimmed down firefox-3.5-plugin-dev package
[00:15] <asac_> so we can still build plugins (which tend to be not as bad to maintain)
[00:16] <asac_> or we review apps manually and decide on case by case base, what we want to keep supporting
[00:16] <asac_> for those we need committmenet to provide backports in time for _all_ supported archs
[00:16] <micahg> does prism come with it's own xul code?
[00:16] <asac_> no
[00:17] <asac_> well. it could be made to have that ... but ;)
[00:17] <asac_> thats getting ugly
[00:17] <micahg> I'm certainlly willing to help with the backporting
[00:18] <micahg> in general, we'll be doing it for the devel release anyways
[00:18] <asac_> we have a few areas that are hard to get right ...
[00:18] <asac_> a) mozjs ... we have couchdb depending on that
[00:19] <asac_> b) we xul apps that would become more or less void
[00:19] <asac_>  -> if we have xulapps without binary components, we should remove them imo -> they can be provided upstream directly somewhat i guess
[00:19] <fta> asac_, i don't get the migrated to webkit part.. why would moving the burden of security maintenance to webkit change anything?
[00:20] <asac_> first: the world moves to webkit. thats a fact ;)
[00:20] <asac_> so we will have to maintain webkit ;)
[00:21] <micahg> asac_: so, is the moziila team expanding to become the browser team?
[00:21] <asac_> second: embedders like webkit more
[00:22] <asac_> i would think that making a browser team in the long run becomes more and more viable ;)
[00:23] <asac_> thunderbird will stay around for a while longer too i guess
[00:23] <fta> and if users like chromium more, would you move firefox to universe?
[00:24] <asac_> stuff gets moved to universe when its not on CD, nor on dvd usually
[00:24] <asac_> on any officially support image is more accurate i guess
[00:24] <micahg> wouldn't that depend on the archive restructuring?
[00:25] <asac_> yes. i have no clue about what exactly will happen then ;)
[00:41] <asac> at some point we should get rid of firefox-3.1 transitional packages i guess
[00:41] <asac> those were only in ppa, right?
[00:42] <asac> should be safe to drop then in lucid i presume
[00:43] <micahg> they certainly weren't in a production release
[00:44] <asac> my innovate gnome component shuffeling didnt work out as good as expected :/
[00:44] <asac> (speaking to myself) ;)
[01:17] <asac> hmm ... xdg-open is kind of borked
[01:18] <micahg> yeah
[01:18] <micahg> I meant to look into that
[01:23] <fta> asac, http://paste.ubuntu.com/330715/
[01:24] <fta> the thing is, i don't know when branches are abandonned
[01:32] <asac> fta: hmm. wasnt gears integrated in chromium?
[01:32] <fta> no
[01:33] <fta> they won't do it
[01:33] <asac> instead?
[01:33] <fta> their prefer to wait for the html5 offline feature
[01:33] <fta> they
[01:33] <asac> is there any mstone targetted for that?
[01:34] <asac> http://stackoverflow.com/questions/1194784/which-browsers-support-html5-offline-storage
[01:35] <asac> Google Chrome: Gears Database API, which is built into Chrome and thus doesn’t require a separate install. Surprisingly, Chrome doesn’t yet natively support any form of HTML5 Storage.
[01:35] <asac> hmm
[01:35] <asac> so only win
[01:37] <asac> http://code.google.com/p/chromium/issues/detail?id=17443
[01:41] <fta> i know
[01:42] <asac> svn20091128r33239/build-tree/src/third_party/protobuf2/src/src/google/protobuf/dynamic_message.cc:66:
[02:30] <fta> http://paste.ubuntu.com/330748/plain/ with trunk
[02:31] <asac> fta: we are well past 2200 ;)
[02:31] <fta> grrr
[02:31] <asac> hehe
[02:31] <asac> ok its saturday
[02:31] <asac> so its ok i guess ;)
[02:31] <asac> what a pity ... gvfs backend for gdocs does not "just work (tm)"
[02:32] <asac> /home/asac/Development/upstream/gvfs/gvfs_gdata/daemon/gvfsgdocsfile.c:665: undefined reference to `gdata_documents_presentation_get_download_uri'
[02:32] <asac> guess we need a better libgdata ;)
[02:34]  * asac spins 0.5.1 from debian sid
[02:34] <asac> rather than 0.4 we have in karmic
[02:35] <asac> so ... i managed to get chromium mailto: handler to work
[02:35] <asac> for yahoo and gmail
[02:35] <asac> except that xdg-open is broken ... but thats probalby xdg bug (escaping?)
[02:35] <asac> but opening mailto: in firefox now opens yahoo/g mail in chromium
[02:37] <asac> now we just need to mount gdocs as HOME/Documents ;) ... and then somehow ensure that we wrap the proper content types by something that opens browser with the right url ;)
[02:39] <asac> and resolve some "minor" online/offline handling issues before we can provide a good user experience ;)
[02:39] <asac> feels hard :/
[02:41]  * asac wonders if gvfs is in theory good for offline
[07:11] <AnAnt_> Hello, why isn't libmozjs1 built for xulrunner-1.9 ?
[07:42] <micahg> AnAnt: what version of ubuntu?
[07:42] <AnAnt> micahg: karmic & lucid
[07:42] <micahg> AnAnt: xul-1.9 doesn't exist in either
[07:42] <AnAnt> errm, oops
[07:43] <AnAnt> 1.9.1
[07:44] <AnAnt> sorry I dunno it is named xulrunner-1.9.1
[07:44] <AnAnt> so, the same issue holds for that version
[07:44] <micahg> I thought it was part of it
[07:44] <AnAnt> why isn't libmozjs1 built for it ?
[07:45] <micahg> AnAnt: I think it's part of xulrunner-1.9.1
[07:46] <AnAnt> micahg: libmozjs-dev is part of xulrunner-dev ?
[07:46] <micahg> yes
[07:46] <micahg> xulrunner-1.9.1-dev
[07:46] <AnAnt> in 'xulrunner' there is libmozjs-dev & libxul-dev
[07:46] <micahg> xulrunner is old
[07:48] <AnAnt> I see, so that's a big deviation from Debian
[07:48] <micahg> AnAnt: we don't import xul from debian
[07:52] <AnAnt> micahg: do you know since which version (1.9 or 1.9.1) did xulrunner start using heartbeat ?
[07:52] <micahg> no, sorry
[07:52] <micahg> idk what heartbeat is
[07:55] <AnAnt> ok
[09:49] <ripps> Damn, chromium is segfaulting on me. Now I have to install the huge debug package and get a backtrace
[09:52] <ripps> okay, nevermind. Everything is segfaulting, I think I just got a kernel bug
[09:59] <micahg> asac: you wouldn't happen to be on would you?
[10:40] <AnAnt> Hello, back to the libmozjs* packages question, I hope that separate packages for libmozjs* are built from xulrunner-1.9.1 (as have been done for old xulrunner)
[10:40] <micahg> AnAnt: they are not and will not be
[10:40] <AnAnt> some packages use libmozjs, and they can't find mozjs library in xulrunner-1.9.1-dev long path
[10:41] <AnAnt> micahg: any reason for this ?
[10:41] <micahg> hmmm
[10:41] <micahg> idk
[10:41] <micahg> simplicity?
[10:41] <micahg> let me see if I can find a bug
[10:42] <AnAnt> micahg: when you said "will not be", I thought you knew a reason for this
[10:42] <micahg> ah, sorry
[10:42] <micahg> that's my tiredness
[10:42] <micahg> 4:45 in the morning :)
[10:42] <AnAnt> I see
[10:43] <AnAnt> you need to sleep
[10:43] <micahg> I meant to say I don't think there are plans to revive it, but I'm trying to see if I can find the reason why it's no longer
[10:43] <AnAnt> ok
[10:44] <AnAnt> so, asac is asleep ?
[10:44] <micahg> well, probably not at noon, but it's sunday
[10:45] <AnAnt> asac is in europe ?
[10:45] <micahg> UTC+1
[10:45] <AnAnt> ok
[10:51] <micahg> I don't think it was ever in 1.9
[10:51] <micahg> so that's since hardy
[10:53] <micahg> AnAnt: asac usually pops in sometime Sunday...I'll try to ask if I remember
[10:57] <micahg> AnAnt: apparently you're not the only one with this issue
[11:11] <AnAnt> ok, thanks
[13:49] <asac> fta: do you see any error here: http://people.canonical.com/~asac/tmp/chromium-browser_4.0.260.0~svn20091128r33239-0ubuntu1~ucd1_armel.build.bak.bz2
[13:49] <asac> it failed to build
[13:49] <asac> but i dont see anything that is an error
[14:37] <asac> ok we worked around it by tweaking as
[18:04] <AnAnt> asac: ping
[18:06] <asac> AnAnt: ?
[18:06] <AnAnt> asac: can separate packages for libmozjs* are built from xulrunner-1.9.1 (as have been done for old xulrunner)
[18:06] <AnAnt> s/are/be
[18:06] <asac> no
[18:08] <AnAnt> why is that ?
[18:08] <asac> there is a abug open about providing a stable ABI/APi
[18:08] <asac> they say they dont want to do that
[18:08] <asac> so shipping libmozjs would be wrong
[18:08] <asac> its not ment for consumption outside of xulrunner/firefox upstream
[18:08] <asac> let me check something
[18:09] <AnAnt> there are packages using libmozjs
[18:10] <asac> https://bugzilla.mozilla.org/show_bug.cgi?id=506890
[18:10] <asac> AnAnt: right. those in theory use something that isnt allowed
[18:10] <asac> its not my decision
[18:10] <asac> read the bug
[18:10] <asac> ;)
[18:11] <asac> anyway. xulrunner will be either removed completely from archive (unlikely) or go to universe
[18:11] <asac> when that happens we can provide a mozjs there
[18:11] <asac> which doesnt really help couchdb ;)
[18:11] <asac> bad situation
[18:12] <asac> thy dont even want to keep abi/api promise within a stable branch ;)
[18:12] <asac> that means: doomed
[18:14] <asac> so all our hope is on libseed ;)
[18:14] <asac> rather webkit ;)
[18:20] <AnAnt> libseed ? webkit ? what's those for ?
[18:22] <asac> other js lib
[18:38] <AnAnt__> so, is xulrunner going to be removed in lucid ?
[18:39] <AnAnt__> removed or go to universe that is
[18:42] <fta> asac, jcastro: http://www.sofaraway.org/ubuntu/tmp/chromium-forest.html  131 releases in 60 days, incl 59 in branches (the rest in trunk)
[18:50] <asac> yes
[18:50] <asac> AnAnt: yes
[18:50] <AnAnt> ok, thanks
[19:33] <fta> asac, i think i will add a get-branch-source target, using something like RELEASE_BRANCH=249, and use that for another PPA
[19:34] <fta> it's probably best to work in a dedicated branch tough :(
[19:34] <fta> +h
[20:11] <micahg> asac: around?
[20:30] <asac> dh_link -p chromium-browser-dbg
[20:30] <asac> dh_md5sums -pchromium-browser-dbg
[20:30] <asac> dh_builddeb -pchromium-browser-dbg -- -Z lzma
[20:30] <asac> dpkg-deb: building package `chromium-browser-dbg' in `../chromium-browser-dbg_4.0.260.0~svn20091128r33239-0ubuntu1~ucd1_armel.deb'.
[20:30] <asac>  \o/
[20:30] <asac> fta: ^^
[20:30] <asac> ;)
[20:31] <asac> micahg: for a moment. yes.
[20:31] <asac> ;)
[20:31] <micahg> ah, ok
[20:31] <micahg> if I'm adding different .desktop translations, are they separate commits in bzr and are they separate lines in the changelog?
[20:32] <asac> micahg: if you add a batch at once you can have them in onecommit/line
[20:32] <asac> but i wouldnt merge them when i land a second translation a few days later
[20:32] <micahg> Lang1, Lang2, Lang3 (LP: 1, LP: 2, LP: 3)?
[20:32] <asac> if they have more than one bug i would still go for the multi commit/changelog approach
[20:32] <micahg> ok
[20:33] <micahg> so one per commit one per line
[20:33] <micahg> do I list the file after each line?
[20:33] <asac> or say something like: add translation for XX (LP: # ...), YY (LP: #...)
[20:33] <asac> but i dont think we need to save lines in changelog ;)
[20:33] <asac> micahg: if you dont merge them, then yes
[20:33] <micahg> ok
[20:33] <asac> i undertand a changelog line as a entry + file modification
[20:33] <micahg> got it, I found 2 other translations over the weekend, so I'm adding them to 3.5.head
[20:34] <asac> hmm. ok
[20:34] <micahg> the other thing is, do you remember why we don't break out libmozjs anymore?
[20:34] <asac> ;)
[20:35]  * asac has to remember to update branch before committing the all-in-one-wonder changes ;)
[20:35] <asac> micahg: we never did it
[20:35] <micahg> asac: why not start that with 3.6 unless we are backporting all in one to hardy
[20:35] <asac> read: https://bugzilla.mozilla.org/show_bug.cgi?id=506890
[20:36] <asac> that explains the reason why what debian does is insane - support wise ;)
[20:36] <micahg> well, it used to be a separate package in xul 1.8
[20:36] <asac> that was debian heritage
[20:36] <micahg> ah
[20:36] <asac> maybe if we go away from xulrunner we can sync debian xulrunner ;)
[20:36] <asac> and then get libmozjs in universe
[20:36] <asac> but even then its a bad feeling because we already know we wont be able to support
[20:37] <asac> (same as for xulrunner we discussed yesterday)
[20:37] <asac> only a subset of applications we can pick and then prepare for porting ;)
[20:37] <asac> thats the same for mozjs
[20:37] <asac> mozjs gets > 1/3 of security fixes
[20:38] <asac> and those are usually of tricky kind (and nont many not working for mozilla - who wont help us according to bug) would be able to maintain that
[20:38] <micahg> wow
[20:39] <asac> if you read bug: they didnt even want to commit to not break API on a stable branch :/
[20:39] <micahg> yeah, I saw that
[20:39] <micahg> that's what the wow was for :)
[20:39] <asac> so asking for stable minimal API across branches is definitly not right
[20:39] <asac> for them ;)
[20:39] <asac> they basically say: dont use mozjs anywhere but in firefox/tbird
[20:40] <micahg> so it almost seems like there's no point in shipping it at all
[20:40] <asac> right ;)
[20:40] <asac> thats the whole point ... and if you ship it you need to hire core js devs from mozilla ;)
[20:41] <micahg> ok, we have a few bugs on this, now I know, should I create a master bug or keep telling people to build against xulrunner-1.9.1-dev
[20:41] <micahg> or both?
[20:41] <asac> we have a master bug afaik
[20:41] <asac> micahg: tell people to not use mozjs ;)
[20:41] <asac> the building against xulrunner-1.9.1-dev has the same messy implications
[20:41] <asac> just that we make it harder for them to do (and increase likelyhood we will bump into them)
[20:41] <micahg> asac: suggest they port to webkit?
[20:41] <asac> maybe ;)
[20:42] <asac> for now its probably the only way we can send them
[20:42] <asac> v8 has same approach as mozjs
[20:42] <asac> i the most accurate answer is: do not use javascript ;)
[20:42] <asac> sad but true
[20:45] <micahg> I don't see a master bug
[20:45]  * asac looks
[20:46] <asac> great. search for "mozjs" on xulrunner-1.9.1 package -> no result
[20:46] <asac> but: bug 486079 exists ;
[20:46] <asac> thats launchpad
[20:46] <micahg> yep
[20:47] <asac> i thought there was a bug open ;)
[20:47] <asac> which bugs do you look at?
[20:47] <asac> maybe i didnt name it MASTER, but consider it a master :)
[20:47] <micahg> generally just ff, but someone came in here last night asking
[20:47] <asac> bug 286906
[20:47] <asac> micahg: yes. that was anant
[20:47] <micahg> yep
[20:47] <asac> already told him that mozjs is bad ;)
[20:48] <micahg> should I make that bug the master?
[20:48] <asac> one sec
[20:48] <asac> maybe i wont fix it
[20:49] <asac> ok cannot find it
[20:49] <asac> go ahead then
[20:49] <asac> move to 1.9.1 i guess
[20:50] <micahg> should I link to the upstream bug also
[20:51] <asac> why not ;)
[20:52] <asac> make it a wishlist bug with title: "provide and support a top-level library package for libmozjs"
[20:52] <asac> make it a wishlist bug with title: "provide and support a top-level library package for libmozjs (Was: Unable to use libmozjs.so in an application, because of library path problem.)"
[20:52] <asac> or something similar
[20:56] <micahg> ok
[22:12] <micahg> ugh, they hijacked the builders again
[22:12] <asac> they == us? or QA folks? ;)
[22:12] <micahg> QA folks it seems :)
[22:12] <asac> there are 5/8/5
[22:12] <micahg> I"m going to pbuilder songbird to see if it works
[22:12] <asac> thtas better than 2/2/3 ;)
[22:13] <micahg> yeah
[22:14] <micahg> asac: it looks like I'm going to have to use songbird's sqlite for the moment
[22:15] <asac> thats in line with everything we do ;)
[22:15] <asac> are you on lucid yet?
[22:15] <micahg> nope
[22:15] <micahg> should I be?
[22:15] <asac> no
[22:15] <asac> just was curious
[22:15] <micahg> I wasn't planning on jumping until beta 1
[22:15] <asac> if sqlite is at least new enough there in theory
[22:15] <fta> asac, could you add "killall -q -v -9 $(basename $TEST)" at the end of debian/run-test.sh and use it on base_unittests?
[22:16] <asac> fta: how do i use it on base_unittests?
[22:16] <fta> debian/run-test.sh path/to/the/bins/base_unittests
[22:17] <asac> hmm... i dont see the base_unitttests
[22:17] <asac> did it clean them at end of build?
[22:17] <asac> oh sorry
[22:17] <asac> wrong host ;)
[22:18] <fta> well, run it from sconsbuild/Release
[22:18] <asac> ./debian/run-test.sh build-tree/src/sconsbuild/Release/base_unittests
[22:18] <asac> Usage: run-test.sh [-x] [-t sec] test_file log_dir [filter]
[22:18] <asac> -x               Run test_file under xvfb -t sec           Timeout in seconds after which we kill the test
[22:18] <asac> hmm
[22:19] <asac> -t20 ?
[22:19] <asac> o log dir was missing
[22:19] <asac> its running
[22:20] <asac> ok had to create the right log subdir too
[22:21] <asac> now running ;)
[22:21] <asac> how long is that supposed to run ;)?
[22:21] <asac> 27873 asac      20   0 76256 2212  364 R 99.1  0.5   0:15.12 base_unittests
[22:21] <asac> running
[22:22] <fta> at most 10 min
[22:22] <asac> on your system ;)?
[22:22] <asac> hehe
[22:22] <asac> ok let me take a quick break
[22:22] <fta> no, it's the timeout
[22:22] <asac> then finish a few specs
[22:22] <asac> hmm ok
[22:22] <asac> already more than a minute CPU time ;)
[22:23] <fta> maybe 10min is not enough to run normally on arm
[22:23] <fta> the log file shoud grow
[22:23] <fta> +l
[22:25] <asac> http://paste.ubuntu.com/331343/
[22:25] <asac> thats what is at end atm
[22:25] <asac> so its either stuck ... at end ... or woking on getting OOM
[22:27] <asac> fta: its already defunct
[22:27] <asac> but looping
[22:27] <asac> http://paste.ubuntu.com/331345/
[22:41] <fta> hm, but it run-test still running?
[22:41] <asac> it runs forever
[22:42] <asac> i restarted in the meantime
[22:42] <asac> so ask in 6 minutes or so ;)
[22:42] <asac> (karmic)asac@jocote:~$ ls -l /tmp/log/build-tree/src/sconsbuild/Release/base_unittests.txt
[22:42] <asac> -rw-r--r-- 1 asac warthogs 29575 Nov 29 22:37 /tmp/log/build-tree/src/sconsbuild/Release/base_unittests.txt
[22:42] <asac> (karmic)asac@jocote:~$ date
[22:42] <asac> so latest at 2247
[22:42] <asac> Sun Nov 29 22:42:16 UTC 2009
[22:42] <asac> it should stop, right?
[22:42] <fta> strange, next time, run it with sh -x
[22:42] <asac> i ran a killall base_unitttests after killing the process
[22:42] <asac> that left a gdb process still running
[22:43] <asac> k
[22:44] <fta> well, if the 1st instance died, i re-run it in gdb, so you have to be patient before killing everything
[22:44] <asac> how patient?
[22:44] <asac> 20muntes?
[22:45] <asac> is that a new log i can check for progress? (with gdb)
[22:45] <asac> [----------] 14 tests from OutOfMemoryTest
[22:45] <asac> [ RUN      ] OutOfMemoryTest.New
[22:45] <asac> [WARNING] /home/asac/chromium-browser-4.0.260.0~svn20091128r33239/build-tree/src/testing/gtest/src/gtest-death-test.cc:741:: Death tests use fork(), which is unsafe particularly in a threaded context. For this test, Google Test couldn't detect the number of threads.
[22:45] <asac> thats really the end from what i can see
[22:45] <asac> maybe that warning is FATAL?
[22:45] <asac> ok 10 minutes almost past ...
[22:45]  * asac waiting
[22:47] <asac> ok 10 minutes done -> gdb appeared
[22:47] <asac> thats correct, right?
[22:47] <fta> during your build, the script properly exited, but with some processes left behind, so here, the script should terminate itself normally too
[22:47] <asac> [WARNING] /home/asac/chromium-browser-4.0.260.0~svn20091128r33239/build-tree/src/testing/gtest/src/gtest-death-test.cc:741:: Death tests use fork(), which is unsafe particularly in a threaded context. For this test, Google Test couldn't detect the number of threads.
[22:47] <asac> Timeout: aborting command ``./build-tree/src/sconsbuild/Release/base_unittests'' with signal 9
[22:47] <asac> Killed
[22:47] <asac> so the killing worked a bit
[22:47] <asac> the defunct proc is gone at least
[22:48] <asac> now i got ## list of FAILED tests:
[22:48] <asac> [  FAILED  ] ConditionVariableTest.FLAKY_MultiThreadConsumerTest (792 ms)
[22:48] <fta> good
[22:48] <fta> and no zombie, gdb, whatever?
[22:49] <fta> the killall i asked you to add has a -v, to show if it has catched something
[22:50] <asac> http://paste.ubuntu.com/331357/
[22:50] <asac> fta: gdb is now active
[22:51] <asac> and apparently under gdb we have a new defunct too
[22:51] <asac> kind of expected
[22:51] <asac> so after another 10 minutes this will finish?
[22:51] <fta> 10min max for a run, so 10min minus the running time
[22:52] <asac> the process with zombie is already dead and gdb keeps on going ...
[22:52] <asac> anyway 4 more minutes at max with gdb i hope
[22:52] <asac> lets see
[22:53] <fta> xul-ext-adblock-plus ? wtf
[22:53] <fta> oh, debian
[22:53] <fta> why am i getting all those debian bug mails?
[22:53] <asac> subscribed to pkg-moz-extmaintainers or something list?
[22:54] <asac> maybe they have that list as maintianer and then mails go there
[22:54] <asac> or its mozillateam malining list ;)
[22:54] <asac> we still get the icedove mail there
[22:54] <asac> (next upload will fix that)
[22:54] <fta> it's the m-t mailing list
[22:55] <fta> from mozilla-devscripts
[23:07] <asac> fta: test ended
[23:07] <asac> [  FAILED  ] ConditionVariableTest.FLAKY_MultiThreadConsumerTest (792 ms)
[23:07] <asac> ---- crash logs ----
[23:07] <asac> Killed base_unittests(29141) with signal 9
[23:07] <asac> Killed base_unittests(29433) with signal 9
[23:07] <asac> no process left
[23:07] <asac> great
[23:07] <asac> hmm
[23:07] <asac> asac     17020     1  0 18:37 ?        00:00:01 Xvfb :99 -screen 0 640x480x8 -extension Composite -nolisten tcp
[23:07] <asac> asac     19033     1  0 19:19 ?        00:00:01 Xvfb :100 -screen 0 640x480x8 -extension Composite -nolisten tcp
[23:07] <asac> asac     22097     1  0 19:51 ?        00:00:01 Xvfb :104 -screen 0 640x480x8 -extension Composite -nolisten tcp
[23:08] <asac> asac     22348     1  0 20:01 ?        00:00:01 Xvfb :106 -screen 0 640x480x8 -extension Composite -nolisten tcp
[23:08] <asac> asac     22368     1  0 20:01 ?        00:00:00 Xvfb :107 -screen 0 640x480x8 -extension Composite -nolisten tcp
[23:08] <asac> those are still running
[23:08] <asac> i guess those were started during tests, but never killed
[23:08] <asac> anything i should do before killing those?
[23:08] <asac> fta: ?
[23:16] <asac> 3
[23:16] <asac> 2
[23:16] <asac> 1
[23:17] <asac> killed ;)
[23:33] <fta> based on the time, yeah, from your previous attempts
[23:33] <micahg> fta: is trunk fixed for you with the funny characters?
[23:34] <fta> asac, ^^, it seems i should kill that too, but the tricky part is to kill only ours
[23:34] <fta> micahg, no idea, i only see that at work, and i'm at home
[23:34] <micahg> ah, ok
[23:38] <micahg> fta: I'm having songbird build it's own sqlite, hope that and a patch refresh will fix it
[23:39] <rcmaehl_linux> I need help
[23:39] <rcmaehl_linux> every time i load firefox i get this
[23:39] <rcmaehl_linux> Could not initialize the application's security component. The most likely cause is problems with files in your application's profile directory. Please check that this directory has no read/write restrictions and your hard disk is not full or close to full. It is recommended that you exit the application and fix the problem. If you continue to use this session, you might see incorrect application behaviour when accessing security
[23:39] <rcmaehl_linux> features.
[23:40] <micahg> rcmaehl_linux: is your home partition full?
[23:45] <rcmaehl_linux> no
[23:45] <rcmaehl_linux> and the guys in #firefox gave me the answer
[23:45] <micahg> ok, bye rcmaehl_linux