[00:18] <asac> @time
[08:25] <[reed]> What's a way to get the current libgtk2.0 version if you don't have libgtk2.0-dev installed (and can't use pkg-config because of that)?
[08:29] <asac> [reed]: gtk_major_version constant?
[08:29] <[reed]> I want a one-liner I can give people to run on the command line
[08:29] <[reed]> to get their current GTK+ version
[08:30] <asac> [reed]: i think you need C for that ... or python if they have that installed?
[08:31] <asac> unless you want to depend on packaging of course
[08:31] <[reed]> lame
[08:31] <[reed]> oh well
[08:32] <asac> [reed]: wait a second ;)
[08:33] <[reed]> I'm looking for a solution that's cross-distro, too
[08:33] <[reed]> pkg-config would have worked, but it requires the dev package
[08:33] <[reed]> which is lame
[08:33] <[reed]> :(
[08:33] <gnomefreak> no ome sees me here
[08:34] <asac> [reed]: mozilla could provie that info in about -> dialog ;)
[08:35] <gnomefreak> what does this package do? libpam-runtime
[08:35] <gnomefreak> IIRC pam == the password dialog
[08:37] <asac> its a authentication framework
[08:37] <gnomefreak> crap
[08:37] <asac> allows you to plugin in new auth mechanisms
[08:38] <gnomefreak> its badly broken
[08:40] <asac> [reed]: in python you can type:
[08:40] <asac> import gtk
[08:40] <asac> gtk.gtk_version
[08:40] <asac> that should give you the version without the need to link or such ;)
[08:41] <asac> of course depends on gtk + python + pygtk
[08:45] <gnomefreak> ok im going back to bed itx early (3:44)
[08:45] <asac> gnomefreak: sleep tight
[09:10] <XioNoX> hi !
[09:11] <fta> strings /usr/lib/libgtk-x11-2.0.so* | grep 2.0 | head
[09:12] <fta> but using the distro pkg tool is probably better
[09:16] <[reed]> fta: looking for distro-agnostic method
[09:19] <kgoetz> [reed]: looks the most agnostic to me ;)
[09:19] <[reed]> yeah
[09:19] <[reed]> my reply was to <fta> but using the distro pkg tool is probably better
[09:19] <[reed]> I like fta's command
[09:26] <noiesmo> can i ask a question about thunderbird extensions here
[09:27] <fta> [reed], doesn't work with debian though :(
[09:56] <asac> i dont see any version with the command above ;)
[09:57] <asac> fta: doesnt even work here ;)
[09:59] <asac> but maybe thats because of my cloak ;)=
[10:26] <XioNoX> asac, it is more difficult that I've though :(
[10:28] <XioNoX> the js don't update the content of the richlistbox
[10:41] <asac> XioNoX: what are you on atm?
[10:41] <asac> implementing your own application-like dialog, right?
[10:41] <XioNoX> yes
[10:43] <XioNoX> I can show you what I've done
[10:43] <asac> go ahead
[10:44] <XioNoX> http://pastebin.mozilla.org/521817
[10:44] <XioNoX> and
[10:44] <XioNoX> http://pastebin.mozilla.org/521818
[10:46] <asac> so you need box in richlistitem?
[10:48] <XioNoX> the application tab have a box element
[10:48] <XioNoX> so i've done the same thing
[10:48] <asac> XioNoX: did you see that in code or DOM inspector?
[10:48] <XioNoX> dom
[10:48] <XioNoX> it is very powerfull
[10:49] <asac> XioNoX: yes. but what you see there is wrong ;)
[10:49] <XioNoX> because of xml ?
[10:49] <asac> well not really wrong, but it pretends to be different to what you have to code
[10:50] <asac> XioNoX: yes. what you see in DOM is the final dom hierarchy... this includes automatically generated elements
[10:50] <asac> if you define in xbl richlistitem like:
[10:50] <XioNoX> but the what you see in the xul file work



[10:50] <XioNoX> only the implementation of js don't
[10:50] <asac> it will look in dom inspector as if <richlistitem><box><test/></box></richlistitem> is senseful xul
[10:50] <asac> XioNoX: right. please do what the .js file does
[10:51] <XioNoX> i've try it too
[10:51] <XioNoX> but with the same result
[10:52] <asac> XioNoX: in dom inspector the "red" elements are generated implicitly by xbl
[10:52] <XioNoX> yeah, i know that
[10:54] <asac> XioNoX: ok. remove everything except the header from this .xul
[10:54] <asac> and just copy the code from application.js
[10:54] <XioNoX> the full .js ?
[10:55] <asac> no ... the _rebuildView code?
[11:01] <XioNoX> ok, but this function use others functions and the XUL of the applications.xul
[11:01] <XioNoX> and preferences.xul
[11:04] <XioNoX> in the application.xul there are a richlistbox with the headder stuff
[11:18] <asac> XioNoX: right. you need that richtlistbox in your xul
[11:18] <asac> the rebuildView thing doesnt really do much
[11:18] <asac> copy that code... replace dynamic elements with static elements for now
[11:18] <asac> shouldnt be a big problem
[11:24] <XioNoX> var _list = document.getElementById("pluginsList");
[11:24] <XioNoX> alert(_list);
[11:24] <XioNoX> return null
[11:24] <XioNoX> but I have this in my xul : <richlistbox id="pluginsList" orient="vertical" persist="lastSelectedType">
[11:39] <asac> XioNoX: well .... maybe you are not in the same document?
[11:40] <XioNoX> I think I'am
[11:40] <XioNoX> it is the same xul file that I've pastbin you
[11:41] <asac> XioNoX: well if you run that code before it has been loaded you wont find anything
[11:41] <asac> you have to put that in a function that gets run when the doucment is loaded
[11:41] <asac> or am i wrong=
[11:42] <XioNoX> ok
[11:42] <XioNoX> We are going to lunch, i'll fix taht after
[11:42] <XioNoX> see you
[11:50] <XioNoX> asac, ok, it work :) I've just put the javascript line of the xul at the end of the xul file :)
[11:51] <asac> XioNoX: thats ugly
[11:51] <asac> use the "load" event please
[11:56] <XioNoX> i know i know, it was just for testing :)
[12:06] <asac> haha
[12:39] <gnomefreak> there is a new email virus out. it comes from airlines with attachment (dont open it)
[12:48] <Kamping_Kaiser> ...
[12:54] <gnomefreak> ;)
[12:56] <gnomefreak> anyone use liferea?
[12:57]  * asac lunch
[12:57] <asac> gnomefreak: fta uses it
[12:57] <Jazzva> gnomefreak, me and fta, AFAIK
[12:57] <gnomefreak> its broken
[12:57] <gnomefreak> it frezzes up
[12:58] <Jazzva> gnomefreak, really? fta asked for a sponsor yesterday (or the day before) to upload new version. Are you talking about that one?
[12:58] <gnomefreak> it might be the updates causing it but i will find out
[12:58] <Jazzva> ok
[12:59] <gnomefreak> term is freazing up as well
[13:00]  * gnomefreak needs a dictionary today
[13:00] <gnomefreak> i guess i go for smoke until updates are done
[13:16] <gnomefreak> look out for http://www.savvywallet.com/2008/07/25/bogus-virus-email-affecting-sun-country-airlines/ im looking into what it does
[13:43] <XioNoX> asac, how can I doo the mimetype ==> human readable conversion ? window.navigator.plugins dont seam to have mimetypes
[14:16] <asac> XioNoX: ill give you something .... just ignore that for now ;)
[14:17] <XioNoX> hu ?
[14:23] <asac> XioNoX: i'll try to find a solution to map a mime-type to a readable name ;)
[14:24] <XioNoX> I'm trying
[14:24] <XioNoX> and I thing I'm not far
[14:24] <XioNoX> yeah it is almost working
[14:28] <XioNoX> asac, check this please : http://pastebin.mozilla.org/521909
[14:29] <XioNoX> the loop stop too early
[14:29] <XioNoX> and don't go througs all mimetypes
[14:31] <Wulfie> hey folks, a while back I asked in here and someone showed me how to change the default "zoom" behaviour in Firefox 3 back to the old behaviour (changing text size not zooming everything) . . . how do I change that back :)
[14:33] <Wulfie> a browser.zoom.full
[14:34] <Wulfie> thanks folks
[14:35] <XioNoX> asac, sorry, it is ok :)
[14:38] <asac> good
[14:38] <asac> let me know when we get to the next step ;)
[14:41] <XioNoX> nxt step ?
[14:41] <XioNoX> not i'm attacking the dropdown menu
[14:42] <XioNoX> who appear when we clic on the line
[14:44] <asac> yeah
[14:44] <asac> thats the right thing
[14:44] <asac> for now just display the matching plugins available
[14:44] <asac> and the current default
[14:44] <asac> which is:
[14:44] <asac> 1. identified by its .so path ... if there is a pref
[14:44] <asac> 2. or the first plugin in the list that matches
[14:45] <asac> (so quite simple)
[14:45] <asac> (though indirect)
[14:46] <XioNoX> . or the first plugin in the list that matches ?
[14:53] <gnomefreak> Jazzva: you gonna be around today?
[14:53] <asac> XioNoX: yes. thats correct
[14:53] <asac> in the plugins array == list
[14:53] <asac> browser.plugins
[14:54] <XioNoX> ok
[14:54] <XioNoX> now i'm trying to understand how the menu works
[14:55] <gnomefreak> bug 492837
[14:55] <gnomefreak> !test
[14:55] <gnomefreak> wtf is wrong with you
[14:56] <asac> !test
[14:56] <asac> works ;)
[15:07] <gnomefreak> yeah just fixed the plugin for bugs but the person sent email with that bug in subject and its not a bug
[15:08] <gnomefreak> ok someone pushed diggler to Intrepid but from looking at https://wiki.ubuntu.com/MozillaTeam/Extensions/List?action=show&redirect=MozillaTeam%2FFirefox3Extensions neo diggler is the one that should be pushed to archives once its worked on
[15:08] <gnomefreak> are they going to conflict?
[15:10] <gnomefreak> once i find out what is wrong with my rules file i will sttart getting info needed for neo
[15:10] <Jazzva> gnomefreak, pretty much, but still working on this school project
[15:12] <Jazzva> gnomefreak, to find out if diggler and neo-diggler (which is based on diggler) are going to conflict, look in their chrome.manifest files
[15:12] <gnomefreak> Jazzva: can you look at something when you get time? i will have to pull up error again but its error in rules was gonna look more into it after email but i didnt see anything wrong with it last night
[15:12] <gnomefreak> Jazzva: than do we drop neo-diggler?
[15:12] <gnomefreak> or will it superseed diggler
[15:12] <Jazzva> gnomefreak, and look at their chrome uri's. if they're the same (meaning the writer of neo-diggler didn't change them), they're probably gonna drop it
[15:12] <Jazzva> s/uri's/URIs/
[15:13] <gnomefreak> 3. Accepted: diggler 0.9-16ubuntu1 (source) (Bhavani Shankar)
[15:13] <gnomefreak> ah ok
[15:13] <Jazzva> gnomefreak, I added neo-diggler because back then diggler wasn't in development anymore. If diggler is in development again, then maybe we don't need to add neo-diggler
[15:13] <gnomefreak> so far no info ws found other than license but i dont trust that since they didnt add any other info
[15:14] <Jazzva> It should be on addons.mozilla.org
[15:14] <gnomefreak> https://addons.mozilla.org/en-US/firefox/addon/3763
[15:14] <gnomefreak> that neo
[15:15] <gnomefreak> Neo Diggler is a tidy-up, bug-fix and minor re-organisation of the original Diggler
[15:15] <Jazzva> yeah... I think we're gonna add neo-diggler
[15:15] <gnomefreak> someone should ask for its removal if its gonna conflict
[15:15] <Jazzva> gnomefreak, diggler: Updated September 27, 2004
[15:15] <gnomefreak> it was pushed on the 18th
[15:16] <gnomefreak> of this month
[15:16] <Jazzva> And it only works for Firefox up to 1.0.*. Maybe someone is updating it in Debian for recent Firefox versions
[15:16] <gnomefreak> anyone know the person that pushed it see ablve
[15:17] <asac> si there an upstreawm update?
[15:17] <asac> otherwise we should migrate users to it
[15:17] <gnomefreak> Jazzva: when you get time (doesnt hav to be today) can you look at http://pastebin.mozilla.org/521926
[15:17] <Jazzva> asac, for diggler? no
[15:17] <asac> to neo-diggler
[15:17] <gnomefreak> asac: neo-diggler is not in devel anymore
[15:17] <asac> or isnt neo diggler similar?
[15:17] <gnomefreak> opps
[15:17] <asac> he?
[15:17] <gnomefreak> i mean diggler isnt
[15:17] <Jazzva> asac, this is the last changelog entry which is related to the source: install.rdf: Allow diggler to work with Iceweasel 2.0.
[15:17] <asac> ok
[15:17] <Jazzva> asac, in 0.9-12
[15:18] <asac> how similar is the featureset of diggler vs. neo-diggler
[15:18] <asac> ?
[15:18] <asac> fta: we have one mui important feature thing to do in this cycle :(
[15:18] <gnomefreak> asac: not sure yet there isnt enough info on the wiki yet unless Jazzva knows
[15:18] <asac> fta: migrating nss/nspr back to upstream soname
[15:18] <Jazzva> asac, I haven't looked at both, but this is what desc for neo-diggler says "Neo Diggler is a tidy-up, bug-fix and minor re-organisation of the original Diggler"
[15:19] <asac> fta: so, byebye shlibs i guess and byebye debian
[15:19] <asac> fta: good thing is that debian wont follow (they are frozen), so they will end up with a less compatible nss
[15:19] <gnomefreak> shit error is http://pastebin.mozilla.org/521945
[15:19] <asac> just kidding ;) ... I dont really want debian any harm
[15:20] <Jazzva> gnomefreak, it doesn't have a build command. I'm not sure if asac pushed med-xpi-pack which should be the default command in case where no build command is defined in debian/rules
[15:20] <asac> gnomefreak: what is your binary package name in control
[15:20] <asac> gnomefreak: and what is the source package name
[15:20] <asac> gnomefreak: if they dont match, you probably have the wrong name in rules
[15:20] <gnomefreak> both same "chatzilla"
[15:20] <asac> whats the build command ?
[15:20] <asac> that appears to be not executed
[15:20] <asac> have you named chatzilla in rules?
[15:20] <asac> paste rules might be a good idea
[15:21] <Jazzva> asac, http://pastebin.mozilla.org/521926
[15:21] <Jazzva> rules
[15:21] <gnomefreak> MOZ_EXTENSION_PKG := chatzilla
[15:21] <asac>  yeah ... there is no build command
[15:21] <asac> no doubt thats a likely reason
[15:21] <asac> for your build doing nothing
[15:21] <gnomefreak> could be but this xpi.template worked for firegpg
[15:22] <asac> gnomefreak: well. that doesnt matter
[15:22] <asac> you need a build command for sure
[15:22] <asac> unless you do other black magic ;)(
[15:22] <Jazzva> and back to thread synchronization. yay... *sigh*
[15:22] <gnomefreak> would rather keep it "official" that way when time to push it doesnt require i play 50 questions
[15:22] <Jazzva> see you later
[15:23] <asac> gnomefreak: firegpg has a build command
[15:23] <gnomefreak> later Jazzva and thanks
[15:23] <Jazzva> no problem :)
[15:23] <gnomefreak> and im sure maybe the CVS of this one does too but itsa old
[15:23] <asac> gnomefreak: no
[15:23] <asac> BUILD_COMMAND is xpi.mk specific
[15:23] <asac> you need one
[15:23] <asac> fix that
[15:24] <gnomefreak> #MOZ_XPI_BUILD_COMMAND = sh build.sh
[15:24] <gnomefreak> thas wrong?
[15:25] <asac> yes
[15:25] <asac> what does that mean=?
[15:25]  * asac is testing gnomefreak ;)
[15:26] <gnomefreak> dont know other than = is same
[15:26] <gnomefreak> well == is
[15:26] <gnomefreak> = mean sum/answer
[15:26] <asac> what does the first letter mean?
[15:26] <gnomefreak> s?
[15:26] <asac> that means that its commented
[15:26] <gnomefreak> yes
[15:26] <asac> # MOZ_XPI
[15:26] <gnomefreak> oh it cant be that easy
[15:26] <asac> -> it doesnt matter
[15:26] <asac> its not enabled
[15:26] <gnomefreak> it cant be that easy
[15:26] <asac> you also need to ensure that there is a build.sh that builds chatzilla
[15:27] <asac> remove the #
[15:27] <asac> if there is no build.sh ... figure what to use to build and use that instead
[15:28] <gnomefreak> i dont remember seeing one but ill look again
[15:28] <gnomefreak> let me finish what im doing first
[15:29] <gnomefreak> debian bug 492837
[15:29] <gnomefreak> that why it wsant on LP
[15:30] <XioNoX> asac, just a little thing, I can't find the page which explain how to get things in the preferences
[15:31] <gnomefreak> ok be back a bit later
[15:32] <asac> XioNoX: ther are other places in the extensions where i get the prefs
[15:32] <asac> search for getCharPref
[15:33] <XioNoX> ok, thx
[15:54] <XioNoX> asac, if modules.plugins.mimetype. how do I know wich plugin is used ?
[15:55] <XioNoX> specially if there are many plugins installed for the same mimetype ?
[16:02] <asac> XioNoX: the two point above where the algorithm to fiture out which is used
[16:02] <asac> figure
[16:03] <XioNoX> 2. or the first plugin in the list that matches ?
[16:03] <XioNoX> so it is a kind of aleatory ?
[16:03] <asac> yes... but first 1.
[16:03] <XioNoX> yeah yeah
[16:04] <asac> aleatory?
[16:04] <asac> dont know what that means ;)
[16:05] <XioNoX> sorry
[16:06] <XioNoX> random
[16:06] <XioNoX> trying to make english words with french one :)
[16:06] <XioNoX> so it is a kind of random ?
[16:07] <asac> yes. thats the whole problem ... and thats why i diud that patch to select a specific plugin for a mime-type
[16:09] <asac> XioNoX: if 2. makes our algorithm to return wrong values, then i need to add support to query for what plugin is used in firefox core
[16:09] <asac> but i think we come along that way.
[16:17] <XioNoX> ok
[17:33] <XioNoX> asac, do you know how the list appear when we clic on the pluginlist ?
[17:34] <XioNoX> or at least how to put things on this list ?
[17:34] <asac> yes. the richlistbox has a onsomething listener which basically transforms the row and replaced the right hand label with a drop down
[17:35] <asac> look in the applicaions.xul
[17:39] <XioNoX> it seam to be set by the xml
[17:40] <XioNoX> so I have to name my functions the same
[17:44] <asac> james_w: do we have something like Vcs-Bzr-upstream Vcs-Bzr-release Vcs-Bzr-nextrelease ? where i can point to "upstream", "release" and "nextrelease" branch?
[17:44] <james_w> no, that's not defined by Debian
[17:45] <asac> the situation is like this: release from ~ubuntu-core-dev branch, which receives merges from ~network-manager branch
[17:45] <james_w> I think at least -upstream would be really useful, but they didn't think to include it
[17:45] <asac> and i have the feeling that choosing any of those is always wrong in some way
[17:45] <asac> e.g. using ~network-manager wont give url to get exactly this release
[17:45] <asac> ~ubuntu-core-dev doesnt tell the user where to develop against
[17:46] <asac> james_w: yes, but even if i had upstream i needed more ;)
[18:57] <saivann> asac : ping
[19:18] <gandi> asac: ping
[20:26] <fta> back
[20:27] <fta> asac, "one mui important", "mui" ? wtfit ?
[20:34] <fta> asac, http://paste.ubuntu.com/39500/
[20:36] <asac> mui == much ;)
[20:57] <Siva> Hi asac, wikz tells me that you had some questions about Spicebird
[20:57] <Siva> I'm one of the developers for Spicebird
[21:06] <fta> asac, for nss, i assume it means rebuilding all deps, right ?
[21:07] <fta> i mean rdeps, of course
[22:52] <asac> fta: not sure ;)
[22:53] <asac> maybe its "just" flipping the direction the links point to ;)
[22:53] <asac> and drop the soname patch
[22:55] <asac>         gcc -x c -shared -Wl,-soname,libsoftokn3.so.0d -o debian/libnss3-0d/usr/lib/libsoftokn3.so.0d - < /dev/null
[22:55] <asac> fta: understand what this is ment to do?
[22:56] <asac> make a null lib?
[22:57] <fta> sure but everything linked to the .1d will need to be relinked with the .so
[22:57] <fta> or did i miss something ?
[22:59] <asac> well. current situation is that upstream builds can use our libs
[23:00] <asac> but the other way around isnt true
[23:00] <asac> so they seem to be related still ;)
[23:00] <asac> lets see whats happening without the soname patch ;)
[23:00] <asac> and a bit .links file shuffeling
[23:01] <fta> afaik, we provide .so links but we use the .1d, not the links
[23:01] <asac> right
[23:01] <fta> others could then use the .so or the .so.1d, we couldn't
[23:01] <asac> thats why i think just flipping that link direction might be enough
[23:01] <fta> oh, ok, i mis-read,
[23:02] <asac> 1. drop soname, 2. flip link direction
[23:02] <fta> i read drop .1d/.0d
[23:02] <asac> 3. take care that upgrade really fixes the links (which might be a tricky thing)
[23:02] <fta> could work
[23:02] <asac> most likely .preinst upgrade and abort required
[23:03] <fta> I had too much beers tonight
[23:05] <asac> hmm. i have to recreate the .symbols files i guess
[23:06] <fta> could we drop the kbsd patches then, they are a pain to keep in sync, and we don't need any of this
[23:06] <asac> sure
[23:07] <asac> fta: how do i recreate those symbols from scratch?
[23:07] <fta> move out the files
[23:09] <asac> hmm we get the full package version
[23:10] <asac> the debian ones were just upstream iirc
[23:10] <fta> grr, +300 new rss entries per day, too much to keep up with
[23:10] <fta> eh ?
[23:10] <fta> oh
[23:10] <asac> ah ok -v
[23:11] <fta> or strip manually
[23:14] <fta> mozilla Bug 356295
[23:18] <fta> mozilla Bug 418129
[23:29] <fta> mozilla Bug 450646
[23:31] <asac> oh dear. i hate writing those scripts for upgrade and downgrade case