=== bjf is now known as bjf[afk] [00:29] if anyone has a second to answer a packaging question... I'm trying to package something that has a gconf schema file. On openSUSE and Fedora, there are some macros in the spec file to add that schema. I was wondering what the Ubuntu way of doing this was? (Still fairly new to Ubuntu or deb packaging) [00:32] sshaw, we have dh_gconf to handle gconf schemas [00:32] how you call that depends on how you're packaging your application [00:33] chrisccoulson: this particular package is at-spi2-atk [00:33] I think its just one key to determine whether to use at-spi or at-spi2 [00:33] eg, if you're using CDBS, including /usr/share/cdbs/1/class/gnome.mk will add the right hooks for you automatically [00:33] its not cdbs [00:34] i have a case of deja-vu here, i'm sure somebody has asked me about at-spi2-atk before :/ [00:34] perhaps i'm just going crazy though ;) [00:34] chrisccoulson: I'm can't remember if I have asked before or not [00:34] i think you have ;) [00:34] you might want to take a look at other gnome apps [00:34] wow, my memory just sucks :) [00:36] I'd assume gedit would be a good example? [00:37] vish: ping [00:39] sshaw, possibly, although i don't know what packaging system at-spi2-atk is using [00:40] chrisccoulson: how can I tell? [00:40] I'm pretty sure its not cdbs [00:40] I can tell you how I packaged it [00:43] actually, as I'm looking at it it looks like it already handles the keys [00:43] can't believe I missed that [00:43] my brain is fried [00:44] ;) [00:44] I think one of the other guys put that in without me knowing it [00:45] luckily these packages will eventually be part of the distro and I won't have to worry about them anymore :) === awalton is now known as awalton__ [01:21] vish: ping pang pong [01:46] dammit, vish :p [02:45] robert_ancell hey dude [02:47] rickspencer3_, hey [02:49] robert_ancell, so ... any change you could spend some more time looking at that cheese bug? [02:50] it's been driving me a bit crazy thinking about it having it in maverick ... and somehow you seem like the guy who can crack it [02:50] rickspencer3_, I'm going to have a look at it today. (yesterday was frantically updating gnome) [02:50] robert_ancell, cool man, thanks [02:51] let me know if you need anyone to send you any hardware or anything like that [02:52] rickspencer3_ ok, will do. Did you add any comments about the hw you have? [02:53] robert_ancell, no [02:54] robert_ancell, what info would help? [02:54] rickspencer3_, yes please, so we can compare the behaviour on our hw and see if it's hw specific [02:55] robert_ancell, right, so I'm looking for the model # of my webcam [02:55] meh, robert_ancell I just realized I'm at a different computer, atm [02:55] I'll track it down when I get back to my desk [03:12] urk, these gstreamer pipelines remind me of writing old school sql queries [03:15] rickspencer3_, heh :) === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away [04:05] robert_ancell, so I'm trying to capture video output on Lucid at 30fps ... [04:05] gstreamer seems to not be keeping up [04:06] so ... I'm not surprised to see regressions in cheese, I wonder if it's it a bit hard to make this work [04:08] rickspencer3_, yeah, there seems to be a lot of performance issues in gst [04:10] robert_ancell, hmm, when I use avimux it works just fine [04:10] so maybe something about theora? [04:15] rickspencer3_: How much CPU usage when you are capturing? [04:16] TheMuso, I'm on my lucid netbook atm [04:16] so, it's probably at best tangentially related to the maverick cheese bug [04:16] but you ask a good question [04:16] ok [04:16] * rickspencer3_ tests [04:17] recording and displaying with avimux = 16% of one core [04:18] with oggmux it's 97% of one core [04:20] oops, robert_ancell TheMuso cheese can't record on my Lucid netbook either! [04:20] I never thought to test it, but it's got 100% of one of my cores [04:20] rickspencer3_: Were you using the same codec for avimux and oggmux? [04:21] uh, I don't know [04:21] I'm just fidling with gstreamer pipelines [04:21] rickspencer3_: it's more that just theora because you can encode using videotestsrc [04:22] robert_ancell, I'm a bit weirded out that I'm seeing this on Lucid, I thought it was a maverick issue [04:23] TheMuso, here's what I know ... this works: [04:23] queue ! avimux ! filesink location=boo.avi [04:23] this pins the CPU: [04:23] theoraenc ! queue ! oggmux ! filesink location=boo.ogg [04:26] nice, meanwhile desktopcouch comes along and takes up 50% of each core [04:27] If you run with GST_DEBUG=v4l*:5,theora*:5,GST_QOS:5, it shows there are about 2 frames per second being generated. But playing back the video doesn't show this. It's like the video is corrupted (it doesn't play smoothly in totem) [04:29] Does anyone know of a tool to dump information about a video file? e.g. number of frames [04:30] From what I remember, the ffmpeg commandline tool wasn't terrible. [04:30] But might not give all the info you want. [04:31] If videotestsrc works but v4l2src doesn't, maybe it's an interaction between timestamps and oggmux? [04:31] robert_ancell, I think mencoder has like every function you could want [04:34] RAOF, does this sound interesting: 0:00:16.537149013 9190 0x22e7470 DEBUG theoraenc gsttheoraenc.c:823:theora_enc_is_discontinuous: Incoming TS 0:00:16.244409842 exceeds expected value 0:00:16.024553226 by too much, marking discontinuity [04:37] Possibly - that looks like the incoming frame is arriving ~.2 sec later than the encoder is expecting. [04:37] That said, why is the encoder looking at the timestamps anyway? I obviously don't know enough about theoraenc. [04:37] hmm, I run "ffmpeg -i test.ogg -r 1 -s WxH -f image2 test-%03d.jpeg" and I get "incorrect frame size" [04:38] oh, no I needed to replace WxH [04:38] :) [04:39] heh [04:39] Interesting - that shows 13 correct frames - so the video data is there, totem just isn't able to play it [04:39] rickspencer3_: can you confirm if you get the same? [04:40] robert_ancell, sorry, I wasn't paying attention, can you tell me exactly what you want me to repro? [04:40] * rickspencer3_ keeps playing with his new webcam app [04:40] rickspencer3_, encode an ogg from you v4l2src, confirm it doesn't play back properly in totem, then run "ffmpeg -i test.ogg -f image2 test-%03d.jpeg" and see if it does have valid video frames inside it [04:42] robert_ancell, what does "doesn't play back properly" entail? [04:42] oh, you don't even need the "-f image2" [04:42] in my case, I see one or a few frames in the output ogg, but ffmpeg shows it does have all the frames [04:42] I'll reproduce with cheese [04:43] robert_ancell, cheese is just flat unusable on this machine [04:44] (well for capturing video anyway) [04:46] robert_ancell, it didn't seem to report an error, but I the resulting jpegs are garbage in eog [04:47] weird [04:48] robert_ancell, well, I am on lucid here [04:48] shall I run upstairs and try on my maverick desktop? [04:49] rickspencer3_, worth a try [04:50] I heard v4l had a reputation for being broken, it may have improved since lucid [04:50] What about using a different codec... [04:56] TheMuso, what encoders do we have in Ubuntu that you can use? [04:57] I was looking but theora sounded like the only available one [04:59] robert_ancell: ffmpeg via the gstreamer ffmpeg package. No idea about how to use it ina pipeline I'm affraid. [05:00] robert_ancell, I'm at my desktop again [05:00] Encode to mpeg or something similar [05:00] There's a hundred and one ffenc_* options available. [05:00] RAOF: heh [05:00] xvidenc might be a winer [05:00] Or even a winner. [05:01] RAOF: separate gstreamer plugin? [05:02] I*sigh* [05:02] robert_ancell, cheese just worked perfectly for me [05:03] rickspencer3, *sigh* [05:03] hmmm [05:04] If I run cheese on the lowest resolution the output video seems to stabilise after 10s. Not sure if this is expected behaviour for a video codec [05:04] hmm, I did just do a dist-upgrade [05:06] robert_ancell, I give up! [05:06] * rickspencer3 thirsts for beer [05:06] actually, I wonder if my webcam app will work on this computer with theora? [05:07] oh, someone updated cheese... [05:07] lol [05:08] don't tell me this was fixed upstream and we just spent all this time debugging it :/ [05:08] lol [05:08] fml [05:11] robert_ancell, I'm seeing the same issue with oggmux in my gstreamer pipeline on maverick as well (that I was seeing on my lucid netbook) [05:12] the performance still seems bad, very hard to tell if it's as bad as it was on lucid. It's a little unpredictable [05:12] The NEWS file doesn't suggest anything major has changed [05:12] hmmm [05:13] well, I really need to roll [05:13] sorry I can't "help" more :/ [05:13] go forth and drink beer! [05:13] :) === oubiwann-away is now known as oubiwann === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away [07:23] sabdfl, I think I can see why you chose natty. Look at the definition on this page http://www.thefreedictionary.com/natty - "Neat, trim, and smart; **dapper**." [07:23] XD [07:27] and471: you missed jaunty :p [07:28] :) [07:35] kenvandine, just read you post on libgwibber - looks interesting :) [07:35] kenvandine, does this mean we should replace the call to 'gwibber-poster' in software-center [07:36] kenvandine, and replace it with something like in your python example? === almaisan-away is now known as al-maisan [08:30] and471: just keepin' it real :-) [08:30] sabdfl, :) [08:31] and471: we need to take away sabdfl's thesaurus ;) [08:31] vish: or remove certain entries from it. [08:32] hehe [08:33] and471: he is having too much fun with it, while we keep guessing what he is gonna name it next.. *or* now that we have found a pattern, we can guess it easier next time :p [08:54] seb128, hey, can you check my update for evince? I think I've got all the library stuff right this time. Not sure if both shlibs variables should be updated though [08:54] hey robert_ancell [08:54] I was just reading your email [08:54] soname is age-revision usually [08:56] hum, not awake yet [08:56] current - age rather [08:57] ie the first and the third number in the 1:2:3 [08:57] ie 5:0:1 -> 5-1 == 6:0:2 -> 6-2 [08:57] seb128, the rule is, only update if you see n:0:0 right? [08:58] the soname changes on abi breakage, ie when the age is set to 0 [08:58] the rule is "match the installed filename on the disk" [08:58] it's easier than trying to read the configure.ac logic ;-) [08:58] but yeah usually when the third number (ie the age) is set to 0 that's an abi break [08:59] that's when the soname changes [08:59] seb128, but a library can make a change 4:0:0 -> 5:0:1 and we don't update right? [08:59] no [08:59] there is compatibility breakage in such cases [08:59] I should clean and publish my script which diff installed packages and deb [08:59] seb128, but we do change binary package name? [09:00] no [09:00] we change when the soname changes [09:00] is change "lib.so." changes "n" [09:00] ie when "lib.so." changes "n" [09:00] the binary is named libname [09:01] ok, so the safest thing to do is a dpkg -L on the currently installed version and a dpkg -c on the new version and see what changed? [09:01] usually what we want is to have abi incompatible versions to be stay around for a while to allow easy transitions [09:01] right [09:01] I should really publish my script [09:01] it basically does that for all the deb in the dir you are [09:01] and diff the lists [09:01] and shows the diff [09:03] robert_ancell, http://people.canonical.com/~seb128/debnbfiles [09:03] very hackish but if you want to try on your recent build [09:03] just run it in the dir with the debs [09:04] robert_ancell, otherwise you didn't reply to my question about the polkit gettext change in the email [09:04] do you think you will have time or interest for this one? [09:04] what about shotwell and f-spot import on first run? [09:05] brb, grabbing coffee [09:05] seb128, bug #619632 [09:05] Launchpad bug 619632 in policykit-1 (Ubuntu) (and 1 other project) "Use gettext for translating user messages (affects: 1) (heat: 6)" [Wishlist,Triaged] https://launchpad.net/bugs/619632 [09:05] robert_ancell, you rock as usual ;-) [09:05] thanks [09:06] did you merge the new gtk from debian today? [09:06] just checking if you didn't do it for a reason since I see no upload [09:06] brb [09:11] seb128, no, I was going to ask you if you knew of any problems with the new gtk - since it has dropped so much api I didn't want us to require two versions on the cd. I thought they were going to make those changes in 3.0! [09:11] I notice that Debian has taken it though [09:11] robert_ancell, they didn't drop apis [09:11] they are marking those deprecated only I think [09:12] robert_ancell, I didn't build evince yet but I think your update missed the libevview soname change [09:13] seb128, according to the GTK+ email it says "Remove all GDK drawing functions, ie gdk_draw_*. Use cairo instead" etc [09:14] robert_ancell, http://git.gnome.org/browse/gtk+/commit/?h=gtk-2-22&id=92055d8d328a7adaa05f3c6ac6d1c496819940ec [09:14] robert_ancell, that's those sort of changes [09:14] they are changing gtk to use cairo rather than gdk_draw_ calls [09:15] I doubt they dropped any public api that would break the abi which is what gtk3 is for [09:18] oh, that sounds safer :) [09:19] I will do the update and see how it goes today [09:19] robert_ancell, did you read my libevview comment? [09:20] seb128, yes, do you mean the gir1.0- package or something else? [09:20] robert_ancell, libevview2 -> libevview3 [09:20] seb128, yeah, did that (I pushed to the u-d branch as UNRELEASED) [09:21] robert_ancell, no, you renamed libevdocument [09:21] damn [09:21] robert_ancell, both need renaming [09:22] robert_ancell, try http://people.canonical.com/~seb128/debnbfiles [09:22] robert_ancell, if you didn't install the new version yet [09:22] trying it now [09:23] ok, pushed changes now [09:24] robert_ancell, seems correct now [09:25] robert_ancell, btw lintian should warn you about names not matchin sonames as well [09:25] robert_ancell, if you have it installed [09:25] right [09:25] so it's usually a hint to think about when you see it ;-) [09:26] does it remind you if you forget to update the shlibs variable though? [09:26] no [09:27] but we should stop using shlibs [09:27] we should use .symbols rather [09:27] right [09:34] hmm, I didn't have lintian installed since I replaced my hdd - no wonder I'm not seeing any warnings! [09:34] heh [09:42] pitti, have you tried the latest simple-scan? I made it do the 2 bit scan for text, see how it looks [09:47] robert_ancell, so shotwell [09:47] robert_ancell, https://blueprints.edge.launchpad.net/ubuntu/+spec/desktop-maverick-shotwell [09:48] doh [09:48] he left ;-) [10:05] bl8: ping [10:33] kiwinote, mpt, vish: hi :) [10:33] devildante: hey [10:33] Good morning devildante [10:34] Good morning you two :) [10:34] * devildante wants mvo back :p [10:34] devildante: hey! [10:34] hey vish :) [10:35] devildante: you ping-a-linged at 5am for me ;p [10:35] vish: it was, like 1am for me, so you're forgiven :p [10:36] vish: I have finished the renaming of update-manager [10:36] mpt: ^ :) [10:37] devildante: now we wait for mvo to return.. [10:38] devildante, mpt, I have started on the treeview that shows the updates http://imgur.com/EvTCF [10:38] devildante: you do realise that there is a large number of packages depending on 'update-manager', 'update-notifier', etc..? [10:39] hi and471. Are you doing this interface from scratch, or is it changes to the existing update-manager code? [10:39] vish, mpt: I'll redo the update-notifier renaming tomorrow, as I want to finish a little project for tomorrow ;) [10:39] mpt, well I decided it best to do it from scratch since software-updater is VERy different from UpdateManager [10:39] all right, and471, you're the best! [10:39] mpt, I can definitely bring some stuff over from update-manager [10:39] mpt, to minimise duplication of effort [10:40] mpt, however I feel even the backend will be from scratch [10:40] kiwinote: Replaces and Conflicts would be enough, I think [10:40] kiwinote: yeah devildante was wondeirng about that, probably we should only do renaming of the UI alone for now and think about the gconf changes for next cycle? [10:40] and471, maybe so, but there are probably many intricate details of update-manager that I don't know about yet, and it seems dangerous to me to try and rewrite them all. [10:40] mpt, as I suspect mvo will want to use aptdaemon+plicykit instead of gksudo [10:40] and471, update-manager in Maverick already uses aptdaemon+policykit, right? [10:41] mpt, I don't know [10:41] yep, parts of it do [10:41] kiwinote, ah [10:41] mpt, I shall have a look, but because the interface is very different, I feel as though form scratch is better [10:41] *from [10:42] and471, I tried to write the spec so that it could be implemented a little bit at a time (as devildante did with the running-on-battery text, for example). [10:42] and471: I could work on the treeview alone for update-manager without starting from scratch [10:42] (if you want of course ;) ) [10:43] mpt, devildante it is just the way software-updater will work with morphing windows means the UI framework is vastly different [10:43] and471: there are a few things hidden in the update-manager code (afaik) like partial updates, dist-upgrades etc [10:43] kiwinote, yup I was thinking about these :) [10:43] and471: as far as I am aware they have some quite complex code ;) [10:43] becuase of these vast differences I felt it was better to start from scratch as otherwise I would end up with quite horrible code [10:44] kiwinote, definitely, but I am just starting with the GUI stuff, I am not confident with aptdaemon etc. [10:44] kiwinote, mpt, devildante, let me quickly have a look at the UM code [10:44] yeah, for the 'normal' updates I think it does make sense to rewrite [10:45] should also check it out myself ;) [10:45] (btw if anyone wants to see the code, it is in lp:~and471/+junk/software-updater) [10:46] and471: does it really make sense to rewrite? as far as I know, only UpdateManager.py and the backends have GUI, so you could only rewrite these [10:46] I'm not an engineer, so I'll defer to mvo on this. Maybe I'm biased against rewrites because I lived through the Mozilla rewrite [10:46] devildante, mpt, I will email mvo for his advice [10:46] devildante, sorry I don't understand [10:47] don't worry I haven't progressed so far that I can't go back and update existing code :) [10:47] (into UM) [10:47] ok [10:47] but I shall slow down to avoid any 'oops I've done this the wrong way and waisted all that time' :) [10:47] just for the record that was only the front end rewrite I was referring, the backend is quite complex as it is.. [10:48] kiwinote, yeah [10:48] and471: I meant that only 2 files uses Pygtk+: UpdateManager.py (the main file) and InstallBackendAptDaemon.py (the backend), so you could only modify these ;) [10:48] kiwinote, I agree, [10:48] devildante, yes but I think rewriting those files [10:48] devildante, is better than [10:49] devildante, going through code that follows an old workflow and trying to make it fit with our new one [10:49] anyway let me have a look [10:50] ok [10:51] I think I shall wait to mvo's much hyped return :) [10:51] hopefully he will know what to do [10:51] to > until [10:52] mpt, I have even wrote gui_tests for the software-updater (the stuff nessita taught me) :) [10:52] bravo [10:52] hehe [10:53] devildante, < I could work on the treeview alone for update-manager> could I ask that we both wait till mvo's return [10:53] devildante, so we avoid duplication fo effort [10:53] *of [10:53] ? [10:53] and471: okay, no problem ;) [10:53] devildante, thanks [10:53] and471: np :) [10:53] asac, hello [10:54] asac, you need your clutter changes in maverick right? [10:54] asac, just checking === chrisccoulson_ is now known as chrisccoulson [10:56] seb128: yes, we upstramed everything and i think pochu wanted to apply this in debian next [10:56] stay tuned for another day or two ... hope we can just sync by then [10:56] ok [10:56] we should get that in this week [10:56] ok. then we might need to prepush that [10:56] we are over the time for changes, we should aim at stabilization ;-) [10:57] seb128: our changes shouldnt destabilize the normal GL stack ;) ... but yeah [10:57] shouldn't != will not ;-) [10:57] thats news to me ;) ... j.k [10:57] is the email you sent the other day current state of the art for those? [10:58] I will check with pochu when if he reviewed it and try to get that in tomorrow [10:58] seb128: alf is fixing one more bug now ... we will ping you when its ready [10:58] thanks [10:58] alf__: ^^ [10:58] if you could rebase on the current version that would be nice as well [10:58] ie do one changelog entry with summarize the changes [10:59] rather than having history of the version you maintained mixed in the changelog [11:03] seb128: This has been mostly fixed in 0ubuntu4unified2 in my ppa [11:04] seb128: I will soon upload 0ubuntu4unified3, I will ping you. Thanks! [11:04] alf__, thank you [11:11] dpm, hi, is bug 560591 related to SC, to me it looks like the reporter's language is set to English [11:11] Launchpad bug 560591 in software-center (Ubuntu) (and 1 other project) "Wrong language shown in Ubuntu Software Center (affects: 1) (heat: 6)" [Low,Incomplete] https://launchpad.net/bugs/560591 [11:12] hi and471, let me have a look [11:12] dpm, thanks [11:15] mpt, are you working on bug 433841? [11:15] Launchpad bug 433841 in software-center (Ubuntu) "Enable users to upload a screenshot (affects: 2) (heat: 10)" [Wishlist,Confirmed] https://launchpad.net/bugs/433841 [11:21] and471, ok, done some quick tests and commented on the bug [11:22] and471, no, it's assigned to me so I can design the interface. Do you have a suggestion? [11:24] seb128: gnome-terminal doesnt do the right thing for me anymore for alt + backspace (e.g. doesnt delete full words) [11:25] seems alt key isnt used at all (e.g. alt+d doesnt delete full word, alt+a doesnt go to front etc.) [11:25] err alt+a never did that ;) [11:25] still alt key is broken ... /me checks gnome-terminal settings [11:26] asac, I don't know about this issue but I'm not the one who did the recent update and I didn't upgrade yet [11:26] ok [11:27] but seems there was a gnome-terminal update [11:28] filed bug [11:29] bug 619754 [11:29] Launchpad bug 619754 in gnome-terminal (Ubuntu) "alt + backspace; alt+d etc. don't work anymore (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/619754 [11:30] dpm, thanks [11:31] mpt, I was going to have a go at designing it and implementing it [11:31] mpt, I was thinking along the same lines as the review dialog, but obviously a bit different [11:33] and471, sure, maybe you could post sketches of the design on a wiki sub-page [11:33] mpt, ok, i''l have a go :) === MacSlow is now known as MacSlow|lunch [11:58] * and471 wonders why wiki.ubuntu.com is so slow... [11:58] mpt, added it to the end of this page https://wiki.ubuntu.com/SoftwareCenter/Comments [12:03] and471, what do you think are the best and worst things about that design? [12:25] any python-webkit experienced guys here? [12:33] seb128, please merge https://code.edge.launchpad.net/~rodrigo-moya/ubuntu/maverick/tomboy/fix-sso-signals/+merge/32982 [12:33] rodrigo_, heh you didn't do the version update! ;-) [12:33] rodrigo_, hey btw [12:33] rodrigo_, who is working on the ubuntuone-client nautilus integration btw? [12:34] rodrigo_, did you notice it's broken since the nautilus 2.31 update? [12:34] rodrigo_, there is no bar displayed, not that I complain but I think it's not wanted [12:34] seb128, no, coming in the next branch [12:34] seb128, I am working on it [12:35] seb128, we only show it now for XDG folders [12:35] seb128, does it show for you in ~/Documents? [12:36] rodrigo_, yes, excellent [12:36] rodrigo_, I was afraid I broke it with the update [12:36] rodrigo_, so the context menu show,hide option doesn't work on non-xdg dirs [12:37] no, it doesn't, since it never shows it [12:37] we need to discuss what's the best way, so will get some bug fixes [12:39] ok === al-maisan is now known as almaisan-away [12:53] good morning folks [12:54] seb128, i'll be a little late today, heading in for a parent-teacher conference in a few minutes [12:54] kenvandine, hey, ok [12:54] kenvandine, btw read the 15 lines backlog before you said hello [12:55] ah! [12:55] that is very good :) [12:56] * kenvandine heads out === MacSlow|lunch is now known as MacSlow === almaisan-away is now known as al-maisan [13:50] * pitti headdesks on bug 612988; c'mon guys [13:50] Launchpad bug 612988 in ubuntuone-client (Ubuntu Maverick) (and 2 other projects) "[nautilus] shows ubuntu-one ribbon in each folder (affects: 7) (dups: 2) (heat: 48)" [Undecided,Confirmed] https://launchpad.net/bugs/612988 [13:53] hey pitti [13:53] * pitti hugs seb128 [13:54] * seb128 hugs pitti [13:55] hi pitti! [13:56] hey chrisccoulson, how are you? [13:56] pitti - i'm good thanks, and you? [13:56] I'm great [13:56] back in Dresden again [13:56] nice quiet train ride with lots of time for hacking [13:57] nice! [13:59] ah, maverick langpacks finished building [14:00] dpm: ^ I started it this morning [14:00] dpm: building locally in the DC, that is (not uploaded yet, want to give them a quick test first) [14:01] pitti, you've been reading my mind, I was just about to ping you about them :) Thanks for the update [14:02] dpm: not quite -- you pinged me over night :) [14:02] hahaha, forgot about the scrollback [14:09] yay, finally! translated evolution again [14:09] firefox and desktop look fine [14:09] \o/ [14:10] dpm: ok, looks good; pushing them archivewards [14:10] brilliant, thanks pitti [14:11] no problem [14:41] pitti, after the full language pack is generated, i take it the deltas will keep being generated and automatically uploaded during development, won't they? (apart from freezes, where I know they need to be disabled IIRC) [14:42]