[12:27] hmm, well this machine has been up for.. 23:27:16 up 4 days, 11:20, 2 users, load average: 0.15, 0.34, 0.41 [12:27] without any restarts.. [12:27] maybe you logged out? [12:27] and in? [12:27] not that I can think of.. [12:28] I am the only user of the computer.. [12:28] strange.. [12:28] maybe a crash? [12:28] while dragging bookmarks :-P [12:28] :) [12:28] lol [12:28] :) [12:28] probably [12:28] honestly i am not sure when bookmarks.html is updated ... e.g. directly when you change bookmark state [12:28] or if you close [12:28] i think the former [12:29] maybe your disk was full? [12:29] this is known to cause plenty problems [12:30] bad thing is that thunderbird is already build :) [12:30] probably i should push fixed version soon [12:31] hmm, disk is nowhere near full [12:31] if i am lucky people will hold back because enigmail or locales are not yet there :) [12:31] crazy thing [12:31] and you don't remember some kind of crash? [12:31] nope [12:31] e.g. maybe even during upgrade? [12:31] hmm, not that I can think of [12:32] or you needed to kill firefox processes? anything else which was "not normal" ? [12:32] then nevermind ;) [12:32] I kill firefox processes all the time lol [12:32] really? [12:32] never did any harm before lol [12:32] yeah ... but there is the chance ... you know the unlikely chance [12:32] yeah, alot when viewing about 30 tabs [12:32] :) [12:33] you kill? [12:33] e.g. like kill PID [12:33] ? [12:33] or through gnome process list? [12:33] well I use killall firefox-bin [12:33] oha [12:33] yeah ... ok then we should file it under that category :) [12:33] thanks for trying though. [12:34] ;) [12:34] yeah, most likely.. no problems :) [12:38] hehe [12:38] https://bugs.launchpad.net/bugs/111818 [12:38] Launchpad bug 111818 in firefox "firefox choose helper application dialog is useless" [Undecided,Confirmed] [12:38] i somehow don't get where people get the energy to talk so much trollish things [12:38] like ... "The choose-helper-application dialog is fundamentally broken in a way [12:38] that's not fixable." [12:39] hmm, I am getting the SSL error now [12:39] then ... File type association and the required user [12:39] interface for it is a tricky process that is quite hard to get right. [12:39] AlexLatchford: yes [12:39] you can fix it like [12:39] cd /usr/lib/firefox (as root) [12:39] ln -s ../nss/libnssckbi.so [12:40] all done as root [12:40] or ln with sudo :) [12:40] ta [12:40] same for tbird 2.0 if you use it [12:41] aha okay [12:41] anyway ... this shows us that not many people are using preview archive [12:41] which we should find a way to change :) [12:42] as its exactly the reason why we have it ;) [12:42] especially when doing major packaging changes [12:42] maybe once gnomefreak is a bit more used to the procedures we should spread the word [12:42] yes [12:43] and at best keep firefox-trunk out of official archive for some time ... e.g. to attract more users ;) [12:43] bad trick ... i know ;) [12:44] even the firefox test plan https://wiki.ubuntu.com/MozillaTeam/QA ... would have revealed that ;) [01:11] ok night === [Cade2] [n=[Cade] @adsl-218-39-122.asm.bellsouth.net] has joined #ubuntu-mozillateam === Cade3 [n=[Cade] @adsl-152-219-198.asm.bellsouth.net] has joined #ubuntu-mozillateam === ubotu [n=ubotu@ubuntu/bot/ubotu] has joined #ubuntu-mozillateam === [Cade2] [n=[Cade] @adsl-224-112-177.asm.bellsouth.net] has joined #ubuntu-mozillateam === hjmf [n=hjmf@6.Red-88-25-28.staticIP.rima-tde.net] has joined #ubuntu-mozillateam === AlexLatchford [n=alex@82-44-193-109.cable.ubr07.haye.blueyonder.co.uk] has joined #ubuntu-mozillateam [10:27] asac: you going to Seville? [10:28] sure [10:28] tomorrow is ramp up ;) === DarkMageZ [n=richard@ppp17-170.lns1.adl2.internode.on.net] has joined #ubuntu-mozillateam === DarkMageZ_ [n=richard@ppp168-24.lns4.syd6.internode.on.net] has joined #ubuntu-mozillateam === DarkMageZ__ [n=richard@ppp36-84.lns4.adl2.internode.on.net] has joined #ubuntu-mozillateam === IdleOne [n=idleone@unaffiliated/idleone] has joined #ubuntu-mozillateam === pochu [n=emilio@ubuntu/member/pochu] has joined #ubuntu-mozillateam === pochu waves! [02:26] asac: the latest firefox upload has broken liferea, it now segfaults at startup, and doesn't build anymore as it is [02:27] checking for MOZILLA... no [02:27] firefox: nochecking for MOZILLA... no [02:27] configure: error: [02:27] *** You must have either the GtkHTML2, XulRunner or the Mozilla [02:27] *** development libraries installed in order to build Liferea! [02:28] but there is firefox-dev 2.0.0.3+3-0ubuntu1 there [02:29] asac: do you know why this can be? [02:41] hmm [02:41] right [02:41] can you try a respin please? [02:41] pochu: ^^^ === asac currently fiddling with wireless network :) [02:42] pochu: what does lifeares use in confiigure.in ? [02:42] firefox-config ? or pkg-config? [02:48] damn ... my archive mirror is pretty slow now [02:48] ok lunch [02:55] asac: tell me when you're back === hjmf [n=hjmf@6.Red-88-25-28.staticIP.rima-tde.net] has joined #ubuntu-mozillateam [03:29] asac: it uses pkg-config [03:41] pochu: maybe look what test fails ... so we know more === ajmitch [n=ajmitch@ubuntu/member/ajmitch] has joined #ubuntu-mozillateam [04:33] asac: this is where liferea looks at the mozilla engine: http://pastebin.ca/470798 [04:44] emilio@kiko:~$ pkg-config --libs-only-L firefox-gtkmozembed [04:44] Package nspr was not found in the pkg-config search path. [04:44] Perhaps you should add the directory containing `nspr.pc' [04:44] to the PKG_CONFIG_PATH environment variable [04:44] Package 'nspr', required by 'XPCOM', not found [04:44] emilio@kiko:~$ [04:45] that's wasn't happening with previous firefox, IIRC [04:45] If I'm true, listen shouldn't build, too [04:46] s/true/right/ [04:52] yes, it fails [04:53] So that's the reason they're failing, I think [04:53] asac: do you know why that's broken? [04:54] debian/control.in, debian/control, debian/rules: use system-nspr and system-nss; drop libnss3 and libnspr4 and friends from control files; remove debhelper files accordingly [04:54] ^ Maybe that's the reason [05:34] hmm [05:34] pochu: [05:35] can you paste the configure.in section that tests this? [05:36] is libnspr4-dev installed for you? [05:38] asac: it isn't, but if I try to install it, it wants to remove half of my system [05:40] pochu: yeah right [05:44] maybe if I add it to build-depends... [05:47] asac: I tried to follow a comment i got in revu about the package [05:47] asac: the best solution would be to apply it on the gtorrent-viewer dir right after unpacking it, and add automake1.4, intltool to Build-Depends (so that itll rerun autotools during the build only), and you should have a cleaner diff.gz. [05:48] asac: I tried doing it, but it mess all up [05:48] asac: do yout think is it possible to do? [05:48] asac: wow, it has worked! :) [05:48] gonna test it now [05:48] pochu: what has worked? [05:49] sorry i dropped the ball :) [05:49] asac: liferea has built :) [05:50] what did you do to fix it? just upgrade everything to latest? [05:50] asac: nope, add "libnspr4-dev" to build-depends [05:50] does that make sense? [05:51] without it, pkg-config didn't find gtkmozembed, I think [05:51] and it really needed a rebuild, because it was crashing [05:51] just after launching it [05:51] it didn't started, even [05:59] asac: both liferea and listen aren't working, so I suppose every other application using the gtkembedmoz engine won't work anymore, and will need a rebuild [05:59] asac: is that ok? [05:59] I say it to upload a new liferea or not :) [06:04] pochu: i think you just have to change build depends to libnspr4-dev [06:04] not libnspr-dev [06:04] if you use libnspr-dev ... packages might not get upgraded properly [06:05] maybe i need to add a conflict somewhere [06:05] but yes ... all applications probably need a respin [06:08] asac: ok, then I'll do it! [06:08] thanks for your help [06:09] and for the transition, you might want to mail the ml :) [06:11] yes definitly :) [06:11] i have to upload another firefox before ... as not all headers had been included properly [06:11] but then i will do :) [06:12] :) [06:12] btw I already have a debdiff for liferea :) [06:12] I'm fast! :-) [06:13] wow :-P [06:49] bluekuja: running autotools during build is usually evil [06:49] asac: :D [06:50] and actually automake-1.4 appeared to have caused the problems ... so if you do it ... use latest automake [06:50] asac: I think that diff problem is quite impossible to make more clean [06:50] you can repack upstream tarball [06:50] e.g. unpack ...run autotools ...pack again [06:51] do you think that GTorrentViewer problem wont happen? [06:51] and BUG upstream to do it for you :) [06:51] when? [06:51] asac: nevermind [06:52] asac: didnt see your text above [06:52] asac: now i try to do it [06:52] unpack, autools, and repack [06:52] gonna ping you with results soon [06:52] yes ... add something to upstream version [06:53] probably i am gone ... i have to finish preparations for travel [06:53] :) [06:53] but you can try [06:53] if you repack ... remove debian directory as well from tarball [06:54] bluekuja: ^^^ [06:54] asac: :D [06:54] asac: going to sevilla? [06:55] yes [06:56] asac: cool, do you travel to italy too sometimes? [06:56] at least if i didn't mess up my booking completely :) [06:56] if there is UDS ;) ... otherwise depends on my holiday planning [06:57] asac: if you come....I'll give you my phone number [06:57] and we can meet somewhere [06:57] :P [06:57] in italy [06:57] sure ... where are you based? [06:57] near venice :D [06:58] oh nice ;) [06:59] asac: for dpkg-source -x should I use diff from revu as you did? [06:59] after unpacking, autotools, repacking [07:00] good question ... try to figure out :) ... if you do right your diff should almost the same then what i posted [07:00] but remember to keep the changelog from upstream debian/ directory [07:00] mmmm...what you mean? [07:01] upstream changelog should be placed where? [07:01] you add it to your debian/ dir [07:01] and add your new entry [07:01] e.g. reuse it [07:01] oh....you mean adding a new entry in debian/changelog with last changes? [07:01] e.g. upstream changelog because ubuntu changelog [07:02] just keep the change histroy of upstream when you delete debian/ dir in upstream tarball [07:02] oh ok [07:02] now I have to figure out [07:02] with that problem [07:03] :D [07:03] ok ... out for a while [07:03] ok ;) [07:03] you will do it ... you learn most if you discover how to do on your own :) [07:11] asac: diff file now it's 10000 lines instead of 21000 [07:11] as before [07:11] 60kb instead of 140 kb [07:12] asac: not really clean as your one (2.9 kb) lol [07:13] asac: still to big? [07:17] asac: rebuilded it....now i get a 2.1 kb diff file [07:18] but it get GTorrentVIewer problem [07:18] damn [09:38] <[Cade2] > Just want to thank you guys for getting FF and TB2 packaged up finally =D [09:47] asac: How do I output diff's to a file? [09:48] I grabbed a copy of TB's source and am messing about trying to create patches, I can get it to see the diff's I have made, but cannot work out how to output them to a file like in the debian/patches format.. [09:56] how do you see the diffs you made? [09:57] AlexLatchford: ^^ [09:57] in the terminal window [09:57] I just added some random text to a few files.. [09:57] asac: README problems fixed [09:58] I am presuming there is just an option I pass to get it to output them into a file.. [09:58] just the help message is darn confusing.. [09:58] AlexLatchford: there are two cases: [09:58] 1. you change something below debian/ [09:59] 2. you change something in mozilla source (e.g. build-tree/mozilla) [09:59] 1. is simple [09:59] I made changes in /mozilla [09:59] in build-tree/mozilla ? [09:59] yes, just some dummy ones.. [09:59] ok [10:00] how do you see the diffs at the moment? [10:00] e.g. you said: "I can get it to see the diff's I have made" [10:00] ? [10:01] Well say I have added the line '' to an XUL file, it then repeats the command back to me.. [10:01] the line even [10:01] but doesn;t seem to produce a diff file under the directory I am running the command from.. [10:01] ah ok [10:01] ok [10:01] we have quilt for patch management [10:02] and you should use it to maintain changes [10:02] its not that difficult [10:02] aha okay [10:02] it just needs a bit concentration that you actually register files you are going to change [10:02] e.g. [10:02] you start from clean sources [10:02] e.g. abort a build [10:02] now if you want to add some feature [10:02] or some change you do: [10:02] https://wiki.ubuntu.com/MOTU/School/PatchingSources [10:02] ah, makes sense [10:03] look in the bottom most box [10:03] you see it? [10:03] its: [10:03] quilt push -a [10:03] yes. [10:03] ... [10:03] and so on [10:03] yeah yeah, seems fairly simple [10:03] right [10:03] give it a try :) [10:04] I will, may as well give the programming knowledge I have trying to fix some of the problems users have [10:04] to produce a patch i the current form i use refresh like this [10:04] quilt refresh --diffstat -U8 [10:04] ;) [10:04] yeah [10:04] go ahead [10:04] aha okay [10:04] if you have edited files that you registered with the topmost patch (see wiki example) [10:05] it will automatically update the diff (or add the new one) [10:05] hmm okay [10:06] just play around with quilt and read manpage [10:06] its fairly simple [10:08] yeah I will do [10:08] but can be tricky ;) [10:09] I know a lot of programming concepts, not many languages though, but it shouldn't be too hard to pick up.. [10:09] yeah [10:14] asac: you flying out to Seville tomorrow? [10:14] prog. concepts are important, but practice is still the single best way :) mozilla code might be tough to start with ;) ... but of course exciting. [10:15] yep [10:15] AlexLatchford: yes [10:15] cool cool [10:16] I am getting the concept of the patching system now, its to allow patches to be abstracted from the core code.. [10:16] good thing for mozilla is that there are various things you can do ... e.g. start with xul, javascript (chrome)... go to more complex javascript components ... then high-level C++ components and then core components :) [10:16] (Was unaware of that before) [10:16] yeah [10:16] AlexLatchford: yes you might say it that way ... though it sound academic :) [10:16] I already know a fair amount of javascript [10:16] (I am like to sound posher than I really am lol) [10:17] sed -i '1 s/^/MUHAHA/' README [10:17] I dont really understand this line.. [10:17] its just a line to change something [10:17] e.g. replace that in your thoughts with editing README file [10:17] or any other file you previously added to your patch [10:18] yeah, I figured it was replacing something, but it is to the README file.. cool [10:18] because README was added further above i guess :) [10:19] hmm okay.. so this basically is allowing you to only change small sections at a time, 1/2 lines [10:19] no you can change as much as you like :) [10:20] but you have to type it into the terminal? [10:20] the sed commmand is just a synonym for "change as much in README file as you like" [10:20] or can you supply files as arguements? [10:20] hmm okay [10:20] i hope you don't want me to explain sed? [10:20] I wont :) [10:20] e.g. as it doesn't matter for this case ;) [10:21] I get the concept of sed :) [10:21] just remember to add a file you want to change to the patch you want the changes to be included in [10:21] then edit that file [10:21] and do quilt refresh [10:22] actually the quilt pop -a unapplies all changes at the end [10:22] which is usually not what you want [10:22] ahhh, okay [10:22] but its just a demonstration [10:22] you can push them all [10:22] or just push some [10:22] yes I see [10:22] or delete a patch you don't want anymore [10:22] yes [10:22] e.g. pop - unapply ... push - apply [10:22] yep [10:23] http://www.xulplanet.com/ [10:23] http://developer.mozilla.org/en/docs/XUL [10:23] those are good places to start with [10:23] probably firs the mozilla link [10:23] then the xulplanet as kind of api reference [10:24] thanks :) [10:24] http://developer.mozilla.org/en/docs/Main_Page [10:24] thats the mainpage of course :) [10:29] btw, mozilla guy finally came to blog about our patch approval :) [10:29] http://steelgryphon.com/blog/?p=100 [10:29] its the blog of mike connor ... owner of the firefox code module in mozilla tree [10:29] http://www.mozilla.org/owners.html [10:30] good place to see what magnitude the mozilla project has :) [10:31] nice [10:34] asac: is possible to optimize javascripts fonts in mozilla? === Naddiseo [n=Naddiseo@d199-126-254-166.abhsia.telus.net] has joined #ubuntu-mozillateam [10:39] asac: hehe, working nicely [10:40] simple little tool that.. [11:03] bluekuja: dunno what you mean by "javascripts fonts" [11:04] asac: a guy reported that when a java application is open in firefox, fonts are quite unreadable [11:04] so he asked if is possible to change/modify them [11:05] *it's [11:06] so ... java is not javascript [11:07] java applets have their own fonts [11:07] i am the wrong guy to ask about how they do integrate with mozilla [11:07] aeh with ubuntu [11:07] ;) [11:18] Admiral_Chicago: the branch urls have changed ... bughelper code was moved to new team realm "~bughelper". cluefiles are still at ~bugsquad [11:19] Admiral_Chicago: just read of proposed mentorees in bts [11:38] asac: i saw that on the ML, i'll review them soon [11:39] and let people know that soon === bluekuja [n=andy@ubuntu/member/bluekuja] has joined #ubuntu-mozillateam === AlexLatchford [n=alex@82.44.193.109] has joined #ubuntu-mozillateam [12:11] Admiral_Chicago: fine [12:11] lets see how this works out :) ... i am excited ;) === Mirv [n=tajyrink@vipunen.hut.fi] has joined #ubuntu-mozillateam === asac_ [n=asac@e177170006.adsl.alicedsl.de] has joined #ubuntu-mozillateam === Naddiseo [n=Naddiseo@199.126.254.166] has joined #ubuntu-mozillateam === IdleOne [n=idleone@68.84.49.90] has joined #ubuntu-mozillateam