[00:15] <fta> *sigh* i trashed my session while debugging and now the snaps are gone
[00:29] <BUGabundo_NCIS> eheh
[00:29] <BUGabundo_NCIS> the perfect solution: start fresh, or else...
[00:37] <BUGabundo_NCIS> nite
[00:44] <fta> http://arstechnica.com/web/news/2010/05/google-offers-web-designers-hosted-open-source-web-fonts.ars
[00:45] <fta> so much for the mysterious new ubuntu font. google did it 1st ;)
[00:46] <BUGabundo_gouki> llo
[05:33] <micahg> ddecator: did you have a chance to check songbird to see if it still builds?
[05:35] <ddecator> micahg: built for me either last night or the night before just fine :)
[05:35] <micahg> ddecator: k, I'll check the merge sat night and if there are no issues, push it up to PPA
[05:36] <ddecator> micahg: sounds good. let me know if there are any issues or if i need to fix anything
[05:38] <micahg> chrisccoulson: I'm back, might not make 11:00 UTC though...
[05:44] <ddecator> micahg: btw, i pushed the latest branch from when i built to my lp account, but the only thing that has changed since i requested the last merge was updates from upstream, nothing i had to change, so i didn't know if you wanted me to bother with another merge request
[05:45] <micahg> ddecator: nah, that's ok as long as nothing was rebased
[05:45] <ddecator> micahg: alright, that's what i thought
[09:17] <BUGabundo_remote> Welcome to Ibiza Summer Time!
[09:50] <asac> BUGabundo_remote: you are on ibiza?
[09:51] <BUGabundo_remote> asac: I wish :)
[09:52] <BUGabundo_remote> asac: still at work.. but ill be taking a week vacation to Algarve next month, if you want to meet up
[09:52] <asac> good. otherwise i would have been unhappy about you having holidays ;)
[09:52] <asac> heh
[09:52] <asac> unfortunately i wont have time till august from what i see
[09:53] <BUGabundo_remote> shame
[09:53] <asac> always travelling and wrestling ;)
[09:53] <BUGabundo_remote> as long as you are happy, hacking and drunk
[09:54] <BUGabundo_remote> erk, that didn't came out right ;P
[09:59] <asac> hehe
[09:59] <asac> no its fine.
[10:52] <cyrus82> Hi. Is anybody working on #507089 (thunderbird segfault with ldap auth in nsswicht)?
[12:38] <fta> asac, why is the n-m ppa stuck?
[12:38] <fta> should i stop the bot?
[12:38] <fta> last update was 3 months ago
[12:44] <asac> fta: cyphermox has to open the changelog up again
[12:44] <asac> nt sure why that hadent happened
[12:44] <asac> i thought he did
[12:44] <asac> i will try to remember to ask him when he comes back
[12:48] <fta> ok
[12:51] <fta> http://www.osnews.com/story/23335/Patent_Troll_Larry_Horn_of_MPEG-LA_Assembling_VP8_Patent_Pool
[12:59] <fta> asac, (another chromium beta incoming)
[13:00] <fta> amazon.de seems to snap quite a lot :(
[13:41] <fta> BUGabundo_remote, do you know where all the videos of the google io sessions are? i just see the intro and old stuff
[13:42] <BUGabundo_remote> I saw a link for it today
[13:42] <BUGabundo_remote> but don't have it on hand
[13:42] <BUGabundo_remote> the wave intro should have all the links
[13:42] <fta> i read some minutes in wave but no video :(
[13:43] <BUGabundo_remote> if I see it again, ill ping you
[13:43] <BUGabundo_remote> really busy today
[13:43] <BUGabundo_remote> 150 hosts to _fix_ dns
[13:44] <BUGabundo_remote> but I've seen more ppl complain that not all videos had been published
[13:46] <fta> oh, in the wave modal box, i see a broken puzzle piece, maybe that's why
[13:53] <fta> BUGabundo_remote, grrr "We will not be streaming Google I/O live via the Internet. However, we will be recording most sessions and making them available on http://code.google.com/io and on YouTube after the event. Please check back after June 1st to view the recorded sessions or follow us on @googleio where we will announce when recordings are available."
[14:03] <BUGabundo_remote> lol
[14:04] <BUGabundo_remote> there you go
[18:28] <micahg> _Tsk_: so, I think I might have an idea about the 64 bit crash for TB, I think it just started me as well, I'm retracing a coredump locally for it
[18:28] <_Tsk_> cool !
[18:29] <micahg> _Tsk_: I'm wondering if it's the xulrunner-1.9.1 + cairo 1.8.10 issue
[18:29] <_Tsk_> micahg: so it would be specific to the linux distri build right ?
[18:29] <micahg> _Tsk_: yes
[18:35] <micahg> _Tsk_: looks like it's something different
[18:58] <chrisccoulson> micahg - i noticed that seahorse in hardy builds a plugin for epiphany
[18:58] <chrisccoulson> i'm not sure what to do with that, as that plugin won't work in the webkit world
[18:58] <micahg> chrisccoulson: SRU it away?
[18:58] <chrisccoulson> yeah, that might be the only option
[18:58] <chrisccoulson> what does asac think?
[18:58] <chrisccoulson> ;)
[19:00] <asac> my brain is empty ;)
[19:01] <asac> chrisccoulson: drop that plugin ... e.g. ship an empty package
[19:01] <chrisccoulson> asac - ok, that's easy enough
[19:01] <chrisccoulson> thanks
[19:01] <asac> unless seahorse plugin now exists for webkit
[19:01] <asac> could be that it exists
[19:01] <asac> or maybe its built-in now
[19:01] <chrisccoulson> i don't think so. i think the plugin has gone away
[19:01] <chrisccoulson> i'll have a look though
[19:08] <micahg> chrisccoulson: oh, one thing I forgot to mention in our chat is about pushed beta full releases to the devel release as well
[19:08] <micahg> *pushing
[19:09] <chrisccoulson> micahg - oh, you mean like pushing build4 now to maverick?
[19:09] <micahg> chrisccoulson: yep
[19:09] <micahg> chrisccoulson: I can take care of that if you want once I have upload rights
[19:09] <chrisccoulson> that makes sense. i need to do an upload to maverick this weekend to disable CSD anyway
[19:09] <micahg> chrisccoulson: it gives us added beta/pre release testing
[19:10] <micahg> chrisccoulson: BTW, there will be a BUILD5 soon
[19:30] <ccheney> micahg, ping
[19:31] <micahg> ccheney: pong
[19:31] <ccheney> micahg, the dictionary symlink cleaning done by debian i believe will only be the removal of the '-' symlinks, the backwards compat will still be around, but we probably need to change the internal symlink of firefox/thunderbird/etc to use /usr/share/hunspell
[19:32] <micahg> ccheney: k, that's no problem
[19:32] <ccheney> micahg, i talked to rene and he is not planning on dropping the /usr/share/myspell dir until after the debian release since they are too close now
[19:32] <ccheney> micahg, so the symlinks in it for the '_' dicts will still be around until after debian releases
[19:32] <micahg> ccheney: as long as we're sure that all the languages are in the hunspell dir, we can switch the symlink for Maverick at any time
[19:33] <ccheney> micahg, they should be afaict but double checking probably wouldn't hurt
[19:34] <micahg> ccheney: I have a work item for the beta release to check that out
[19:34] <ccheney> micahg, i checked them before lucid release and they looked ok, but another set of eyes wouldn't hurt
[19:34] <ccheney> micahg, well actually there were a few bugs in lucid but i fixed all the ones i found :-)
[19:34] <ccheney> micahg, ok, wasn't sure if the item about symlinks encompassed that too
[19:34] <micahg> ccheney: k, I'll ping you if I have any questions later with that
[19:34] <ccheney> micahg, ok
[19:35] <micahg> ccheney: well, the item really should be to make sure that the mozilla apps no longer have dupes :)
[19:35] <ccheney> yea, no dupes will be good too :)
[19:39] <fta> asac, jcastro, jdstrand: I'm preparing yet another version of chromium for maverick, that will be the 3rd update that lucid missed. users keep asking me why the upgrades stopped, should i tell them to use a PPA instead?
[19:40] <jcastro> fta: yeah
[19:40] <jcastro> fta: asac had a plan for it but I totally forgot
[19:41] <jcastro> micahg: do you remember?
[19:41] <jcastro> did we write it down?
[19:41] <fta> jcastro, he said the security team was supposed to do it
[19:41] <fta> that has yet to happen
[19:41] <chrisccoulson> right, that's something i'll probably be involved with
[19:41] <asac> the plan is to just do it
[19:41] <asac> i dont know who is doing it though
[19:41] <micahg> jcastro: yeah, the security team was supposed to do it :)
[19:41] <jcastro> now would be a good time to figure it out!
[19:42] <fta> should i just push and wait?
[19:42] <fta> or will it be rejected?
[19:42] <asac> fta: push and wait? try to get the process actively started .folks will not find what to push etc.
[19:42] <asac> fta: jdstarnd or chrisccoulson should push that to the security ppa
[19:42] <asac> jdstrand: ^^
[19:43] <asac> fta: you cant push anyway. but having a branch they can use and clear instructions how to upload might help. ask chrisccoulson to help you getting it up
[19:43] <asac> he knows how to upload security fixes
[19:43] <asac> remember to document the security issues fixed
[19:43] <asac> otherwise its hard to push out
[19:43] <asac> if you dont know what was fixed, then pretend that you know and just document whatever was fixed on stable in between
[19:44] <fta> what about the exception thingy for browsers?
[19:44] <asac> once we have stable we will push everything
[19:44] <asac> fta: not needed. it will just happen
[19:44] <asac> fta: there was never an exception to push stuff without security issues ;) ... the idea was to make clear that we will hav eto push securtity with other stuff together
[19:44] <asac> but thats understood. tech board said, its not a tech board issue, so its security team decision how to do that
[19:45] <asac> talk to rickspencer3
[19:45] <asac> he will help you
[19:45] <asac> he wants to push chromium to main ;)
[19:45] <fta> the thing is, each time i'm late for an update, i loose users in favor of chrome
[19:45] <asac> right. so it needs to be sorted
[19:45] <asac> but its not a big deal imo atm
[19:45] <asac> you will gain all default netbook installs ;)
[19:46] <asac> thats the big cake ... ;)
[20:10] <fta> http://people.ubuntu.com/~fta/popcon-20100521.png
[20:10] <fta> asac, ^^
[20:43] <jdstrand> fta, asac, chrisccoulson, micahg: what did I miss? a chromium update?
[20:43] <jdstrand> I was not told I needed to push anything
[20:43] <micahg> jdstrand: well, now it's number 3 that Lucid didn't get
[20:43] <jdstrand> it is in universe, so it isn't on our team
[20:44] <jdstrand> if a community person or someone else wants it updated, I can sponsor it
[20:44] <micahg> fta: ^^^
[20:44] <jdstrand> I have not been approached to do that
[20:45] <jdstrand> I figured it would be dealt with in the same way that seamonkey is-- ie, it is built in a ppa somewhere, gets testing, then I am asked to push through -security
[20:45] <micahg> jdstrand: well, we were talking about that a few minutes ago, would you prefer that to just sponsoring?
[20:46] <jdstrand> micahg: if it is a debdiff, I can spnsor. if it is a full release like ff and seamonkey, it should really have a team/person maintaining it like we have for mozilla
[20:46] <jdstrand> micahg: and a process in place to test it
[20:46] <jdstrand> let me put it this way
[20:47] <jdstrand> I don't get paid to test seamonkey updates, so the mozilla team/community needs to do all the work on that, and then ask me to push it into -security
[20:47] <jdstrand> at that point I just do that-- I don't test it cause the mozilla team/community already did it
[20:48] <jdstrand> we need the same thing to happen with chromium
[20:48] <micahg> jdstrand: k, should we use the mozilla-security PPA for that or something else?
[20:48] <fta> jdstrand, what i send to the repos already lives in a ppa beforehand
[20:48] <jdstrand> micahg: I don't care-- ubumtu-mozilla-security is nice cause it is already there and non-virtual so I can do a direct pocket copy
[20:49] <jdstrand> fta: what kind of ppa is it? virtual or native?
[20:49] <fta> jdstrand, atm, it's the chromium beta ppa. but i advise to take either what i send to maverick, or the last tag in the bzr branch
[20:50] <jdstrand> fta: so that is a virtual ppa
[20:50] <fta> i don't have native ppa unfortunately
[20:50] <fta> maverick is native :)
[20:50] <jdstrand> fta: that will have to be rebuilt in -security ppa or corrdinated with the mozillateam ppa
[20:50] <fta> jdstrand, can't you take it from maverick/universe?
[20:51] <jdstrand> I can't pocket copy it, no
[20:51] <fta> oh
[20:51] <fta> *sigh*
[20:51] <micahg> fta: does the target for maverick just need to change?
[20:51] <fta> micahg, yes, that and the version number
[20:51] <jdstrand> it needs to be built with the same toolchain and libraries for which it is going to land
[20:52] <micahg> fta: can you prepare the bzr branch for Lucid and then tell chrisccoulson what to do to generate the upload so he can push to mozilla-security PPA?
[20:53] <fta> (feels weird to use a mozilla-* location)
[20:53] <fta> but well..
[20:53] <micahg> fta: I think we're all intertwined anyways ;)
[20:54] <jdstrand> fta: the alternative is to create source packages for each release you want to provide them for, then someone from the ubuntu-security team can upload them to ubuntu-security-proposed
[20:54] <jdstrand> fta: and then ultimately get them into -proposed
[20:55] <jdstrand> fta: that would be a way to use the existing infrastructure and get people to try out the builds before pushing them to -security
[20:55] <jdstrand> fta: basically, the process is not defined for chromium, and it needs to be (until it ends up in main, at which point chrisccoulson/micahg or someone will likely start working on it)
[20:57] <jdstrand> fta: fyi, if going the ubuntu-security-proposed route: if you want that done early next week, I will be gone. you can ask mdeslaur or kees to do that for you
[20:58] <fta> jdstrand, not sure where i should stop then. it's easy to see which version is in maverick/universe, then lucid needs the same thing. the tarball is in maverick, the packaging is in bzr with a tag
[20:59] <jdstrand> fta: we need full source packages for each release you want uploaded
[20:59] <jdstrand> fta: ie, we need to upload it to build it from source
[21:00] <fta> sure, but it's a simple merge, i don't see the difficulty here
[21:00] <fta> or i'm missing something
[21:01] <fta> it could also be dget from maverick, update d/changelog, new source package, push
[21:01] <fta> there are plenty of options
[21:01] <micahg> fta: don't you want to maintain a .lucid branch in bzr?
[21:02] <jdstrand> fta: I don't have anything to upload on your behalf, ie to 'sponsor'. how the security team normally works with security updates for community supported packages is that the debdiff is provided for an existing package *or* the community person supplies signed and 'tested on that release' source packages
[21:02] <fta> micahg, i initially wanted to do that, but since i can't upload
[21:03] <jdstrand> fta: chromium needs a process for building and testing. aiui, you are asking me to just do it all. I don't have the resources to do that
[21:03] <fta> why isn't it like the NEW queue??
[21:03] <fta> jdstrand, the process is already there
[21:03] <jdstrand> the process for the devel release is, but not -security
[21:03] <jdstrand> which is why we are talking about it now
[21:04] <micahg> fta: it seems like either we have to push to a native PPA or you or someone else needs to provide signed source builds
[21:04] <fta> but the package is exactly the same, it's flexible enough to be built from +1 down to hardy
[21:04] <jdstrand> fta: perhaps it would be easier to say that this is very similar to an SRU where you want to do a microrelease bump
[21:05] <jdstrand> fta: sure, I could pull the branch and do all the version changes, etc, etc. but then the build is not tested
[21:05] <jdstrand> the build 'on that release of Ubuntu'
[21:06] <jdstrand> fta: would you ask ubuntu-sru to create the source packages for you and upload them on your behalf?
[21:06] <fta> it has already lived in the beta PPA for a few days, before i release it to +1.
[21:06] <fta> it's not enough?
[21:06] <jdstrand> I think we are not communicating effectively
[21:06] <jdstrand> I don't know what testing you have done
[21:06] <jdstrand> I just heard that there is an update for chromium
[21:06] <jdstrand> chromium is in universe
[21:07] <jdstrand> it is up to the community to provide updates for universe packages
[21:07] <jdstrand> you are (presumably) that community for chromium
[21:07] <jdstrand> if you wanted to do an sru for chromium in lucid, how would you proceed?
[21:08] <jdstrand> the process is not really much different for ubuntu-security
[21:09] <asac> hd
[21:09] <asac> jdstrand: only chriscoulson and you can push to the security ppa
[21:09] <jdstrand> asac: yes, and I said that if I were provided tested source packages I would upload them on his behalf
[21:10] <asac> fta: cant you do that?
[21:10] <asac> ;)
[21:10] <asac> point jdstrand to tested sources to push?
[21:10] <asac> after adjusting target to lucid-security i guess
[21:10] <asac> so i give up making a real script in upstart .conf
[21:10] <asac> thats really painful
[21:11] <micahg> asac: I think keybuk did that on purpose :)
[21:15] <fta> what should i happened after to the version?
[21:15] <fta> -to
[21:16] <micahg> ubuntu0.10.04.1?
[21:18] <fta> nothing less ugly? ;)
[21:18] <fta> i see other packages don't add anything
[21:18] <micahg> fta: other packages generally don't have the same version released to multiple Ubuntu releases AFAIK
[21:19] <fta> Get:5 http://archive.ubuntu.com/ubuntu/ lucid-updates/main apt-transport-https 0.7.25.3ubuntu9 [80.7kB]
[21:19] <fta> Get:6 http://archive.ubuntu.com/ubuntu/ lucid-updates/main libpangomm-1.4-1 2.26.2-0ubuntu1 [62.2kB]
[21:19] <fta> Get:7 http://archive.ubuntu.com/ubuntu/ lucid-updates/main software-center 2.0.4 [278kB]
[21:19] <fta> those are in all versions
[21:19] <asac> fta: new upstream versions in security is rare
[21:19] <asac> so what micahg said is right
[21:19] <asac> ubuntu0.9.10.1 ubuntu0.10.04.1 etc.
[21:20] <jdstrand> fta: https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update%20the%20packaging has tips on versioning
[21:20] <fta> -chromium-browser (5.0.375.38~r46659-0ubuntu1) maverick; urgency=low
[21:20] <fta> +chromium-browser (5.0.375.38~r46659-0ubuntu0.10.04.1) lucid-security; urgency=low
[21:20] <fta> ?
[21:21] <jdstrand> fta: which is basically what micahg and asac said when you have the same base version
[21:21] <jdstrand> fta: looks good
[21:21] <asac> fta: yeah thats correct
[21:21] <asac> then you have to do a trick to push that to lucid in some ppa .. you have to directly upload to the lucid/ folder
[21:21] <jdstrand> fta: the thing to remember is a user needs to be able to upgrade to the next release of Ubuntu
[21:22] <fta> that i already know :) i'm not new to packaging
[21:24] <jdstrand> fta: heh
[21:24] <jdstrand> fta: I didn't mean to imply that-- versioning can be tricky with new sources is all
[21:26] <fta> jdstrand, ok so lp:~chromium-team/chromium-browser/chromium-browser.lucid has it. what do you need now?
[21:26] <fta> a source package somewhere?
[21:26] <jdstrand> fta: signed and tested, yes
[21:30] <fta> jdstrand, can't i just have a native ppa to push everything i need there and let you copy afterwards? because here, it's just the browser, but some other time, it will be also the codecs and/or gyp and/or libvpx
[21:31] <jdstrand> fta: current policy is that only canonical employees can have a native ppa (I didn't make that policy)
[21:32] <fta> then a canonical employee should do all that
[21:32] <jdstrand> fta: the ubuntu-security team is happy to upload packages into ubuntu-security-proposed and then pocket copy to -proposed on your behalf
[21:32] <fta> i can just sit on my hands and watch the dailies build
[21:32] <jdstrand> fta: a canonical employee should do what?
[21:33] <micahg> fta: if you don't want to, I can make the source package and test locally over the weekend
[21:34] <micahg> fta: s/if you don't want to/if you want me to/
[21:34] <fta> micahg, it's not the problem, it only one brz bd --merge away for me, it's just that there are so many barriers preventing good wills like myself to properly maintain released stuff
[21:34] <jdstrand> fta: I'm not sure what the problem is. I asked for a signed source package that is tested, that is all
[21:35] <micahg> fta: well, most packages don't need updates like this, generally the ones that allow micro-releases are maintained in main by canonical
[21:35] <fta> jdstrand, you'll have it once it's uploaded somewhere
[21:35] <jdstrand> fta: that is no more or less than I ask of any other sponsored security upload
[21:35] <BUGabundo> o/
[21:35] <micahg> hi BUGabundo, welcome to the Chromium browser saga :)
[21:36] <BUGabundo> come again?
[21:36] <micahg> BUGabundo: check the logs in 25 minutes :)
[21:36] <jdstrand> fta: I'm sorry if there is some frustration here. I appreciate that you are doing the work. keeping a browser up to date with new point releases is hard, and is why there is a whole team dedicated to it for mozilla
[21:36] <BUGabundo> don't tell me your vacations made you swicht sides too?
[21:37] <jdstrand> fta: I hope that such a team will exist for chromium, especially if it is going to main...
[21:37] <micahg> jdstrand: team ATM = myself + chrisccoulson :)
[21:37] <BUGabundo> jdstrand: I already said several times: rename ubuntu-mozilla-team, Ubuntu Browser Team
[21:37] <jdstrand> micahg: currently, but your team has a clearly defined process for updates in stable releases
[21:37] <BUGabundo> micahg: forgetting Jon ?
[21:37] <micahg> BUGabundo: asac and I talked about that actually
[21:37] <micahg> BUGabundo: he's not doing packaging ATM
[21:38] <BUGabundo> :(
[21:38]  * micahg doesn't know how fta does it
[21:39] <BUGabundo> he is a super machine
[21:39] <BUGabundo> with a lot of scripts and bots
[21:39] <BUGabundo> *if* one day he looses his hard drive
[21:39] <BUGabundo> he will go baserk
[21:39] <fta> jdstrand, http://people.ubuntu.com/~fta/lucid/
[21:40] <jdstrand> fta: my plan is to upload to ubuntu-security-proposed and then pocket copy to lucid-proposed for wider testing. is this acceptable?
[21:41] <fta> jdstrand, sure, whatever you want, it's better than no upload at all
[21:41] <fta> upgrade
[21:41] <fta> jdstrand, and thanks
[21:42] <jdstrand> sure, np
[21:42] <fta> jdstrand, and you can expect another update in a few days, i already have 5.0.375.53~r47719 in progress for maverick
[21:43] <jdstrand> fta: ok. I won't be around the beginning of next week, so get mdeslaur or kees to do it
[21:43] <fta> ok
[21:45] <fta> micahg, the golden rule is automation. if i have to some something once, it's fun, twice, it's boring, three times, it's unacceptable, i write a script
[21:45] <BUGabundo> me too
[21:47] <fta> -some+do
[21:49] <fta> http://ubuntu-virginia.ubuntuforums.org/showthread.php?p=9338769 :(
[21:49] <fta> i should stop this google alert, it's making me sad
[21:50] <BUGabundo> wow
[21:50] <BUGabundo> what DID YOU DO?
[21:50] <BUGabundo> chromium is SLOOWWWW loadong
[21:51] <BUGabundo> *loading
[21:51] <fta> nothing
[21:51] <BUGabundo> it used to be *instantenous
[21:51] <fta> don't blame me
[21:52] <BUGabundo> I have to 'blame' someone
[21:52] <micahg> fta: will I have profile isssues if I switch between beta and daily?
[21:52] <BUGabundo> and you are in ping reach
[21:52] <fta> micahg, beta->daily, no, daily->beta, more than probable
[21:52] <micahg> :(
[21:53] <fta> depends on how big the gap is
[21:53] <micahg> fta: I guess I"ll use a temp profile dir
[21:53] <fta> i remember in had to trash my session once
[21:53] <fta> -in+i
[21:53] <fta> (i hate this new keyboard)
[21:54] <BUGabundo> ahaaha
[21:54] <fta> curve my *s
[21:54] <BUGabundo> micahg: alias chromiumnew='chromiumdatadir="$(mktemp -d)";chromiumdiskcache="$(mktemp -d)";chromium-browser --user-data-dir=$chromiumdatadir --disk-cache-dir=$chromiumdiskcache
[21:54] <BUGabundo> here's something I learned from fta
[21:54] <BUGabundo> then I automated it :D
[21:55] <fta> apparently, --user-data-dir is enough
[21:55] <BUGabundo> DOH
[21:55] <BUGabundo> you fail
[21:57] <micahg> BUGabundo: chromiumnew started pacman :)
[21:58] <BUGabundo> I like that to test our servers and sites.
[21:58] <BUGabundo> always brand new profiles
[21:58] <BUGabundo> no cache,  passwords, logins, cookies
[21:58] <BUGabundo> its AWESOME
[21:59]  * micahg should do that for firefox too :)
[21:59] <BUGabundo> also kewl to login to a site more then once with 3 or more accounts
[21:59] <BUGabundo> cause private navigation only allows one window
[21:59] <BUGabundo> micahg: it will... once it does PID separation
[22:02] <fta> only one?
[22:02] <fta> i can start several
[22:02] <BUGabundo> fta: private??
[22:02] <fta> yes
[22:03] <BUGabundo> but they all share the same PID
[22:03] <BUGabundo> and logins/cookies are tied
[22:06] <fta> http://www.osnews.com/story/23334/The_In-depth_Technical_Analysis_of_VP8_Counterpoints
[22:07] <fta> http://www.osnews.com/story/23335/Patent_Troll_Larry_Horn_of_MPEG-LA_Assembling_VP8_Patent_Pool
[22:08] <BUGabundo> heh
[22:08] <BUGabundo> how is that going?!
[22:08] <BUGabundo> will webm really be patent free?
[22:29] <jdstrand> fta: fyi-- uploaded to ubuntu-security-proposed: https://launchpad.net/~ubuntu-security-proposed/+archive/ppa/+packages
[22:30] <fta> \o/
[22:31] <jdstrand> :)
[22:32] <jdstrand> fta: I'll keep an eye on it and pocket copy it to -proposed. I'll also file a bug so it can be tracked (as per SecurityTeam/SponsorsQueue)