[02:39] <micahg> chrisccoulson: wow, you keep crazy hours like me :)
[02:39] <chrisccoulson> micahg - yeah, i normally sleep quite late ;)
[02:39] <chrisccoulson> but i'm going to go to bed shortly
[02:40] <micahg> chrisccoulson: BTW, you can do a release commit as well if you like
[02:40] <chrisccoulson> yeah, can do. i'll do that now
[02:49] <chrisccoulson> micahg, that's done now. i put the tarball here too: http://people.canonical.com/~chrisccoulson/
[02:50] <micahg> chrisccoulson: great, thanks, I'll see if I can get someone to upload once I merge it in
[02:50] <chrisccoulson> thanks
[02:50] <micahg> chrisccoulson: I'm working on a merge for conkeror from debian right now
[02:50] <chrisccoulson> anyway, i must get some sleep now :)
[02:50] <micahg> chrisccoulson: night, thanks
[02:50] <chrisccoulson> good night
[02:56] <ddecator> my head hurts...
[02:59] <ddecator> micahg: i have no idea what's causing the problem...
[03:08] <ddecator> the rules file looks like it points to /deps, but then debuild looks in /deps/checkout
[03:08] <micahg> ddecator: there's a foreach loop there
[03:09] <ddecator> micahg: didn't know that was a loop
[03:11] <ddecator> still not seeing where it would look in checkout for the linux-x86_64 folder, but my understanding of code is pretty basic
[03:14] <micahg> ddecator: each of these dirs: checkout build linux-$(MACHINE) under here: $(SRC_DIR)/deps have mkdir -p run against them
[03:15] <ddecator> micahg: what does the -p argument do?
[03:15] <micahg> ddecator: create parent dirs
[03:15] <micahg> then later, it does into deps and decompresses a tarball
[03:16] <micahg> oops
[03:16] <micahg> I have that backwards
[03:16] <micahg> it creates a tarball
[03:19] <ddecator> the 'tar cf - linux-$(MACHINE)' part you mean?
[03:20] <micahg> yeah
[03:20] <micahg> it's failing on the line in between
[03:21] <ddecator> ok...
[03:22] <ddecator> well i say that it creates Makefile.songbird successfully, or at least there is a file in that folder by that name, but i'm not sure what the rest of the line is doing
[03:23] <ddecator> s/say/see
[03:23] <micahg> ddecator: no, make is a program that compiles songbird
[03:25] <micahg> ddecator: or rather executes instructions that then run the compiler to be more precise
[03:25] <ddecator> micahg: ah, ok, so it's running that file as part of the building process?
[03:25] <micahg> yep
[03:27] <ddecator> micahg: ok, i'm not seeing anything in that make file that would cause that crash
[03:29] <ddecator> oh wait...
[03:29] <micahg> ddecator: check the Makefile.songbird and see if you can find the commands there
[03:30] <ddecator> the rules file point out a SB_VENDOR_BUILD_ROOT but the make file looks for SB_VENDOR_BUILD_DIR
[03:31] <micahg> the makefile doesn't look for this at all: SB_VENDOR_BUILD_ROOT?
[03:31] <ddecator> micahg: nope: cd $(SB_VENDOR_BUILD_DIR) && $(CMAKE) $(CMAKE_ARGS) \
[03:32] <micahg> well, you can modify the rules file then, but that's not where it's failing now
[03:33] <ddecator> well...the make file is looking for SB_RUN_CONFIGURE := 0 and the rules file has SB_VENDOR_GENERATE_SYMBOLS=0 but idk if those are related...
[03:34] <micahg> ddecator: it's failing on a find isn't it?
[03:35] <ddecator> micahg: the only "find" in the makefile is this: $(FIND) $(SB_CONFIGURE_PREFIX) -name '*_c.*' -exec rm -v {} \;
[03:36] <micahg> nope
[03:40] <ddecator> it fails after the end of the makefile...
[03:45] <ddecator> no...i'm extremely confused right now
[06:00] <ddecator> well i definitely have a new appreciation for packagers and debuggers...
[11:31] <nikolam> hi. Do you think Seamonkey 2.0 coould be imported in repositories now? There is working 2.0.3 for all supported Ubuntu releases, available on Joe Lesko PPA : https://launchpad.net/~joe-nationnet/+archive/ppa-seamonkey2
[11:32] <nikolam> Bug: https://bugs.launchpad.net/ubuntu/+source/seamonkey/+bug/461864
[11:32] <nikolam> How to make it happen in repositories?
[11:32] <nikolam> What might be the procedure for that?
[13:51] <asac> chrisccoulson: for thunderbird you have to put the upstream tar.bz2 in the checked out bzr tree ... and run the create-orig-source thing or whatever that rule is called
[13:55] <asac> chrisccoulson: anything you need while i am still online in the airport lounge?
[13:55] <chrisccoulson> hi asac
[13:55] <asac> hi
[13:55] <chrisccoulson> i think i'm ok for the time being. micahg merged the security updates in to bzr last night
[13:56] <asac> chrisccoulson: did you figure how to create the +nobinonly tarball from the upstream tarball?
[13:56] <asac> chrisccoulson: hmm. ok i think i should generate the tarball and sponsor it to the security ppa
[13:56] <asac> probably makes most sense
[13:56] <asac> if you want to put the orig.tar.gz somewhere thats even better (or in your own ppa)
[13:57] <asac> e.g. you could put this in your ppa and i can source copy it to the security ppa
[13:57] <chrisccoulson> asac - i put the tarball at http://people.canonical.com/~chrisccoulson/
[13:57] <asac> chrisccoulson: you could really upload it to your ppa ,)
[13:57] <asac> i would check an source copy it
[13:58] <chrisccoulson> yeah, i will do that
[13:58] <asac> then we do one more security round for ffox xul and then i add you to the security ppa team
[13:58] <asac> cool
[13:58] <chrisccoulson> it will take a little while though
[13:58] <chrisccoulson> thanks :)
[13:58] <asac> chrisccoulson: well. i will be on the plane ;)
[13:58] <asac> will not be back online until like 2100 UTC
[13:58] <asac> so take your time ;)
[13:58] <chrisccoulson> heh, i will probably have faster upload bandwidth than you while you are flying ;)
[13:59] <asac> right.
[13:59] <chrisccoulson> ok, i'll do that this afternoon anyway
[13:59] <asac> so when we did that we should someone resurrect the idea to announce such uploads on some blogs/mailing list, so we pick up more security ppa users again ;)
[13:59] <asac> maybe think about doing that ;)
[13:59] <chrisccoulson> yeah, that sounds like a good idea
[13:59] <asac> the standard notion is:
[13:59] <asac> security ppa is usually safe because only stable updates go there
[14:00] <asac> but its really important and users can make a difference. if they discover a bug they help millions of users ;)
[14:00] <asac> chrisccoulson: i think i should have mails i sent usually
[14:01] <asac> will get such a mail when home ;)(
[14:01] <chrisccoulson> thanks
[14:01] <chrisccoulson> which list did you normally send the mails too?
[14:01] <chrisccoulson> (i could check the archive)
[14:01] <asac> i think ubuntu-mozillateam ;)
[14:01] <chrisccoulson> ah, i'll have a look there
[14:01] <chrisccoulson> thansk
[14:01] <asac> but i probably stopped a year ago or so (basically when i stopped doing backports)
[14:01] <chrisccoulson> s/thansk/thanks
[14:01] <asac> e.g. when dapper went EOL
[14:02] <asac> just was too busy ;) and we had quite a few users at that time
[14:02] <asac> but everytime you dist-upgrade you automatically disable it again
[14:02] <asac> so we should constantly do that ;)
[15:06] <micahg> hi chrisccoulson
[15:06] <chrisccoulson> hi micahg
[15:07] <micahg> chrisccoulson: after I went to sleep I realized that I was only subscribe to 2 of the TB stable branches
[15:08] <micahg> I'm merging the other 2 now
[15:08] <chrisccoulson> ah, i did wonder why you only merged 2 ;)
[15:08] <chrisccoulson> i'm just uploading the packages to my PPA now, and asac said he would copy them to the security PPA later
[15:09] <micahg> chrisccoulson: k, I guess he can source copy
[15:09] <micahg> chrisccoulson: can you do the same thing for seamonkey 1.1.19?
[15:10] <chrisccoulson> yeah, can do
[15:10] <micahg> I'll push a seamonkey stable branch for karmic and use lp:seamonkey/1.1 for lulcid
[15:10] <micahg> *lucid
[15:26] <micahg> chrisccoulson: thunderbird all merged
[15:26] <chrisccoulson> excellent, thanks
[15:41] <micahg> chrisccoulson: I have to figure out if the same USN applies to seamonkey or a different one
[16:01] <fta> hi
[16:01] <fta> micahg, m-d & tb2, i don't think so.
[16:01] <micahg> fta: k, so, same for seamonkey 1.1, right?
[16:02] <fta> micahg, yep, but it's easy (if not trivial) to add the feature
[16:02] <micahg> fta: it's the last release for SM1.1 and probably TB2 as well, so I don't think it's worth it
[16:03] <fta> k
[16:05] <fta> !info chromium-browser lucid
[16:06] <fta> damn, why isn't 5.0.307.11 there
[16:09] <fta> pushed
[16:10] <fta> strange.. i prepared it weeks ago but never pushed it
[16:10] <fta> or it was rejected for some reason
[16:10] <fta> or lost
[16:13] <fta> asac, jdstrand: will _full_ updates of chromium be allowed even after release or what?
[16:14] <micahg> fta: they're both not here
[16:28] <BUGabundo_remote> fta: aint that against FF and release guidelines?
[16:29] <fta> BUGabundo_remote, ??
[16:29] <BUGabundo_remote> (2010-03-17 16:13:03) fta: asac, jdstrand: will _full_ updates of chromium be allowed even after release or what?
[16:29] <fta> BUGabundo_remote, my question is how to maintain ch after lucid is out
[16:30] <BUGabundo_remote> ah
[16:30] <fta> the only thing i can do is continue to push full updates in sync with the beta channel, then stable channel
[16:30] <fta> but noway i have the time/resources to identify and backport fixes
[16:31] <fta> if the later is required, then i have to give up
[16:31] <fta> +t
[16:40] <BUGabundo_remote> I understand fta
[16:40] <BUGabundo_remote> and get upstream to help on that task?
[16:41] <fta> they are busy too, they will just point users to their builds
[16:43] <BUGabundo_remote> but we are a distro
[16:43] <BUGabundo_remote> not users
[17:09] <ejat> fta .. just wondering .. when will it support pdf ?
[17:11] <fta> pdf plugin?
[17:11] <fta> when i click on a pdf, it works like ff, i.e. i get my preferred pdf viewer
[17:12] <jcastro> fta: it would make sense that we should do for chromium what we do for FF and follow the stable release channel - upstream isn't going to support old-stable stuff
[17:13] <ejat> fta: is it can be view like ff .. inside the browser
[17:13] <fta> jcastro, yep, that's the plan, but no stable for linux yet, hence the beta channel
[17:13] <jcastro> right, I mean eventually
[17:14] <fta> ejat, no idea, there's probably an upstream bug
[17:14] <jcastro> but if it goes stable after lucid is out we should probably update what's in the archive and just follow -stable at that point.
[17:14] <ejat> fta : http://code.google.com/p/chromium/issues/detail?id=11551 :(
[17:20] <ejat>  .. /usr/lib/xulrunner-1.9.0.14 <-- inside my adobe reader
[17:20] <ejat> for HTML rendering library .. is it correct?
[17:21] <BUGabundo_remote> ejat: why do ppl like _stuff_ inside their browsers?? I know I've always pulled everything I could OUT of them... I wish I could do the same with html5/flash videos
[17:22]  * ejat just asking .. 
[17:22] <BUGabundo_remote> fta: so if lucid *LTS* is going with ch4/5 and with the hugelly fast release cycle ch has
[17:22] <BUGabundo_remote> how do you plan to support ch im lucid?
[17:22] <BUGabundo_remote> stop providing new versions, once ch4/5 hits EOL?
[17:23] <BUGabundo_remote> ejat: I'm also asking. I would like to understand that too
[17:25] <fta> BUGabundo_remote, nope, just follow beta (then stable), disregarding the version number
[17:25] <BUGabundo_remote> ahh
[17:26] <BUGabundo_remote> and you just don't do that with FF, cause Mozilla doesn't want us to?
[17:26] <fta> i thought asac wanted to do the same for ff
[17:27] <fta> google supports the latest LTS so it should work
[17:28] <fta> the question is what happens when two LTS overlaps
[17:28] <fta> -s
[17:40] <BUGabundo_remote> eheh
[17:40] <BUGabundo_remote> good luck with that
[17:40] <BUGabundo_remote> :p
[18:11] <mahfouz> two LTS overlapping is like a solar eclipse
[18:12] <micahg> mahfouz: why?  it gives people a year to migrate :)
[18:12] <mahfouz> rly?
[18:13] <mahfouz> didn't know that
[18:13] <mahfouz> I always upgrade to alpha :)
[18:13] <micahg> for desktops at least
[18:15] <micahg> on servers people can skip 1 LTS release and still have a year to upgrade
[18:16]  * micahg waits for beta to upgrade desktop and release for server
[18:17] <mahfouz> then it's more like a divorce where you are in separation for 1 year and only then re-marry
[18:18] <chrisccoulson> micahg - you're not running lucid yet?
[18:18] <micahg> chrisccoulson: no, I'll upgrade over the weekend, why?
[18:19] <chrisccoulson> oh, i was just a bit surprised that you weren't just yet ;)
[18:19] <micahg> chrisccoulson: I wait for beta as this is my main machine
[18:19] <chrisccoulson> i suppose it's probably more difficult for me not to run lucid, with the other components i work on
[18:19] <micahg> and yes, I don't have to dogfood the desktop packages :)
[18:20] <chrisccoulson> yeah, that's why i need to run lucid really
[18:20] <chrisccoulson> it would be very difficult for me if i didn't ;)
[18:20] <micahg> chrisccoulson: I've been running Firefox 3.6 though since beta 1 or 2 :)
[18:20] <chrisccoulson> i shall probably need to start running the early beta's too ;)
[18:24] <mahfouz> I might not have installed if I would have known about the network manager problems
[18:24] <mahfouz> wpa2 connections such
[18:24] <mahfouz> suck
[18:24] <mahfouz> there is a very nasty bug there
[20:27] <dimitri__> i have a thunderbird problem using imap mail someone help me please
[22:32] <BUGabundo> asac:
[22:32] <BUGabundo> (2010-03-17 22:26:25) _Groo_: i found out why some 3g modems arent showing up in network manager
[22:32] <BUGabundo> (2010-03-17 22:27:02) _Groo_: BUGabundo: its not actually a bug but a priority order
[22:32] <BUGabundo> (2010-03-17 22:27:30) _Groo_: BUGabundo: 3g isnt showing up because modemmanager is getting called AFTER networkmanager is already running
[22:32] <BUGabundo> (2010-03-17 22:29:26) _Groo_: BUGabundo: the problem is AFTER the 3g is up and running (like seen in dmesg, usb 2-3: GSM modem (1-port) converter now attached to ttyUSB0 gos up and all), nm-applet NEVER shows up the 3g
[22:32] <BUGabundo> (2010-03-17 22:30:02) _Groo_: BUGabundo: the cure is to stop nm, kill -9 modemmanager, get it um first and restart nm
[22:32] <BUGabundo> (2010-03-17 22:30:29) _Groo_: BUGabundo: this will make 3g show up in NM applet
[23:12] <gnomefreak> piority order is a bug sometimes
[23:13] <gnomefreak> priority even
[23:19] <BUGabundo> fta: ch snapping
[23:19] <BUGabundo> fta: like this page http://www.cyanogenmod.com/downloads/audio-resources
[23:32] <BUGabundo> fta: http://code.google.com/p/chromium/issues/detail?id=38467
[23:34] <BUGabundo> fta: http://blog.chromium.org/2010/03/native-client-and-web-portability.html  isn't our build already native on 64bits?
[23:50] <gnomefreak76> @whoami
[23:50] <gnomefreak76> :)