[00:10] <Jazzva> asac, lp:~jazzva/firefox-extensions/mozilla-ctxextensions.ubuntu are ready for merge with ubuntu-dev's branch. Rev 15 is the one. If it's still not showing up, wait a minute, it will :)
[00:11] <Jazzva> asac, and I'll start using "open tree for development", UNRELEASED as dist and similar in the next cycle of updates :)
[00:57] <Jazzva> asac, lp:~jazzva/firefox-extensions/mozilla-livehttpheaders.ubuntu are ready for merge. Rev 17 is the one...
[00:57] <Jazzva> s/are/is/
[01:02] <asac> ok off. have a dentist appointment tomorrow morning and dont want to be completely wasted there ;)
[01:02] <Jazzva> uh... dentist
[01:02] <asac> yeah
[01:02] <Jazzva> umm... good luck :)
[01:02] <asac> hopefully can help me without much pain ;)
[01:02] <asac> ill try to do those two first thing in the morning
[01:02] <Jazzva> take your time
[01:02] <asac> well. things should go up ;)
[01:02] <Jazzva> after dentist is fine too :)
[01:02] <asac> hehe yeah
[01:03] <asac> not before for sure
[01:03] <asac> quite early
[01:03] <asac> cu
[01:03] <Jazzva> cu
[01:03] <Nafallo> asac: do we have vimperator packaged? ;-)
[08:02] <asac> Nafallo: vimperator?
[09:01] <asac> Jazzva: did we ever file a bug for the webkit MIR?
[09:04] <asac> bug 250738
[09:21] <XioNoX> hi
[09:22] <asac> hi XioNoX
[09:24] <XioNoX> Back at work
[09:25] <XioNoX> I've miss my flight yesterday, so it is why i wass not connected
[09:29] <asac> XioNoX: oh. so you have to fly in every week?
[09:30] <XioNoX> no, i've just left 1 week
[09:30] <XioNoX> now i'm up to work 5 weeks
[09:31] <asac> how did you manage to miss your flight? ;)
[09:36] <XioNoX> I was working at a music festival, from the 16 to the 20 (helping the computer team), and I've left earlier (midnight) the sunday (after seeing the Hive) to go back home (150km). And my flight was at 6 am. I've decided to sleep 2h at home, but i was so tired that I haven't hear my alarm clock.
[09:37] <XioNoX> but the plane company change my flight for free, so I've arrived yesterday afternoon
[09:41] <asac> XioNoX: argh. sorry for that. i feel with you
[09:41] <asac> XioNoX: (sorry for missing flight) ... great to hear that they changed for free
[09:41] <XioNoX> :D
[09:42] <XioNoX> it was this festival : http://www.vieillescharrues.asso.fr/festival/programmation_2008.php
[09:43] <asac> motorhead still exists ;) ... fun.
[09:45] <XioNoX> it was cool
[09:45] <Nafallo> asac: http://vimperator.mozdev.org/
[09:45] <Nafallo> :-)
[09:45] <asac> lol
[09:46] <asac> Nafallo: reads like good crack ;)
[09:50] <XioNoX> asac, i've read all the xpcom tutorial, and i don't realy know how we use it (and why)
[09:54] <asac> XioNoX: what is unclear?
[09:55] <XioNoX> what does an XPCOM component?
[09:56] <XioNoX> what it is used for ?
[09:58] <asac> XioNoX: thats a tough question ;)
[09:58] <XioNoX> i know
[09:59] <XioNoX> but maybe just an exemple will be enough
[09:59] <asac> XioNoX: ok. components implement interfaces that define a service in a cross-language-fashion ;)
[10:00] <XioNoX> implement interfaces ?
[10:00] <asac> XioNoX: do you know OO programming?
[10:00] <asac> Object-Oriented
[10:00] <XioNoX> a little bit
[10:00] <XioNoX> with C++
[10:00] <asac> then you should know what an interface is ;)
[10:01] <asac> ok in C++ its similar to the class definition
[10:01] <asac> e.g. just the contract, not the implementation
[10:01] <XioNoX> ok
[10:01] <asac> class declaration is the right word, sorry
[10:01] <asac> so now instead of writing
[10:01] <asac> class A {
[10:01] <asac>  public:
[10:01] <asac>   int x;
[10:01] <asac>   int func();
[10:01] <asac> };
[10:01] <asac> you have a syntax that is language independent
[10:02] <asac> namely IDL
[10:02] <asac> Interface Definition Language
[10:02] <asac> you can find plenty of .idl files in your mozilla  source tree
[10:03] <asac> so what xpcom provides is that you can call and implement such classes/objects in a across-language boundaries
[10:04] <XioNoX> ok
[10:04] <asac> e.g. you can implement a Car class in javascript and call it from C++ or vv
[10:05] <asac> now there are two use cases of xpcom interface implementations:
[10:06] <asac>  1. service - only one instance exists per process (like a singleton)
[10:06] <asac>  1. instances - you create new instances of a certain interface implementation as you like
[10:06] <asac> 2. ;)
[10:07] <asac> does that help you already?
[10:07] <XioNoX> yep
[10:08] <asac> XioNoX: so one thing you can do with interfaces is that you can have multiple implementations of the same
[10:08] <XioNoX> it is more clear now
[10:08] <asac> XioNoX: which comes handy in our case as we want to make something extensible in a pluggable fashion
[10:09] <XioNoX> ok
[10:09] <XioNoX> and I'm reading the rdf stuff
[10:10] <asac> ok
[10:10] <XioNoX> the dor is bigger but it is easier to understand
[10:10] <asac> dor?
[10:11] <XioNoX> sorry, doc
[10:47] <asac> Nafallo: https://www.mozdev.org/bugs/show_bug.cgi?id=19598
[10:47] <asac> Nafallo: could you add that extension to the Firefox3Extensions page in wiki
[10:47] <asac> so it doesnt get lost?
[10:47] <Nafallo> sure
[10:47] <asac> http://wiki.ubuntu.com/MozillaTeam/Firefox3Extensions
[10:48] <asac> Nafallo: i think it should go into the "Missing Detail" table ... at best with the bug link above somehow attached so we know where discussion is going on
[10:48] <asac> maybe put the bug link in the "extension developer contact" column ;)
[11:00] <Nafallo> added :-)
[11:08] <armin76> buuuuuuuuuumb!
[11:08]  * armin76 files 30 bugs for bumbing
[11:13] <armin76> lolz
[11:13] <armin76> asac: you broke firefox on ia64!
[11:13] <armin76> ah
[11:13] <armin76> its the dependencies stuff
[11:14] <armin76> still, bets that it segfaults on ppc and sparc? :D
[11:15] <asac> on my way
[11:19] <asac> armin76: BUMMMMMBED!
[11:19] <asac> deep impact
[11:19] <armin76> lies
[11:19] <asac> on hardy-updates
[11:19] <asac> what a breathtaking moment
[11:19] <asac> armin76:
[11:19] <asac> 12:18 < asac> so ffox and xul sources+ bits can go
[11:19] <asac> 12:18 < pitti> asac: awesome; copying
[11:21] <armin76> bumbing!
[11:58] <Jazzva> asac, thanks for opening the bug for webkit. I asked you a few days ago should we open a bug now, or when we get the review. You probably missed it, and the I forgot to re-ask
[12:00] <asac> Jazzva: no problem
[12:01] <asac> https://wiki.ubuntu.com/MainInclusionProcess
[12:01] <asac> thats the process
[12:01] <Jazzva> wow... sage is also updated. I thought they stopped its development. Guess I'll update it now :)
[12:01] <Jazzva> asac, thanks :)
[12:02] <asac> good
[12:04] <asac> Jazzva: when you done with that ping me so i can upload all three ;)
[12:04]  * asac going lunch ;)
[12:04] <Jazzva> k :)
[12:04] <Jazzva> have fun
[12:04] <Jazzva> it's gonna be four of them. foxyproxy needs update, too :)
[12:09] <asac> thats
[12:25] <armin76> asac: omggggggggg!
[12:25] <armin76> looks like sparc intrepid doesn't sigbus! :D
[12:43] <armin76> uh, wtf
[12:43] <armin76> why doesn't ports.ubuntu.com have hardy-updates and proposed on Release?
[12:43] <armin76> asac: fix!
[12:44] <armin76> bah, stupid!
[12:55] <armin76> uh...nah, it gives bus error anyway
[12:55] <armin76> takes a lot more, though
[12:55] <armin76> on hardy it just gives bus error at the start
[12:56] <asac> armin76: ok lets be focussed
[12:56] <asac> what patches shall i apply
[12:58] <armin76> no idea :P
[12:58] <armin76> i don't apply any patch to fix the sigbus
[13:00] <Jazzva> asac, can mozilla-devscripts use patching system?
[13:01] <Jazzva> *package using mozilla-devscripts
[13:01] <asac> Jazzva: it could, but wouldnt make much sense
[13:01] <asac> except when we cherry-pick to stable release branches
[13:01] <asac> but for that we can also merge individual commits imo
[13:01] <Jazzva> so, to change the source directly?
[13:01] <Jazzva> sorry... I meant can package using mozilla-devscripts use patching system?
[13:01] <asac> Jazzva: mozilla-devscripts is a native package . there is no orig.tar.gz ... so you develop _inside_ the package
[13:02] <asac> Jazzva: ah
[13:02] <asac> havent tried ;)
[13:02] <asac> but why not
[13:02] <Jazzva> can I just use quilt and include in the rules
[13:02] <Jazzva> ok, i'll try
[13:02] <asac> as long sa the .xpi is produced by build command
[13:02] <asac> maybe we need to tweak a hook or something
[13:03] <asac> Jazzva: Jazzva but in general the idea is t change _in-source_
[13:03] <asac> in the .ubuntu branch
[13:03] <Jazzva> aha... ok
[13:03] <asac> i dont expect lots of patches to accumulate in extensions
[13:03] <asac> usually just a maxVersion bump
[13:03] <asac> and maybe a quick fix or cherry-pick for some stable updates
[13:04] <Jazzva> well, sage package has some patch that should fix two CVEs. Now I'm wondering if that still applies... The code didn't change, so that's why I wonder
[13:04] <asac> armin76: so is it a sigbus in libc?
[13:05] <asac> Jazzva: how intrusive are those changes?
[13:05] <asac> can you post them?
[13:06] <asac> if they are not packaging related we should push it to upstream i guess
[13:06] <Jazzva> not too big
[13:06] <Jazzva> http://paste.ubuntu.com/29282/
[13:06] <Jazzva> but look reasonable
[13:07] <Jazzva> looking at the upstream bts
[13:08] <XioNoX> asac, who have decided to keep the old skin on firefox 3 whereas the beautiful new one ?
[13:14] <Jazzva> asac, it's marked as fixed here
[13:15] <Jazzva> https://www.mozdev.org/bugs/show_bug.cgi?id=15101
[13:22] <asac> XioNoX: he?
[13:22] <asac> XioNoX: linux uses gnomestripe
[13:22] <asac> er have that as default
[13:23] <XioNoX> why they don't have the big back button ?
[13:23] <asac> XioNoX: thats windows
[13:23] <XioNoX> and mac
[13:23] <XioNoX> it is the "default" firefox theme
[13:23] <XioNoX> no ?
[13:23] <asac> most likely moz devs didnt care _enough_
[13:24] <asac> for linux
[13:24] <Jazzva> asac, I'll test sage without the patch on some security tests which are reported in bug report.
[13:24] <asac> to do that or thought that it wouldnt fit nicely into gnome desktop
[13:24] <asac> Jazzva: the bug is fixed
[13:24] <asac> according to bug tracker ;)
[13:25] <asac> yes pleaes test then
[13:25] <Jazzva> asac, umm... that's what I saw :)
[13:25] <asac> maybe we can drop them ;)
[13:25] <Jazzva> asac, but I would like to
[13:27] <XioNoX> asac, for exemple, this theme will fit perfectly in gnome : https://addons.mozilla.org/fr/firefox/addon/7379
[13:27] <XioNoX> and he have the firefox 3 looks
[13:27] <Jazzva> XioNoX, I think it's because FF will use icons from current gnome theme
[13:28] <Jazzva> s/will use/uses/
[13:28] <XioNoX> and who manage that ?
[13:28] <Jazzva> umm... what do you mean?
[13:29] <Jazzva> FF picks up the icons from your current gnome theme and uses them. If they used only one icons for back and forward, it would fit well with the rest of the gnome desktop.
[13:29] <XioNoX> because i've heared a lot of people complaining about the firefox 3 theme on ubuntu
[13:30] <XioNoX> and why we don't install by default a firefox skin
[13:30] <XioNoX> ?
[13:30] <Jazzva> As far as I can see, if they wanted to use big back/small fwd button, they would have to hardcode the icons. That way, it would fit with the rest...
[13:31] <Jazzva> XioNoX, we do have default FF3 theme... It's the one we use. It's just that it's a bit different than from win/mac skin. It's adapting to your current theme.
[13:31] <asac> XioNoX: you are the first i hear complaining ...everone else i talked to cheered ;)
[13:31] <XioNoX> but we can install a theme like the one i've show you easily through amo
[13:32] <asac> XioNoX: we can certainly package skins as xpi in ubuntu, but that wont become the default for sure
[13:32] <XioNoX> another exemple here : http://brainstorm.ubuntu.com/idea/5754/
[13:32] <Jazzva> XioNoX, it's true. But that would break the uniformity of the look of the desktop.
[13:32] <asac> we are happy that we are finally integrated with gnome theme
[13:32] <Jazzva> +1 on that :)
[13:33] <XioNoX> ok
[13:33] <asac> "Linux has the best theme for Firefox 3.
[13:33] <asac> Just look at the Windows theme for Firefox 3 it looks absolutely horrible. "
[13:34] <asac> "Proto is hated by Mac users, because of the roundness and the big back-forward button, they like more this: http://www.takebacktheweb.org/ .
[13:34] <asac> Themes for Windows look completely amateur. Both. The colors, the shapes... Hahaha... "
[13:34] <Jazzva> XioNoX, that's the way firefox developers designed it. Windows and Mac have already built themes. But, afaik, windows' and mac's desktop environment are not that easily skinable.
[13:34] <asac> i think this is something you cannot find a solution where everyone agrees
[13:34] <Jazzva> XioNoX, that's why the fixed theme in win and mac won't break the look of the rest of the desktop
[13:34] <asac> as a matter of fact the default gnome theme isnt that bad
[13:35] <Jazzva> On the other hand, gnome is designed to be easily skinable. If you would use fixed theme for Fx, it wouldn't fit well with the rest of the desktop. I suppose that's the reasoning of FF developers.
[13:36] <XioNoX> ok
[13:36] <asac> Jazzva: yeah. but the size of the back button could probably not be tuned
[13:36] <asac> thats a design devision i guess
[13:36] <asac> decision
[13:36] <XioNoX> that explaination it enough for me
[13:36] <Jazzva> asac, that too... If they wanted to use big button, I suppose all gnome themes should add one big button...
[13:36] <Jazzva> XioNoX, I'm glad we could help :)
[13:36] <asac> anyway, we can package themes up if there is really demand
[13:36] <asac> not sure about that though
[13:38] <XioNoX> ok
[13:41] <XioNoX> I didn't know that the firefox theme was linked to the gnome theme
[13:43] <armin76> asac: i have no clue
[13:44] <armin76> asac: as i said, it takes more time to sigbus than in previous versions
[13:44] <armin76> i don't know if thats due to firefox or libc
[13:44] <armin76> need to test on ppc
[14:02] <Jazzva> asac, this is the feed that has the tests
[14:02] <Jazzva> http://www.gnucitizen.org/blog/cross-context-scripting-with-sage/feed.xml
[14:03] <Jazzva> I have tested it. It does interpret it as script, as no text is shown, but it doesn't give me the alert window...
[14:04] <Jazzva> I'll test with the patch now
[14:04] <Jazzva> if it shows that script as text, I'll use the patch
[14:04] <asac>  Jazzva try to alert in the exception case for the unix paths
[14:05] <asac> e.g. catch (e) {} => catch (e) { alert('here goes the rdv'); }
[14:05] <Jazzva> mhm... ok
[14:05] <asac> at best the exception
[14:05] <asac> whats the CVE id?
[14:05] <asac> (for that test?)
[14:06] <Jazzva> CVE-2006-4711 and -4712
[14:07] <Jazzva> test is located at mozdev bug
[14:07] <jt1> asac: hey there!
[14:07] <Jazzva> mozdev bug 15101
[14:07] <Jazzva> hmm
[14:07] <Jazzva> https://www.mozdev.org/bugs/show_bug.cgi?id=15101
[14:09] <asac> ubottu: CVE-2006-4711
[14:09] <asac> hi jt1
[14:10] <jtv> ha, that's better
[14:10] <asac> jtv: you should start a _real_ irc client ;)
[14:10] <jtv> asac: still haven't finished our discussion of the file_references issue!
[14:10] <asac> we havent?
[14:10] <asac> ;)
[14:10] <jtv> asac: I used to, and people told me to use this one instead.  :-)
[14:10] <asac> not that i thought otherwise :-D
[14:11] <asac> Jazzva: i think the feed.xml is to show CVE-2006-4712
[14:12] <XioNoX> asac, if you are not busy, can we talk about what do you want that I do ? because xul templates tuto is very boring, it would be cool to know on what i'll apply it, and using what already exist to learn.
[14:12] <asac> for CVE-2006-4711 executing javascript without cross context appears to be enough
[14:12] <XioNoX> same for xpcom
[14:12] <asac> XioNoX: sure
[14:13] <asac> XioNoX: lets start with a simple modification of the "Get Addons" tab in addons dialog
[14:13] <asac> so you get used to that huge code ;)
[14:13] <XioNoX> ok
[14:13] <jtv> asac: anyway, the question was this: if we start using proper XPI paths for file references in new XPI imports (as opposed to the pseudo-XPI paths we have now), would that be a big problem for you?
[14:14] <asac> XioNoX: do you have a hg trunk tree?
[14:14] <asac> XioNoX: do you have a place where you can push your "topic" branches?
[14:14] <XioNoX> nop
[14:14] <Jazzva> asac, tested... not getting any alerts :/
[14:14] <XioNoX> not yet
[14:14] <asac> XioNoX: ok so for now we need patches then i guess ;)
[14:14] <asac> (to show me)
[14:14] <XioNoX> ?
[14:14] <asac> Jazzva: ok. so the script is not executed at all?
[14:15] <asac> XioNoX: well ... since you cannot publish your private hg branches you will be working on you need to show me patches when you want feedback on your changes
[14:15] <Jazzva> asac, it looks like. But I'm still confused why it hides the script code. If it's not executed, it should be visible, since it's marked as text
[14:16] <asac> XioNoX: ok. you need a hg clone that you can build
[14:16] <asac> XioNoX: doy ou have that already?
[14:16] <XioNoX> nop
[14:16] <XioNoX> i've nothing yet
[14:17] <asac> XioNoX: ok, get such a tree then ;)
[14:17] <asac> http://developer.mozilla.org/en/docs/Mercurial
[14:17] <asac> and make it build
[14:17] <XioNoX> i've already used mercurial
[14:17] <XioNoX> but not for firefox
[14:17] <asac> XioNoX: yes, but you have to build the tree ;)
[14:17] <XioNoX> i need to get all the sources of firefox ?
[14:17] <asac> otherwise you cannot test your changes
[14:17] <asac> XioNoX: yes
[14:18] <XioNoX> and what is the url of the trunk ?
[14:19] <asac> XioNoX: so first thing is to add a new tab like the "Get-Addons Tab" to the addons dialo
[14:19] <XioNoX> ok
[14:19] <asac> http://developer.mozilla.org/en/docs/Mozilla_Source_Code_(Mercurial)
[14:20] <XioNoX> add a tab like the extention, theme, laguage, etc... ?
[14:20] <asac> the code we will be mostly working in is toolkit/mozapps/extensions/
[14:21] <asac> XioNoX: yes. thats the idea. dont spend too much time on detail. we have to think how it should actually look like and probably need a few prototypes later :)
[14:21] <asac> XioNoX: call it Plugin-Wizard ;)
[14:21] <asac> or whatever
[14:22] <asac> and then we will try to move the plugin finder service there ;)
[14:22] <XioNoX> http://hg.mozilla.org/ ?
[14:22] <XioNoX> which one should I get ?
[14:22] <asac> read the urls i gave you :)
[14:23] <XioNoX> mozilla-central ?
[14:23] <asac> yes
[14:23] <asac> its all on the page ;) ... http://developer.mozilla.org/en/docs/Mozilla_Source_Code_(Mercurial)
[14:23] <XioNoX> The integration repository for Mozilla 2 development is mozilla-central
[14:23] <XioNoX> ha
[14:23] <XioNoX> Mozilla 2
[14:23] <XioNoX> not firefox 2
[14:24] <asac> mozilla 2 ... but current focus should be 1.9.1
[14:27] <XioNoX> done
[14:28] <XioNoX> 34564 files updated
[14:28] <XioNoX> 260,0 Mio
[14:29] <XioNoX> :~/Stage/Plugin-Wizard/src/toolkit/mozapps/extensions$ ls
[14:29] <XioNoX> content  jar.mn  Makefile.in  public  service  src  test
[14:29] <XioNoX> there are a lot of files
[14:29] <asac> XioNoX: do a build first
[14:29] <asac> want to be sure you can test what you code ;)
[14:30] <XioNoX> run allmakefiles.sh ?
[14:30] <asac> its on that website ;)
[14:31] <XioNoX> i try to go too fast
[14:31] <asac> most likely
[14:34] <XioNoX> /bin/sh: autoconf-2.13: not found
[14:35] <XioNoX> but autoconf2.13 exist
[14:35] <asac> most likely AUTOCONF is wrong then
[14:35] <asac> in .mozconfig
[14:36] <XioNoX> okay it work
[14:36] <XioNoX> I have all the -dev package to install
[14:36] <Jazzva> asac, applying the patch produces the same result
[14:37] <Jazzva> guess we can drop it then :/
[14:41] <XioNoX> asac, configure: error: Could not compile basic X program.
[14:41] <Jazzva> now there's another problem... sage and sage-too replace each-other in Tools menu... they both use the same shortcut. Maybe using Conflicts field in debian/control?
[14:41] <asac> XioNoX: you lack build dependencies
[14:41] <asac> install the ones we use for xulrunner-1.9 and firefox-3.0 package
[14:42] <asac> Jazzva: are sage and sage-too independent projects?
[14:42] <Jazzva> sage-too is a fork of sage
[14:42] <asac> but both are active?
[14:42] <Jazzva> yes
[14:42] <Jazzva> I thought sage is inactive until yesterday...
[14:43] <Jazzva> but then I found out it has update dated june 23rd on amo
[14:43] <asac> why cant we fix the overlay?
[14:43] <asac> so they dont conflict?
[14:43] <Jazzva> hmm... good :)
[14:43] <Jazzva> I'll push sage unchanged, since sage-too is a fork
[14:43] <Jazzva> I'll also see with the upstream to fix this, if they can
[14:43] <asac> ok. do we have sage-too alredy in archive?
[14:44] <Jazzva> not atm... waiting to see about copyright issues
[14:44] <Jazzva> sage also misses LICENSE file, but copyright mentiones it's licensed under trilicense, so I suppose it was sorted out before. Anyway, I sent an e-mail to the upstream to see if they can add license...
[14:44] <XioNoX> it is running
[14:45] <Jazzva> s/also misses/is also missing/
[14:45] <asac> XioNoX: good
[14:45] <asac> XioNoX: so in public/ there are the .idl files
[14:45] <asac> look at them ;)
[14:46] <asac> nsIAddonRepository.idl
[14:46] <asac> defines abstract contract to implement backend that gets result from addons databases (like amo)
[14:46] <asac> we could use that to search for extensions available in ubuntu
[14:47] <asac> but thats not the start here ;)
[14:47] <asac> the xul pieces are in content/
[14:47] <Jazzva> asac, mozilla-ctxextensions, foxyproxy, mozilla-livehttpheaders and firefox-sage are ready for upload
[14:47] <Jazzva> do you need branch links?
[14:47] <XioNoX> modules/libpr0n
[14:47] <XioNoX> o_O
[14:48] <asac> XioNoX: yeah. you dont want to touch that unless you really want to get dirty
[14:48] <asac> lol
[14:48] <Jazzva> haha :)
[14:49] <asac> XioNoX: so the idea is to add a nsIPluginRepository.idl and use that to implement the plugin-by-mime-type-search that we want to put into the new tab
[14:50] <XioNoX> ok
[14:51] <Jazzva> asac, sorry... I forgot to add "New upstream release" to changelog for firefox-sage. I pushed new revision
[15:04] <XioNoX> asac, will I have to build firefox at each modification ?
[15:13] <asac> XioNoX: yes and no
[15:13] <asac> usually just the subdirectory needs to be rebuild
[15:13] <XioNoX> ok
[15:13] <XioNoX> and i don't really know how to start
[15:14] <asac> XioNoX: yeah. you probably should try to match what you see with the code you read to get a basic idea
[15:14] <asac> and then look more in detail
[15:14] <XioNoX> ok
[15:49] <Jazzva> asac, the problem might also be that they're using sage instead of sage-too name in chrome.manifest
[15:50] <asac> thats not so great ;)
[15:50] <Jazzva> yeah...
[15:50] <asac> we can change that here, but should tell upstream about thta
[15:50] <Jazzva> it needs a lot of changes
[15:50] <Jazzva> well... there is one neat (maybe not so clean way)
[15:50] <Jazzva> s/sage/sageToo/
[15:51] <Jazzva> s/Sage/SageToo/
[15:51] <Jazzva> :)
[15:53] <Jazzva> hmm... and both sage and sage-too have minVersion set to 3.0b1
[15:53] <Jazzva> asac, please don't upload firefox-sage for now. I would like to see if it's compat with FF2
[15:58] <XioNoX> asac, i don't know what i have to put in the idl file
[15:58] <XioNoX> i've put the default lines, but it is all
[16:11] <asac> XioNoX: thats a good start
[16:11] <asac> XioNoX: you can now go to the xul part ;)
[16:12] <asac> and add a new item to the addons dialog
[16:12] <XioNoX> where is the xul ? in the .js files ?
[16:12] <asac> in the .xul, js and .xml files
[16:12] <asac> e.g. in the content/ folder
[16:12] <XioNoX> ok
[16:12] <XioNoX> i haven't see the content folder
[16:16]  * asac goes stocking up food
[16:26] <Jazzva> lol... now it's called SageToo-Too :)... forgot to fix SageToo-Too back to Sage-Too :)
[16:28] <Jazzva> yay, Sage and Sage-Too are not clashing anymore :)
[16:40] <XioNoX> asac, the PluginWizard will replace the exixting plugin tab ?
[16:40] <XioNoX> if not, how will we call it ?
[16:47] <asac> no
[16:47] <asac> not for now
[16:48] <asac> "get plugins"?
[16:48] <XioNoX> okay
[16:49] <XioNoX> <radio id="get-plugins-view" label="&get-plugins.label;" oncommand="showView('get-plugins');" persist="last-selected"/>
[16:50] <XioNoX> I don't get this part in the .js file :
[16:51] <XioNoX> in the case "get-plugins":
[16:51] <XioNoX>       prefURL = PREF_EXTENSIONS_GETMOREPLUGINSURL;
[16:51] <XioNoX>       types = [ [ ["plugin", "true", null] ] ];
[16:51] <XioNoX>       showCheckUpdatesAll = false;
[16:51] <XioNoX> and int the "normal" plugin view, there are no link to the AMO
[16:52] <Jazzva> asac, hmm... looks like sage is not working with ff-2
[16:53] <asac> XioNoX: you can not map that one-by-one
[16:54] <asac> what we want is to have the ability to search by mime-type for now
[16:54] <asac> and display a list of results with the install ... button
[16:54] <asac> (just like that plugin finder result)
[16:54] <Jazzva> asac, ok, firefox-sage is also ready.
[16:54] <XioNoX> and search where ?
[16:54] <asac> advanced searches like  by name or description are not yet useful
[16:54] <asac> XioNoX: in a search field like in get addons
[16:55] <XioNoX> ok
[16:56] <XioNoX> okay
[17:10] <XioNoX> how can I test that I've done ?
[17:10] <asac> start the firefox you built ;) and look in addons dialog
[17:13] <XioNoX> how ?
[17:14] <XioNoX> i've just done  make -f client.mk build
[17:14] <Jazzva> asac, XioNoX: are you implementing plugin finder directly in ff? cool :D
[17:16] <XioNoX> It is the goal of my intership, but i have to learn everything
[17:22] <Jazzva> XioNoX, Mozilla internship? or here in ubuntu? :)
[17:23] <XioNoX> Mozilla Europe
[17:23] <XioNoX> for 6 weeks
[17:23] <Jazzva> Cool :)
[17:23] <XioNoX> yep
[17:23] <XioNoX> Jazzva, what do you do you ?
[17:24] <Jazzva> I'm a student. that's mostly what I do :)]
[17:24] <XioNoX> where ?
[17:24] <Jazzva> And I volunteer at Ubuntu, because I like it and I can learn new things :)
[17:25] <Jazzva> School of electrical engineering, University of Belgrade... That's in Serbia
[17:25] <XioNoX> ha ok
[17:26] <XioNoX> nice
[17:26] <Jazzva> It's ok :)
[17:26] <XioNoX> what do you do on ubuntu ?
[17:27] <Jazzva> Mostly on extensions maintenance at the moment. Maintainer of one package, beside this. A bit of bug triaging... And try to find if I can fix something broken :)
[17:27] <XioNoX> ok
[17:29] <Nafallo> asac: I have another one for you :-D
[17:29] <XioNoX> do you know how to compil firefox ?
[17:29] <XioNoX> :D
[17:29] <asac> Nafallo: if its not complete add it to the same table ;)
[17:30] <Nafallo> http://www.asnumber.networx.ch/
[17:30] <asac> Nafallo: you could help by bugging upstream about license file in top-level .xpi directory ;)
[17:30] <Nafallo> :-P
[17:30] <asac> that turned out to be the most cumbersome step when looking at packaging extensions
[17:30] <Jazzva> XioNoX, no ;). I haven't tried that... I'm scared my computer would die :)
[17:30] <Nafallo> haven't even checked out the code for any of those ;-)
[17:30] <XioNoX> asac ?
[17:31] <asac> Nafallo: you dont need to. as long as it works, and it is licensed under a free license we can probably package it ;)
[17:31] <Jazzva> XioNoX, did you ask that me or asac?
[17:31] <asac> XioNoX: it should be like on the website
[17:31] <Nafallo> asac: kewl. I'll have a look this evening unless someone goes to the pub :-P
[17:31] <asac> haha
[17:31] <XioNoX> you because asac was'nt responding but now that he is back
[17:32] <asac> XioNoX: dont know how to help you ;)
[17:33] <asac> dont even knew that the build didnt succeed
[17:33] <asac> for you
[17:33] <XioNoX> he have succeed, but no bin file
[17:34] <asac> XioNoX: how do you know?
[17:34] <asac> where did you look?
[17:34] <XioNoX> he have succeed because there were no error message :)
[17:34] <XioNoX> and I've look in my src folder
[17:34] <asac> XioNoX: yeah. but where did you look for the binaries
[17:35] <asac> your soure folder?
[17:35] <asac> firefox is in the dist/bin directory
[17:35] <asac> you have to do a complete firefox build ... which probably takes a while
[17:36] <asac> then there is a dist/bin directory in the top-level tree
[17:36] <XioNoX> it was not write in the wiki page :o
[17:36] <XioNoX> i've found it :D
[17:36] <asac> XioNoX: well. that is even more basic ;)
[17:36] <asac> the document just taught the basics for the new mercurial biult
[17:37] <asac> i actually assumed that you knew how to built old mozillas
[17:37] <XioNoX> nop
[17:37] <asac> but well  ... now you know
[17:37] <XioNoX> I've never worked on mozilla
[17:51] <XioNoX> the searchbox doesn't appear, even in the "normal"  get exentions
[17:54] <asac> XioNoX: "doesnt't appear" anymore?
[17:54] <asac> or never
[17:55] <XioNoX> i haven't test withour any modifications
[17:55] <XioNoX> but I haven't touch the get extention part
[17:56] <asac> maybe its hidden because amo doesnt support 3.0.1 yet?
[17:56] <asac> in applicaiton.ini you can probably set 3.0 as version
[17:56] <XioNoX> i don't know
[17:56] <asac> above i ment 3.1.0
[17:56] <asac> fta: do you see something similar in 3.1.0 or arent you running that yet?
[17:57] <XioNoX> it work better, but still no search box
[17:58] <asac> XioNoX: is it still in code?
[17:59] <XioNoX> ?
[17:59] <asac> XioNoX: anyway. in the end we dont need a search field for now
[17:59] <asac> we need a hidden thing so we can set a mime-type to search for
[17:59] <asac> XioNoX: is the search box still in code
[17:59] <asac> or is it gone
[17:59] <XioNoX> it is still in the code
[17:59] <XioNoX> i think i've done something wrong
[18:00] <XioNoX> the mime-type will be for deb vs tar.gz ?
[18:01] <asac> XioNoX: try without your changes for now
[18:01] <XioNoX> haaaaaaa
[18:01] <XioNoX> i've find
[18:01] <asac> the mime-type will be for searching for the proper plugin ;)
[18:01] <asac> XioNoX: used the same id?
[18:01] <XioNoX> document.getElementById("searchPanel").hidden = (aView != "search" || aView != "get-plugins");
[18:02] <XioNoX> i've add  || aView != "get-plugins")
[18:02] <XioNoX> i think the error is here
[18:02] <XioNoX> but it is kind difficult
[18:04] <asac> yeah
[18:04] <asac> thats better
[18:04] <asac> XioNoX: you should also use a distinct element id name ... not searchPanel
[18:04] <asac> otherwise you might end up with wierd things
[18:04] <XioNoX> it is the original name
[18:04] <XioNoX> i've got to go
[18:04] <asac> like "pluginSearchPanel"
[18:05] <asac> yes i know its the original because there was only one search panel
[18:05] <asac> in the dialog
[18:05] <asac> now we have two, so we should rename
[18:05] <XioNoX> beer between mozilla members
[18:05] <asac> XioNoX: ok cu tomorrow
[18:05] <XioNoX> cu
[18:20] <asac> Jazzva: so where are we for the extensions
[18:21] <asac> ok looking for mozilla-ctxextensions
[18:22] <Jazzva> asac, mozilla-ctxextensions, mozilla-livehttpheaders, foxyproxy, firefox-sage
[18:22] <Jazzva> I updated those
[18:29] <asac> Jazzva: urgh
[18:29] <Jazzva> asac, a problem?
[18:29] <asac> Jazzva: you need to bump depends on mozilla-devscripts
[18:29] <asac> ;)
[18:29] <asac> we need to upload that too for this
[18:29] <Jazzva> ok... give me 5 minutes
[18:30] <Jazzva> oh, we don't need :)
[18:30] <Jazzva> I included med-xpi-pack in debian ;)
[18:30] <asac> not for ctxextensions
[18:30] <Jazzva> and build comand is debian/med-xpi-pack blabla
[18:30] <asac> hmm
[18:30] <Jazzva> but it's there...
[18:30] <asac> thoguth we had a default build command that uses med-xpi-pack shipped by devscript
[18:30] <asac> what happened to that idea?
[18:31] <Jazzva> asac, I thought you still didn't release that...
[18:31] <Jazzva> did you release it?
[18:31] <asac> chmod a+x debian/rules debian/med-xpi-pack
[18:31] <asac> chmod: cannot access `debian/med-xpi-pack': No such file or directory
[18:31] <asac> make: *** [build/mozilla-ctxextensions] Error 1
[18:31] <asac> Jazzva: did release what?
[18:31] <asac> devscripts?
[18:31] <asac> i am confused :/
[18:32] <Jazzva> hm...
[18:32] <Jazzva> did you release mozilla-devscripts 0.10?
[18:32] <Jazzva> I wouldn't put med-xpi-pack inside debian if I knew it was released
[18:32] <asac> no. thats what i meant ;) ... we need that for this round of updates
[18:32] <asac> Jazzva: ok
[18:32] <asac> lets go your way then
[18:33] <asac> and remove those copies when we released the right aproach
[18:33] <asac> still ctxextensions branch doesnt have that file
[18:33] <Jazzva> that's why i adopted this now... less work to do once mozilla-devscripts 0.10 is released
[18:33] <Jazzva> lemme check
[18:34] <asac> Jazzva: http://paste.ubuntu.com/29353/
[18:34] <asac> thats what i merged
[18:34] <Jazzva> I tried to push now, but it says no new revisions. bzr diff reports no changes...
[18:34] <Jazzva> hmm
[18:34] <asac> the script is not there
[18:34] <Jazzva> stupid
[18:34] <Jazzva> bzr add *
[18:34] <asac> https://code.edge.launchpad.net/~jazzva/firefox-extensions/mozilla-ctxextensions.ubuntu
[18:34] <asac> thats what is online right now
[18:34] <asac> and proposed for merging to the release branch
[18:34] <Jazzva> right... somehow, i missed to add med-xpi-pack
[18:35] <Jazzva> try to branch now... should be at rev16
[18:35] <asac> hehe
[18:35] <asac> ok
[18:41] <Jazzva> huh... sage author says sage-too is illegally using sage's name and logo... not good news for sage-too in ubuntu, for now
[18:55] <Jazzva> Ok... I'm off for a while. See you later :)
[19:16] <armin76> asac: omg, it doesn't crash on ppc :P
[19:17] <asac> armin76: i fixed it :-P
[19:28] <saivann> asac : Do you think that this bug should be reported upstream? bug 235900
[19:28] <saivann> asac : I added steps to reproduce it in the description
[19:29] <asac> saivann: so is this "firefox window dimensions exceed screen dimensions"?
[19:30] <saivann> Yes, and cover the gnome-panel
[19:31] <saivann> Firefox takes all the screen, but the content of the firefox window is all on the screen (it does not go out of the screen)
[19:31] <saivann> asac : Actually it does not go out of the screen, but it covers everything on the screen, including gnome-panel
[19:31] <asac> like when using f11?
[19:32] <saivann> No, because the Firefox menu appears on the top
[19:33] <saivann> asac : I added demonstration videos to the bug report, see comment 14 and 15
[19:33] <saivann> asac : It covers the screen like when you press f11, but this is not the same mode because firefox menus are shown like if firefox was not in fullscreen mode
[19:33] <saivann> Also, windows border does not appears
[19:35] <asac> saivann: compiz?
[19:36] <asac> try without
[19:36] <saivann> asac : Let me test, but I don't think so
[19:36] <fretchen> asac : after deleting a patch the buildeb walked well trough the build but failed why calling dh_md5sums .  After the describtion ofter manpage I should find it in the debian folder, but it isnt't there ? Could you help me here ?
[19:38] <asac> fretchen: dh_md5sums should never really fail
[19:38] <asac> whats the error you get?
[19:40] <fretchen> asac : I am still rebuilding, as it seems like he doesn't save the last builds. I'll tell when it reappears :(
[19:41] <asac> mozilla bug 398810
[19:42] <asac> fretchen: use "--dont-purge" option
[19:42] <asac> if you use bzr builddeb
[19:43] <fretchen> asac : I used bzr builddep --merge --dont-purge
[19:49] <saivann> asac : Right, only reproducible with compiz. Someone said to me that he reproduced this bug with metacity, but from my side, it works correctly with metacity 100% of the time, and it does not work with compiz 100% of the time
[19:52] <saivann> (the problem is always reproducible with compiz only)
[19:54] <saivann> asac : I know no apps that have this problem with compiz, so do you think that we should add compiz package to the bug report, or the problem is in firefox?
[19:57] <asac> fretchen2: yeah your tree is in build-area after that
[19:58] <asac> go there, fix things, adapt patches (as usualy) and copy changes over to bzr tree when readhy
[19:58] <asac> saivann: add that to the repro instructions in bug and reassign to compiz please
[19:58] <saivann> asac : Thanks
[20:34] <armin76> asac: i doubt it :P
[21:26]  * asac off playing with NM for a few
[21:30] <fretchen2> asac : the build stops with error code 512 . And dpkg-shlibdeps can't find the libs like libxpcom_core.so
[21:43] <asac> thats not a problem
[21:44] <asac> paste the last 20 lines or so
[21:46] <asac> fretchen2: ^^
[21:51] <fretchen2> asac : http://pastebin.ubuntu.com/29400/  (sry for the french output, but I don't know how to change the locales)
[21:57] <fretchen2> asac : does this help ?
[22:05] <asac> fretchen2: you have a wrong distribution in changelog
[22:05] <asac> UNRELEASED is ok
[22:05] <asac> DUNRELEASED is wrong
[22:10] <fta> Main frozen for Alpha 3, hmm
[22:11] <fta> how come we could already have 3 alpha with so few core devs feeling concerned
[22:31] <Volans> asac: just a question... the firefox default start page is the same for all the Ubuntu installations?
[22:31] <asac> Volans: no
[22:31] <asac> fta: because most were stuck in 8.04.1
[22:31] <Volans> I mean *ubuntu, obviously for each release there is a new version
[22:32] <asac> Volans: yes i understood that
[22:32] <fta> asac, why start alphas so soon then ? it's mostly wasted cycles
[22:32] <Volans> so there are different version of ubufox for Kubuntu, Xubuntu?
[22:33] <asac> fta: its debated ... mostly they exist to give the installer guys a kick in the ass to have something workable
[22:33] <asac> and to flash out most critical issues
[22:35] <fta> asac, maybe a LTS+1 release should start a bit later. alpha1 had nothing new except an almost ready tool chain, alpha2 had a bunch of updated packages, now alpha3 has seriously regressed, at least for me
[22:35] <asac> fta: right. its recognized that something has to be done for the releases surrounding LTS in future
[22:35] <asac> its just not clear what ;)
[22:37] <asac> starting later shortens the release cycle
[22:37] <asac> and hides things even longer
[22:38] <asac> at least the QA has something they can poke us with if we hand out CDs ;)
[23:05] <Jazzva> evening
[23:12] <asac> hi
[23:12] <Jazzva> hey asac :)
[23:13] <Jazzva> thanks for uploading ctx :)
[23:13] <asac> yeah. i failed to continue somewhat
[23:13] <asac> most likely because i ended up fighting with bzr :(
[23:13] <Jazzva> heh... take your time ;)
[23:14] <Jazzva> I have to consult with the rest of the crew about Sage-Too...
[23:14] <Jazzva> So, here's the situation...
[23:14] <Jazzva> Sage is a project whose development stopped some time ago. Some folks forked from there, and made Sage-Too.
[23:15] <Jazzva> They both have the same icon and the similar names...
[23:16] <Jazzva> As Sage-Too's developer said, Sage started development again just in time to make it Fx3 compatible, few days before Fx3 release. I contacted Sage's developers to see about licensing and stuff and how they feel about Sage-Too...
[23:16] <Jazzva> So, Sage has its license in headers of all files since 1.4, as its developer said. It's licensed under tri-license, meaning that they're not too comfortable having Sage-Too using similar name and logo
[23:17] <Jazzva> On the other hand, Sage-Too's developer said that they received the icon for the project from someone, when Sage stopped development, and later he noticed Sage is using the same.
[23:17] <Jazzva> So, he thinks that Sage actually took their logo.
[23:18] <Jazzva> But, IIRC, Sage had this icon even in the old package, ... or did I add it last year, when I was adding data to app-data... Hmm, can't remember
[23:19] <Jazzva> And, Sage-Too's developers are also developing WizzRSS, which is another extension for Fx. They encouraged us to package it instead of Sage-Too, if licensing is a problem
[23:19] <asac> Jazzva: ok. i think sage-too should be considered a fork
[23:19] <asac> and thus has to change its extension id
[23:19] <asac> actually we should ask both to change extension id to avoid confusion
[23:19] <Jazzva> extension id? I think they don't have the same id
[23:19] <asac> ok
[23:19] <asac> thats a good start
[23:19] <Jazzva> It's just the fuss about name and logo...
[23:19] <asac> then they should take care that they dont conflict overlay wise
[23:20] <Jazzva> Both sides are telling they first started using that logo
[23:20] <asac> Jazzva: what is the problem from that point of view for us?
[23:20] <Jazzva> well, I just think that it might be a problem to include Sage-Too, if they didn't use the logo first... at least, that's what Sage's dev said. And that MPL doesn't allow to use the same name/logo in a fork
[23:21] <Jazzva> Or something like that...
[23:21] <Jazzva> But, I can't really believe to anyone of them, since both can say that they're first that used the logo...
[23:22] <Jazzva> I don't know if that's a problem to us...
[23:23] <Jazzva> and this is the comment from mail from the sage-too's developer "Please don't waste any of your time on this issue. As far as I'm concerned, it isn't worth it."
[23:29] <Jazzva> asac, what was the problem with bzr? Can I help somehow?
[23:30] <asac> Jazzva: well. network-manager branches are currently based on launchpad sync branches
[23:30] <asac> i want to but my changes on top of the official gnome bzr mirros though
[23:31] <asac> (which is now directly synched in launchpad as lp:network-manager)
[23:31] <asac> but that breaks because of incompatible branch formats :(
[23:31] <Jazzva> branch update :)?
[23:31] <asac> yes
[23:31] <asac> maybe i should really upgrade my local branch first ;)
[23:31] <asac> good idea
[23:31] <Jazzva> yay :)
[23:33]  * asac upgrades to --rich-root-pack
[23:33] <asac> not sure what --rich-root does different
[23:33] <asac> that didnt work
[23:33] <asac> shame
[23:33] <Nafallo> asac: gives you ssu or something probably ;-)
[23:33]  * asac tries the --rich-root
[23:34] <asac> huh?
[23:34] <asac> i have the feeling that this fails now :/
[23:35] <asac> oh, still running ... good sign?
[23:35] <Nafallo> supersuperuser? :-)
[23:35] <Jazzva> hopefully...
[23:41] <asac> took a while, but failed in a miserable way :(
[23:41] <Jazzva> ouch
[23:41] <asac> no way to upgrade to rich-root for my network-manager pack-0.92 branch
[23:41] <asac> fail
[23:43] <asac> thats it. off now. have to travel early tomorrow  ... will be in before lunch again ;)
[23:43] <asac> cu
[23:43] <Jazzva> asac, it's older bug
[23:43] <Jazzva> bug 203607
[23:43] <Jazzva> have fun tomorrow
[23:43] <Jazzva> hmm... fix released though :/
[23:45] <Jazzva> asac, this might be useful too for your problem https://lists.ubuntu.com/archives/bazaar/2008q2/041026.html