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