[00:28] <Kamping_Kaiser> hi mozilla team :)
[00:33] <Kamping_Kaiser> would i be correct in assuming that (almost) all firefox-* files are replaced with DEBIANNAME?
[00:44]  * Kamping_Kaiser attempts to do another build
[00:45] <Kamping_Kaiser> i'm there, but i'm not :) *suspects hes doing it all wrong*
[00:57] <Kamping_Kaiser> having looked i'm none the wiser, so my question is: i'm trying to build a modified (branding wise) FF3 package, and the tarball getting used isfirefox-3.0_3.0.1+build1+nobinonly.orig.tar.gz downloaded from a mirrror, not one of my locally generated ones. where can i look to try and debug this?
[01:08] <wgrant> Kamping_Kaiser: Do you know of the existence of abrowser? It's an alternative set of branding for Firefox that was upload to Intrepid a couple of days ago.
[01:09] <Kamping_Kaiser> wgrant, yes, i've been watching the discussion. and assuming it builds on hardy it may be worth me looking at.
[09:51] <gnomefreak> bug 201655
[10:00] <gnomefreak> what is firefox-3.0-branding?
[10:03] <gnomefreak> the description needs work for -branding
[10:13]  * gnomefreak is learning there are alot of people doing very stupid things :(
[10:14] <Kamping_Kaiser> :/
[10:15] <gnomefreak> asac: this is bad
[10:15] <gnomefreak> asac: why does abrowser conflict with firefox? you should beable to have both
[10:16] <gnomefreak> Depends: firefox-3.0, abrowser-3.0-branding
[10:16] <gnomefreak> The following packages will be REMOVED: firefox firefox-3.0-branding firefox-launchpad-plugin
[10:17] <gnomefreak> hmmmmm why do we have both firefox and firefox-3.0
[10:17] <gnomefreak> but either way it shouldnt conflict
[10:18]  * gnomefreak is gonna regret trying to install 3D drivers
[11:04] <gnomefreak> there bug is filed
[11:04] <gnomefreak> ^^ for X
[11:07] <gnomefreak> can i still run firefox?
[11:09] <gnomefreak> i guess not
[11:13] <gnomefreak> ok so firefox-3.0 is needed for abrowser but firefox is removed. i cant run firefox-3.0 from terminal since there is no icon for it. firefox-3.0 loads abrowser. shouldnt we make it so we can remove firefox-3.0 if installing abrowser
[11:14] <gnomefreak> or atleast run both.
[17:29] <asac_11> hi
[17:29] <asac_11> +1:30h mozillateam meeting ;)
[18:39] <mdke> asac: still around?
[18:52] <asac> yes
[18:52] <asac> meeting in a few minutes ;)
[18:53] <Jazzva> asac, I didn't put it on the agenda, but I would like to see what we're gonna do about automatic update process for extensions...
[18:53] <mdke> asac: hi. I've been looking at trying to remove the startpage localisation script stuff from *ubuntu-docs and mozilla-firefox-locale-all. You may remember we discussed doing it last cycle on the basis that it's not used now because ubufox handles the startpage
[18:53] <asac> Jazzva: yeah. add it ;)
[18:53] <asac> mdke: what info do you need?
[18:54] <mdke> asac: if you are happy for that stuff to be removed, I'll remove it from the -docs packages, but it should also be removed from mozilla-firefox-locale-all too (I think that has to be done first)
[18:54] <asac> mdke: hmm
[18:54] <asac> mdke: thats firefox-2 right?
[18:54] <mdke> asac: I don't know, I have to confess I don't know anything about firefox
[18:54] <asac> yeah right
[18:55] <mdke> ok so that package isn't even used by firefox 3?
[18:55] <asac> mdke: i'll add an agenda item for "remove firefox 2" for the meeting
[18:55] <asac> if we remove it, the langpacks can go too
[18:55] <asac> mdke: no its not used by firefox
[18:55] <mdke> asac: fine. Can you let me know how it goes? :)
[18:55] <asac> 3
[18:55] <mdke> asac: I won't do anything with ubuntu-docs until that's sorted, because mozilla-firefox-locale-all depends on ubuntu-docs
[18:55] <asac> mdke: meeting starts in 5  minutes in -meeting
[18:56] <asac> mdke: we can put that agenda point on top if you have to go ;)
[18:56] <mdke> asac: ok, I'll try and follow
[18:56] <mdke> yes, if you could do it first, that would be great, I have to disappear shortly
[18:57] <asac> mdke: sure
[18:57] <mdke> thanks
[19:08] <fta2> hi
[19:08] <Volans> fta2: in #ubuntu-meeting ;)
[19:08] <fta2> sorry, i'm late for the meeting (traffic jam, 2h stuck)
[19:08] <Volans> only 8 minutes, if you want I can pastebin the log
[19:17] <mdke> asac: as a matter of interest, is something special required to remove the alternatives, like in the postinst, or can I just remove the script that provides them?
[19:17] <mdke> (no need to reply now if you're busy with the meeting)
[19:28] <asac> mdke: the removal code should be in the current ubunt-docs package that gets replaced
[19:28] <asac> we should ensure that that works properly for all cases
[19:28] <asac> but lets talk later about that
[20:30] <mdke> asac: ah, damn - I thought it would be simpler!
[20:31] <asac> mdke: so it doesnt work=
[20:31] <asac> ?
[20:31] <asac> mdke: at best let me check the scripts tomorrow. is that a bzr branch?
[20:32] <mdke> asac: no, I mean - I thought that it would be enough to remove the existing scripts; I now understand from your message above that we need to add some new scripts to remove the alternatives?
[20:32] <asac> mdke: that depends on whether the previous scripts were correct
[20:32] <asac> if they were they should remove the alternatives
[20:32] <asac> if not we need to hack/fix it in the new scripts
[20:33] <asac> so ... what we need to do is to try ... and see if any clutter is left over
[20:33] <fta> what the hell id https://edge.launchpad.net/~deadubuntuteam ?
[20:33] <fta> is
[20:33] <asac> if yes -> look into it ... otherwise all fine
[20:34] <mdke> asac: ah... well they were done by Ian Jackson, so I hope they'd be correct :) you can see them in the ubuntu-docs source
[20:34] <asac> mdke: ok. i'd say: just remove them from current scripts. then upload to PPA and lets test
[20:34] <asac> is that ok?
[20:35] <mdke> asac: sure. What I intend to do is this - http://doc.ubuntu.com/~mdke/ubuntu-docs.remove_startpage_translations_script.diff
[20:35] <mdke> asac: unless you can see anything already wrong from that patch :)
[20:38] <asac> urgh. thats bloody perl ;)
[20:38] <asac> fta: ^^
[20:39] <mdke> yes, it is
[20:39] <asac> mdke: looks good from what i can tell without looking at the complete sources
[20:41] <mdke> asac: okey. This will be my first use of PPA so lemme check how it works
[20:41] <fta> i can easily understand it but it looks more cryptic than mine ;)
[20:42] <asac> fta: q
[20:42] <asac> yeah. .. thats the code from ian jackson
[20:42] <asac> the author of dpkg and all the tools
[20:44] <fta> i already patched some of his scripts, i find his perl old stylish
[20:44] <asac> fta: really?
[20:45] <asac> what is "old style" perl?
[20:45] <fta> like perl4
[20:45] <mdke> that particular one is two years old, fwiw
[20:46] <fta> the code above is definitely perl 5 but with some old perl 4.0.36 style in it ;)
[20:46] <fta> perl 5 is ~15y old
[20:47] <mdke> ah
[20:47] <asac> fta: interesting
[20:50] <fta> some of my (old) code is public: http://www.cpan.org/modules/by-authors/id/FTASSIN/
[20:51]  * Volans back, finished now to read the log
[20:53] <fta> gasp, seems i haven't pushed anything to CPAN since 1999
[20:54] <asac> fta: did your patches to iwj's scripts get merged into the official branches=
[20:54] <fta> iwj ?
[20:54] <asac> fta: or is there something we should merge?
[20:54] <asac> ian jackson
[20:54] <asac> sorry
[20:55] <Volans> asac: I have just read the last part of the meeting and I'll be happy to help in some way for the automatization of the extentions
[20:55] <Volans> so feel free to ask
[20:56] <asac> Volans: cool
[20:57] <asac> Volans: feel free to work on whatever you want. we tried to split this up in multiple scripts
[20:57] <fta> i'm concerned by my last cairo update.. i introduced a regression with that lcdfilter stuff but i can't clearly identify what's wrong :(
[20:57] <asac> needed is download-amd-xpi <extensionname> <version>
[20:57] <fta> people are complaining
[20:57] <asac> fta: have you asked keybuk?
[20:59] <fta> asac, he said he'll have a lot, no answer since
[21:01] <fta> -lot+look, wtf, i can't type today
[21:02] <Volans> asac: what do you mean exactly with download-amd-xpi?
[21:02] <Volans> in particular "amd"
[21:07] <asac> Volans: sorry: amo
[21:07] <Volans> ah ok :)
[21:07] <asac> the script should download a particular version of an xpi from amo
[21:08] <Volans> the last one is not the right one always?
[21:08] <Volans> public, obviously
[21:08] <asac> Volans: no. we need a particular version i think
[21:08] <asac> Volans: we want to connect that on a higher level with fta's check extension script
[21:08] <asac> which basically gives you the latest version
[21:09] <asac> Volans: i think <extensionname> probably should be <amoid>
[21:09] <Volans> because if you remember some times ago I have found 2 different manners to automatically download file from AMO
[21:09] <Volans> one that after 3 automatic redirects take the last public versione of an extension
[21:10] <Volans> the second is to watch a watchable url that have all the public versions of an extension
[21:11] <asac> Volans: right. you think any of those approaches would allow us to download specific versions?
[21:11] <Volans> the first one no, it download always the latest public version in AMO
[21:12] <Volans> the second sure, is a public folder
[21:12] <Volans> we can download the version we want
[21:12] <Volans> fta: how do you find/choose the extension's version with your script?
[21:13] <fta> I parse the page as my goal is to find the last one
[21:13] <asac> another nice to have would be to commit all intermediate releases to bzr too
[21:13] <asac> but thats not important to start with
[21:14] <asac> and only gives a bit finer granularity - e.g. to track down regressions
[21:14] <Volans> sincerly I think is not necessary fta
[21:14] <asac> Volans: well. in that way we probably get the latest officially released version, dont we?
[21:15] <Volans> when I say public I was meaning "officially", those that have been public in AMO, not in sandbox
[21:15] <fta> my script was a quick hack i wrote when we first discussed about that topic here, i plan to rewrite it when i have time to add hooks to trigger actions
[21:16] <asac> fta: trigger actions?
[21:17] <fta> such as: if amo vers != ubuntu vers => start dl_from_amo_and_commit_in_upstream_branch
[21:17] <asac> hmm
[21:17] <asac> ok
[21:18] <fta> actions like that being external scripts with a stable api (list of arguments)
[21:18] <asac> ok. but thats probably far away right?
[21:18] <asac> so we can ignore that approach for what we are doing now?
[21:19] <fta> no, not really, it's a progressive approach
[21:19] <asac> or wouldnt that kind of trigger logic be implemented on a higher level?
[21:19] <asac> e.g on top of check-extensions
[21:19] <Volans> fta: why not to watch a simple folder instead of parsing the web page?
[21:20] <Volans> asac: probably after the download of the xpi you want some "report" from the script before continue with branches
[21:20] <fta> Volans, this is a detail in the implementation so it's isolated and could be changed easily.. sure not in the current shell script, but the idea is there
[21:21] <asac> Volans: yes. the script probably should echo the downloaded file and the version
[21:29] <sebner> asac: Alexander, why abrowser? O_o
[21:30] <asac> sebner: webbrowser didnt make it through the archive admins
[21:31] <sebner> asac: wouldn't it be easier to sync iceweasel or do we have technical problems then?
[21:31] <asac> no ... we maintain things anyway. so it doesnt add much extra work
[21:31] <asac> and iceweasel is a political problem
[21:31] <asac> also we dont have all patches against xulrunner that debian has
[21:32] <asac> so it would become difficult mostl ikely
[21:32] <fta> asac, ff3.1 a2 as it was or as my b1pre is today ?
[21:32] <sebner> asac: I see but in generel what is the difference between abrowser and iceweasel?
[21:32] <asac> fta: please the official tag
[21:33] <asac> at least thats QAed by upstream somehow
[21:33] <fta> asac, for the src sure but the packaging ? my b1pre has abrowser-3.1, not the a2 i had a few weeks ago
[21:33] <asac> fta: ah. the latest packaging :)
[21:34] <fta> ok
[21:34] <asac> not sure how to best to id
[21:34] <asac> it
[21:34] <asac> but most likely we need to create a .dev branch as the intrepid release branch
[21:34] <asac> and that version lowering could be done there=
[21:34] <asac> ?
[21:34] <asac> i guess you will find a way ;)
[21:35] <fta> sure
[21:37] <fta> does it matter if the 1.9.1 changelog contains the most recent UNRELEASED 1.9 entry ?
[21:41] <asac> hmm ... cant that be converted to intrepid?
[21:41] <asac> e.g. bump down -> push to release branch -> merge up -> bump version to 3.0.2bpre?
[21:43] <fta> what i mean it i currently have 2 "UNRELEASED": http://paste.ubuntu.com/46980/
[21:44] <fta> -it+is
[21:47] <IntuitiveNipple> RFC: Any ideas why xulrunner-1.9 c(onfigured with --enable-debug) would get a SIGILL (Illegal Instruction) when firefox is started from a terminal, but not when started via a Gnome launcher icon?
[21:48] <asac> IntuitiveNipple: you sure both use that build?
[21:48] <asac> how do you use it?
[21:49] <IntuitiveNipple> asac: what do you mean by 'both' ? Firefox and xulrunner?
[21:50] <asac> IntuitiveNipple: a) firefox started from launcher  b) terminal
[21:51] <IntuitiveNipple> asac: I'm working on that issue we talked of last week, and for some reason something in my xulrunner-1.9 build/install configuration seems to have changed because recent builds of xulrunner-1.9 cause this... if I drop the "--enable-debug" from configure, it doesn't SIGILL.
[21:51] <IntuitiveNipple> asac: Oh... I see what you mean... let me work it out :)
[21:52] <Jazzva> fta, afaik that is not a problem. But the release entry should have a proper release name.
[21:52] <IntuitiveNipple> well, the launcher is "firefox %U" and I've tried both "firefox" and "export NSPR_LOG_MODULES=HelperAppService:5; export NSPR_LOG_FILE=/home/tj/Desktop/xulrunner-1.9.log; /usr/lib/firefox-3.0.1/firefox" and get the same thing. Let me recheck this, maybe I've got myself mixed up :)
[21:54] <fta> Jazzva, i know it's not a technical problem, just best practice. here, i try to keep the branches as close as possible so this is a side effect
[21:54] <Jazzva> fta, I think I've seen that somewhere before... so, I suppose it should be ok. but not 100% sure :)
[21:55] <Jazzva> fta, check in #ubuntu-motu
[21:56] <fta> either i pretend the last 1.9 is released, or it's a lot of work to rebase everything on the last 1.9 really released
[21:57] <fta> or we close and push that 1.9 now ;) even better
[22:01] <IntuitiveNipple> asac: According to strace both end up doing execve("/usr/lib/firefox-3.0.1/firefox", ...
[22:02] <fta> does it SIGILL inside a debug code ?
[22:03] <IntuitiveNipple> asac: Also, both using "/usr/lib/xulrunner-1.9.0.1"
[22:03] <fta> can you get a trace ?
[22:04] <IntuitiveNipple> fta: I haven't looked too hard as yet, but it looks like XPCOM / javascript ... let me pastebin the stacktrace
[22:06] <IntuitiveNipple> Here we go: http://paste.ubuntu.com/46989/
[22:07] <IntuitiveNipple> It must be caused by something I've done doing this debugging, but I can't figure out what!
[22:07] <IntuitiveNipple> The only changes to the configure options I've got are "--disable-optimize \	--enable-debug \"
[22:19] <fta> can you run it inside gdb and show us 'bt' after the crash ?
[22:20] <fta> Could not write out perisistant registry!
[22:20] <fta> ###!!! ASSERTION: Default pref file not parsed successfully.: 'Error', file nsPrefService.cpp, line 723
[22:20] <fta> WARNING: Error parsing GRE default preferences. Is this an old-style embedding app?: file nsPrefService.cpp, line 791
[22:26] <IntuitiveNipple> Yes, I'm rebuilding it atm just-in-case it's some weird transient. I don't get why it starts fine if not from the xterminal
[22:30] <fta> asac, i branched 1.9.1.head at my a2 commit and cherry picked the improvements on top, leaving all the b1pre out
[22:32] <IntuitiveNipple> fta: There a lot of ASSERTION failures so is that one significant? I don't see anything obvious in the profile's prefs.js
[22:33] <fta> difficult to say from here without a proper backtrace of the crash
[22:33] <IntuitiveNipple> yeah... if it still happens after this build (with dbgsyms) it might be easier to work out
[22:34] <fta> asac, http://paste.ubuntu.com/46997/
[22:36] <Volans> fta: I have a proposal: add the AMO watchable dir in the debian/watch file on the *.ubuntu-dev branches and the use the standard packaging tool uscan and uupdate (just rename the downloaded .xpi file to .zip before running uupdate)
[22:37] <Volans> s/and the/and then/
[22:57] <IntuitiveNipple> fta asac: OK, figured it out. One of my lines of code was using PromiseFlatCString() without calling the .get() method in a LOG() statement :p
[22:59] <IntuitiveNipple> I guess if the console is detached it doesn't evaluate some part of that - can't think of any other rational explanation anyhow :)
[23:05] <pwnguin> i wish people wouldn't post unrelated crap to a bug just because it's being looked at by people or sabdfl
[23:25] <asac> IntuitiveNipple: haha
[23:25] <asac> ok
[23:25] <asac> pwnguin: which bug?
[23:34] <pwnguin> asac: the EULA bug hit slashdot
[23:49] <fta> bug 269656
[23:49] <fta> asac, i thought i blocked that a long time ago
[23:49] <fta> did you revert it ?
[23:50] <Jazzva> hmm... what's in the eula? and why do we need it now?
[23:52] <fta> strange, i blocked it in commit #262
[23:53] <fta> timestamp: Sat 2008-05-10 23:21:49 +0200
[23:53] <asac> pwnguin: EULA bug?
[23:53] <Jazzva> asac, look at bug 269656
[23:54] <Volans> also slashdot mention it ;)
[23:54] <Volans> fta: what do you think about my previous proposal?
[23:56] <pwnguin> asac: everyone else knows which bug I meant ;)
[23:56] <fta> Volans, i need to think about it, my brain is not working correctly today. at 1st glance, it could be ok but then the script can't dl without beeing in a branch and at the proper location
[23:57] <fta> pwnguin, i just happened to read http://ubuntuforums.org/showthread.php?t=919444 in my rss feeds
[23:59] <Volans> fta: yes, this is a limitation, but if you plan to have a long-time maintenance of extensions probably you will have a place whith all the *.ubuntu-dev branches and a master script can cycle through every branch, searching for a new upstream version and made all the stuff explained in the LargeScaleMaintenance
[23:59] <Volans> another way is to make a script that only check the latest version in the watchable dir and download only the extensions that have a new version