[00:16] <gnomefreak> i see alot of "-" on the extension page email
[00:16] <gnomefreak> crimsun: thanks for the flash comments
[00:18] <gnomefreak> side note what is ECL license
[00:19] <gnomefreak> i see Jazzva started changing the names
[00:20] <Jazzva> gnomefreak, most are done. just to move MT/Firefox3ExtensionsBzr, and provide MozillaTeam/Extensions home page
[00:20] <gnomefreak> Jazzva: cool
[00:21] <Jazzva> :)
[00:23] <gnomefreak> did anyone get my mail to the mailing list?
[00:28] <Jazzva> gnomefreak, which one?
[00:28] <gnomefreak> asac: fta2 whom ever is on firefox-3 next update please grey out the automatic update in the preferences>advanced>update see bug220341
[00:28] <gnomefreak> Jazzva: the tags email
[00:29] <Jazzva> I did, still didn't read it though. was too long for my condition at that moment...
[00:29] <Jazzva> Will take a look at it tomorrow.
[00:29] <Jazzva> asac (and anyone else who knows regexes), is this legitimate regex to strip filename from some path?
[00:29] <Jazzva> sed "s/\/[a-zA-Z0-9.]*$//"
[00:30] <gnomefreak> its mainly my thoughts on what stays and what goes but IMHO this needs to be taken care of soon so people can read the page and learn how to triage bugs. but its mainly everyone j=not just you :)
[00:30] <Jazzva> it works here... strips the last "/" and whatever comes after...
[00:31] <Jazzva> gnomefreak, I know. Just said that I still didn't read it :).
[00:31] <gnomefreak> as long as people got it im happy but since i dont get repies it worry that it didnt go through
[00:34] <gnomefreak> remind me why im supposed to love log files please
[00:43] <gnomefreak> im thinking flashgot is gonna be a bad extension to maintain on our part
[00:45] <gnomefreak> things like I don't like FlashGot redirecting the browser on its welcome page every time I upgrade it. Is there any way to prevent this?   Yes, I love FlashGot, but having it updated every 15-20 days is too often for me. What can I do?  First of all, let me remark that FlashGet (the well known download manager) is NOT FlashGot, the integration bridge which makes Firefox talk with the best download ect....
[00:47] <gnomefreak> lol he tells you all about himself except how to contact him
[00:48] <gnomefreak> ah found it
[00:50] <gnomefreak> Jazzva: for extenion upsteam contact in the table should we use his email or like his contact page?
[00:51] <Jazzva> I think we're using e-mails, but you can put contact page too, if mail is unavailable...
[00:51] <gnomefreak> ok i added his email but was sure
[00:52] <gnomefreak> flashgot almost has all info needed. just need to find a svn or cvs or whatnot of the source and someone can feel free to work on it ;)
[00:53] <Jazzva> great :)
[01:08] <gnomefreak> ok LP is borked
[01:16] <[reed]> asac / gnomefreak: How does somebody on gutsy get Firefox 3 from Ubuntu repos?
[01:17] <gnomefreak> oh shit
[01:17] <gnomefreak> ok we were gonna get it backported
[01:17] <gnomefreak> but im not sure anyone did. I will file a bug and build it this week sometime for backports to Gutsy
[01:18] <gnomefreak> pleaes remind me mid week
[01:18] <gnomefreak> Jazzva: i just emailed flashgot dev about finding an svn or cvs or what not to get source code for it and explained why
[01:19] <gnomefreak> anyone else doing bug woirk from email have an issue with status changes in email?
[01:19] <Jazzva> ok
[01:19]  * gnomefreak very pissed about not allowing it in beta code for LP
[01:22] <gnomefreak> ill be working on flash if anyone needs me
[01:26] <gnomefreak> [reed]: nss and nspr need to be backported too?
[01:27] <[reed]> probably, yes
[01:28] <gnomefreak> ok will work on it this week
[01:28] <[reed]> Thanks
[01:30] <gnomefreak> np
[01:41] <gnomefreak> just what i needed libflashsupport issues
[01:49] <gnomefreak> god this better work
[01:51] <gnomefreak> crimsun: libflashsupport for gutsy needs libpulse so im backporting that so i can get libflash built but backporting only in my PPA at this point until you decide what to do with PA in Gusty and or Hardy but i think we are safe in Hardy with libflash and flashplugin
[01:51] <gnomefreak> ok looks like a long build ill be back to check on it later
[02:09] <gnomefreak> ok PA uploading i will do libflash tomorrow sometime
[02:10] <gnomefreak> asac: looks like im gonna backport ff3 nss nspr to gutsy sometime this week. Ill stop in before i go to drs. tomorrow if you need anything.
[03:30] <Jazzva> asac, there by any chance?
[04:58] <saivann> asac : I confirmed bug 235900 and added steps to reproduce it, in case you want to take a look
[08:33] <AnAnt> Hello, will xulrunner 1.9 be merged from Debian or not ?
[08:36] <gnomefreak> AnAnt: i dont think we merge xulrunner
[08:36] <AnAnt> is there a reason ?
[08:37] <gnomefreak> AnAnt: off hand dont remember
[08:37] <gnomefreak> AnAnt: we dont merge anything from debian with mozilla apps we maintain (liferea might but that isnt our teams package)
[08:38] <gnomefreak> AnAnt: svn for our packages are newer than debians
[08:39] <gnomefreak> i do think we push to debian after (example sunbird we get it from mozilla and than we push to debian as iceowl after we push to ours
[08:39] <gnomefreak> )*
[08:39] <gnomefreak> plus mozilla-devscripts wont work merging from debian ;)
[09:29] <AnAnt> Hello, is there an xulrunner-dev in Intrepid ?
[09:31] <Festor> Does anyone know anything about the library libmozembed-linux-gtk2?
[09:31] <Festor> I have not been able to find its source
[09:31] <Festor> Many Java applications distributed its source code with this library precompiled
[09:31] <Festor> Despite these applications are GPL
[09:38] <gnomefreak> AnAnt: xulrunner-1.9-dev package is in intrepid
[09:38] <gnomefreak> Festor: are you sure thats not a tri license
[09:39] <Festor> two examples
[09:39] <Festor> http://www.ted.nu/
[09:39] <Festor> http://www.frostwire.com/
[09:39] <asac> AnAnt: not yet
[09:39] <asac> but will be soon
[09:39] <AnAnt> asac: thanks
[09:40] <asac> xulrunner-1.9-dev
[09:40] <asac> is the package as gnomefreak said
[09:40] <asac> but we will not merge from debian
[09:41] <gnomefreak> 1.9+nobinonly-0ubuntu2 is in intrepid for 1.9-dev
[09:41] <gnomefreak> Festor: i cant seem to find source all i find is RPM
[09:41] <Festor> yeah... :(
[09:41] <gnomefreak> wait
[09:42] <gnomefreak> closest i found was http://www.igniterealtime.org/fisheye/browse/svn-org/spark/branches/spark_2_5_6_branch/build/lib/dist/linux/libmozembed-linux-gtk2.so
[09:43] <gnomefreak> asac: you know where source for libmozembed-linux-gtk2 im assuming this is the source package name but i could be very off
[09:43] <gnomefreak> bug 177777
[09:44] <gnomefreak> oh flash is done for gutsy and hardy ;)
[09:45] <gnomefreak> he wants me to work on a bug from the ui and he knows i cant get into it
[09:48]  * gnomefreak goes for smoke and thinks about how to get into a private bug
[09:55] <Festor> I found libmozembed lib
[09:55] <Festor> http://packages.debian.org/sid/libjdic-bin
[09:57] <asac> i dont know about that lib
[09:57] <Festor> This lib is that I want libmozembed-linux-gtk2.so
[09:57] <asac> except the gtkmozembed API provided by mozilla itself (in xulrunner)
[09:58] <Festor> and this package http://packages.debian.org/sid/libjdic-bin
[09:58] <Festor> has my lib
[09:58] <gnomefreak> it is in xulrunner?
[09:58] <gnomefreak> ha i thought it was but didnt know for sure
[09:58] <asac> gnomefreak: its in libxul.so
[09:59] <asac> Festor: whats your question then? thats a java library
[09:59] <Festor> I need this lib for package a app for Ubuntu
[10:00] <Festor> People of #ubuntu-motu sent me here
[10:05] <asac> Festor: is that a java app?
[10:05] <Festor> ye
[10:05] <Festor> yes
[10:05] <Festor> frostwire
[10:05] <Festor> and other java app called "ted"
[10:06] <asac> i still dont get the problem here ... is that package not in intrepid?
[10:06] <Festor> these apps have a precompiled lib called "libmozembed-linux-gtk2.so"
[10:06] <asac> libjdic?
[10:06] <asac> Festor: are they using swing or swt?
[10:07] <asac> otherwise its most likely the swt mozilla embed library
[10:07] <Festor> I dont know... :(
[10:08] <gnomefreak> we cant view flash bugs that are private :(
[10:09] <gnomefreak> Jazzva: i got reply from flashgot maintainer i will post it to mailing list unless you want it fowarded to you?
[10:10] <gnomefreak> there is not svn or cvs of the flashgot source :(
[10:10] <gnomefreak> source is in .xpi (not a fan of that)
[10:11] <asac> thats ok
[10:11] <asac> gnomefreak: only important thing is that he puts license.txt file in top-level .xpi dir
[10:12] <gnomefreak> ill check when i get a minute most likely later today or tonight
[10:13] <gnomefreak> asac: im gonna start on gutsy backports for nss nsrp and ff3 final oh crap i have to backport xulrunner too
[10:13] <gnomefreak> asac: any other package you can think of offhand
[10:19] <asac> gnomefreak: read the changelogs of the previous xulrunner backports
[10:19] <asac> they should list the most important things you have to do
[10:19] <gnomefreak> asac: ok
[10:19] <asac> gnomefreak: nss/nspr we dont need to backport. we can use in-source
[10:19] <gnomefreak> hping i dont have to backport a full system
[10:19] <asac> but you will see that in changelog i guess
[10:19] <asac> jdong did it right back then
[10:19] <gnomefreak> asok
[10:19] <gnomefreak> asac: ok good
[10:20] <asac> gnomefreak: try to build xulrunner in gutsy
[10:20] <asac> maybe its just works
[10:51] <gnomefreak> i wish he would have told me this like a week ago :(
[10:52] <gnomefreak> now i have to rebuild all packages with ~hardy0~jjv because it seems ~8.04~jjv is higher than ~hardy1 (it shouldnt be since it has ~jjv at the end
[11:58] <asac> gnomefreak: huh?
[11:59] <asac> what does ~jjv stand for?
[11:59] <gnomefreak> asac: i used ~8.04~jjv and was told backported packages will have ~hardy1
[11:59] <gnomefreak> asac: my name
[11:59] <gnomefreak> so i have to redo all of them
[11:59] <asac> ah
[12:00]  * gnomefreak thinking of using ~hardy0 
[12:00] <asac> well .. so they say that -backports have ~hardy whily -proposed have ~8.04?
[12:00] <gnomefreak> asac: i guess
[12:00] <asac> is hardy higher than 8.04?
[12:00] <gnomefreak> i thought 8.04 was always the backported and proposed
[12:00] <gnomefreak> asac: no ~8.04 is higher im told
[12:01] <asac> gnomefreak: no
[12:01] <asac> dpkg --compare-versions "9" "ge" "8" && echo yes.
[12:01] <gnomefreak> directhex > directhex@mortos:~$ dpkg --compare-versions  1.0-1~8.04~jjv gt 1.0-1~hardy1 || echo "the jjv one  is higher"
[12:01] <gnomefreak> 06:07 <       directhex > the jjv one is higher
[12:01] <asac> so 9 is greater or equal 8
[12:01] <asac> (makes sense)
[12:02] <asac> dpkg --compare-versions "hardy" "ge" "8.04" && echo yes.
[12:02] <asac> so hardy is greater or equal 8.04
[12:02] <asac> so => works well
[12:02] <asac> use ~hardy
[12:02] <gnomefreak> than wtf
[12:02] <gnomefreak> if ~hardy is >= why cant i use ~8.04
[12:02] <gnomefreak> because of the =?
[12:02] <asac> gnomefreak: if you use || you negate the test ;)
[12:03] <asac> replace || by && and it should be silent
[12:03] <asac> in your test 9 will be less than 8
[12:03] <asac> (i think)
[12:03] <Nafallo> which was pointed out at the time, I might add :-)
[12:03] <gnomefreak> Nafallo: not to me until today
[12:04] <Nafallo> gnomefreak: I saw the text you quoted. wgrant said to use && instead of || directly after.
[12:04] <Nafallo> anyway. not an issue now that've seen the truth
[12:04] <gnomefreak> Nafallo: yes that i saw
[12:04] <jtv> asac: hi there!  Could you have a look at a sample XPI file for me one of these days and see if there are any problems beyond the ones we discussed?
[12:04] <jtv> asac: https://chinstrap.canonical.com/~jtv/test-ff.xpi
[12:05] <asac> jtv: beyond we discussed: missing non .dtd/.properties files?
[12:06] <jtv> asac: we discussed that :-P
[12:06] <gnomefreak> oh son of a bitch
[12:06] <jtv> asac: and you gave me a much better idea of how to deal with them.
[12:06] <gnomefreak> ill be back :(
[12:06] <asac> jtv: cant you put that somewhere without restrictions?
[12:06] <asac> jtv: :)
[12:07] <asac> now i have to tweak wget on command line ;/
[12:07] <jtv> asac: look at launchpad-translations-tools on LP for working examples of saving your credentials on the command line.  :-)
[12:07] <asac> i think i got it
[12:08] <asac> jtv: why the hell is that many megabytes large?
[12:08] <jtv> asac: because, just to stress the code to its limit, I exported the full Firefox translations as a single file.
[12:08] <jtv> asac: not asking you to go through everything, but I wanted maximum change to expose any problems.
[12:09] <asac> jtv: did you test that thing?
[12:09] <jtv> asac: Didn't expect it to work in production yet, because of those other files that aren't in there yet.
[12:09] <asac> jtv: they are of no use for ffox 3
[12:09] <asac> so it should work
[12:10] <asac> i found out that the current ones are left overs from ffox 2 and are not used anymore
[12:10] <jtv> asac: for a moment there, I parsed that very differently.  :-)
[12:10] <asac> (which doesnt mean that we dont need them)
[12:10] <asac> (for proper xpi export)
[12:10] <jtv> asac: well, if this is "good enough for now," then I would much prefer to take this one step forward and fix up the rest later.
[12:10] <asac> the chrome.manifest looks quite complete
[12:11] <asac> 1. please dont include en-US
[12:11] <asac> or if its a UI thing make it obvious that its usually something not wanted
[12:11] <jtv> asac: the manifest only contains the locale lines...  Didn't know what to do about the other ones.
[12:11] <asac> jtv: you need locale lines yes.
[12:12] <asac> jtv: did you include the "include lines" in the .dtd?
[12:12] <jtv> asac: I've also seen "override" lines IIRC
[12:12] <asac> e.g. there are a few entity refs we parse
[12:12] <jtv> asac: no, that was one of the problems I mentioned yesterday.  That'll take a whole extra layer of work.
[12:12] <asac> jtv: i have to think a bit about the override lines. usually those are shipped in the application/extension chrome.manifest and are locale independent
[12:13] <asac> jtv: without those includes it wont work
[12:13] <asac> thats essential
[12:13] <asac> jtv: did you think about the way to handle those i proposed once?
[12:13] <asac> like just managing those as "normal" entities with a special meaning?
[12:14] <asac> in that way you would be able to preserve the order easily - which would even be more than my po2xpi processor currently can do
[12:17] <Jazzva> asac, is this good for -unpack? http://paste.ubuntu.com/25899/
[12:17] <jtv> asac: I did consider it, but it means changing the schema.  Still considering that, but it could be pretty far-reaching, so for now I'm thinking to parse the template and just copy its include tags into the translation on export.
[12:17] <asac> jtv: how do you preserve the order?
[12:17] <asac> which is important
[12:18] <Jazzva> asac, similar is for -pack. just to find out how to lose the storing of the whole path in zip. http://paste.ubuntu.com/25900/
[12:19] <asac> Jazzva: looks reasonable
[12:19] <Jazzva> (the zip in for loop in -pack is wrong)
[12:19] <asac> i am not sure if nested .jar files are a real use case ;)
[12:19] <asac> i doubt it is ;)
[12:19] <Jazzva> yep.
[12:19] <asac> now looking at -pack
[12:19] <Jazzva> and I suppose most of them use a-zA-Z0-9 and dot in their names :)
[12:20] <asac> Jazzva: i think you have to cd into the directory you want to zip in pack or does it provide something similar than -d ?
[12:21] <Jazzva> -d deletes files from zip here. similar to -d of what command?
[12:21] <asac> unzip
[12:22] <jtv> asac: sorry for the delay, dealing with other users.  :)
[12:22] <Jazzva> it provides -j, that doesn't store relative path. but that strips every path information, so it reports duplicated files and stuff...
[12:23] <jtv> asac: internally we keep all translation strings in the order in which they're found in the template.
[12:23] <jtv> asac: so on export, I can parse the template and remember that e.g. "there's a message #151.5" (so to speak).
[12:23] <Jazzva> asac, anyway, I'll find how to remove the first part of the path. :)
[12:24] <asac> jtv: ok. so you can remember not-translatable messages
[12:24] <asac> that would work
[12:24] <jtv> asac: not really "remember": they're not going into the database.  But if I'm going to have to dissect the template during export anyway, might as well add this.
[12:24] <asac> Jazzva: i usually do: sh -c "cd $ABS_XPI_DIR; zip -r $ABS_XPI_PATH ."
[12:24] <asac> Jazzva: for that i have to get absolute paths though, but thats as simple as:
[12:25] <Jazzva> $(pwd)$REL_PATH?
[12:25] <asac> abspath=`cd $relpath; pwd`
[12:25] <jtv> asac: I'll have a kind of "pluggable XPI traversal," with one being all the things we do for an import, and another doing "if it's a DTD, check for includes; if it's a properties file, ignore it; otherwise, copy it."
[12:27] <asac> jtv: so you use the .dtd during export?
[12:27] <asac> or is that during import as well?
[12:28] <jtv> asac: during import we parse it for entities but ignore the includes.  During export we'll add them again but ignore the entities.
[12:28] <jtv> asac: come to think of it, the one big advantage to exporting multiple languages in a single XPI file is that I won't have to repeat that for every language...
[12:30] <asac> for me that sounds complicated ;). having hidden entities that are treated special sound simpler for the unknowing outsider :)
[12:30] <asac> so dont take my comments serious
[12:31] <jtv> asac: it's simpler, but the change is more fundamental.  We'd be introducing a new kind of translation message record that isn't a translation.
[12:31] <jtv> asac: Which can be useful for other things as well, but we'd have to make sure all code knows about it.
[12:32] <jtv> asac: another question... is there anything I should be doing with "override" lines in the manifest?  IIRC that's the only other kind of line I've seen besides locale lines.
[12:35] <jtv> asac: also, please let me know if these exports are (for now!) something you can work with.  If they are, then I can land it a few weeks from now and we can do incremental improvement from there.
[12:37] <jtv> asac: in fact, the XPIPO option won't go away, so even if it's not quite good enough yet, it may be worth landing in an incomplete form.
[12:38] <asac> jtv: if en-US is included in the export the override lines are probably required
[12:38] <asac> otherwise they should be skipped
[12:39] <asac> jtv: i cannot work with them if the entity includes are missing
[12:39] <AnAnt__> Hello, may I know when will xulrunner-dev be done ?
[12:39] <asac> AnAnt__: why? for now you can just use xulrunner-1.9-dev
[12:39] <AnAnt__> there is at least one package in Debian that build-depends on xulrunner-dev
[12:39] <AnAnt__> that's swt-gtk
[12:39] <asac> AnAnt__: there are plenty
[12:40] <asac> you can change build-depends for now ;)
[12:40] <asac> otherwise the next intrepid upload will include it
[12:40] <AnAnt__> asac: well, why not do a Provides: xulrunner-dev in xulrunner-1.9-dev
[12:40] <asac> its already committed to .head bzr branch
[12:40] <asac> i doubt it works well
[12:41] <asac> empty package that depends on 1.9 is the way we are going now
[12:42] <jtv> asac: now that you mention it, right now, the en-US that's included in a full "all languages" export is generated.  It's not a copy of the original.  So even that doesn't have the includes.
[12:42] <jtv> asac: oh, you were talking about the overrides, not the includes.  Sorry.
[12:42] <asac> i didnt assume that it has them ;)
[12:43] <Jazzva> asac, it works http://paste.ubuntu.com/25904/
[12:43] <AnAnt__> asac: when is next intrepid upload ?
[12:44] <Jazzva> I also silented the outputs of zip and unzip, so it doesn't overfill the screen, and put some informal messages for the user
[12:44] <Jazzva> and the output of pushd and popd
[12:46] <Jazzva> the only point of $JAR_FILE is to output it to the user. It's relative path, so it's shorter than absolute, and it from the output it looks like the script is doing all from one directory.
[12:46] <Jazzva> (well, almost)
[12:49] <asac> Jazzva: ok. will look at it in 20 min
[12:49] <Jazzva> ok
[12:51] <Jazzva> asac, http://paste.ubuntu.com/25907/ and http://paste.ubuntu.com/25908/ , in case you want to test it :)
[12:51] <Jazzva> (these are with the silented outputs)
[12:54] <gnomefreak> anyone opeing text docs without an extension(example without .txt or .doc) just a plain named file and got a header error as if text editor isnt being used to open it but open with text editor works (this is intrepid btw)
[12:55] <gnomefreak> i cant for the life of me figure out what is trying to open it
[12:57] <Jazzva> gnomefreak, regarding mail from flashgot maintainer. I can update the table, if it's needed. I don't see the need for fwding e-mail :).
[12:58] <AnAnt__> when is next intrepid upload for xulrunner ?
[13:02] <asac> Jazzva: looks good. maybe match jar! in the -pack scripts for
[13:03] <asac> not just !$ ;)
[13:03] <asac> AnAnt__: there exists no schedule. usually upstream releases dates which are always followed by an upload
[13:04] <AnAnt__> ah, ok
[13:04] <gnomefreak> Jazzva: he says source is in .xpi but i will look at it this week. i would like to get most of my backporting done today all flash and PA stuff and maybe start on ff3 and friends
[13:04] <Jazzva> asac, you mean in find?
[13:04] <asac> Jazzva: yes and maybe in sed too ;)
[13:05] <asac> to improve corner case handling ;)
[13:05] <Jazzva> right :)
[13:05] <asac> not really important though
[13:05] <XioNoX> hi
[13:05] <asac> hi XioNoX
[13:05] <gnomefreak> im still abit on edge with flashgot due to what i read lastnight and posted here, updates within a week and other things that make it hard to maintain in a stable release.
[13:05] <Jazzva> well, then I'll match with *jar! in find, instead of *!*. nested jars are not usual :)
[13:06] <gnomefreak>  but ill leave that up to you to decide since your the expert on extensions and im apparently the expert on backporting :/
[13:06] <XioNoX> asac I'm startigg to work on the FirefoxSafeUpgrades
[13:06] <Jazzva> asac, can I push that to mt branch then :)?
[13:06] <asac> Jazzva: you can use find . -type d -name \*.jar\! i guess
[13:06] <asac> no need for * at the end
[13:07] <gnomefreak> im getting ready to leave for dr. but would like to know if the firefox upgrade and thunderbird upgrade pages are ours to update and if you run across them before i do the links would be great.
[13:07] <Jazzva> asac, done. It still works :)
[13:07] <XioNoX> and i'll need some help
[13:08] <asac> XioNoX: what info do you need?
[13:08] <XioNoX> I don't know exactly
[13:09] <asac> XioNoX: i think we have a few options here. we should probably start adding a button that allows you to restart firefox
[13:09] <XioNoX> now, im trying to use the yellow bar
[13:09] <asac> then we make that button hidden by default and show it only when we detected that a restart is required
[13:09] <asac> XioNoX: thats good too
[13:09] <asac> notification box i guess
[13:09] <XioNoX> the restart button works
[13:10] <XioNoX> but i can't make the notificationbox happening
[13:10] <asac> XioNoX: did you add that to ubufox?
[13:10] <asac> XioNoX: ok
[13:10] <XioNoX> asac, i'm making an extention
[13:11] <asac> XioNoX: can you put that into ubufox directly?
[13:11] <asac> XioNoX: ls -la /var/lib/update-notifier/user.d/firefox-3.0-restart-required
[13:11] <asac> thats the file that you need to check for (consider to hard code it for now)
[13:11] <XioNoX> $ ls -la /var/lib/update-notifier/user.d/firefox-3.0-restart-required
[13:11] <XioNoX> -rw-r--r-- 1 root root 456 2008-06-11 07:45 /var/lib/update-notifier/user.d/firefox-3.0-restart-required
[13:11] <asac> if that file is newer than the current firefox process life-time, then we need to restart
[13:13] <XioNoX> if many people use firefox, they all will show this message ?
[13:13] <gnomefreak> asac: did you get my post about the preference>advanced>update not being greyed out?
[13:13] <gnomefreak> kind of important IMO
[13:14] <asac> XioNoX: yes
[13:14] <asac> XioNoX: we should test the "last-modified" time of ls -dl ProfD
[13:14] <asac> err
[13:14] <asac> of ProfD
[13:14] <asac> ;)
[13:14] <Jazzva> asac, just few more questions. Is it ok if I push med-xpi-* to the branch, and add them to mozilla-devscripts.install to install them to /usr/bin?
[13:14] <asac> if that is newer than the restart-required file, then we should ask to restart
[13:14] <Jazzva> And do I need to add GPL notice to them?
[13:15] <asac> gnomefreak: for me Firefox is greyes out (though checked- which is a visualization bug i guess)
[13:15] <XioNoX> asac, You prefere that I code everything directly in ubunfox, or i put this function in a spare extention and fusion them later ?
[13:15] <asac> XioNoX: yes please
[13:15] <asac> that eases the pain of merging later
[13:15] <gnomefreak> asac: its not greyed out here
[13:15] <asac> XioNoX: we have a bzr branch ... just base your work on that
[13:15] <XioNoX> asac, ok
[13:15] <asac> and you can commit to your own branch
[13:16] <XioNoX> I've vever used bzr
[13:16] <gnomefreak> atleast wasnt with fta's build i dowgraded today to official release for other reasons but didnt check
[13:16] <asac> XioNoX: https://code.edge.launchpad.net/~asac/ubufox/main
[13:16] <asac> its easy
[13:16] <asac> XioNoX: you most likely just need: bzr branch URL, bzr commit, bzr push :)
[13:16] <asac> maybe bzr revert
[13:17] <asac> and bzr uncommit
[13:17] <asac> :)
[13:17] <XioNoX> ok
[13:17] <asac> XioNoX: so get the branch like bzr branch https://code.edge.launchpad.net/~asac/ubufox/main ubufox.main
[13:17] <asac> and build a xpi inside ubufox.main by running build.sh
[13:17] <asac> sh build.sh ;)
[13:17] <asac> then you get a .xpi
[13:17] <asac> the directory structure should be self explaining
[13:17] <gnomefreak> asac: official build in intrepid its greyed out i wonder if it is in hardy
[13:18] <asac> gnomefreak: its greyed out here too
[13:18] <gnomefreak> can someone check hardys build of ff3 in preferneces>advanced>updates to see if the first option is greyed out
[13:18] <asac> post a screenshot please
[13:18] <asac> gnomefreak: for me its greyed out (though checked)
[13:18] <gnomefreak> asac: i have it greyed out in official build but not ftas build
[13:18] <asac> and Help -> Check for updates ... is disabled too
[13:19] <asac> gnomefreak: might be
[13:19] <gnomefreak> here as well
[13:19] <XioNoX> asac, i'll try but I can't make an xpi each time I need to test it
[13:19] <asac> XioNoX: youll figure
[13:19] <asac> install it that way on first time
[13:19] <asac> then edit in .mozilla or something
[13:19] <XioNoX> and it will not be in conflict with the existing ubufox ?
[13:19] <asac> XioNoX: no. the profile one will be preferred
[13:20] <asac> so the system one is just hidden
[13:20] <XioNoX> ok
[13:20] <asac> you can also uninstall it by apt-get remove ubufox
[13:20] <XioNoX> thanks
[13:20] <asac> +cp
[13:20] <asac> np
[13:20] <asac> :)
[13:20] <gnomefreak> ok ill be back later i will look at my logs for the bug number when i get home
[13:20] <gnomefreak> so i can ask what build they are using
[13:20] <asac> XioNoX: when you committed your changes push like bzr push bzr+ssh://bazaar.launchpad.net/~$YOURLPID/ubufox/main
[13:20] <asac> i can review and give you updates ;)
[13:21] <gnomefreak> later guys
[13:21] <XioNoX> ok
[13:21] <XioNoX> gnomefreak, bye
[13:21] <asac> gnomefreak: cu later ;)
[13:21] <asac> gnomefreak: good luck
[13:47] <Jazzva> asac, tested the installation, and it works. Ok to push?
[13:47] <Jazzva> Should I just push the files, or also to add changelog entries?
[14:23] <asac> Jazzva: new features should be documented in README
[14:23] <asac> and changelog
[14:23] <asac> Jazzva: take care that they get properly installed in the package as well
[14:23] <Jazzva> ok, I'm thinking about one more thing...
[14:24] <Jazzva> med-xpi-unpack will exit if output dir already exists. med-xpi-pack will exit if dest xpi file already exists. Do we want this behaviour, or maybe to just overwrite outdir/dest xpi?
[14:44] <asac> Jazzva: hmm. not sure
[14:44] <asac> i would probably not exit if the dir exists
[14:44] <asac> but exit if file exist
[14:45] <Jazzva> so, to remove output directory first if exists for -unpack
[14:46] <asac> Jazzva: ah for unpack
[14:46] <asac> well. lets just exit ;)
[14:47] <Jazzva> ok, so to summary
[14:47] <Jazzva> for -unpack it exits if xpi file doesn't exist, or if output dir exists
[14:47] <Jazzva> for -pack it exits if input dir doesn't exist, or if output xpi file exists
[14:48] <asac> Jazzva: ack.
[14:49] <Jazzva> good :)
[14:49] <Jazzva> i'll push the changes to mozilla-devscripts branch, just to document the changes :)
[14:51] <asac> sure
[14:53] <XioNoX> asac, it is in good progress, just an issue with the gBrowser.getNotificationBox(browser);...     ...it don't want my gBrowser :s
[14:55] <XioNoX> gBrowser is not defined
[15:01] <asac> XioNoX: how do you do it? overlay?
[15:06] <XioNoX> for the moment I've made a toolbar with buttons
[15:06] <XioNoX> to test it
[15:06] <XioNoX> the date check works perfectly
[15:06] <XioNoX> the restart function too
[15:07] <XioNoX> it remain the notification bar, the autorun, and the check periodically
[15:08] <XioNoX> notification bar have just a kind of bug
[15:11] <asac> XioNoX: ok check periodically probably shoud be done by setTimeout
[15:12] <XioNoX> ok
[15:12] <asac> autorun? not sure what that means. my approach would introduce an overlay that then gets loaded when browser is loaded; at that time i would schedule setTimeout
[15:14] <XioNoX> yes, i've call autorun the fact that it run with the brother
[15:14] <XioNoX> browser
[15:16] <XioNoX> I can send you a part of the code if you want
[15:17] <Jazzva> asac, what version to use? 0.09.1? Current is 0.09
[15:21] <asac> Jazzva: make a commit with a new changelog entry 0.10 and UNRELEASED before you commit
[15:21] <asac> e.g. "* open tree for 0.10 development"
[15:21] <asac> ;)
[15:21] <asac> then commit the rest and accompany each commit with a changelog entry
[15:22] <Jazzva> right.
[15:28] <asac> Jazzva: when done we should integrate that in xpi.mk
[15:29] <asac> as default build cmd imo
[15:29] <Jazzva> so, if we unpack jar to blabla.jar!, then chrome.manifest will know to look in it
[15:29] <Jazzva> and we don't need to pack it again in rules
[15:29] <Jazzva> right? :)
[15:29] <Jazzva> (provided that blabla.jar!/ is what is used in chrome.manifest)
[15:30] <asac> Jazzva: no. we have to pack it in rules
[15:30] <asac> thats the idea
[15:30] <asac> (in rules == default in xpi.mk)
[15:31] <Jazzva> would be easier this way :)
[15:31] <asac> hehe
[15:32] <Jazzva> cool, my first push to mozillateam branch done :)
[15:33] <asac> Jazzva: good timing ;) ... fta wont be back for some time ;)
[15:33] <Jazzva> meaning? :unsure:
[15:33] <asac> hehe
[15:34] <Jazzva> we won't mess the branch with pushes at the same time?
[15:34] <asac> i am happy with that change (without looking) ... fta might have other ideas, but well. thats how it works when maintaing things in temas
[15:34] <asac> :)
[15:34] <asac> so dont bother
[15:34] <Jazzva> I guess his script would be shorter and use much cooler regexes :)
[15:34] <Jazzva> anyway, it's open to changes ;)
[15:37] <asac> Jazzva: more explicit scripting is often better
[15:37] <asac> even if it introduces some redundancy in code (which isnt the case here)
[15:37] <Jazzva> mhm...ok
[15:38] <Jazzva> so, for xpi.mk...
[15:38] <Jazzva> maintainer unpacks the xpi with med-xpi-unpack
[15:39] <asac> fine
[15:39] <Jazzva> and in rules it doesn't call anything, because in xpi.mk med-xpi-pack is called
[15:39] <asac> Jazzva: yep
[15:39] <Jazzva> s/it/he\/she/
[15:39] <Jazzva> :)
[15:39] <asac> Jazzva: i think the default BUILD_CMD should just be set to med-xpi-pack
[15:39] <asac> in xpi.mk
[15:39] <Jazzva> it can't, we need to pass something to med-xpi-pack.
[15:40] <asac> hmm
[15:40] <Jazzva> that would be MOZ_XPI_NAME and ... input directory
[15:40] <Jazzva> MOZ_XPI_FILE
[15:40] <Jazzva> maybe we could suppose that the input directory has the same name like xpi file.
[15:40] <asac> med-xpi-pack $(MOZ_XPI_FILE) $(DEB_SRCDIR)
[15:40] <asac> maybe that?
[15:40] <Jazzva> could work :)
[15:40] <asac> Jazzva: hmm
[15:41] <asac> Jazzva: the xpi name doesnt matter as the top level dir is the xpi name
[15:41] <asac> e.g. flashblock-1.10/install.rdf and flashblock-1.10/debian ...
[15:41] <Jazzva> now I think I already have a bug in med-xpi-pack :)... lemme see
[15:43] <Jazzva> yep. The xpi doesn't contain the directory to which we should unpack, but I pack it with the input directory
[15:44] <Jazzva> fixed, I think
[15:44] <Jazzva> just some more thinking...
[15:45] <Jazzva> we have xpi in our build/ dir, and unpack it to build/out/
[15:45] <Jazzva> then we run debuild from there, which call rules, which call med-xpi-pack from build/out/. it will put the packed xpi to build/out/ too... is that good?
[15:46] <asac> why build at all?
[15:46] <asac> the default xpi.mk assumes that the result .xpi is in top-level directory
[15:47] <Jazzva> right, that's where we need to have resulting xpi file.
[15:47] <Jazzva> (that's build/out/ in this example...)
[15:47] <asac> Jazzva: ok, my complete procedure would be like:
[15:48] <asac> bzr branch URL.upstream upstream-tree
[15:48] <asac> wget http://latest.xpi
[15:48] <asac> med-xpi-unpack latest.xpi upstream-tree/
[15:48] <asac> then to pack id just want to use:
[15:48] <asac> cd upstream-tree; med-xpi-pack myxpi.xpi .
[15:49] <Jazzva> right, that's what I said... or thought.
[15:49] <armin76> why not bumb!
[15:50] <Jazzva> lol
[15:50] <asac> armin76: what?
[15:50] <armin76> lol
[15:50] <asac> armin76: you always miss the object in your sentence
[15:50] <armin76> okay
[15:50] <armin76> bumb asac
[15:50] <asac> and who?
[15:50] <asac> that either misses the object or subject :)
[15:51] <asac> armin76: why dont you bumb asac ;)
[15:51] <asac> Jazzva: ok. then all fine i guess
[15:51] <armin76> bah, always complaining :P
[15:52] <Jazzva> just to test if med-xpi-pack will work correctly :)
[15:52] <asac> Jazzva: actually: cd upstream-tree; rm -rf *; med-xpi-unpack /path/to/new.xpi .
[15:52] <asac> bzr commit -m "* new upstream thingy 12345"
[15:55] <Jazzva> asac, do we need manpage for med-xpi-*? lintian complains...
[15:55] <vadi2> http://distrowatch.com/weekly.php?issue=20080707#statistics, https://bugs.launchpad.net/bugs/241132
[15:55] <asac> Jazzva: not now ;)
[15:55] <Jazzva> good :)
[15:55] <asac> Jazzva: maybe --help ?
[15:56] <asac> with some basic infos?
[15:56] <Jazzva> lintian complains even more :)
[15:56] <Jazzva> W: mozilla-devscripts: copyright-without-copyright-notice
[15:56] <armin76> Jazzva: bumb asac
[15:56] <asac> e.g. a usage() function which is pritnting
[15:56] <asac> printed when wrong arguments or --help :)
[15:56] <Jazzva> armin76, is there a new version of asac :P?
[15:56] <asac> i wish there was a new version ;)
[15:56] <Jazzva> asac, it already prints some basic info for that.. though, not for -h/--help
[15:56] <asac> maybe that one could do a marathon ;)
[15:57] <Jazzva> and lintian is stupid...
[15:57] <asac> Jazzva: ok. clean way is to implement usage() {
[15:57] <asac> echo info
[15:57] <asac> exit 1
[15:57] <asac> }
[15:57] <asac> or something
[15:57] <asac> Jazzva: i wouldnt be too bothered by warnings
[15:57] <asac> errors are sometimes important though
[15:58] <Jazzva> no, actually... lintian is smart. copyright holders should be listed at Copyright: line...
[16:06] <Jazzva> asac, well, there's something wrong with "med-xpi-unpack /path/to/xpi.xpi ." ;). It won't overwrite the contents of the output dir, and will exit if it already exists
[16:07] <Jazzva> but, I think we can use "med-xpi-unpack lala.xpi output"
[16:11] <asac> Jazzva: you have to force overwrite in unzip
[16:12] <asac> Jazzva:  unzip -o ...
[16:12] <Jazzva> asac, it's not that. It's the check at the beginning of the med-xpi-unpack. If the dir exists, it will exit. we agreed on that ;). But I can change it...
[16:15] <asac> k
[16:37]  * asac sports bbl
[18:36] <nikolam> Hi
[18:36] <nikolam> i can`t compile seamonkey I downloaded from mozilla/seamonkey site
[18:37] <nikolam> I need it to compile it so that i can make one extension for seamonkey I need
[18:38] <nikolam> this is output from compiling, together with .mozconfig :
[18:38] <nikolam> http://paste.ubuntu.com/25974/
[18:42] <nikolam> this is precedure I used to compile seamonkey and enigmail extension for it:
[18:43] <nikolam> http://paste.ubuntu.com/25975/
[18:47] <Volans> nikolam: why you can use the builded tar.gz from mozilla site?
[18:48] <Volans> s/can/can't/
[18:48] <nikolam> I want to make 64-bit enigmail extension for seamonkey
[18:48] <nikolam> there is no 64-bit enigmail seamonkey extension available
[18:49] <Volans> ah ok... so I think I can't help you... maybe someone more expert ;)
[18:49] <nikolam> so i need to compile seamonkey
[18:50] <nikolam> to make that *.xpi
[18:51] <gnomefreak> why not use our maintained source and change as needed since you know it builds already
[18:51] <gnomefreak> that way its easier to chace problems
[18:52] <nikolam> I used to trz that before with no success .
[18:53] <nikolam> But now I am trzing just that again
[18:54] <nikolam> I upacked mantained source and applied patch with dpkg-source -x *.dsc
[18:54] <nikolam> renamed dir to mozilla
[18:55] <nikolam> and run procedure: http://paste.ubuntu.com/25975/
[18:55] <nikolam> It is compiling again. Cross fingers for me :)
[18:57] <nikolam> I am using 1,1,9 since mantained 1,1,10 seamonkey is not available yet.
[19:01] <nikolam> damn ERROR again
[19:01] <nikolam> even with Source from Ubuntu aargh
[19:01] <nikolam> pangocairo again aaah
[19:03] <nikolam> ERROR compiling seamonkey From Ubuntu-provided AND mantained source:
[19:03] <nikolam> http://paste.ubuntu.com/25980/
[19:05] <nikolam> Now I am trying to compile with dpkg-buildpackage -rfakeroot -us -uc
[19:05] <nikolam> and i don`t know if enigmail will want to compile after making *.deb`s
[19:17]  * Volans go to dinner see you later
[19:53] <asac> nikolam: still there?
[19:53] <nikolam> aham
[19:54] <nikolam> asac yes
[19:54] <asac> nikolam: we should build the enigmail extension from the enigmail source package ;)
[19:54] <nikolam> That is what I am trying to do :)
[19:55] <asac> nikolam: i am talking about the ubuntu/debian package
[19:55] <asac> nikolam: for that you dont need seamonkey
[19:55] <nikolam> aha. But there is NO enigmail source package for seamonkey. Only for Thunderbird.
[19:55] <nikolam> At least no in repo
[19:56] <nikolam> I suppose
[19:56] <nikolam> I use 64-bit repo and sm
[19:56] <asac> nikolam: right. the idea is to use that source package
[19:56] <asac> nikolam: it provided both in the past; we should get back to that
[19:57] <nikolam> Source package for Thunderbird cannot be used for seamonkey
[19:57] <asac> i think there are even still leftovers from that are
[19:57] <asac> nikolam: we dont use any source
[19:57] <asac> nikolam: we use thunderbird-dev/icedove-dev
[19:57] <nikolam> There is source for enigmail intended for seamonkey on main site
[19:57] <nikolam> ah.
[19:58] <nikolam> I am lost again.
[19:58] <asac> let me check
[19:58]  * asac didnt really latest enigmail developments
[19:58] <nikolam> ah, I shoul install those packages then
[19:58] <asac> nikolam: if you look at the link you'll see that its the same source ;)
[19:59] <asac> http://www.mozilla-enigmail.org/download/source/enigmail-0.95.6.tar.gz
[19:59] <asac> seamonkey 1.1 and tbird 2
[19:59] <nikolam> hmm :) Nice
[19:59] <nikolam> wow
[19:59] <nikolam> sooooo
[20:00] <nikolam> Maybe I could rename enigmail package for Thunderbird and compile it for Seamonkey? Hm I don`t know how to do that
[20:01] <asac> nikolam: thats nonsense ;)
[20:01] <nikolam> Thank you
[20:01] <nikolam> :)
[20:01] <asac> hehe
[20:02] <asac> the idea is to buld the thunderbird bits and then either build the seamonkey bits or just rearrange the tbird bits so they work with seamonkey
[20:02] <nikolam> So when I compile enigmail I should see how to make it "usable" for seamonkey, right.
[20:02] <nikolam> Uh
[20:03] <asac> nikolam: a good start would be to update enigmail package to latest sources from upstream ;)
[20:03] <asac> we are somewhat still stuck with 0.95
[20:03] <Jazzva> asac, I don't know about enigmail a lot, but couldn't we just put it in /usr/share/enigmail, and then make symlinks from /usr/lib/{thunderbird,seamonkey}/extensions/\{....\} to there?
[20:03] <nikolam> No wonder I got this response few months ago: http://www.mozilla-enigmail.org/forum/viewtopic.php?f=4&t=291
[20:03] <nikolam> Ahaaa hmm
[20:04] <asac> Jazzva: the whole painful thing about seamonkey is that it doesnt have the toolkit extension manager
[20:04] <nikolam> I have one brand-new Virtual machine with updated Xubuntu 64-bit 8.04.1 for testing
[20:04] <asac> so extensions are technically done in a different fashion
[20:04] <nikolam> eh, that`s it.
[20:04]  * Jazzva googles "toolkit extensions manager"
[20:04] <asac> thus we have to arrange the bit differently and take care that the chrome registration is done properly
[20:04] <nikolam> Eh that`s the trouble.
[20:04] <Jazzva> I see...
[20:05] <asac> not sure if it makes sense to document these old rotten procedures
[20:05] <asac> let me check something
[20:08] <nikolam> hm, should I post a bug about ubdating enigmail to 0.95.6 or something. I don`t know. It`s waz over my skills. I tried to compile Sm and then make *.xpi directly but with no luck.
[20:08] <asac> nikolam: ok. in enigmail package there is still debian/rules.mailnews ;)
[20:09] <asac> nikolam: in debian/rules that is commented out
[20:09] <asac> maybe enabling it is a good start ;)
[20:09] <nikolam> aah
[20:10] <nikolam> I have no clue abou development process. I managed to compile my *.deb `s for newer source that is ubout so far
[20:10] <asac> ok
[20:12] <nikolam> I think that If I could compile original source taken from mozilla site, that I could make that enigmail *.xpi and that will be it.
[20:13] <nikolam> But without using ubuntu source, i can`t even compile Seamonkey
[20:13] <nikolam> on Ubunut
[20:17] <asac> nikolam: yeah. thats likely. you probably miss a patch
[20:18] <asac> take that from seamonkey sources ;)
[20:18] <asac> and use  similar configure options
[20:20] <Jazzva> asac, I'm gonna do some more pushes to mozilla-devscripts branch... Improved med-xpi-pack and doc... In case you planned to use it :)
[20:21] <stek79_> Hi asac! Can we talk about the Firefox 3 gmail slowness bug?
[20:22] <stek79_> I made some measurements, I'm willing to track this down If I can help
[20:22] <asac> stek79_: yes. i thought it was fixed by gmail to some degree
[20:22] <stek79_> Hi! Too bad the problem is thill there
[20:22] <stek79_> bug # 217580
[20:23] <asac> bug 217580
[20:23] <stek79_> If you take a look at my last posts, I made some measuerements with top and oprofile
[20:23] <stek79_> I have hardy up-to-date and I can say (as others) that the problem is still there...
[20:23] <stek79_> the scrolling is slow and the CPU goes to 100%, as you can see from the top log I attached
[20:24] <stek79_> about 50% of CPU spent in FF3, the other 50% in Xorg
[20:24] <asac> stek79_: have you looked at the upstream bug?
[20:24] <asac> and the bug that that depends on?
[20:24] <asac> https://bugzilla.mozilla.org/show_bug.cgi?id=422330
[20:24] <stek79_> which one? It seems that there are some open bug about scrolling
[20:24] <asac> https://bugzilla.mozilla.org/show_bug.cgi?id=424423
[20:24] <asac> stek79_: the bug linked in the launchpad bug ;)
[20:25] <asac> we have already connected it with one of the upstream bugs
[20:25] <stek79_> I've seen the one regarding dotted and dashed borders, but I don't think it is gmail case
[20:25] <stek79_> ok thanks, I missed that
[20:25] <asac> stek79_: so to summarize: its a border painting issue
[20:25] <stek79_> where can I see the linked upstream bug?
[20:25] <asac> which is slow due to cairo
[20:25] <asac> stek79_: in th elaunchpad bug
[20:25] <asac> right on top
[20:25] <asac> https://bugs.edge.launchpad.net/ubuntu/+source/firefox-3.0/+bug/217580
[20:25] <stek79_> ok I take a look
[20:25] <asac> XulRunner
[20:26] <asac> stek79_: i pasted the upstream bugs above
[20:26] <asac> stek79_: try the patch from the second one
[20:26] <stek79_> thanks!
[20:26] <stek79_> ok, sorry where can I find a patch?
[20:29] <stek79_> ok I've seen it.
[20:30] <stek79_> Assuming that this actually fixes the problem, is there a chance to see this patch included in ubuntu firefox3?
[20:33] <Jazzva> asac, how does this look like for default build cmd?
[20:33] <Jazzva> MOZ_XPI_BUILD_COMMAND ?= med-xpi-pack `pwd` $MOZ_EXTENSION_PKG.xpi
[20:36] <Jazzva> added "rm -f `pwd`/*.xpi" before med-xpi-pack, just to be sure we won't get error from med-xpi-pack
[20:36] <stek79_> I took a look at the patch, it seems that it deals with drawing of rounded rectangles. But I ask: if it is a problem of FF3, why with windows xp there is NOT any slowness?
[20:46] <Jazzva> asac, yay. xpi.mk works :)
[20:46] <Jazzva> I mean, the part with the default build command.
[20:47] <Jazzva> damn, it doesn't actually :)
[20:47] <Jazzva> need to skip debian and temp-* dir in med-xpi-pack, if they exist
[20:55] <Jazzva> asac, another question. We want med-xpi-pack to unpack jar files, after it produces xpi, in order to leave sources intact, right?
[20:58] <Jazzva> ok, i'm gonna do it that way. I think it's ok
[21:01] <asac> stek79_: its because the rendering is done completely different on linux
[21:02] <asac> Jazzva: yes, filterout files that are not .xpi :)
[21:02] <stek79_> ok, thanks. Last question: when this fix will be included in ubuntu?
[21:02] <stek79_> (the mainstream patch)
[21:02] <asac> stek79_: upstream will land it once its proven to work
[21:02] <Jazzva> asac, done. Also did the unpacking of jar files, in order to get intact source. looks good :)
[21:03] <asac> stek79_: most likely we will get it through security update ... unless upstream asks us to test for them
[21:04] <asac> Jazzva: good. did you already add the xpi.mk rule?
[21:04] <stek79_> ok, many thanks for your willingness, I sincerely admire your work.
[21:04] <asac> no prob
[21:04] <asac> welcome
[21:04] <stek79_> a side question: I've opened a bug which seems to be not considered in launchpad
[21:04] <stek79_> #243704
[21:04] <Jazzva> asac, didn't push it yet
[21:04] <asac> bug #243704
[21:05] <stek79_> I don't know if it is something broken in my profile or that stuff... basically the application association does not work in my case
[21:05] <stek79_> yes that one
[21:05] <stek79_> every now and then FF keeps asking me which app it should use
[21:05] <stek79_> anyone ever had this problem?
[21:06] <stek79_> it was there since FF2 (in my case at least)
[21:06] <Jazzva> asac, maybe we can remove last three lines from this paste, since now we're sure we have some build cmd
[21:06] <Jazzva> http://paste.ubuntu.com/26015/
[21:07] <Jazzva> and the first line is the one i added
[21:09] <asac> stek79_: kde?
[21:09] <stek79_> no, gnome
[21:10] <asac> stek79_: firefox-gnome-support installed?
[21:10] <stek79_> yes: ii  firefox-gnome- 3.0+nobinonly- meta package pointing to t
[21:11] <stek79_> ii  firefox-gnome-support                        3.0+nobinonly-0ubuntu0.8.04.1
[21:17] <asac> stek79_: i think there is a bug for which mike hommey has written a patch
[21:17] <asac> about mailcap brokenness
[21:17] <asac> that one should fix it
[21:18] <asac> mozilla bug 440840
[21:18] <asac> mozilla bug 442629
[21:18] <asac> stek79_: look at those
[21:19] <asac> i think 440840 is your bug
[21:19] <asac> try that patch
[21:21] <stek79_> guys, you're awesome!
[21:22] <stek79_> a huge thanks
[21:22] <stek79_> I'll look at those
[21:23] <asac> stek79_: let me know of your findings
[21:27] <Jazzva> asac, I think I'm done with changes to mozilla-devscripts. All changes are pushed to the branch.
[21:27] <asac> Jazzva: great ... next todo is waiting :-D
[21:28] <asac> Jazzva: have you tested the ./debian/rules clean
[21:28] <Jazzva> We will have to update rules files in some extensions (the one I did for sure), when new mozilla-devscripts get uploaded to the archive
[21:28] <asac> leaves a clean source tree?
[21:28] <asac> Jazzva: what needs to be changed?
[21:28] <asac> most likely the upstream branch etc.?
[21:29] <Jazzva> mine rules file do what med-xpi-pack do... not sure how that and med-xpi-pack will cooperate ;)
[21:29] <Jazzva> eg. pack the jar file, pack the xpi...
[21:29] <asac> Jazzva: i think we have to fix rules when we switch to new upstream format
[21:29] <Jazzva> and yeah, the upstream branch. it needs to have unpacked jar files in *.jar! dirs
[21:30] <asac> Jazzva: i think only extensions that dont set a custom BUILD_CMD are affected?
[21:30] <Jazzva> new upstream format? the one med-xpi-unpack produces?
[21:30] <asac> Jazzva: yes
[21:30] <Jazzva> asac, some of mine don't set that cmd...
[21:30] <asac> i think almost no upstream branch has that format
[21:30] <asac> so we have to do that for everything
[21:30] <asac> xpi based
[21:30] <asac> Jazzva: right. so those need to be fixed now
[21:31] <asac> maybe just by setting an empty BUILD_CMD?
[21:31] <Jazzva> that could do for now.
[21:31] <asac> then we have to migrate all xpi based extensions to new upstream format and drop the BUILD_CMD used
[21:31] <Jazzva> asac, we don't need to drop it, if the rules use build cmd provided by the upstream (sh build.sh)
[21:37] <Jazzva> hmm... it doesn't leave clean sources. there's a xpi file in t-l directory...
[21:38] <Jazzva> can I just add "rm -f *.xpi to xpi-clean target in xpi.mk?
[21:38] <Jazzva> or to clean target?
[21:38] <asac> Jazzva: hmm.
[21:39] <asac> the .xpi file should already be automatically removed
[21:39] <asac> in toplevel dir
[21:39] <Jazzva> if no build command is provided, yes, in clean target...
[21:39] <Jazzva> At least, that's what was done in xpi.mk
[21:40] <Jazzva> and I removed that part in the last (or commit before the last), since we have default build command
[21:42] <asac> Jazzva: you sure it only removed the .xpi if there was no build command?
[21:42] <Jazzva> http://paste.ubuntu.com/26015/
[21:42] <Jazzva> asac, there are the last three lines
[21:42] <Jazzva> right, if build cmd is provided
[21:43] <asac> see ;)
[21:43] <Jazzva> my mistake in reading ifneq as ifeq... will fix that
[21:43] <asac> Jazzva: backout the last patch and do it proper ;)
[21:44] <asac> backout is usually done by reverse applying
[21:44] <Jazzva> right
[21:44] <Jazzva> hmm...
[21:44] <asac> do we really need to remove .xpi in BUILD_COMMAND?
[21:44] <Jazzva> but, now we don't need the ifneq test. there is always a build_cmd
[21:44] <Jazzva> no, if we do it in clean :)...
[21:44] <asac> Jazzva: well. it might have been explicitly unset
[21:45] <Jazzva> ahaa...
[21:45] <asac> Jazzva: ok.
[21:45] <asac> Jazzva: for instance your packaging could define it as empty
[21:45] <Jazzva> right.
[21:45] <asac> not sure if it works with ?= though
[21:45] <asac> but i think it should
[21:46] <asac> Jazzva: i think `pwd` should be $(DEB_SRCDIR) or if that is not set $(CURDIR)
[21:47] <asac> assuming that -pack  can deal with relative paths
[21:49] <Jazzva> I think it can. It only uses indir in push $INDIR...
[21:49] <Jazzva> and pushd can take relative paths
[21:51] <Jazzva> testing with $(CURDIR)
[21:54] <Jazzva> yay. works and ./debian/rules clean leaves clean source :)
[21:55] <asac> great
[21:57] <stek79_> asac, how can I test the mozilla patches? I have to build a new FF3 I think...
[22:01] <Jazzva> ok, these changes are pushed :)
[22:01] <asac> stek79_: no, xulrunner-1.9
[22:01] <asac> (most likely the patches are xulrunner patches)
[22:01] <Jazzva> nope, still not pushed:)
[22:03] <asac> stek79_: you install bzr-builddeb and then get the bzr branch lp:~mozillateam/xulrunner/xulrunner-1.9.head
[22:03] <stek79_> is there some tutorial about rebuilding it?
[22:03] <asac> and in xulrunner-1.9.head you run
[22:03] <asac> bzr bd --merge --dont-purge
[22:03] <stek79_> ok, I have to learn bazar :)
[22:04] <stek79_> never used it :(
[22:07] <Jazzva> done... now to make usage() functions for med-xpi-* and to use them :)
[22:14] <asac_> sorry reconnect
[22:14] <asac_> stevel:
[22:14] <asac_> hmm
[22:14] <stevel> asac_: hrm?
[22:14] <asac_> stevel: sorry. wrong auto complete ;)
[22:14] <asac_> stek is gone ;)
[22:15]  * stevel points at stek79_ 
[22:15] <Volans> asac_ sorry for the OT question... if I have a question about python on Ubuntu where is the right place to ask?
[22:15] <asac_> stek79_: last seen:
[22:15] <asac_> 23:04 < stek79_> never used it :(
[22:15] <asac_> Volans: depends in which direction the question is going
[22:15] <stek79_>  ok, I have to learn bazar :)
[22:15] <stek79_>  never used it :(
[22:16] <Volans> module loading that work in gutsy and not in hardy due to a change of the path of the module (xml.dom module)
[22:21] <asac_> Volans: is that a main package?
[22:21] <Volans> is in the python-xml package let me check
[22:21] <asac_> and whats the problem?
[22:22] <Volans> universe
[22:22] <Volans> I have a script that works well in gutsy but in hardy crash with a error loading module
[22:22] <Volans> while the module is installed as I know, the packages are the same
[22:23] <Volans> but in a different path
[22:23] <Volans> changed from /usr/lib/python2.5/site-packages/_xmlplus/dom/.... in gutsy to  /usr/lib/python2.5/site-packages/oldxml/_xmlplus/dom/... in hardy
[22:24] <asac> Volans: yes, then we upgraded to a new version which probably doesnt have that module anymore
[22:25] <Volans> the error is in the xml.dom ext module in particular, but I can't exclude that other module loaded after going to do the same
[22:39] <Jazzva> usage done :)
[22:42] <asac> Volans: do you have a simple testcase?
[22:42] <Volans> from xml.dom import ext
[22:42] <Volans> I think is enough ;)
[22:43] <Volans> you can try in the interactive shell I think, with the python-xml package installed
[22:49] <Volans> asac: have you tried if the import work on hardy?
[22:54] <asac> Volans: yeah it fails
[22:55] <Volans> and you think is a path problem or something more in-depth?
[22:56] <Volans> I need only the PrettyPrinter function and the Printer.py file is already there
[22:56] <asac> Volans: i think that ext is obsolete
[23:02] <asac> Volans: maybe ask on #ubuntu-devel. not sure if thats the right forum though ;) ... if its still there but in a non-default folder you could add that path to PYTHONPATH in your install i think
[23:02] <Volans> ok... and you know the "obvious" substitution for PrettyPrint? perhaps a lxml function
[23:04] <asac> hmm ... anyone sees pidgin crashin wiht hardy-proposed?
[23:04] <asac> Volans: no clue. i only use python when i bump into it ;)
[23:04] <Volans> ok thanks a lot :)
[23:26] <Jazzva> asac, pidgin crashes in group chat?
[23:26] <asac> Jazzva: no it crashes on startup for me :(
[23:26] <asac> so in short: i cannot start it anymore :(
[23:26] <Jazzva> asac, sorry...
[23:26] <asac> not even with clean profile ;)
[23:26] <Volans> gdb?
[23:26] <Volans> :)
[23:26] <Jazzva> Don't know if I don't use that one...
[23:26] <Jazzva> but it crashes in group chat for me
[23:27] <asac> Jazzva: group chat?
[23:27] <asac> irc?
[23:27] <Volans> ah asac for the python proble I have found the bug 199014
[23:27] <Jazzva> asac, no... more people in same msn chat room...
[23:27] <asac> ok
[23:27] <asac> never used that
[23:27] <Jazzva> good for you (seriously :))
[23:29] <Volans> ubottu: are you sleeping?
[23:35] <asac> Volans: look what other packages did to fix it ;)
[23:37] <Volans> I have found the solution in the bug replies
[23:37] <Volans> add: sys.path.append('/usr/lib/python%s/site-packages/oldxml' % sys.version[:3])
[23:37] <Volans> before the first xml import
[23:37] <Volans> and works
[23:46] <asac> Volans: and what is the _new_ way?
[23:46] <Volans> I heard that "lxml" is the best xml dom atm for python, but is an external module
[23:47] <Volans> I have used xml.dom because except for that function is integrated in the standard python
[23:47] <Volans> so more simple to use
[23:48] <Volans> If you have 5 minutes I have a proposal I have already sent to the ubuntu-web list (the new Web Presence Team)
[23:49] <asac> not sure if i can be of help there ;)
[23:49] <Volans> no news2000 tell me to ask you ;)
[23:49] <asac> what is it about?
[23:50] <Volans> I can forward to you the mail I think is better and quickest
[23:52] <Volans> sent!