[00:06] <chrisccoulson> micahg - i'm just about to upload now
[00:06] <micahg> chrisccoulson: k
[00:06] <chrisccoulson> have you tested the changes to the apparmor bits in the postinst script?
[00:06] <chrisccoulson> jdstrand ? ^^
[00:19] <chrisccoulson> ok, uploaded now
[00:19] <chrisccoulson> in time for the freeze ;)
[00:51] <Dimmuxx> is the ui freeze at the same time as beta freeze?
[00:56] <micahg> Dimmuxx: yes, why?
[00:59] <Dimmuxx> micahg: I was just wondering. I wanna see the final theme design :)
[03:30] <jdstrand> chrisccoulson: I did test the postinst bits, yes. I assume you mean the ones I botched and then fixed ;)
[08:44] <sugnan> hello can some one please help, am trying to use the plugin https://addons.mozilla.org/en-US/firefox/addon/4522/, but getting the following error Failed to load shared librararies and/or register XPCOM componenets for XML Digital Signature tool .
[08:45] <sugnan> Make sure that DLLs (shared libraries) from Apache Xerces-C++ and Xalan-C++ (for FF2 only) are in your PATH (LD_LIBRARY_PATH) environment variable
[08:46] <sugnan> i have installed all xmlsec related librarie
[11:45] <gnomefreak> micahg: did you ever pushed the symlink patch to thunderbird daily PPA
[13:07] <fta2> chrisccoulson, d'oh! your last nss/nspr killed chromium
[13:07] <chrisccoulson> fta2 - what did it break?
[13:07] <fta2> $ chromium-browser
[13:07] <fta2> [5855:5900:410194104:ERROR:base/nss_util.cc(149)] NSS_VersionCheck("3.12.3") failed.  We depend on NSS >= 3.12.3, and this error is not fatal only because many people have busted NSS setups (for example, using the wrong version of NSPR). Please upgrade to the latest NSS and NSPR, and if you still get this error, contact your distribution maintainer.
[13:07] <fta2> /usr/lib/chromium-browser/chromium-browser: symbol lookup error: /usr/lib/libnssutil3.so: undefined symbol: PL_ClearArenaPool
[13:08] <chrisccoulson> hmmm, that symbol was added to the latest nspr version
[13:09] <chrisccoulson> fta2 - you've not updated nss without nspr have you? (although, that shouldn't be possible anyway)
[13:09] <fta2> it's after a reboot of a fully updated maverick
[13:10] <fta2> libnspr4-0d 4.8.6-0ubuntu1 & libnss3-1d 3.12.7-0ubuntu1
[13:11] <chrisccoulson> hmmm, i wonder if it's picking up an older nspr from somewhere else. what is the output of "ldd /usr/lib/libnssutil3"?
[13:11] <fta2>         libnspr4.so => /usr/lib/libnspr4.so (0x00007f7a92944000)
[13:12] <chrisccoulson> fta2 - is this a version that still has the LD_LIBRARY_PATH hack to /usr/lib/xulrunner-*?
[13:13] <fta2> oh, that damn openjdk workaround maybe
[13:13] <chrisccoulson> yeah, i bet it's getting the older nspr from xulrunner
[13:13] <chrisccoulson> which is missing that symbol
[13:14] <chrisccoulson> it's strange that it doesn't get nss from the same place though
[13:14] <chrisccoulson> i would try removing that and see if it works
[13:14] <fta2> correct, it worked without the workaround
[13:15] <fta2> how come i didn't catch that earlier
[13:15] <fta2> the workaround has been there for weeks
[13:16] <chrisccoulson> fta2 - the new nspr version was only uploaded yesterday
[13:16] <chrisccoulson> which xulrunner version do you have btw?
[13:16] <fta2> xulrunner-1.9.1.13pre/ xulrunner-1.9.2.10pre/ xulrunner-2.0b5pre
[13:16] <fta2> $ xulrunner --gre-version
[13:16] <fta2> 1.9.1.13pre
[13:16]  * gnomefreak misses Maverick
[13:16] <fta2> that's from umd
[13:17] <chrisccoulson> ah, so that must be shipping it's own nspr version for some reason. the in-archive version isn't doing that
[13:18] <fta2> i don't need xul 1.9.1, it's obsolete, right?
[13:18] <gnomefreak> tbird-3.0?
[13:19] <chrisccoulson> not quite obsolete yet, but you probably don't need it
[13:19] <gnomefreak> nevermind it cant be
[13:19] <gnomefreak> you dont need it, well at least i dont have itinstalled
[13:19] <fta2> the question is, which is xulrunner still pointing at 1.9.1 and not 1.9.2?
[13:20] <chrisccoulson> fta2 - ok, so 1.9.1.13 is shipping it's own (slightly older) nspr, which is why you see the problem
[13:20] <fta2> shouldn't we drop the alternative?
[13:20] <chrisccoulson> that doesn't affect the in-archive version, but you probably want to drop the LD_LIBRARY_PATH change anyway (it doesn't seem to be needed now)
[13:21] <fta2> purged xul191 and it's fine now
[13:21] <chrisccoulson> you can update the link to point to 1.9.2 with update-alternatives. i've been thinking of using the link priority to migrate that automatically so that the latest stable version gets priority
[13:22] <chrisccoulson> at the moment, all the xulrunner versions have the same link priority, so you end up with the link pointing to the older version when you install a new version
[13:23] <fta2> it should point to the version used by the supported firefox
[13:28] <chrisccoulson> fta2 - that's why: http://bazaar.launchpad.net/~mozillateam/xulrunner/xulrunner-1.9.1.head/revision/537
[13:29] <fta2> yep, but that's meant for xul/ff own needs
[13:29] <fta2> sigh
[13:30] <chrisccoulson> mdeslaur, can i have a USN for TB3.0.7 please?
[13:32] <fta2> workaround dropped from ch.head
[13:33] <mdeslaur> chrisccoulson: sure, hold on
[13:34] <mdeslaur> chrisccoulson: 978-1
[13:34] <chrisccoulson> mdeslaur, thanks
[15:39]  * gnomefreak getting really pissed off with tb now
[15:42] <gnomefreak> it is failing to connect on more than one address it worked fine yesterday morning than later it was 1 address now 2+ address' are haivng the password errors
[15:48] <gnomefreak> same problem in safe mode
[16:21] <chrisccoulson> jdstrand, for seamonkey updates, we're currently doing a rebuild after the official release, just to add MFSA numbers to the changelog
[16:21] <chrisccoulson> which seems a little crazy
[16:21] <chrisccoulson> do you think there would be any issues with just having a link to something like http://www.mozilla.org/security/known-vulnerabilities/seamonkey20.html ?
[16:22] <chrisccoulson> (in the changelog)
[16:23] <jdstrand> chrisccoulson: in the past we have referenced MFSAs. That said, seamonkey is in universe and you could probably figure something out that would better utilize your time than spelling all that out in the changelog and leaving the link.
[16:23] <jdstrand> chrisccoulson: that said, MFSAs are preferred, but I'd take the link-- just be clear that it fixes everything after the previous version
[16:25] <chrisccoulson> jdstrand, yeah, i'll ty and find a link to a page which makes it more obvious what issues are fixed (perhaps the release notes?)
[16:25] <chrisccoulson> it just seems a little wasteful to do a whole rebuild just to add information to the changelog
[16:26] <chrisccoulson> jdstrand, perhaps we could maintain our own page with the information on?
[16:27] <jdstrand> chrisccoulson: we have the ubuntu-cve-tracker for that
[16:27] <jdstrand> chrisccoulson: the changelog really does need to say that it is a SECURITY UPDATE. spelling out the MFSAs in the changelog or pointing to the upstream link is up to you
[16:28] <chrisccoulson> jdstrand, yeah, the issue is that we don't have visibility of the CVE's when we do the initial build, unless there is some way we could make use of that without intially having that information
[16:28] <jdstrand> chrisccoulson: people make decisions based on the changelog -- if it isn't clear it is a security update and what is fixed, they might not upgrade
[16:28] <jdstrand> chrisccoulson: this is why we assign USNs for firefox and tbird
[16:29] <jdstrand> chrisccoulson: seamonkey doesn't get a USN so we are kinda stuck
[16:29] <chrisccoulson> jdstrand, yeah, so we should make clear it is a security update. but the situation is similar for firefox (in that the changelog doesn't really say anything, other than give a USN)
[16:29] <chrisccoulson> so people still need to find the USN before making a decision on what to do
[16:30] <chrisccoulson> do people read changelogs though? ;)
[16:30] <jdstrand> chrisccoulson: it is precisely the same as for firefox, but seamonkey doesn't get a USN, so we need to do something else. providing the aforementioned link is fine. in the past, seamonkey builds lagged, so it wasn't a problem
[16:30] <chrisccoulson> my GF doesn't even upgrade - she just closes update-manager without even acknowledging it!
[16:30] <jdstrand> chrisccoulson: update-manager can display them and there is also apt-listchanges. it is really all anyone has for universe stuff
[16:31] <jdstrand> chrisccoulson: well, your GF notwithstanding, we need to provide the info to those who are looking :)
[16:31] <chrisccoulson> heh ;)
[16:31] <chrisccoulson> she needs re-educating really ;)
[16:31] <chrisccoulson> i wonder how many other people just close update-manager?
[16:34] <jdstrand> chrisccoulson: I suggest you set her up to install security updates automatically in the background
[16:34] <jdstrand> chrisccoulson: I started doing that with all my non-technical users
[16:35] <jdstrand> they don't get -updates, but they are safe
[16:35] <chrisccoulson> yeah, i suppose i could do that
[16:39] <glassresistor> does anyone else have issues with ff4 in gmail where when you try and send an email it says SENDING up at the top and never thinks it got sent, it does get sent but the page basically freezes
[17:21] <chrisccoulson> glassresistor, no, that seems to work ok here
[17:21] <micahg> chrisccoulson: why is xulrunner building its own nspr?
[17:22] <chrisccoulson> micahg, because you bumped the minimum version to 4.6.8 in .head ;)
[17:23] <chrisccoulson> micahg - http://bazaar.launchpad.net/~mozillateam/xulrunner/xulrunner-1.9.1.head/revision/537
[17:23] <glassresistor> im having other issues as well i can't load this one page other people on my network can, its worked in ff4 but not ff3 then its stopped working in ff4 after an update
[17:23] <glassresistor> and by page i mean anything from one domain
[17:24] <micahg> chrisccoulson: ah, I'll revert that :)
[17:24] <chrisccoulson> micahg - yes please, if you don't mind
[17:24] <chrisccoulson> i'll get 1.9.1 in to the security PPA then as well
[17:25] <chrisccoulson> that will just leave 1.9.2 then
[17:25] <chrisccoulson> thunderbird and seamonkey are in the PPA
[17:25] <micahg> chrisccoulson: which we still have to wait on upstream for a decision on nspr
[17:25] <chrisccoulson> yeah, that's why i've left that one for now
[17:25] <chrisccoulson> FF3.6.9 is built on all releases too
[17:27] <micahg> chrisccoulson: k, reverted
[17:27] <chrisccoulson> cool, thanks
[17:27] <micahg> chrisccoulson: TB 3.1.3 should wait as well for the NSPR outcome
[17:27] <chrisccoulson> yeah, no problem
[17:31] <glassresistor> >	im getting a file not found when trying to manage profiles jar:file:///usr/lib/firefox-3.6.10pre/chrome/browser-branding-en-US.jar!/locale/branding/browserconfig.properties
[17:33] <glassresistor> its seems like something about the dailybuild ppa is messing with my profiles, cookies, and cache
[17:33] <glassresistor> gonna pop out and restart
[17:45] <chrisccoulson> i didn't realise 1.9.1 was that out of date on karmic
[17:45] <chrisccoulson> i thought we were on 1.9.1.10 at least. i'm not sure what happened to that though
[17:50] <micahg> chrisccoulson: nope :)
[17:51] <micahg> we skipped it in the rush to get 3.6.4/6 in
[17:52] <chrisccoulson> yeah, that was a bit of an oversight. i even tagged the branch for 1.9.1.10 (and i've got a build of it here too)
[17:52] <chrisccoulson> we just must have forgotten to publish it ;)
[18:41] <chrisccoulson> urgh, the xulrunner-1.9.1 builds are failing to upload after building
[18:42] <chrisccoulson> easy fix though :)
[18:42] <chrisccoulson> 2010-08-26 17:35:41 WARNING 	xulrunner-dev_1.9.1.12+build1+nobinonly-0ubuntu0.9.10.1_amd64.deb: Version older than that in the archive. 1.9.1.12+build1+nobinonly-0ubuntu0.9.10.1 <= 1.9.2.8+build1+nobinonly-0ubuntu0.9.10.1
[18:42] <chrisccoulson> i need to drop the xulrunner-dev binaries from this update
[18:42] <chrisccoulson> it sucks that it waited until they were built before telling me that
[19:29] <fta> 626 jobs (17 hours)...
[19:45] <chrisccoulson> hmmm, where did all those builds come from? :/
[19:47] <micahg> chrisccoulson: lack of PPA builders, so the queue builds
[19:49] <fta> not entirely, as there are on 6 packages in q for amd64
[19:50] <micahg> fta: yes, but arch all packages build on i386 so the queue is inherently longer
[20:57] <micahg> chrisccoulson: any chance of being able to push thunderbird crashes to mozilla as well?
[20:57] <chrisccoulson> micahg - possibly, although only when i no longer have to push symbols over my own connection ;)
[20:58] <micahg> chrisccoulson: k :) that'll reduce the number of bugs greatly :)
[21:01] <chrisccoulson> micahg - have you upgraded to maverick yet?
[21:01] <micahg> chrisccoulson: nope, will do next thursday after beta release
[21:01] <chrisccoulson> yeah, that's normally when i upgrade my stable desktop too
[21:02] <chrisccoulson> (my GF wouldn't be too happy having to run the alpha's)
[21:02] <chrisccoulson> but she probably won't even notice if i upgrade after beta ;)
[21:02] <micahg> I only have one machine I use at the moment, after I upgrade my server to lucid, I'll start doing most of my packaging work on it
[21:02] <micahg> I use xfce, so not much will change on the desktop, but at least I'll get a lot of updated apps and can quite backporting stuff to lucid :)
[21:03] <micahg> *quit
[21:03] <chrisccoulson> ooh, my wallpaper just changed
[21:04] <chrisccoulson> presumably the new default ;)
[21:42] <gnomefreak> ok it is thunderbird that is causing the password incorrect errors
[21:43] <gnomefreak> its failing on 3or4 of 8
[21:43] <micahg> gnomefreak: BTW, well, I'm waiting for upstream before I can fix teh current FTBFS for TB
[21:43] <gnomefreak> micahg: ok didnt know there was a FTBFS
[21:44] <micahg> gnomefreak: yeah, there's a discussion of what the required NSPR version for the 1.9.2 branch is ATM
[21:45] <micahg> oh right, it builds on maverick :)
[21:45] <micahg> gnomefreak: you should be using thunderbird from the daily PPA if you're on maverick
[21:46] <gnomefreak> micahg: using it on Lucid atm i wont have a woprking maverick until nvidia gets fixed
[21:46] <gnomefreak> other wise thunderbird is usless to me
[21:46] <micahg> gnomefreak: ah, ok, so the latest version is FTBFS
[21:46] <fta> (nvidia is fine on maverick)
[21:46] <gnomefreak> no it isnt
[21:46] <fta> i'm using it
[21:47] <gnomefreak> nvidia-current is broke
[21:47] <micahg> fta: probably depends on which chipset, the newer ones probably are, but the older ones are broke I thought
[21:47] <fta> was broken for a day or two 2w ago, but fixed since
[21:47] <gnomefreak> see bug 616023
[21:47] <ubot2> Launchpad bug 616023 in nvidia-graphics-drivers (Ubuntu Maverick) (and 1 other project) "nVidia card : X won't start since 1.9 update, no screens found (affects: 73) (dups: 3) (heat: 400)" [High,Triaged] https://launchpad.net/bugs/616023
[21:47] <gnomefreak> https://lists.ubuntu.com/archives/ubuntu-devel-announce/2010-August/000744.html
[21:47] <gnomefreak> as well
[21:47] <gnomefreak> other bugs too but trying to get my emails atm
[21:48] <fta> with IgnoreABI=True, it's fine
[21:48] <gnomefreak> not here
[21:48] <gnomefreak> not for a few people that i have spoke to
[21:49] <fta> wfm on 3 boxes with different nvidia cards
[21:49] <gnomefreak> make that 5 of 8
[21:49] <gnomefreak> fails here on the 5200 and the 6200
[21:50] <micahg> fta: we just got back some PPA builders :)
[21:50] <micahg> 5 hrs now
[21:55] <gnomefreak> micahg: the FTBFS is in reguards to the symlink patch
[21:55] <gnomefreak> ?
[21:56] <micahg> gnomefreak: no, that's fixed for thunderbird, thunderbird-3.1 won't be updated anymore, but I won't delete it until thunderbird builds properly
[21:57] <gnomefreak> 3.1 wont be updated?
[21:57] <micahg> thunderbird is 3.1 ATM
[21:57] <micahg> thudnerbird-3.1 won't be updated
[21:57] <gnomefreak> micahg: the dailies wont get updated
[21:57] <micahg> gnomefreak: that's not what I said
[21:57] <micahg> the source thunderbird-3.1 will be deleted shortly
[21:57] <micahg> thunderbird is 3.1.x
[21:58] <gnomefreak> right
[21:58] <gnomefreak> you said 3.1 wont be updated anymore. you have 2 builds going stable and daily
[21:59] <micahg> gnomefreak: tb-stable isn't at 3.1 yet, I will try to update that soon
[21:59] <gnomefreak> oh its just your PPA than
[21:59] <micahg> I meant the thunderbird-3.1 source won't be updated in teh daily PPA
[21:59] <fta> micahg, btw, I deleted tb-3.1 from umd yesterday
[21:59] <micahg> fta: oh, ok then :)
[22:00] <fta> was tough because of stupid lp timouting on everything
[22:02] <gnomefreak> is 3.2 going to replace 3.1 umd?
[22:03] <micahg> gnomefreak: no, I'm going to create thunderbird-trunk (3.3a1pre ATM), and thunderbird-next (3.2a1pre)
[22:03] <gnomefreak> oh
[22:04] <micahg> gnomefreak: that way we don't have to renumber everything when there's a major version bump
[22:04] <micahg> like chromium with the channels
[22:04] <gnomefreak> they will still be daily time PPA though?
[22:04] <micahg> gnomefreak: yes
[22:04] <gnomefreak> ok that makes sence
[22:05] <micahg> thunderbird-next might not always exist though in the dailies if trunk is the current next
[22:07] <gnomefreak> can i rename .thunderbird-3.1 to .thunderbird and use it with your PPA thunderbird?
[22:07] <micahg> gnomefreak: you'll be prompted to import 3.1 profile when you launch thunderbird the first time
[22:08] <micahg> oh, I didn't push that to my PPA...
[22:08] <micahg> that woudl be in the dailies...
[22:08] <gnomefreak> oh
[22:09] <micahg> gnomefreak: I can push an update to my PPA if you want of the version from maverick, I can't upload to tb-stable w/out fixing the wrapper script for TB2 updates
[22:09] <gnomefreak> i thought i got thunderbird when i added it for enigmail
[22:09] <micahg> gnomefreak: yes, but I didn't have the wrapper script updated when I pushed to my PPA initially
[22:09] <gnomefreak> oh ok
[22:09] <micahg> gnomefreak: so, should I push an update?
[22:10] <gnomefreak> no need
[22:10] <gnomefreak> as ong as it works im good
[22:10] <gnomefreak> s/ong/long
[22:10] <micahg> gnomefreak: well, the current version in my PPA wont' import the 3.1 profile from .thunderbird-3.1, daily PPA and maverick version will
[22:11] <gnomefreak> it seems the version of thunderbird i have is from daily and the version of 3.1 i have is from dailies. on eis 3.1.2 and the other is 3.1.3
[22:12] <gnomefreak> thunderbird: Installed: 3.1.2+nobinonly-0ubuntu1~umd1~lucid
[22:12] <micahg> gnomefreak: yeah, I didn't think it would push 3.1.2
[22:12] <micahg> gnomefreak: so that version should prompt to import the 3.1 profile
[22:12] <gnomefreak> k
[22:13] <gnomefreak> lets try :)
[22:14] <gnomefreak> " do you want to import your mail and other settings from thunderbird 3.0, replacing your sttings from thunderbrid 3.1 beta"
[22:14] <gnomefreak> where did 3.0 come from
[22:14] <micahg> that's the default assumption now that 3.0 was the previous version
[22:15] <micahg> so you don't want to "import" you want to use the beta settings
[22:15] <gnomefreak> k
[22:16] <gnomefreak> and yet still it doesnt work
[22:16] <micahg> gnomefreak: which part?
[22:17] <gnomefreak> connecting
[22:17] <gnomefreak> al though only 3 failing
[22:18] <micahg> oh, ok, well that could indeed be a bug, but when 3.1.4pre builds you'll get a bunch of fixes, but idk about this one
[22:18] <gnomefreak> i can log in to web address just tb wont connect due to wrong password
[23:02] <micahg> chrisccoulson: is xdg-open the standard now for the default?
[23:02] <micahg> *default browseR?
[23:02] <micahg> I'm won't fixing bug 538912 and I want to suggest what needs to be done for other apps
[23:02] <ubot2> Launchpad bug 538912 in links2 (Ubuntu) (and 1 other project) "xlinks shouldn't replace Firefox as /etc/alternatives/x-www-browser (affects: 4) (heat: 28)" [Undecided,Confirmed] https://launchpad.net/bugs/538912
[23:32] <fta> oo opens firefox even if it's not my default browser :(
[23:32] <micahg> fta: I'd say that's a bug, the only thing that should do that is apport
[23:33] <chrisccoulson> micahg - xdg-open isn't a good way either
[23:33] <chrisccoulson> for GNOME apps, it's done via gvfs
[23:33] <micahg> chrisccoulson: so how does an app use the setting of deault rbowser on the desktop
[23:34] <micahg> ah
[23:34] <chrisccoulson> micahg - it happens automatically for apps that are opening URI's via glib calls
[23:34] <chrisccoulson> there's a gvfs module that gets the user configuration for URI handlers
[23:34] <micahg> chrisccoulson: sounds like we need a platform wide reliable way of doing this
[23:35] <micahg> which I guess is what the alternatives system and xdg-open were attempting
[23:35] <chrisccoulson> those both predate the current ways though, and they're pretty limited with what they do
[23:36] <chrisccoulson> update-alternatives doesn't allow any per-user config, and xdg-open is really only there for applications that don't actually want to integrate in to the DE
[23:36] <chrisccoulson> which i suspect is what OO is using, which would explain why it opens firefox for fta ;)
[23:37] <micahg> hmmm
[23:37] <micahg> well, what do we do for apps that shouldn't integrate into the desktop (do they really need code for KDE/GNOME/Xfce?)