/srv/irclogs.ubuntu.com/2008/07/22/#ubuntu-mozillateam.txt

Jazzvaasac, 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:10
Jazzvaasac, and I'll start using "open tree for development", UNRELEASED as dist and similar in the next cycle of updates :)00:11
Jazzvaasac, lp:~jazzva/firefox-extensions/mozilla-livehttpheaders.ubuntu are ready for merge. Rev 17 is the one...00:57
Jazzvas/are/is/00:57
asacok off. have a dentist appointment tomorrow morning and dont want to be completely wasted there ;)01:02
Jazzvauh... dentist01:02
asacyeah01:02
Jazzvaumm... good luck :)01:02
asachopefully can help me without much pain ;)01:02
asacill try to do those two first thing in the morning01:02
Jazzvatake your time01:02
asacwell. things should go up ;)01:02
Jazzvaafter dentist is fine too :)01:02
asachehe yeah01:02
asacnot before for sure01:03
asacquite early01:03
asaccu01:03
Jazzvacu01:03
Nafalloasac: do we have vimperator packaged? ;-)01:03
=== asac_ is now known as asac
asacNafallo: vimperator?08:02
asacJazzva: did we ever file a bug for the webkit MIR?09:01
asacbug 25073809:04
ubottuLaunchpad bug 250738 in webkit "[MIR] promote webkit to main" [Undecided,Confirmed] https://launchpad.net/bugs/25073809:04
XioNoXhi09:21
asachi XioNoX09:22
XioNoXBack at work09:24
XioNoXI've miss my flight yesterday, so it is why i wass not connected09:25
asacXioNoX: oh. so you have to fly in every week?09:29
XioNoXno, i've just left 1 week09:30
XioNoXnow i'm up to work 5 weeks09:30
asachow did you manage to miss your flight? ;)09:31
XioNoXI 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:36
XioNoXbut the plane company change my flight for free, so I've arrived yesterday afternoon09:37
asacXioNoX: argh. sorry for that. i feel with you09:41
asacXioNoX: (sorry for missing flight) ... great to hear that they changed for free09:41
XioNoX:D09:41
XioNoXit was this festival : http://www.vieillescharrues.asso.fr/festival/programmation_2008.php09:42
asacmotorhead still exists ;) ... fun.09:43
XioNoXit was cool09:45
Nafalloasac: http://vimperator.mozdev.org/09:45
Nafallo:-)09:45
asaclol09:45
asacNafallo: reads like good crack ;)09:46
XioNoXasac, i've read all the xpcom tutorial, and i don't realy know how we use it (and why)09:50
asacXioNoX: what is unclear?09:54
XioNoXwhat does an XPCOM component?09:55
XioNoXwhat it is used for ?09:56
asacXioNoX: thats a tough question ;)09:58
XioNoXi know09:58
XioNoXbut maybe just an exemple will be enough09:59
asacXioNoX: ok. components implement interfaces that define a service in a cross-language-fashion ;)09:59
XioNoXimplement interfaces ?10:00
asacXioNoX: do you know OO programming?10:00
asacObject-Oriented10:00
XioNoXa little bit10:00
XioNoXwith C++10:00
asacthen you should know what an interface is ;)10:00
asacok in C++ its similar to the class definition10:01
asace.g. just the contract, not the implementation10:01
XioNoXok10:01
asacclass declaration is the right word, sorry10:01
asacso now instead of writing10:01
asacclass A {10:01
asac public:10:01
asac  int x;10:01
asac  int func();10:01
asac};10:01
asacyou have a syntax that is language independent10:01
asacnamely IDL10:02
asacInterface Definition Language10:02
asacyou can find plenty of .idl files in your mozilla  source tree10:02
asacso what xpcom provides is that you can call and implement such classes/objects in a across-language boundaries10:03
XioNoXok10:04
asace.g. you can implement a Car class in javascript and call it from C++ or vv10:04
asacnow there are two use cases of xpcom interface implementations:10:05
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 like10:06
asac2. ;)10:06
asacdoes that help you already?10:07
XioNoXyep10:07
asacXioNoX: so one thing you can do with interfaces is that you can have multiple implementations of the same10:08
XioNoXit is more clear now10:08
asacXioNoX: which comes handy in our case as we want to make something extensible in a pluggable fashion10:08
XioNoXok10:09
XioNoXand I'm reading the rdf stuff10:09
asacok10:10
XioNoXthe dor is bigger but it is easier to understand10:10
asacdor?10:10
XioNoXsorry, doc10:11
asacNafallo: https://www.mozdev.org/bugs/show_bug.cgi?id=1959810:47
ubottuwww.mozdev.org bug 19598 in General "Please include License.txt file in your released .xpi" [Normal,New]10:47
asacNafallo: could you add that extension to the Firefox3Extensions page in wiki10:47
asacso it doesnt get lost?10:47
Nafallosure10:47
asachttp://wiki.ubuntu.com/MozillaTeam/Firefox3Extensions10:47
asacNafallo: 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 on10:48
asacmaybe put the bug link in the "extension developer contact" column ;)10:48
Nafalloadded :-)11:00
armin76buuuuuuuuuumb!11:08
* armin76 files 30 bugs for bumbing11:08
armin76lolz11:13
armin76asac: you broke firefox on ia64!11:13
armin76ah11:13
armin76its the dependencies stuff11:13
armin76still, bets that it segfaults on ppc and sparc? :D11:14
asacon my way11:15
asacarmin76: BUMMMMMBED!11:19
asacdeep impact11:19
armin76lies11:19
asacon hardy-updates11:19
asacwhat a breathtaking moment11:19
asacarmin76:11:19
asac12:18 < asac> so ffox and xul sources+ bits can go11:19
asac12:18 < pitti> asac: awesome; copying11:19
armin76bumbing!11:21
Jazzvaasac, 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-ask11:58
asacJazzva: no problem12:00
asachttps://wiki.ubuntu.com/MainInclusionProcess12:01
asacthats the process12:01
Jazzvawow... sage is also updated. I thought they stopped its development. Guess I'll update it now :)12:01
Jazzvaasac, thanks :)12:01
asacgood12:02
asacJazzva: when you done with that ping me so i can upload all three ;)12:04
* asac going lunch ;)12:04
Jazzvak :)12:04
Jazzvahave fun12:04
Jazzvait's gonna be four of them. foxyproxy needs update, too :)12:04
asacthats12:09
armin76asac: omggggggggg!12:25
armin76looks like sparc intrepid doesn't sigbus! :D12:25
armin76uh, wtf12:43
armin76why doesn't ports.ubuntu.com have hardy-updates and proposed on Release?12:43
armin76asac: fix!12:43
armin76bah, stupid!12:44
armin76uh...nah, it gives bus error anyway12:55
armin76takes a lot more, though12:55
armin76on hardy it just gives bus error at the start12:55
asacarmin76: ok lets be focussed12:56
asacwhat patches shall i apply12:56
armin76no idea :P12:58
armin76i don't apply any patch to fix the sigbus12:58
Jazzvaasac, can mozilla-devscripts use patching system?13:00
Jazzva*package using mozilla-devscripts13:01
asacJazzva: it could, but wouldnt make much sense13:01
asacexcept when we cherry-pick to stable release branches13:01
asacbut for that we can also merge individual commits imo13:01
Jazzvaso, to change the source directly?13:01
Jazzvasorry... I meant can package using mozilla-devscripts use patching system?13:01
asacJazzva: mozilla-devscripts is a native package . there is no orig.tar.gz ... so you develop _inside_ the package13:01
asacJazzva: ah13:02
asachavent tried ;)13:02
asacbut why not13:02
Jazzvacan I just use quilt and include in the rules13:02
Jazzvaok, i'll try13:02
asacas long sa the .xpi is produced by build command13:02
asacmaybe we need to tweak a hook or something13:02
asacJazzva: Jazzva but in general the idea is t change _in-source_13:03
asacin the .ubuntu branch13:03
Jazzvaaha... ok13:03
asaci dont expect lots of patches to accumulate in extensions13:03
asacusually just a maxVersion bump13:03
asacand maybe a quick fix or cherry-pick for some stable updates13:03
Jazzvawell, 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 wonder13:04
asacarmin76: so is it a sigbus in libc?13:04
asacJazzva: how intrusive are those changes?13:05
asaccan you post them?13:05
asacif they are not packaging related we should push it to upstream i guess13:06
Jazzvanot too big13:06
Jazzvahttp://paste.ubuntu.com/29282/13:06
Jazzvabut look reasonable13:06
Jazzvalooking at the upstream bts13:07
XioNoXasac, who have decided to keep the old skin on firefox 3 whereas the beautiful new one ?13:08
Jazzvaasac, it's marked as fixed here13:14
Jazzvahttps://www.mozdev.org/bugs/show_bug.cgi?id=1510113:15
ubottuwww.mozdev.org bug 15101 in Javascript "sage fails many of the tests in the feed reader XSS test suite" [Critical,Resolved: fixed]13:15
asacXioNoX: he?13:22
asacXioNoX: linux uses gnomestripe13:22
asacer have that as default13:22
XioNoXwhy they don't have the big back button ?13:23
asacXioNoX: thats windows13:23
XioNoXand mac13:23
XioNoXit is the "default" firefox theme13:23
XioNoXno ?13:23
asacmost likely moz devs didnt care _enough_13:23
asacfor linux13:24
Jazzvaasac, I'll test sage without the patch on some security tests which are reported in bug report.13:24
asacto do that or thought that it wouldnt fit nicely into gnome desktop13:24
asacJazzva: the bug is fixed13:24
asacaccording to bug tracker ;)13:24
asacyes pleaes test then13:25
Jazzvaasac, umm... that's what I saw :)13:25
asacmaybe we can drop them ;)13:25
Jazzvaasac, but I would like to13:25
XioNoXasac, for exemple, this theme will fit perfectly in gnome : https://addons.mozilla.org/fr/firefox/addon/737913:27
XioNoXand he have the firefox 3 looks13:27
JazzvaXioNoX, I think it's because FF will use icons from current gnome theme13:27
Jazzvas/will use/uses/13:28
XioNoXand who manage that ?13:28
Jazzvaumm... what do you mean?13:28
JazzvaFF 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
XioNoXbecause i've heared a lot of people complaining about the firefox 3 theme on ubuntu13:29
XioNoXand why we don't install by default a firefox skin13:30
XioNoX?13:30
JazzvaAs 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:30
JazzvaXioNoX, 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
asacXioNoX: you are the first i hear complaining ...everone else i talked to cheered ;)13:31
XioNoXbut we can install a theme like the one i've show you easily through amo13:31
asacXioNoX: we can certainly package skins as xpi in ubuntu, but that wont become the default for sure13:32
XioNoXanother exemple here : http://brainstorm.ubuntu.com/idea/5754/13:32
JazzvaXioNoX, it's true. But that would break the uniformity of the look of the desktop.13:32
asacwe are happy that we are finally integrated with gnome theme13:32
Jazzva+1 on that :)13:32
XioNoXok13:33
asac"Linux has the best theme for Firefox 3.13:33
asacJust look at the Windows theme for Firefox 3 it looks absolutely horrible. "13:33
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
asacThemes for Windows look completely amateur. Both. The colors, the shapes... Hahaha... "13:34
JazzvaXioNoX, 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
asaci think this is something you cannot find a solution where everyone agrees13:34
JazzvaXioNoX, that's why the fixed theme in win and mac won't break the look of the rest of the desktop13:34
asacas a matter of fact the default gnome theme isnt that bad13:34
JazzvaOn 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:35
XioNoXok13:36
asacJazzva: yeah. but the size of the back button could probably not be tuned13:36
asacthats a design devision i guess13:36
asacdecision13:36
XioNoXthat explaination it enough for me13:36
Jazzvaasac, that too... If they wanted to use big button, I suppose all gnome themes should add one big button...13:36
JazzvaXioNoX, I'm glad we could help :)13:36
asacanyway, we can package themes up if there is really demand13:36
asacnot sure about that though13:36
XioNoXok13:38
XioNoXI didn't know that the firefox theme was linked to the gnome theme13:41
armin76asac: i have no clue13:43
armin76asac: as i said, it takes more time to sigbus than in previous versions13:44
armin76i don't know if thats due to firefox or libc13:44
armin76need to test on ppc13:44
Jazzvaasac, this is the feed that has the tests14:02
Jazzvahttp://www.gnucitizen.org/blog/cross-context-scripting-with-sage/feed.xml14:02
JazzvaI have tested it. It does interpret it as script, as no text is shown, but it doesn't give me the alert window...14:03
JazzvaI'll test with the patch now14:04
Jazzvaif it shows that script as text, I'll use the patch14:04
asac Jazzva try to alert in the exception case for the unix paths14:04
asace.g. catch (e) {} => catch (e) { alert('here goes the rdv'); }14:05
Jazzvamhm... ok14:05
asacat best the exception14:05
asacwhats the CVE id?14:05
asac(for that test?)14:05
JazzvaCVE-2006-4711 and -471214:06
Jazzvatest is located at mozdev bug14:07
jt1asac: hey there!14:07
Jazzvamozdev bug 1510114:07
ubottuLaunchpad bug 15101 in linux-meta "linux-image-2.6-686 depends on linux-image-2.6.8.1-3-686 for Hoary" [Medium,Invalid] https://launchpad.net/bugs/1510114:07
Jazzvahmm14:07
Jazzvahttps://www.mozdev.org/bugs/show_bug.cgi?id=1510114:07
ubottuwww.mozdev.org bug 15101 in Javascript "sage fails many of the tests in the feed reader XSS test suite" [Critical,Resolved: fixed]14:07
asacubottu: CVE-2006-471114:09
ubottuSorry, I don't know anything about cve-2006-471114:09
asachi jt114:09
=== jt1 is now known as jtv
jtvha, that's better14:10
asacjtv: you should start a _real_ irc client ;)14:10
jtvasac: still haven't finished our discussion of the file_references issue!14:10
asacwe havent?14:10
asac;)14:10
jtvasac: I used to, and people told me to use this one instead.  :-)14:10
asacnot that i thought otherwise :-D14:10
asacJazzva: i think the feed.xml is to show CVE-2006-471214:11
XioNoXasac, 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
asacfor CVE-2006-4711 executing javascript without cross context appears to be enough14:12
XioNoXsame for xpcom14:12
asacXioNoX: sure14:12
asacXioNoX: lets start with a simple modification of the "Get Addons" tab in addons dialog14:13
asacso you get used to that huge code ;)14:13
XioNoXok14:13
jtvasac: 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:13
asacXioNoX: do you have a hg trunk tree?14:14
asacXioNoX: do you have a place where you can push your "topic" branches?14:14
XioNoXnop14:14
Jazzvaasac, tested... not getting any alerts :/14:14
XioNoXnot yet14:14
asacXioNoX: ok so for now we need patches then i guess ;)14:14
asac(to show me)14:14
XioNoX?14:14
asacJazzva: ok. so the script is not executed at all?14:14
asacXioNoX: 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 changes14:15
Jazzvaasac, 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 text14:15
asacXioNoX: ok. you need a hg clone that you can build14:16
asacXioNoX: doy ou have that already?14:16
XioNoXnop14:16
XioNoXi've nothing yet14:16
asacXioNoX: ok, get such a tree then ;)14:17
asachttp://developer.mozilla.org/en/docs/Mercurial14:17
asacand make it build14:17
XioNoXi've already used mercurial14:17
XioNoXbut not for firefox14:17
asacXioNoX: yes, but you have to build the tree ;)14:17
XioNoXi need to get all the sources of firefox ?14:17
asacotherwise you cannot test your changes14:17
asacXioNoX: yes14:17
XioNoXand what is the url of the trunk ?14:18
asacXioNoX: so first thing is to add a new tab like the "Get-Addons Tab" to the addons dialo14:19
XioNoXok14:19
asachttp://developer.mozilla.org/en/docs/Mozilla_Source_Code_(Mercurial)14:19
XioNoXadd a tab like the extention, theme, laguage, etc... ?14:20
asacthe code we will be mostly working in is toolkit/mozapps/extensions/14:20
asacXioNoX: 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
asacXioNoX: call it Plugin-Wizard ;)14:21
asacor whatever14:21
asacand then we will try to move the plugin finder service there ;)14:22
XioNoXhttp://hg.mozilla.org/ ?14:22
XioNoXwhich one should I get ?14:22
asacread the urls i gave you :)14:22
XioNoXmozilla-central ?14:23
asacyes14:23
asacits all on the page ;) ... http://developer.mozilla.org/en/docs/Mozilla_Source_Code_(Mercurial)14:23
XioNoXThe integration repository for Mozilla 2 development is mozilla-central14:23
XioNoXha14:23
XioNoXMozilla 214:23
XioNoXnot firefox 214:23
asacmozilla 2 ... but current focus should be 1.9.114:24
XioNoXdone14:27
XioNoX34564 files updated14:28
XioNoX260,0 Mio14:28
XioNoX:~/Stage/Plugin-Wizard/src/toolkit/mozapps/extensions$ ls14:29
XioNoXcontent  jar.mn  Makefile.in  public  service  src  test14:29
XioNoXthere are a lot of files14:29
asacXioNoX: do a build first14:29
asacwant to be sure you can test what you code ;)14:29
XioNoXrun allmakefiles.sh ?14:30
asacits on that website ;)14:30
XioNoXi try to go too fast14:31
asacmost likely14:31
XioNoX/bin/sh: autoconf-2.13: not found14:34
XioNoXbut autoconf2.13 exist14:35
asacmost likely AUTOCONF is wrong then14:35
asacin .mozconfig14:35
XioNoXokay it work14:36
XioNoXI have all the -dev package to install14:36
Jazzvaasac, applying the patch produces the same result14:36
Jazzvaguess we can drop it then :/14:37
XioNoXasac, configure: error: Could not compile basic X program.14:41
Jazzvanow 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
asacXioNoX: you lack build dependencies14:41
asacinstall the ones we use for xulrunner-1.9 and firefox-3.0 package14:41
asacJazzva: are sage and sage-too independent projects?14:42
Jazzvasage-too is a fork of sage14:42
asacbut both are active?14:42
Jazzvayes14:42
JazzvaI thought sage is inactive until yesterday...14:42
Jazzvabut then I found out it has update dated june 23rd on amo14:43
asacwhy cant we fix the overlay?14:43
asacso they dont conflict?14:43
Jazzvahmm... good :)14:43
JazzvaI'll push sage unchanged, since sage-too is a fork14:43
JazzvaI'll also see with the upstream to fix this, if they can14:43
asacok. do we have sage-too alredy in archive?14:43
Jazzvanot atm... waiting to see about copyright issues14:44
Jazzvasage 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
XioNoXit is running14:44
Jazzvas/also misses/is also missing/14:45
asacXioNoX: good14:45
asacXioNoX: so in public/ there are the .idl files14:45
asaclook at them ;)14:45
asacnsIAddonRepository.idl14:46
asacdefines abstract contract to implement backend that gets result from addons databases (like amo)14:46
asacwe could use that to search for extensions available in ubuntu14:46
asacbut thats not the start here ;)14:47
asacthe xul pieces are in content/14:47
Jazzvaasac, mozilla-ctxextensions, foxyproxy, mozilla-livehttpheaders and firefox-sage are ready for upload14:47
Jazzvado you need branch links?14:47
XioNoXmodules/libpr0n14:47
XioNoXo_O14:47
asacXioNoX: yeah. you dont want to touch that unless you really want to get dirty14:48
asaclol14:48
Jazzvahaha :)14:48
asacXioNoX: 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 tab14:49
XioNoXok14:50
Jazzvaasac, sorry... I forgot to add "New upstream release" to changelog for firefox-sage. I pushed new revision14:51
XioNoXasac, will I have to build firefox at each modification ?15:04
asacXioNoX: yes and no15:13
asacusually just the subdirectory needs to be rebuild15:13
XioNoXok15:13
XioNoXand i don't really know how to start15:13
asacXioNoX: yeah. you probably should try to match what you see with the code you read to get a basic idea15:14
asacand then look more in detail15:14
XioNoXok15:14
Jazzvaasac, the problem might also be that they're using sage instead of sage-too name in chrome.manifest15:49
asacthats not so great ;)15:50
Jazzvayeah...15:50
asacwe can change that here, but should tell upstream about thta15:50
Jazzvait needs a lot of changes15:50
Jazzvawell... there is one neat (maybe not so clean way)15:50
Jazzvas/sage/sageToo/15:50
Jazzvas/Sage/SageToo/15:51
Jazzva:)15:51
Jazzvahmm... and both sage and sage-too have minVersion set to 3.0b115:53
Jazzvaasac, please don't upload firefox-sage for now. I would like to see if it's compat with FF215:53
XioNoXasac, i don't know what i have to put in the idl file15:58
XioNoXi've put the default lines, but it is all15:58
asacXioNoX: thats a good start16:11
asacXioNoX: you can now go to the xul part ;)16:11
asacand add a new item to the addons dialog16:12
XioNoXwhere is the xul ? in the .js files ?16:12
asacin the .xul, js and .xml files16:12
asace.g. in the content/ folder16:12
XioNoXok16:12
XioNoXi haven't see the content folder16:12
* asac goes stocking up food16:16
Jazzvalol... now it's called SageToo-Too :)... forgot to fix SageToo-Too back to Sage-Too :)16:26
Jazzvayay, Sage and Sage-Too are not clashing anymore :)16:28
=== Moot2 is now known as MootBot
XioNoXasac, the PluginWizard will replace the exixting plugin tab ?16:40
XioNoXif not, how will we call it ?16:40
asacno16:47
asacnot for now16:47
asac"get plugins"?16:48
XioNoXokay16:48
XioNoX<radio id="get-plugins-view" label="&get-plugins.label;" oncommand="showView('get-plugins');" persist="last-selected"/>16:49
XioNoXI don't get this part in the .js file :16:50
XioNoXin 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
XioNoXand int the "normal" plugin view, there are no link to the AMO16:51
Jazzvaasac, hmm... looks like sage is not working with ff-216:52
asacXioNoX: you can not map that one-by-one16:53
asacwhat we want is to have the ability to search by mime-type for now16:54
asacand display a list of results with the install ... button16:54
asac(just like that plugin finder result)16:54
Jazzvaasac, ok, firefox-sage is also ready.16:54
XioNoXand search where ?16:54
asacadvanced searches like  by name or description are not yet useful16:54
asacXioNoX: in a search field like in get addons16:54
XioNoXok16:55
XioNoXokay16:56
XioNoXhow can I test that I've done ?17:10
asacstart the firefox you built ;) and look in addons dialog17:10
XioNoXhow ?17:13
XioNoXi've just done  make -f client.mk build17:14
Jazzvaasac, XioNoX: are you implementing plugin finder directly in ff? cool :D17:14
XioNoXIt is the goal of my intership, but i have to learn everything17:16
JazzvaXioNoX, Mozilla internship? or here in ubuntu? :)17:22
XioNoXMozilla Europe17:23
XioNoXfor 6 weeks17:23
JazzvaCool :)17:23
XioNoXyep17:23
XioNoXJazzva, what do you do you ?17:23
JazzvaI'm a student. that's mostly what I do :)]17:24
XioNoXwhere ?17:24
JazzvaAnd I volunteer at Ubuntu, because I like it and I can learn new things :)17:24
JazzvaSchool of electrical engineering, University of Belgrade... That's in Serbia17:25
XioNoXha ok17:25
XioNoXnice17:26
JazzvaIt's ok :)17:26
XioNoXwhat do you do on ubuntu ?17:26
JazzvaMostly 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
XioNoXok17:27
Nafalloasac: I have another one for you :-D17:29
XioNoXdo you know how to compil firefox ?17:29
XioNoX:D17:29
asacNafallo: if its not complete add it to the same table ;)17:29
Nafallohttp://www.asnumber.networx.ch/17:30
asacNafallo: you could help by bugging upstream about license file in top-level .xpi directory ;)17:30
Nafallo:-P17:30
asacthat turned out to be the most cumbersome step when looking at packaging extensions17:30
JazzvaXioNoX, no ;). I haven't tried that... I'm scared my computer would die :)17:30
Nafallohaven't even checked out the code for any of those ;-)17:30
XioNoXasac ?17:30
asacNafallo: you dont need to. as long as it works, and it is licensed under a free license we can probably package it ;)17:31
JazzvaXioNoX, did you ask that me or asac?17:31
asacXioNoX: it should be like on the website17:31
Nafalloasac: kewl. I'll have a look this evening unless someone goes to the pub :-P17:31
asachaha17:31
XioNoXyou because asac was'nt responding but now that he is back17:31
asacXioNoX: dont know how to help you ;)17:32
asacdont even knew that the build didnt succeed17:33
asacfor you17:33
XioNoXhe have succeed, but no bin file17:33
asacXioNoX: how do you know?17:34
asacwhere did you look?17:34
XioNoXhe have succeed because there were no error message :)17:34
XioNoXand I've look in my src folder17:34
asacXioNoX: yeah. but where did you look for the binaries17:34
asacyour soure folder?17:35
asacfirefox is in the dist/bin directory17:35
asacyou have to do a complete firefox build ... which probably takes a while17:35
asacthen there is a dist/bin directory in the top-level tree17:36
XioNoXit was not write in the wiki page :o17:36
XioNoXi've found it :D17:36
asacXioNoX: well. that is even more basic ;)17:36
asacthe document just taught the basics for the new mercurial biult17:36
asaci actually assumed that you knew how to built old mozillas17:37
XioNoXnop17:37
asacbut well  ... now you know17:37
XioNoXI've never worked on mozilla17:37
XioNoXthe searchbox doesn't appear, even in the "normal"  get exentions17:51
asacXioNoX: "doesnt't appear" anymore?17:54
asacor never17:54
XioNoXi haven't test withour any modifications17:55
XioNoXbut I haven't touch the get extention part17:55
asacmaybe its hidden because amo doesnt support 3.0.1 yet?17:56
asacin applicaiton.ini you can probably set 3.0 as version17:56
XioNoXi don't know17:56
asacabove i ment 3.1.017:56
asacfta: do you see something similar in 3.1.0 or arent you running that yet?17:56
XioNoXit work better, but still no search box17:57
asacXioNoX: is it still in code?17:58
XioNoX?17:59
asacXioNoX: anyway. in the end we dont need a search field for now17:59
asacwe need a hidden thing so we can set a mime-type to search for17:59
asacXioNoX: is the search box still in code17:59
asacor is it gone17:59
XioNoXit is still in the code17:59
XioNoXi think i've done something wrong17:59
XioNoXthe mime-type will be for deb vs tar.gz ?18:00
asacXioNoX: try without your changes for now18:01
XioNoXhaaaaaaa18:01
XioNoXi've find18:01
asacthe mime-type will be for searching for the proper plugin ;)18:01
asacXioNoX: used the same id?18:01
XioNoXdocument.getElementById("searchPanel").hidden = (aView != "search" || aView != "get-plugins");18:01
XioNoXi've add  || aView != "get-plugins")18:02
XioNoXi think the error is here18:02
XioNoXbut it is kind difficult18:02
asacyeah18:04
asacthats better18:04
asacXioNoX: you should also use a distinct element id name ... not searchPanel18:04
asacotherwise you might end up with wierd things18:04
XioNoXit is the original name18:04
XioNoXi've got to go18:04
asaclike "pluginSearchPanel"18:04
asacyes i know its the original because there was only one search panel18:05
asacin the dialog18:05
asacnow we have two, so we should rename18:05
XioNoXbeer between mozilla members18:05
asacXioNoX: ok cu tomorrow18:05
XioNoXcu18:05
asacJazzva: so where are we for the extensions18:20
asacok looking for mozilla-ctxextensions18:21
Jazzvaasac, mozilla-ctxextensions, mozilla-livehttpheaders, foxyproxy, firefox-sage18:22
JazzvaI updated those18:22
asacJazzva: urgh18:29
Jazzvaasac, a problem?18:29
asacJazzva: you need to bump depends on mozilla-devscripts18:29
asac;)18:29
asacwe need to upload that too for this18:29
Jazzvaok... give me 5 minutes18:29
Jazzvaoh, we don't need :)18:30
JazzvaI included med-xpi-pack in debian ;)18:30
asacnot for ctxextensions18:30
Jazzvaand build comand is debian/med-xpi-pack blabla18:30
asachmm18:30
Jazzvabut it's there...18:30
asacthoguth we had a default build command that uses med-xpi-pack shipped by devscript18:30
asacwhat happened to that idea?18:30
Jazzvaasac, I thought you still didn't release that...18:31
Jazzvadid you release it?18:31
asacchmod a+x debian/rules debian/med-xpi-pack18:31
asacchmod: cannot access `debian/med-xpi-pack': No such file or directory18:31
asacmake: *** [build/mozilla-ctxextensions] Error 118:31
asacJazzva: did release what?18:31
asacdevscripts?18:31
asaci am confused :/18:31
Jazzvahm...18:32
Jazzvadid you release mozilla-devscripts 0.10?18:32
JazzvaI wouldn't put med-xpi-pack inside debian if I knew it was released18:32
asacno. thats what i meant ;) ... we need that for this round of updates18:32
asacJazzva: ok18:32
asaclets go your way then18:32
asacand remove those copies when we released the right aproach18:33
asacstill ctxextensions branch doesnt have that file18:33
Jazzvathat's why i adopted this now... less work to do once mozilla-devscripts 0.10 is released18:33
Jazzvalemme check18:33
asacJazzva: http://paste.ubuntu.com/29353/18:34
asacthats what i merged18:34
JazzvaI tried to push now, but it says no new revisions. bzr diff reports no changes...18:34
Jazzvahmm18:34
asacthe script is not there18:34
Jazzvastupid18:34
Jazzvabzr add *18:34
asachttps://code.edge.launchpad.net/~jazzva/firefox-extensions/mozilla-ctxextensions.ubuntu18:34
asacthats what is online right now18:34
asacand proposed for merging to the release branch18:34
Jazzvaright... somehow, i missed to add med-xpi-pack18:34
Jazzvatry to branch now... should be at rev1618:35
asachehe18:35
asacok18:35
Jazzvahuh... sage author says sage-too is illegally using sage's name and logo... not good news for sage-too in ubuntu, for now18:41
JazzvaOk... I'm off for a while. See you later :)18:55
armin76asac: omg, it doesn't crash on ppc :P19:16
asacarmin76: i fixed it :-P19:17
saivannasac : Do you think that this bug should be reported upstream? bug 23590019:28
ubottuLaunchpad bug 235900 in firefox-3.0 "firefox 3 displays full screen on start " [Medium,Confirmed] https://launchpad.net/bugs/23590019:28
saivannasac : I added steps to reproduce it in the description19:28
asacsaivann: so is this "firefox window dimensions exceed screen dimensions"?19:29
saivannYes, and cover the gnome-panel19:30
saivannFirefox 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
saivannasac : Actually it does not go out of the screen, but it covers everything on the screen, including gnome-panel19:31
asaclike when using f11?19:31
saivannNo, because the Firefox menu appears on the top19:32
saivannasac : I added demonstration videos to the bug report, see comment 14 and 1519:33
saivannasac : 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 mode19:33
saivannAlso, windows border does not appears19:33
asacsaivann: compiz?19:35
asactry without19:36
saivannasac : Let me test, but I don't think so19:36
fretchenasac : 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:36
asacfretchen: dh_md5sums should never really fail19:38
asacwhats the error you get?19:38
fretchenasac : I am still rebuilding, as it seems like he doesn't save the last builds. I'll tell when it reappears :(19:40
asacmozilla bug 39881019:41
ubottuMozilla bug 398810 in General "Remove MOZILLA_1_8_BRANCH ifdefs from core on trunk" [Normal,Resolved: fixed] http://bugzilla.mozilla.org/show_bug.cgi?id=39881019:41
asacfretchen: use "--dont-purge" option19:42
asacif you use bzr builddeb19:42
fretchenasac : I used bzr builddep --merge --dont-purge19:43
saivannasac : 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 time19:49
saivann(the problem is always reproducible with compiz only)19:52
saivannasac : 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:54
asacfretchen2: yeah your tree is in build-area after that19:57
asacgo there, fix things, adapt patches (as usualy) and copy changes over to bzr tree when readhy19:58
asacsaivann: add that to the repro instructions in bug and reassign to compiz please19:58
saivannasac : Thanks19:58
armin76asac: i doubt it :P20:34
* asac off playing with NM for a few21:26
fretchen2asac : the build stops with error code 512 . And dpkg-shlibdeps can't find the libs like libxpcom_core.so21:30
asacthats not a problem21:43
asacpaste the last 20 lines or so21:44
asacfretchen2: ^^21:46
fretchen2asac : http://pastebin.ubuntu.com/29400/  (sry for the french output, but I don't know how to change the locales)21:51
fretchen2asac : does this help ?21:57
asacfretchen2: you have a wrong distribution in changelog22:05
asacUNRELEASED is ok22:05
asacDUNRELEASED is wrong22:05
ftaMain frozen for Alpha 3, hmm22:10
ftahow come we could already have 3 alpha with so few core devs feeling concerned22:11
Volansasac: just a question... the firefox default start page is the same for all the Ubuntu installations?22:31
asacVolans: no22:31
asacfta: because most were stuck in 8.04.122:31
VolansI mean *ubuntu, obviously for each release there is a new version22:31
asacVolans: yes i understood that22:32
ftaasac, why start alphas so soon then ? it's mostly wasted cycles22:32
Volansso there are different version of ubufox for Kubuntu, Xubuntu?22:32
asacfta: its debated ... mostly they exist to give the installer guys a kick in the ass to have something workable22:33
asacand to flash out most critical issues22:33
ftaasac, 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 me22:35
asacfta: right. its recognized that something has to be done for the releases surrounding LTS in future22:35
asacits just not clear what ;)22:35
asacstarting later shortens the release cycle22:37
asacand hides things even longer22:37
asacat least the QA has something they can poke us with if we hand out CDs ;)22:38
Jazzvaevening23:05
asachi23:12
Jazzvahey asac :)23:12
Jazzvathanks for uploading ctx :)23:13
asacyeah. i failed to continue somewhat23:13
asacmost likely because i ended up fighting with bzr :(23:13
Jazzvaheh... take your time ;)23:13
JazzvaI have to consult with the rest of the crew about Sage-Too...23:14
JazzvaSo, here's the situation...23:14
JazzvaSage is a project whose development stopped some time ago. Some folks forked from there, and made Sage-Too.23:14
JazzvaThey both have the same icon and the similar names...23:15
JazzvaAs 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
JazzvaSo, 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 logo23:16
JazzvaOn 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
JazzvaSo, he thinks that Sage actually took their logo.23:17
JazzvaBut, 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 remember23:18
JazzvaAnd, 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 problem23:19
asacJazzva: ok. i think sage-too should be considered a fork23:19
asacand thus has to change its extension id23:19
asacactually we should ask both to change extension id to avoid confusion23:19
Jazzvaextension id? I think they don't have the same id23:19
asacok23:19
asacthats a good start23:19
JazzvaIt's just the fuss about name and logo...23:19
asacthen they should take care that they dont conflict overlay wise23:19
JazzvaBoth sides are telling they first started using that logo23:20
asacJazzva: what is the problem from that point of view for us?23:20
Jazzvawell, 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 fork23:20
JazzvaOr something like that...23:21
JazzvaBut, I can't really believe to anyone of them, since both can say that they're first that used the logo...23:21
JazzvaI don't know if that's a problem to us...23:22
Jazzvaand 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:23
Jazzvaasac, what was the problem with bzr? Can I help somehow?23:29
asacJazzva: well. network-manager branches are currently based on launchpad sync branches23:30
asaci want to but my changes on top of the official gnome bzr mirros though23:30
asac(which is now directly synched in launchpad as lp:network-manager)23:31
asacbut that breaks because of incompatible branch formats :(23:31
Jazzvabranch update :)?23:31
asacyes23:31
asacmaybe i should really upgrade my local branch first ;)23:31
asacgood idea23:31
Jazzvayay :)23:31
* asac upgrades to --rich-root-pack23:33
asacnot sure what --rich-root does different23:33
asacthat didnt work23:33
asacshame23:33
Nafalloasac: gives you ssu or something probably ;-)23:33
* asac tries the --rich-root23:33
asachuh?23:34
asaci have the feeling that this fails now :/23:34
asacoh, still running ... good sign?23:35
Nafallosupersuperuser? :-)23:35
Jazzvahopefully...23:35
asactook a while, but failed in a miserable way :(23:41
Jazzvaouch23:41
asacno way to upgrade to rich-root for my network-manager pack-0.92 branch23:41
asacfail23:41
asacthats it. off now. have to travel early tomorrow  ... will be in before lunch again ;)23:43
asaccu23:43
Jazzvaasac, it's older bug23:43
Jazzvabug 20360723:43
ubottuLaunchpad bug 203607 in bzr "bzr unable to upgrade to rich-root/rich-root-pack format (dup-of: 177874)" [Undecided,New] https://launchpad.net/bugs/20360723:43
ubottuLaunchpad bug 177874 in bzr "upgrading to rich-root-pack fails" [Critical,Fix released] https://launchpad.net/bugs/17787423:43
Jazzvahave fun tomorrow23:43
Jazzvahmm... fix released though :/23:43
Jazzvaasac, this might be useful too for your problem https://lists.ubuntu.com/archives/bazaar/2008q2/041026.html23:45

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!