[00:50] asac: still awake? [00:52] asac: mozgest is ready: https://code.launchpad.net/~bdrung/firefox-extensions/mozgest.ubuntu/+merge/9280 [10:54] hi. When will we push seamonkey 1.1.17 [10:58] to Hardy, Interpid. [10:59] i am using it for some time now, I get source from PPA of gnomefreak [11:00] I see no reason for 1.1.17 Seamonkey not to be pushed to Karmic, Interpid and Hardy. (I am on hardy 64) [11:29] nikolam: yes. thats on my list to do [11:30] e.g. gnomefreak asked me to sponsor it and i failed to follow up yet. [11:31] asac, I can do testing if wanted [11:32] I run 64-bit hardy, i can do testing in vm`s for other versions , too and 32 bit [11:32] nikolam: cool. please add https://edge.launchpad.net/~ubuntu-mozilla-security/+archive/ppa to your sources everywhere [11:32] thats the staging area where we will put security updates a few days before we roll it to the masses [11:33] asac will see to it, where is reporting of results of testing done? [11:33] nikolam: at best complain here if there are regressions [11:33] nikolam: if you give positive feedback thats even better [11:34] ok :) [12:29] nikolam: i am preparing the bits now. so in a few hours there should be hardy - karmic builds to test in that archive [12:31] asac, will see to it. I will probably test hardy on my working hardy 64 [12:31] will prepare other ones [12:31] nikolam: that would be precious [12:32] but i use it on it for some time now, since, i made it myself hihi [12:33] hmm [12:33] maybe i should use gnomefreaks tarball rather than minde [12:34] asac it dies sometimes like 1.1.5 was [12:34] * asac wants to be nice) [12:34] nikolam: dies? [12:34] nikolam: what dies? [12:34] (sorry i think I lack context here) [12:34] yup, i have big inbox`es and news and bunch of windows [12:35] seamonkey, after few hours of hard work :) [12:35] ah [12:35] but i also have flash plugin 10 latest :) [12:35] are you also running 2.0beta1? [12:35] nevermint, see in few hours :) [12:35] or was it alphoa3? [12:36] nikolam: yeah [12:36] I have it installed [12:36] nikolam: does it work good [12:36] ? [12:36] 2 works ok [12:36] or even better than 1.1.7? [12:36] hmm, havent been there for a long time and not shure what version of SM 2 is that , will check [12:37] just wondering if we should rather put 2.0 beta in karmic [12:37] than sticking yet another round with 1.1.7 [12:37] than sticking yet another round with 1.1.x [12:37] 2.0~b1~hg20090512r2611+nobinonly-0ubuntu1.8.04~jjv [12:37] yeah i think they even released b1 upstream already [12:38] asac, Me thinking, 2-0 should sit beside 1.x for now.. it`s not released officially yet [12:38] yeah ... well, but its really not used by many so having it side-by-side means extra effort [12:38] wrt security et al [12:39] I know, but I won`t count on 2.0 to be for production use, untill upstream says so. [12:39] for testing, quite ok [12:40] It is shame btw, that Debian ditched SM (Iceape) from its repos [12:43] nikolam: thought they only ditchted it from stble release [12:43] but not from unstable [12:44] its a security support problem [12:44] asac, i think its not there at all. I think it was unmaintained [12:44] noone has the time to do mozilla security support [12:44] i did that for a good amount of time, but nobody else felt like its their obligation [12:44] now i stopped it for debian [12:44] as i know, mozilla security support is just publishing newer versions of products, yes? [12:45] (i even was accussed of doing it wrong, which is really ridiculous) [12:45] nikolam: thats the case until mozilla stops to support their software. then its painful backporting [12:45] which is what i basically did [12:46] (even though folks are lame they somehow get new upstreams uploaded) [12:46] so the problem was that for years i prepared the individual patches/backports; sent them to all the right folks [12:46] and ended doing _all_ packages on my own [12:47] I am fully interested in doing SM stuff, since I ma using it for very long time. i lack some experience with ppa`s and package management, etc [12:47] nikolam: its really not that hard to prepare new upstream packages for seamonkey [12:47] we have pretty good branches .. that make it rather trivial [12:48] if you want to help out on mozilla packaging just stay in this channel ;) [12:48] I plan to add enigmail for seamonkey later. [12:48] OKi :) [12:48] nikolam: enigmail is probably the worst task you could start with [12:49] But it is done on enigmail forum, i made it myself using instructions there [12:49] its really difficult. i packaged it up in an ugly way at some point by doing some crazy build system hackage ... [12:49] Ok, but later ok. [12:49] ok ;) [12:50] problem is that you need a full source tree to produce enigmail, while want to produce it outside [12:50] ok ttyl [12:50] yes, I also needed to compile all SM to produce enigmail, too [12:50] ok, [12:50] ok hardy is uploading ... intrepid, jaunty, karmic will happen right afterwards [12:50] nikolam: right thats basically the problem [12:50] Nice, will do it in an hour or so [12:51] nikolam: the current enigmail package builds against system seamonkey ... which is the hard part of ti [12:51] asac, maybe putting just .xpi i deb :) [12:51] nikolam: problem is that enigmail has binary stuff in it, so it needs to get built for every arch [12:51] so we cannot just use .xpi packaging ;) [12:51] see this [12:51] http://www.mozilla-enigmail.org/forum/viewtopic.php?f=12&t=616 [12:51] http://www.mozilla-enigmail.org/forum/viewtopic.php?f=12&t=598 [12:52] Ok, cu l8r man [12:52] bye [13:20] asac: did you saw my merge request for mozgest? [13:21] bdrung_: yes. thats next on my list [13:21] seamonkey sponsoring request was like 20 days old :( [13:21] asac: thanks [13:21] * asac wonders if i can just "pull" a merge request ;) [13:22] :) [13:22] maybe pull and push requests should be implemented ;) [13:23] asac: in this case you could just pull it. [13:23] bdrung_: hmm. maybe consider to use topic names for your branches ;) [13:23] like mozgest.ubuntu.2.1.karmic [13:23] or something [13:24] asac: ok, i will try to remember for the next time [13:24] in that way you dont need to trash your branch and you can just mark it as merged and keep it for reference [13:24] yeah [13:24] also i can just brnach both in the same dir without needing to htink about a dir name ;) [13:25] asac: or i become motu and push directly to the repository :) [13:25] bdrung_: can you please make a release commit ? [13:25] like: dch -r -Dkarmic [13:25] then debcommit -r [13:26] e.g. i i run iot like that i own the changelog afterwards [13:26] which i dont want ... i can modify the changelog manually if you dont want to do that now [13:26] let me know [13:27] i will do it. [13:28] ok greawt. [13:28] bdrung_: usually i prefer a commit like: RELEASE 0.0-0ubuntu1 to ubuntu/karmic [13:28] but the debcommit -r does releasing version 0.0-0ubuntu1 [13:28] so i usually do: [13:28] debcommit -r -e [13:28] and then append the "to ubuntu/karmic" ;) [13:29] * asac tries to take a mental note to improve decommit -r [13:29] but if you dont care a debcommit -r is good enough ;) [13:29] (it also tags your branch with the debian version) [13:31] so the new idea where mozilla-devscripts should install the links to is: [13:31] /usr/lib/mozilla/extensions/$TARGET_APPID/$extension_id [13:31] ok, i have pushed it [13:31] thx [13:31] this could be done all magic by parsing install.rdf [13:31] i learn two new command (debcommit and how to remove a tag) [13:32] ;) [13:32] bdrung_: you removed the tag? [13:32] (probably ok here) [13:32] first i used debcommit without -e, then i removed the commit and the tag and run debcommit with -e :) [13:33] asac: $TARGET_APPID? [13:34] bdrung_: yes. if you check install.rdf there are targetApplications with em:id [13:34] those are basically the applications (firefox, etc.) [13:34] thats what $TARGET_APPID is supposed to be [13:35] that basically replaces the need for MOZ_XPI_MOZILLA_DIRS [13:35] we could then also add a mapping for target appids to packages that we could then automatically put in depends of control magically with [13:35] and solves the problem of the names (firefox, abrowser, iceweasel) [13:35] ${xpi:depends} [13:35] or something [13:35] yeah [13:36] well. the name list needs to be maintained somewhere [13:36] but its a central place [13:36] I am waiting for ${xpi:Depends} [13:36] ;) [13:37] asac: so transitions will be easier (firefox-2.0 bug report is still not fixed for all packages). [13:37] bdrung_: did you test the mozgest extension? or do i need to test it? [13:37] ack [13:38] asac: i am currently using it. if you want to test it: https://launchpad.net/~bdrung/+archive/ppa [13:38] no thats ok [13:38] uplaoding [13:38] asac: thanks [13:40] asac: do you sponsor other packages, too? [13:41] bdrung_: sounds like a tricky question ;) [13:42] usually yes. for two extensions prepared i can fastpath another package ;) [13:42] :-P [13:42] seems you have one credit already :) [13:43] bdrung_: are you @bdrung on identi.ca? [13:43] asac: yes, it is. i am waiting for a sponsor for xmms2: ounds like a tricky quest [13:43] copy paste did not work: https://bugs.launchpad.net/ubuntu/+source/xmms2/+bug/398481 [13:44] i do not use identi.ca, but the name "bdrung" is unique on the net. [13:44] http://identi.ca/notice/7031548 [13:44] yeah seems youz hnave no account there ;) [13:45] hmm ... not even on twitter valid [13:47] may i give identi.ca a try? [13:47] till now, i only use a blog [13:48] bdrung_: at least get your account name ;) [13:48] if you use it or not you can decide later ;) [13:48] if twitter is free get one there two ... you can setup identi.ca to mirror your stuff to twitter [13:49] bdrung_: personally i like microblogging, to send out stuff that isn't worth a full blog post [13:54] asac: ok, bdrung now belongs to me. [13:55] bdrung_: great. so the debdiff for xmm2 is quite excessive [13:55] bdrung_: cant we do a minimal one for pulse and get the rest synched from debian? [13:55] or first get it synched and then get the pulse stuff? [13:56] asac: the problem is, that i need a sponsor and then the package needs to go through NEW. the most client updates depends on xmms2-icon. [13:57] asac: so i assume, we have not enough time for that way [13:57] hmm [13:57] bdrung_: thats through binary NEW though, isnt it? [13:57] yes [13:57] binary new is usually much quicker iirc [13:58] bdrung_: noone in the Uploaders has upload power? [13:59] asac: don't know. [14:00] Florian Ragwitz [14:01] 0.6DrMattDestruction-1 [14:01] what kind of funny thing is that? [14:02] i already asked him, but he said, that he has no time. [14:06] asac: rafl is the maintainer (do not count him as uploader) and he has upload rights [14:07] asac: do you use any microblogging program? [14:09] gwibber last i heard [14:09] bdrung_: gwibber, yeah [14:10] in karmic its pretty good now [14:10] still has a bunch of threading issues, but that will go away with 2.0 [14:10] * asac takes a note to review merge requests so we can cut off a 1.2 branch [14:11] bdrung_: have you asked rafl if we would be ok to add Dm-Upload thing? [14:11] * asac runs out to get some stock [14:13] asac: i asked him now and wait for an response now. [14:26] fta: do you think the build failure fro chromium on 25th was an upstream bug? [14:26] i worked against 24th ... wondering if todays build will fail against in libbrowser.so stuff [14:38] fta: hello, i just read in the description of your launchpad ppa that you're not able to maintain updates for some packages. it seems, seamonky is one of them, i can't find it any more. Is that right? I'm on the hunt for a 64bit jaunty seamonkey 2.0 package. Any hints? [14:38] stefg: its been done waiting for upload [14:38] brilliant... thanks [14:38] seamonkey-2 i am waiting to work out problems but if you found it in my PPA than you see 1.1.17 there [14:41] gnomefreak: dont you have a sm2 build in your ppa? [14:41] stefg: i update seamonkey 1 within 2 days of release. That has not changed (assuming i am able to be here) [14:42] asac: yes old one though. has some issues but mostly works well. stefg if you go to my PPA you can use the search to go to succeded builds and pull seamonkey2 out of it if you dont want to add it to sources. list file. here is link [14:42] https://launchpad.net/~gnomefreak/+archive/ppa [14:43] thx [14:43] np [14:45] gnomefreak: stefg i think last successful build should be in the pool stil. so just adding souzrces should be ok (no need to download mnually) [14:45] but i could be wonrg [14:45] wrong [14:45] i'll try and see [14:46] well maybe but PPA only shows the Karmic failed one. [14:46] and its something i know about but havent had a chance to update it to latest version but it will be fixed for that version. [14:47] Package: mozilla-thunderbird None [modified: /var/lib/dpkg/info/mozilla-thunderbird.list] [14:47] it would be nice is Apport would report the version installed. [14:50] alright synaptic is done... let's see [14:50] gnomefreak: sm 1.1.17 is now in -security ppa fwiw [14:50] sorry for the delay [14:50] gnomefreak: can you mark your branches merged? [14:50] gnomefreak: also you had two branches ... i picked the one that also removed the patches ;) [14:53] gnomefreak: i got Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b5pre) Gecko/20090513 SeaMonkey/2.0b1pre from your ppa, while i have Build identifier: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.9.1.1pre) Gecko/20090717 SeaMonkey/2.0b1 running from /opt. This means language pack not working ... [15:01] ... and BTW http://mozilla.qa.ubuntu.com/ needs updating. Dapper Desktop is EOL, may it rest in peace... so should be no more fumbling on FF 1.5 packages necessary [15:06] asac: whitch ones? [15:06] which even [15:08] asac, it give me no upgrade when enabled security repo. :) Will deinstall and install again SM [15:16] nikolam: sm 1.1.17 hasnt been pushed to repos official ones anyway [15:18] asac: on bug 379470 do you see a way to remove the files in comment #1? they are the crash files [15:20] i found it [15:24] gnomefreak, i had made it myself :) [15:26] !info firefox-2.0 jaunty [15:26] Package firefox-2.0 does not exist in jaunty [15:27] it give me no upgrade when enabled security repo. [15:27] its not in repos yet so it wont give you update [15:30] i enabled security repo , installing.. [15:33] We also have much Old noscript. [15:40] asac: if i mark my SM1 dev branched as merged than i have to repush the whole thing again in a few weeks when i update it to 1.1.18 [15:41] i say few week it maybe a moneh but normally they are good with security releases in a month [15:44] marking my (still working from) brnahes as merged isn't something i like doing. The ones that i push to fix bugs im fine with because they are not something i use alot. [15:44] * gnomefreak still looking for grub2 (menu.lst) i know it moved and its named something else. [15:47] it seems to be grub.cfg [15:47] /boot/grub.cfg i really wish they wouldnt do that [15:52] gnomefreak: So it seems seamonkey 2.0b(non-pre) as distributed as .tgz by mozilla directly has difficulties in getting its plugins. So when do you expect the sm-2.0 official beta to hit your ppa? It probably takes me longer to sort the plugin trouble than to just wait for you ppa :-) [15:53] stefg: at this time not sure. im waiting for m-d to get updated since atm its grabbing 2.1 sources [15:53] i will be gone for ~1week after i log off today [15:54] depending on when i get my new glasses [15:54] nikolam: maybe you need to add the ppa key [15:54] ... yu [15:55] i dont know how hardy behaves now that the repos are signed [15:55] gnomefreak: yup... i recently started to need glasses for computer work, too. Man, i'm getting old [15:55] asac: that reminds me. my surgery is tomorrow morning i will not beable to see anything up close at all so i will be back when i get reading glasses :) [15:55] stefg: want to help out with mozilla.qa.ubuntu.com? [15:55] stefg: i would love to resurrect using it for getting pre-QA ... but i usually fail because i am fighting various things [15:55] asac: if i can (and finf time to do so), sure [15:56] stefg: it basically involves setting up new security update builds there when i upload [15:56] stefg: and then sending an announcement to the subscribers [15:56] but thats templated [15:56] asac: thanks for the push for SM1 [15:56] * gnomefreak just opened gwibber [15:56] asac: estimated time needed per day / week ? [15:56] stefg: i see you irc is not always online. i think that would be great so i can dump you a ping when uploading etc. [15:57] stefg: firefox releases every month [15:57] stefg: its a quick thing ... problem is that it needs some responsiveness [15:57] (e.g. we often have like 4 days of testing, so if we get this out on day 3 its not really good) [15:57] usually i would love to have like a week in security QA [15:58] stefg: i think for "regular" releases there should be enough time [15:58] asac: and that's hard for me to guarantee, to be honest. I'm a project manager and if my companie needs to push out some new releases i'm pretty much eaten up by that. [15:58] ok [15:59] stefg: we could do the releases and i can then do those for firedrills if you are not available ;) [15:59] stefg: i know about scheduled releases like 2 weeks up front. so if i upload and the qa announcement takes a day or two its not a problem [16:01] bdrung_: http://paste.ubuntu.com/233933/ [16:01] also: find debian/mozgest | pastebinit [16:01] http://paste.ubuntu.com/233935/ [16:01] not sure why dh_link is in there though ;) [16:02] well. and MOZ_XPI_MOZILLA_EXTRA_DIRS is not yet implemented ;) [16:05] asac i installed SM from security repo seems to work ok, together with new addons [16:06] what is testing procedure [16:06] asac: looks, good. will test it. [16:08] asac: Alright, i don't think i will get overwhelmed by that. So how is it going to work ? [16:08] asac: do you push it to the bazaar branch? [16:09] bdrung_: yes ... i want to check with a real package first though ;) [16:14] asac: how about moving the temp-xpi-unpacked directory to debian/temp-xpi-unpacked? [16:15] asac: check MT Ml post for Freedy please. I am gone now have fun this week ill be back as soon as i can [16:19] asac: your patch works with mozgest [16:20] bdrung_: committed [16:21] bdrung_: hmm. maybe debian/temp-xpi/unpacked [16:21] asac: or that. hauptsache its in the debian directory [16:21] bdrung_: does firefox still pick it up with the new links? have you checked? [16:22] asac: i only testing building. now i will test install. [16:22] yeah. thats probably the more "important" part of it [16:24] stefg: thats a good question. i think you need to get an account first [16:24] otherwise its hard to explain [16:24] the UI is a bit retarded (at least when i used it last time) [16:25] its basically adding the new build for each ubuntu release [16:25] asac: no, firefox does not pick it up. [16:25] asac: lp-account ? i have one [16:26] stefg: i am not sure if its coupled with lp yet. i dont think it. [16:26] bdrung_: hmm [16:26] bdrung_: firefox 3.5? [16:26] asac: both 3.0 and 3.5 (using jaunty packages) [16:26] that sucks ;) [16:26] are the ids correct? [16:27] bdrung_: maybe ffox 3.6? ;) [16:27] let me check the code [16:27] asac: mom [16:28] asac: why do i have an empty /usr/share/mozilla/extensions directory? [16:29] asac: ls /usr/lib/mozilla/extensions: {3550f703-e582-4d05-9a08-453d09bdfdc6} {ec8030f7-c20a-464f-9b0e-13a3a9e97384} {92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a} [16:30] asac: I found the bug [16:30] ? [16:30] asac: you said /usr/lib/mozilla/extensions/$TARGET_APPID/$extension_id should be used, but /usr/lib/mozilla/extensions/$TARGET_APPID/ was used [16:31] oh yeah [16:31] ;) [16:31] good catch [16:31] can you check it manually? [16:31] yes [16:32] bdrung_: http://paste.ubuntu.com/233947/ [16:32] try that [16:32] oh sorry ;) [16:33] http://paste.ubuntu.com/233949/ [16:33] rather that one [16:34] bdrung_: ^^ [16:36] dh_link -pmozgest /usr/share/mozgest /usr/lib/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/; dh_link -pmozgest /usr/share/mozgest /usr/lib/mozilla/extensions/{3550f703-e582-4d05-9a08-453d09bdfdc6}/; dh_link -pmozgest /usr/share/mozgest /usr/lib/mozilla/extensions/{92650c4d-4b8e-4d2a-b7eb-24ecf4f6b63a}/; [16:36] ln: angegebenes Ziel „debian/mozgest/usr/lib/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/“ ist kein Verzeichnis: No such file or directory [16:36] bdrung_: XPI_EMID is empty? [16:36] odd [16:37] oh [16:37] http://paste.ubuntu.com/233952/ [16:38] bdrung_: that makes a call out of it ... which hopefully does the trick [16:40] asac: the links destination is now wrong [16:40] ? [16:40] /usr/share/mozgest [16:41] is the right location. isnt it? [16:41] at least it seems to crate the expected links now [16:43] it points to the location with the install.rdf. ... that should be ok [16:44] its the same target that was used before [16:44] asac: something went wrong, when i installed the package. after purging and reinstalling the links are now correct. [16:44] asac: firefox-3.5 works [16:45] asac: firefox-3.0, too [16:45] really great [16:45] thats indeed good news [16:45] thanks [16:45] bdrung_: i think you might have had problems because there were wrong links before [16:46] so it basically created the links inside the mozgest directory after following the existing links during install [16:46] which certainly might have messed up stuff [16:46] badly [16:46] seams plausible [16:47] asac: do you work on ${xpi:Depends}? [16:47] bdrung_: thats one of the next things. didnt plan to do that today though (want to do some game playing now ;)) [16:48] bdrung_: if you want go ahead. you just need to find a good way to specify a ID -> package mapping [16:48] and then append a variable xpi:Depends= .... in debian/$(MOZ_EXT_PACKAGE).substvars [16:48] asac: we could use a config file for that [16:48] bdrung_: yeah. though i would prefer to keep all in the xpi.mk [16:49] asac: do you know how to check the version? [16:49] maybe something like XPI_APPID_MAP_{xxxx-xxx-xx} = firefox-3.0 firefox-3.5 iceweasel firefox firefox-3.6 [16:50] maybe something like XPI_APPID_MAP_{yyyy-yyy-yy} = thunderbird thunderbird-3.0 thunderbir-3.1 icedove icedove-3.0 icedove-3.1 [16:50] bdrung_: the version makes it difficult imo [16:50] bdrung_: i would be happy to have something like above for now [16:50] i have to test if 3.5 is lower than 3.6a1pre, e.g. [16:50] we could also do something like: [16:51] asac: do you know a program which can determine this relation? [16:51] XPI_APPID_MAP_VERSION_CHECK_thunderbird = $(shell test $(1) lt 2.0.0. lt $(2)) [16:51] (that wont work [16:51] bdrung_: we need to write somethign on our own [16:52] XPI_APPID_MAP_VERSION_CHECK_thunderbird = $(shell test $(1) lt 2.0.0. lt $(2) && echo yes) [16:52] ;) [16:52] asac: i am good in writing ugly looking makefiles: http://code.google.com/p/gnome-colors/source/browse/trunk/gnome-colors/Makefile [16:53] why should e.g. firefox be an dependency? to which version of firefox do the firefox package refer? [16:53] bdrung_: cool. so you are the right candidate for extending this already ugly looking xpi.mk ;) [16:53] asac: do you know gnome-colors? [16:54] bdrung_: you are right. firefox was the equivalent for icedove (e.g. icedove-2) [16:54] we shouldnt use that [16:55] no i dont know gnome-colors [16:55] asac: should we use the same dependency for debian and ubuntu packages? or should the debian package depend on iceweasel, and the ubuntu one on firefox? [16:56] asac: http://www.gnome-look.org/content/show.php/GNOME-colors?content=82562 [16:56] asac: http://www.gnome-look.org/content/show.php/Shiki-Colors?content=86717 [16:56] asac: http://www.gnome-look.org/content/show.php/Arc-Colors+GDM-Walls?content=88305 [16:56] asac: it the best theme i saw. [16:56] bdrung_: i think we can add both [16:56] hey kids [16:57] asac: https://bugs.edge.launchpad.net/bugs/404624 [16:57] can you mark it WontFix please [16:57] bdrung_: at least debian folks might have unofficial repo with our packages ported or something [16:57] bdrung_: and i have no problem to have unofficial repos with ice* ported to us if that exist [16:57] at least i wouldnt mid [16:58] asac: ok, that makes it easier [16:58] BUGabundo: done [16:58] asac: thanks [16:58] bdrung_: could be that debian pkg-ext maintainer complain, but i think its ok. we share the app id and most extensions should not be a problem to use back and forth [16:59] bdrung_: at some point we might want to add magic to determine xulrunner min version during linking [16:59] asac: can you push your fixes? [16:59] if it contains binary components [16:59] bdrung_: yes [17:00] asac: how can i grab em:maxVersion from a specific em:id? [17:02] bdrung_: 207 [17:02] bdrung_: thats painful [17:02] bdrung_: lets do the filtering later [17:03] bdrung_: basically using xpath [17:03] asac: the poor rickspencer subbed to me on identica! [17:03] :p [17:03] haha [17:03] not a good experience if you dont have many subs ;) [17:04]