[00:00] <micahg> chrisccoulson: cool, I'm happy doing locally though as it allows me to test builds, but good to know in case I'm stuck on low BW
[00:01] <chrisccoulson> i shall be using it for the daily builds ;)
[00:01] <micahg> chrisccoulson: speaking of daily builds, would you be up for adding the crons for chromium to your build crons?
[00:02] <chrisccoulson> micahg, maybe once i've got the firefox builds going
[00:02] <chrisccoulson> in any case, i don't have access to the PPA's or branches anyway
[00:02] <chrisccoulson> so i can't do that
[00:02] <micahg> chrisccoulson: ok, I was thinking alternatively of switching to build recipes since it's svn based
[00:03] <chrisccoulson> ah, ok
[00:03] <micahg> chrisccoulson: yeah, I'll fix that soon, need to send an e-mail
[00:03] <chrisccoulson> i've been cloned now: https://launchpad.net/~chrisbot
[00:03] <micahg> but that's not happening until next week
[00:03]  * micahg is still in crisis mode
[00:03] <micahg> excellent...
[00:04] <chrisccoulson> thanks to robohash for the avatar :)
[00:04] <micahg> now we just need to train it to fix the build failures :)
[00:08] <chrisccoulson> ok, i have a good tarball again :)
[00:08] <chrisccoulson> now to make sure i delete the *correct* one this time
[00:08] <chrisccoulson> with the correct one being the broken one
[00:08] <chrisccoulson> now i'm confused ;)
[00:13] <chrisccoulson> micahg, m_conley bought up an interesting problem at the end of last week. how do we warn users before upgrading firefox or thunderbird that some of their extensions might not work afterwards?
[00:13] <chrisccoulson> the upstream updater checks this before offering an upgrade
[00:13] <chrisccoulson> and tells you if any of your extensions will stop working
[00:14] <chrisccoulson> i want to be able to do something similar from update-manager
[00:14] <micahg> chrisccoulson: we don't unfortunately, nor do I think we can, on first run, the new version checks for compatibility and warns if something won't work
[00:14] <chrisccoulson> we can :)
[00:15] <chrisccoulson> we can check the extensions that are installed and probe for updates ourselves
[00:15] <chrisccoulson> i'm sure i can write a tool which will do just that, which we could hook in to update-manager
[00:15] <micahg> updates aren't always needed
[00:16] <micahg> but I suppose you could make the calls to AMO for compatibility and display something nice
[00:16] <chrisccoulson> right, but there's no reason i can't do exactly the same thing that firefox does before offering an upgrade
[00:16] <chrisccoulson> yeah, that's what i was hinting at
[00:16] <chrisccoulson> i might start writing something this week to do that
[00:17] <micahg> cool, I think that will make users happy
[00:17] <chrisccoulson> yeah, it would be nice to have something like that
[00:17] <micahg> but I really don't like the idea of people not upgrading due to extensions breaking...
[08:05] <Ruedii> Does anyone know what the network.http.qos entry is in Firefox?
[15:34] <chrisccoulson> yay! all the builders came back :)
[20:16] <FernandoMiguel> evening	
[20:22] <chrisccoulson> m_conley, when you listen for new messages on nsIMsgMailSession, does OnItemAdded fire before or after filters run on the new message?
[20:22] <chrisccoulson> eg, what happens if the spam filter marks it as spam, and it is moved to the junk folder?
[20:22] <m_conley> chrisccoulson: hm - good question.
[20:23] <m_conley> chrisccoulson: maybe ask bienvenu in #maildev?
[20:23] <chrisccoulson> m_conley, yeah, could do
[20:24] <chrisccoulson> ah, he's not there atm :/
[20:24] <m_conley> chrisccoulson: or Standard8.  I can't say I'm too familiar with the order of events wrt filters.
[20:25] <chrisccoulson> the only reason i mentioned it is because someone sent me an e-mail saying that the messaging menu notifies them of messages that get moved to their junk folder, from a POP account
[20:25] <chrisccoulson> and we're meant to ignore those
[20:25] <chrisccoulson> but the log he sent me suggests that we get an event before the message is marked as junk
[20:26] <chrisccoulson> but then he sent me another message saying the latest version seemed to fix it, but i'm not sure :/
[20:42] <m_conley> chrisccoulson: hrm
[20:43] <m_conley> chrisccoulson: I suppose we should wait to see if it *really* fixed it, which I somewhat doubt.
[20:43] <m_conley> chrisccoulson: while I have you, though, I was wondering if you knew the easiest way for me to get the debug symbols for libgio?
[20:44] <chrisccoulson> m_conley, this should help - https://wiki.ubuntu.com/DebuggingProgramCrash :)
[20:44] <m_conley> chrisccoulson: excellent, thank you. :)
[20:51] <chrisccoulson> m_conley, hmm, IIUC, it looks like filters are applied before we get notified
[20:51] <chrisccoulson> which is good :)
[20:51] <chrisccoulson> doesn't explain why it didn't work for this guy though :/
[20:52] <m_conley> hrm
[23:07] <FernandoMiguel> nite every1
[23:15] <spikebike> Anyone know if thunderbird on ubuntu uses the system wide SSL certs?
[23:15] <spikebike> i.e. /etc/ssh/certs
[23:15] <micahg> spikebike: yes, it does in the stable releases, I"ll be updating NSS and thunderbird soon
[23:16] <micahg> spikebike: err, it uses NSS, not ca-certificates
[23:16] <spikebike> ah
[23:16] <spikebike> ok, that's consistent with what I'm seeing
[23:16] <micahg> spikebike: are you concerned about the diginotar stuf?
[23:16] <spikebike> seems like University of California is standardizing on InCommon certs
[23:16] <spikebike> ah, no
[23:16] <micahg> ok
[23:17] <micahg> spikebike: we'll probably switch it to use internal NSS at some point
[23:17] <spikebike> InCommon has a komodo signed cert but I think the trust between the two is missing
[23:17] <spikebike> er comodo
[23:17] <micahg> spikebike: what release are you running?
[23:17] <spikebike> natty
[23:17] <micahg> ok, so the NSS version is a little behind and we're missing new roots
[23:18] <micahg> we'll probably update that soon
[23:18] <spikebike> https://spaces.internet2.edu/display/InCCollaborate/InCommon+Cert+Types
[23:18] <micahg> spikebike: does Firefox in natty have the root?
[23:18] <spikebike> that's the one that seems to be missing
[23:18] <spikebike> oh umm, checking
[23:19] <spikebike> is /etc/ssl/certs/mozilla certs that mozilla trusts?
[23:19] <spikebike> or certs that mozilla asked ubuntu to trust?
[23:20] <spikebike> firefox likes it, mostly anyways
[23:20] <micahg> hmm, that seems to have disappered in oneiric...
[23:20] <micahg> spikebike: ok, so the NSS update should fix it for thunderbird as well then
[23:21] <spikebike> it shows a blue bar, verified by internet2, but owner is listed as (unknown)
[23:21] <micahg> well, that's the specific site, not the cert listed on it
[23:22] <spikebike> yeah, not sure what field it's looking at though
[23:22] <micahg> spikebike: and that patch is maintained with ca-certificates which is another package that has certs in it, it gets periodic updates of the latest certs from NSS
[23:22] <spikebike> sounds promising
[23:22] <micahg> s/patch/path/
[23:23] <spikebike> thunderbird was rather unhappy with a similar InCommon cert, no matter what I did in /etc/ssl/certs it made me view and approve an exception
[23:23] <micahg> spikebike: yeah, thunderbird will ignore that path, you can import the cert in the thunderbird certificate manager
[23:24] <micahg> assuming you've verified it's authentic
[23:24] <spikebike> yeah, of course, and that's what I did... I was hoping to support a larger group of users though
[23:25] <spikebike> so google chrome and firefox like it, looks like thunderbird in natty doesn't
[23:28] <micahg> spikebike: the addtrust root seems to be in the latest versions
[23:28] <micahg> so, an NSS update should suffice
[23:30] <spikebike> cool
[23:30] <spikebike> I wish ssl was handled like dnssec
[23:30] <spikebike> just upload the equivalent of a DS record to your registrar
[23:30] <micahg> there are those discussing that