[05:03] <pitti> Good morning
[06:37] <BigWhale> @#$#@!!! Morning.
[06:42] <didrocks> good morning
[06:43] <pitti> bonjour didrocks
[06:43] <pitti> BigWhale: what's up? :-)
[06:43] <didrocks> salut pitti, ça va?
[06:43] <pitti> ça va bien! et toi?
[06:43]  * pitti was watching you live yesterday
[06:43] <didrocks> ça va, ça va :)
[06:43] <pitti> UbunTv!
[06:43] <didrocks> pitti: oh, which session? :)
[06:44] <pitti> integrating the phablet apps into ubuntu
[06:44] <highvoltage> bonjour á tous
[06:44] <didrocks> ah ok :-)
[06:44] <didrocks> bonjour highvoltage ;)
[06:44] <pitti> bonjour highvoltage, comment vas-tu?
[06:44] <highvoltage> bien merci et toi?
[06:44] <didrocks> pitti: I find it a little bit difficult to lead a session, with all the tabs opened + the hangout window
[06:44] <didrocks> I guess it's a question of habit
[06:44] <pitti> yeah
[06:45] <pitti> following a session with video, irc, and etherpad works rather well I find
[06:45] <BigWhale> pitti, I'm up, that's what .. :/ six hours of sleep in two days and today will be the same and I have to make a new release of Kazam so it will get uploaded to Raring.
[06:45] <didrocks> but I found it way more tiring than leading a session at a non virtual UDS
[06:45] <didrocks> right
[06:45] <pitti> but not when having an "active" hangout
[06:45] <didrocks> exactly
[06:45] <didrocks> not sure what can be done for that though
[06:45] <pitti> BigWhale: trying sleep compression?
[06:46] <pitti> didrocks: not sure either, maybe hangout on the tablet/netbook/second screen?
[06:46] <pitti> with a bigger monitor, having two windows side by side ought to work, too
[06:46] <didrocks> pitti: yeah, I think that's a viable option
[06:46] <pitti> that gets quite crammed with my 1280 pixels, though
[06:46] <BigWhale> Two people should lead the sessions. One taking care of video and the other of IRC. And the second person would then pass the info from irc to the first person
[06:47] <BigWhale> it's hard to keep track of all the people chatting in irc
[06:47] <didrocks> BigWhale: yeah, that doesn't fix the "issue" with sessions where you have a ton of tabs
[06:47] <pitti> yeah, we need some kind of moderation there
[06:47]  * RAOF will get to see this in action when there's a vUDS that doesn't go from 1am to 6am.
[06:47] <didrocks> but agree that someone modering IRC is a first step :)
[06:48] <didrocks> moderating*
[06:48] <BigWhale> pitti, I'll just stuff myself with energy drinks and green smoothies :>
[06:52] <didrocks> BigWhale: green smoothies, what do you put in it? :)
[06:53] <BigWhale> didrocks, lots of stuff that tastes awful and that really wakes you up! ;>
[06:53] <didrocks> :)
[06:53] <BigWhale> everything from cabbage to broccoli
[06:54] <BigWhale> lettuce
[06:54] <BigWhale> mint ... and few more stuff that I'd have to google their English names  :)
[06:54] <didrocks> interesting, I drinked a lot of smoothies in Ireland, but never such ones :)
[06:54] <didrocks> ahah
[06:55] <mlankhorst> RAOF: not missing much
[06:56] <BigWhale> rolling release session was quite good, but inconclusive :)
[06:56] <BigWhale> ah well, have to run to the office.
[06:56] <BigWhale> later :)
[07:48] <czajkowski> morning folks
[08:02] <didrocks> hey czajkowski
[08:28] <seb128> hey desktopers
[08:38] <Sweetsha1k> seb128: ho
[08:38] <seb128> Sweetshark, hey, how are you?
[08:40] <Sweetshark> Mostly fine, except from the "arrgh fuuu LibreOffice on raring ate my data" mail from jono in the morning.
[08:40] <seb128> oh, it did?
[08:42] <Sweetshark> seb128: we should update away from that beta ASAP. 4.0.1 final is going to be released ... *cough* soon, so we should update along with that.
[08:43] <Sweetshark> I have a 4.0.1~rc2 at https://launchpad.net/~bjoern-michaelsen/+archive/libreoffice-nattytest2 to be copied over to the ppa when its done.
[08:43] <seb128> is there any other blocker since you fixed the libcmis issue?
[08:43] <Sweetshark> rc2 is expected to be final.
[08:43] <Sweetshark> no other blockers except DMB review ;)
[08:51] <seb128> Sweetshark, great, let's hope bdrung has time to review/sponsor it ;-)
[08:52] <Sweetshark> seb128: I see no trouble there, bdrung was very quick with the libcmis thing.
[08:53] <seb128> excellent
[09:10] <seb128> pitti, hey, I saw you assigned you the gvfs bug, do you plan to do the update as well? ;-)
[09:11] <Laney> howdy
[09:11] <seb128> Laney, hey, how are you?
[09:12] <Laney> good, but tired! We went to a comedy show last night which started/finished quite late
[09:12] <Laney> how about you?
[09:13] <seb128> I'm good thanks
[09:13] <seb128> I was too exhausted after vUDS to go anywhere though :p
[09:14] <Laney> yeah I'd have rather it was another day but we already booked it
[09:17] <seb128> I hope the show was good at least ;-)
[09:17] <Laney> yep :)
[09:45]  * seb128 uninstall a stack of kernels and gets back 1GB of disk space
[09:46]  * chrisccoulson should try that
[09:47] <Laney> http://paste.ubuntu.com/5589957/ !!!!!!!
[09:47] <seb128> Laney, see!
[09:48] <seb128> Laney, do you have a magical command or did you list them by hand? (I do list by hand)
[09:48] <seb128> using autoremove doesn't clean those for me
[09:48] <Laney> oh, that was just autoremove
[09:49] <didrocks> autoremove clearly does for me :)
[09:49] <didrocks> just cleaned 2.7 GB, I kept the old kernels for a long time due to the network issue
[09:52] <chrisccoulson> autoremove freed up nearly 1GB here, but it left most old kernels
[09:52] <chrisccoulson> i guess i'll clean those manually
[09:53] <Laney> perhaps it only notices ones which were installed after that feature got added
[09:54] <chrisccoulson> i've got 3.0 kernels installed here. how old are those?
[09:54] <Laney> oneiric ish
[09:56] <chrisccoulson> nice, another 3GB
[09:56] <chrisccoulson> quick, fill the space with another chromium build!
[09:57] <czajkowski> how to make chrisccoulson - free him up space
[09:57] <chrisccoulson> czajkowski, i literally fight over tens of MB here, so a few GB is quite welcome
[09:57]  * chrisccoulson wishes for a bigger SSD
[09:58] <seb128> same here
[09:58] <seb128> 80G ssd is short
[09:58] <chrisccoulson> yeah, i struggle with 120GB!
[09:59] <chrisccoulson> which reminds me. i'm sure that i'm due a laptop refresh ;)
[09:59] <czajkowski> yeah I'm thinking of investing in a desktop and throwing a lot of storage at it, having to do testing in Vms is driving me insane
[09:59] <czajkowski> I love this laptop but it's not built for testing
[10:00] <czajkowski> it does test my patience from time to time
[10:00] <czajkowski> or lack of...
[10:02] <Laney> do you have an SSD?
[10:02] <Laney> made such an amazing difference when I upgraded just that one thing on my laptop
[10:02] <seb128> yeah, same here
[10:02] <seb128> I wonder if I should format it though
[10:04] <seb128> https://plus.google.com/u/0/107564545827215425270/posts/V3UH5SUXJcT
[10:05] <chrisccoulson> i've got 4.5GB of free space now \o/
[10:06] <Sweetshark> chrisccoulson: I have a build tree that would just fit in there nicely ....
[10:06] <Sweetshark> bdrung: http://people.canonical.com/~bjoern/libreoffice4/ <- 4.0.1 proposal btw ...
[10:06] <chrisccoulson> Sweetshark, you can get a build tree in 4.5GB? lucky you ;)
[10:07] <Sweetshark> chrisccoulson: a developer build, not a release build.
[10:07] <chrisccoulson> ah :)
[10:19] <marga> Hi.  I've created a custom indicator.  To find out about the available icons, I used the icon library browser.  But now I'm finding out that they don't look the same in unity and cinnamon
[10:19] <seb128> marga, right, cinnamon uses a different icon theme
[10:19] <marga> For example, I'm using emblem-default-symbolic, and in cinnamon it looks awfully big
[10:20] <seb128> seems like a bug in their theme then?
[10:20] <marga> :-/
[10:21] <marga> Well, I'm not sure... It's the same icon, just bigger
[10:21] <marga> I think it's the indicator that somehow is screwing this up
[10:22] <seb128> marga, why?
[10:22] <marga> because the icon is available in multiple sizes, but it's showing the wrong size
[10:23] <seb128> maybe it's not available in the wanted size in the theme?
[10:23] <marga> Sorry, it's actually a scalable svg
[10:23] <marga> the icon library browser shows 3 sizes, by scaling
[10:24] <seb128> marga, where did you get the cinnamon icon theme?
[10:24] <seb128> it doesn't seem to be into the archive
[10:24] <marga> uhm... it's the gnome theme, I think
[10:25] <marga> the library browser says 'inherited from gnome'
[10:25] <marga> It's in the gnome-icon-them-symbolic
[10:26] <pitti> seb128: I don't think there's an "update" as such, it requires debugging why it doesn't work
[10:26] <pitti> oh, there's 1.15.4, indeed
[10:26] <seb128> pitti, versions disagrees with you
[10:26] <seb128> pitti, ;-)
[10:27] <pitti> ah, released on Monday, that was after I checked last
[10:29] <pitti> seb128: but still, support for powering off was in 1.15.1, so it's still not just the new version
[10:29] <seb128> pitti, well, it's build time enabled though, did you try rebuilding with the new udisk?
[10:29] <pitti> yes
[10:29] <seb128> ok
[10:29] <seb128> pitti, the "update" comment was orthogonal, I've "update gvfs" in my tomboy
[10:30] <seb128> but that tomboy note is endless, so I'm happy to let it to somebody else :p
[10:30] <Laney> ah /me was looking at that
[10:30] <Laney> happy to leave it to pitti though if you're debugging something else anyway
[10:30] <seb128> Laney, there is a bunch of other GNOME updates to do if you feel like doing those
[10:30] <pitti> Laney: ok, WFM; I'll do the update, and debug the poweroff thing
[10:30] <seb128> I was just going to do gtk3
[10:31] <pitti> seb128: is there a new 3.6.5? or are we going for 3.7.x at last?
[10:32] <seb128> Laney, gssdp and gupnp (sync the new version from debian?),  libpango/glib/gtk-perl, glibmm, gnome-keyring, gtkmm3, libsecret, etc
[10:32]  * pitti HUDs for "disks", gets totem, o_O, and tries again
[10:32] <seb128> pitti, still baking 3.7 in the ppa
[10:33] <seb128> pitti, we have some regressions still, theming issues
[10:33] <seb128> https://bugzilla.gnome.org/show_bug.cgi?id=694217
[10:33] <ubot2`> Gnome bug 694217 in general "drag&drop half-broken – items get stuck while dragging" [Normal,Unconfirmed]
[10:33] <seb128> gnome-screenshots turn your screen white
[10:33] <pitti> meh, and searching for d-feet doesn't work at all -- what the heck is wrong with hud search?
[10:33] <seb128> pitti, hud or dash?
[10:33] <didrocks> pitti: yeah, regression in the dash
[10:33] <seb128> hud is looking in menus only
[10:33] <pitti> sorry, dash
[10:33] <didrocks> pitti: the fix is merging
[10:34] <didrocks> with a test :p
[10:34]  * pitti hugs didrocks
[10:34] <seb128> regression from the new libcolumbus version
[10:34] <seb128> what didrocks said
[10:34]  * didrocks hugs pitti back
[10:35] <seb128> marga, I don't really have time to look at the issue atm, it's weird because that symbolic icon is only shipped in one package ... does the cinnamon theme inherit from GNOME?
[10:35] <marga> it does, yes
[10:35] <seb128> marga, in any case have a bug report with a small testcase would be useful
[10:35] <seb128> larsu can probably help you to figure out what's wrong when he's up in a few hours
[10:35] <pitti> at least calling PowerOff on udisks2's d-bus iface works, so gvfs' fault
[10:35] <marga> Ok, will look a bit deeper into this to try to find the culprit
[10:41] <Laney> bah, typing "spotif" into the dash gets me gedit instead of spotify
[10:42] <pitti> Laney: sounds like the same error I just complained about, where didrocks says it's being fixed?
[10:42] <Laney> oh, didn't read scrollback, sorry
[10:42] <Laney> ah
[10:42] <Laney> yes, thanks
[11:03] <tkamppeter> seb128, hi
[11:07] <xnox> pitti: so I used the g-doc parser against Gtk.gir to generate the docs. I see all the classes in the dot notation & hierarchy which is nice. But no functions/parameters/signals?!
[11:08] <ritz> cyphermox hi, wrt https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/965895
[11:08] <ubot2`> Launchpad bug 965895 in network-manager-applet "After boot, NetworkManager indicator menu only shows four entries" [High,In progress]
[11:10] <pitti> xnox: signals are in the per-class docs; I also see the arguments of methods and signals
[11:10] <xnox> pitti: hmm...
[11:10] <pitti> xnox: the functions seem to be there, but that part is buggy
[11:10] <pitti> Index.main
[11:10] <pitti> Runs the main loop until Index.main_quit is called.
[11:10] <pitti> that should say "Gtk", not "Index"
[11:11] <xnox> pitti: here is what I have: http://people.canonical.com/~xnox/yelp/doc/index.html
[11:11] <xnox> did I generate it wrong?
[11:11] <xnox> there are .pages as well...
[11:11] <pitti> hm, that looks incomplete indeed; I was checking in ylep
[11:11] <pitti> yelp, too
[11:12] <xnox> g-ir-doc-tool --language=Python -o /home/tdlk/build/doc /usr/share/gir-1.0/Gtk-3.0.gir
[11:12]  * pitti runs yelp-build
[11:12] <xnox> yelp index.page is same....
[11:12] <xnox> for me anyway.
[11:14] <xnox> i do have -dev -doc etc packages installed. Should I be doing this doc generation in the source package?
[11:14] <pitti> xnox: hm, in *.html I get the complete docs, too
[11:16] <pitti> xnox: so compare http://people.canonical.com/~xnox/yelp/doc/Gtk.FontChooser.html with http://people.canonical.com/~pitti/tmp/Gtk.FontChooser.html
[11:16] <pitti> xnox: (sorry, didn't copy the .js and css bits along)
[11:16] <pitti> done now
[11:16] <xnox> pitti: nice. So how come i'm not getting that?! =))))
[11:17] <pitti> xnox: did you not feed it enough cookies?
[11:17] <pitti> no off-hand idea, I'm afraid
[11:17] <xnox> gobject-introspection	1.35.8+git20130220-0ubuntu1
[11:17] <pitti> xnox: I have yelp-tools and yelp-xsl installed
[11:17] <xnox> libgtk-3-dev	3.6.4-0ubuntu6
[11:18] <xnox> pitti: yeah, same here.
[11:18] <pitti> xnox: but if the .page files are already missing the info, it's on the g-ir-doc-tool side
[11:19] <pitti> http://people.canonical.com/~xnox/yelp/doc/Gtk.FontChooser.page looks really poor
[11:20] <xnox> pitti: right, so the Notify.gir works here. So not sure what's wrong with Gtk3.
[11:20]  * xnox really needs/wants Gtk, GLib, Gdk.
[11:23] <xnox> GdkX11 worked, Gdk/gtk/glib didn't =(
[11:25] <xnox> pitti: i'm on raring, are you?
[11:25] <pitti> xnox: yes, raring du jour
[11:42] <tkamppeter> seb128, around?
[11:48] <pitti> seb128: ok, I demystified bug 1067876
[11:48] <ubot2`> Launchpad bug 1067876 in gvfs (Ubuntu) "Missing "Safely Remove Drive" option from Quicklists. Only have "Eject"." [Low,In progress] https://launchpad.net/bugs/1067876
[11:48] <pitti> seb128: it's again a "hardware lies, we have no information what's right" case, and really tricky to work around
[11:48] <pitti> seb128: but for now, showing "Eject" for USB sticks doesn't break the world IMHO
[12:02] <seb128> tkamppeter, hey, sorry I was away for a bit
[12:02] <seb128> pitti, oh, ok, thanks for figuring it out!
[12:03] <tkamppeter> seb128, I have a problem with GNOME's printer setup tool and do not know how to debug it.
[12:03] <seb128> tkamppeter, what sort of problem?
[12:03] <tkamppeter> seb128, I am on Raring and if I run system-config-printer from the command line (old UI) it detects all my printers, in the network and on USB.
[12:05] <tkamppeter> seb128, if I use the new tool on my laptop (real-iron Raring), I see only network printers and no USB printers, looks like the new tool only checks via Bonjour but does not ask CUPS.
[12:05] <tkamppeter> seb128, on a Raring VM no printers are found at all, probably also not asking CUPS and not finding anything via Bonjour as it has its own network inside my PC.
[12:06] <seb128> could be, did you look at the code? or maybe ask upstream (I think he's mkasik on the GNOME IRC)
[12:06] <seb128> need to be away a few minute, I will read the scrollback
[12:06] <seb128> brb
[12:06] <tkamppeter> seb128, so the problem seems that the new tool is not asking CUPS (via s-c-p D-Bus service) to detect printers.
[12:11] <bdrung> Sweetshark: libcmis is uploaded. thanks for your work on that. i will review 4.0.1
[12:12] <Sweetshark> bdrung: please hold back uploading 4.0.1 a bit still
[12:12] <bdrung> okay
[12:14] <Sweetshark> bdrung: some test have been proven to be flaky in general (as they failed on the backports builders too). So Ill disable them, so that we dont end up with a 24 hour armhf build that then fails to complete.
[12:14] <Sweetshark> bdrung: you can go ahead and review 4.0.1 already though as this will only be a minor change.
[12:14] <bdrung> Sweetshark: "new upstream release candidate" -> "new upstream release"
[12:26] <seb128> tkamppeter, have you looked at the GNOME tool's code to see what it's doing exactly?
[12:26] <tkamppeter> seb128, not yet.
[12:27] <seb128> tkamppeter, it seems like they use org.opensuse.CupsPkHelper.Mechanism DevicesGet method
[12:34] <tkamppeter> seb128, how do I fire up the printer tool from the command line, to see its warnings, and is there perhaps a debug mode for more verbose console logging?
[12:37] <seb128> tkamppeter, try "G_DEBUG_MESSAGES=all gnome-control-center printers"
[12:37] <seb128> but it doesn't seem like there are lot of debug code in the source
[12:40] <tkamppeter> seb128, thanks for the hint, there is no output at all.
[12:41] <Sweetshark> bdrung: fixed in http://anonscm.debian.org/gitweb/?p=pkg-openoffice/libreoffice.git;a=commit;h=36f27eb52d7c35b9a0ff59fb9298c11a3f64759a which also has the disabling of tests by ricotz. http://people.canonical.com/~bjoern/libreoffice4/ is updated too.
[12:43] <tkamppeter> seb128, I reported https://bugzilla.gnome.org/show_bug.cgi?id=695286 now.
[12:43] <ubot2`> Gnome bug 695286 in Printers "Printer tool of GNOME Control Center does not get info about available printer devices from CUPS" [Normal,Unconfirmed]
[12:43] <seb128> tkamppeter, did you figure out what is wrong or just reported the issue?
[12:45] <Sweetshark> bdrung: also, its official now: http://blog.documentfoundation.org/2013/03/06/the-document-foundation-announces-libreoffice-4-0-1/
[12:46] <seb128> tkamppeter, you might want to join irc.gnome.org #control-center and ping mkazik to discuss the issue
[12:50] <BigWhale> is it just me or bzr is acting a little bit strange?
[12:56] <bdrung> Sweetshark: for what reason does libreoffice-help-en-us conflict with all other help packages?
[12:57] <Sweetshark> bdrung: bug 957589
[12:57] <ubot2`> Launchpad bug 957589 in Ubuntu Translations "Localized LibreOffice Help files ignored when help for en-US is installed" [Medium,Triaged] https://launchpad.net/bugs/957589
[12:59] <bdrung> thanks
[13:02] <tkamppeter> seb, thanks for the hint, I am connecting now.
[13:07] <seb128> re
[13:08] <seb128> ogra_, what's the recommended way to put raring on the nexus7 nowadays? did you say usb-creator works for it?
[13:17] <ricotz> bdrung, hi, will you upload the new libreoffice within the next hours?
[13:37] <desrt> good morning, hax0rs
[13:38] <bdrung> ricotz: i will review it and upload, but i can't promise it to be in the next few hours
[13:38] <mterry> attente, https://apps.ubuntu.com/cat/applications/precise/super-hexagon/
[13:38] <desrt> mterry: nooooooo
[13:38] <seb128> hey desrt mterry
[13:39] <desrt> seb128: hey
[13:39] <mterry> seb128, desrt: Morning!
[13:39] <desrt> seb128: i took your advice
[13:39] <desrt> https://launchpad.net/~desrt/+archive/ppa
[13:39] <desrt> testing now
[13:39] <seb128> great
[13:39] <attente> mterry: oh cool
[13:40] <desrt> seb128: is there anyone we can talk to about PPAs effectively being overnight delivery now?
[13:40] <seb128> you mean?
[13:41] <seb128> build time issues?
[13:41] <desrt> yes
[13:41] <seb128> i386 backlog is down to 1h40
[13:41] <desrt> waiting 12 hours for a trivial build is not the best thing for productivity
[13:41] <seb128> I think that's going to solve itself in a bit
[13:41] <desrt> oh.  good.
[13:42] <seb128> we accumulated delays for some reasons
[13:42] <seb128> but builders are back and catching up
[13:43] <desrt> hm.  looks like i screwed something up.
[13:44] <desrt> oh.  dailies.
[13:45] <ricotz> bdrung, ok, thanks
[13:51] <mterry> So there was a session on rolling release yesterday.  I looked through its notes, but didn't see anything interesting.  Now an email to the ubuntu-desktop list says we decided to release 13.04 after all?  What happened at that session?
[13:52] <bdrung> Sweetshark: the changelog order is wrong. 1:4.0.0~beta2-0ubuntu2 should come before 1:4.0.0-1
[13:52] <seb128> mterry, you can watch the video on youtube, nothing was decided
[13:53] <mterry> seb128, that would take time  :)
[13:53] <seb128> mterry, basically there is a good part of the people who feel like we commited to have a 13.04 and it's late to bail out from that commitement
[13:53] <seb128> mterry, but there was no conclusion
[13:53] <seb128> mterry, it seems like middle ground was to do a release but only support it for security
[13:53] <seb128> e.g not do SRUs
[13:54] <seb128> suggest to people who want the fixes to just keep rolling on the rolling release from there
[13:54] <tkamppeter> seb128, you will participate in the printing session in 5 minutes?
[13:54] <tkamppeter> pitti, will you participate in the printing session in 5 minutes?
[13:55] <ogra_> seb128, well, it is supposed to, otherwise use the manual way via fastboot
[13:56] <ogra_> (usb-creator for flashing)
[13:56] <pitti> tkamppeter: yes, I'll listen in
[13:56] <seb128> ogra_, ok, let me try that ;-)
[13:56] <ogra_> unzip the .gz first
[13:57] <desrt> mterry: you wrote parts of the datetime panel, right?
[13:58] <desrt> particularly the part for turning datetimes into a number to stick into a spinbox and using that number to render the date/time values
[13:59] <desrt> anyway.. i was testing my recent changes there
[13:59] <desrt> so i changed the time manually... that worked OK
[13:59] <GeorgeTorwell> Unity sucks
[13:59] <desrt> then i tried changing the date
[14:00] <desrt> that didn't go so well
[14:00] <desrt> GeorgeTorwell: i know, eh?  seriously!
[14:00] <GeorgeTorwell> Yeah it sucks so hard bro. Cinnamon ftw
[14:00] <desrt> GeorgeTorwell: now that we've covered unity let's move on to why you don't like your science teacher
[14:00] <Sweetshark> bdrung: no, changes need to be ordered in the way they appeared in the ubuntu releases. thus if 1:4.0.0~beta2-0ubuntu2 already merged changes from 1:4.0.0-1 in packaging the order has to be as is.
[14:01] <GeorgeTorwell> desrt: I'm not a neckbeard like you. And no amount of passive aggressive neckbeard rage is going to change the fact that unity sucks and it sucks hard.
[14:02] <desrt> GeorgeTorwell: i think i was suggesting that you were too young to grow a beard, actually
[14:02] <desrt> but the fact remains that you're the one here making useless remarks, obviously to very much the wrong channel
[14:02] <bdrung> Sweetshark: 1:4.0.0~beta2-0ubuntu2 came directly after 1:4.0.0~beta2-0ubuntu1 and did not merge the _full_ changes from 1:4.0.0-1
[14:02] <GeorgeTorwell> And now Ubuntu wants to come up with Mir, its own replacement for X instead of just using wayland? Well shit on a stick (ironically this is also desrt's nickname), how buggy is that going to be
[14:03] <desrt> GeorgeTorwell: in fairness, X kinda sucks
[14:03] <mterry> desrt, yeah
[14:03] <desrt> in fact, X sucking is a good part of the reason for compiz sucking which is, in turn, a good part of the reason for unity sucking
[14:04] <GeorgeTorwell> X does suck
[14:04] <desrt> mterry: can you reproduce the issue i describe?
[14:04] <GeorgeTorwell> but holy shit there's this thing called WAYLAND
[14:04] <bdrung> Sweetshark: cherry-picking is different to merging
[14:04] <GeorgeTorwell> which Ubuntu was supposed to ship with in the future
[14:04] <desrt> GeorgeTorwell: can you please tell me what wayland is?
[14:04] <GeorgeTorwell> the replacement for X, and the future of linux
[14:04] <desrt> right
[14:04] <desrt> so if you could go ahead and arm yourself with some more facts before you start coming in here and babbling, that'd be great
[14:05] <desrt> wayland is just a protocol, you know?
[14:05] <mterry> desrt, did you edit the date text or use the up/down buttons?
[14:05] <GeorgeTorwell> no shit faggot, I said it was a replacement for x
[14:05] <desrt> mterry: up button, specifically
[14:05] <desrt> GeorgeTorwell: that language is utterly unacceptable.  please leave.
[14:06] <GeorgeTorwell> lolno
[14:06] <jasoncwarner_> I just popped in for a sec
[14:06] <mterry> desrt, works for me.  You may have to wait a few seconds for the change to show up (not sure why on that off the top of my head)
[14:06] <kenvandine> hey jasoncwarner_!
[14:06] <pitti> hey jasoncwarner_
[14:06] <desrt> jasoncwarner_: hey.  how's your back?
[14:06] <pitti> jasoncwarner_, tkamppeter: is the session actually happening? IRC is quiet and video doesn't work
[14:07] <desrt> mterry: hm.  when i change it, i find myself in 1970 :)
[14:07] <desrt> even after ppa-purge and a reboot
[14:07] <Sweetshark> bdrung: a linear changelog cant handle branching and merging properly, but if you insist on keeping that futile illusion ...
[14:08] <mterry> desrt, not the worst place to be, but not expected, no
[14:08] <desrt> :)
[14:08] <mlankhorst> bdrung: dpkg-mergechangelog merges everything :X
[14:08] <desrt> lemme toss this guy under G_DBUS_DEBUG and see what's going on
[14:12] <bdrung> Sweetshark: doko took 1:4.0.0~beta2-0ubuntu1 and did one change and uploaded it as 1:4.0.0~beta2-0ubuntu2. after the 1:4.0.0~beta2-0ubuntu2, you merged the changes from Debian
[14:12] <desrt> hm... no D-Bus involvement.  quite odd!
[14:12] <bdrung> maybe this chronology didn't end up in the same way in git
[14:12] <desrt> kinda takes all of the parts i've spent the last day or two breaking out of the picture
[14:17] <Sweetshark> bdrung: http://anonscm.debian.org/gitweb/?p=pkg-openoffice/libreoffice.git;a=blobdiff;f=changelog;h=0ff1ae001f6e7c7d0e979f48e4dd0b7ef1ec6304;hp=0dd26df29d611f408a75c28f2d17742f5d49bb2c;hb=42dd5bc7d7fbd2b2ac410eb39fd114aab072ead0;hpb=574cc9f0fbaf8b1d7a4dc1bc287cda55403be432
[14:19] <Sweetshark> bdrung: yes, doko sponsored a changed libreoffice package to raring, without pushing his changes to DSCM or even notifying anyone about, leaving others to clean up the mess for his. :/
[14:19] <Sweetshark> s/his/him/
[14:22] <bdrung> Sweetshark: you can simplify "(LP: #785518) (LP: #949997)" to "(LP: #785518, #949997)"
[14:22] <ubot2`> Launchpad bug 785518 in libreoffice (Ubuntu) "[Upstream] soffice.bin crashed with SIGSEGV in SdrEndTextEdit()" [Medium,Fix committed] https://launchpad.net/bugs/785518
[14:22] <ubot2`> Launchpad bug 949997 in libreoffice (Ubuntu) "[Upstream] Ctrl + z and Enter soffice.bin crashed with SIGSEGV in SfxLinkUndoAction::~SfxLinkUndoAction()" [Medium,Confirmed] https://launchpad.net/bugs/949997
[14:28] <seb128> ls
[14:28] <seb128> ups
[14:40] <desrt> mterry: lol.
[14:41] <desrt> mterry: this is one of those "only in canada" bugs
[14:42] <desrt> mterry: in en_CA, %x (which is the format you use for printing the date) gives a 2-digit year
[14:43] <desrt> so when you parse it back again, we find ourselves in the year .... 13
[14:43] <desrt> that results in GDateTime giving a rather large negative value for the unix timestamp
[14:43] <desrt> which the spinbox then truncates to zero
[14:43] <desrt> and.... ta da!  1970
[14:44] <mterry> desrt, hrm
[14:44] <desrt> here's one thing i don't understand: you use %x for the date, which is locale-specific
[14:44] <desrt> so should be mm/dd/yyyy in US, right?
[14:44] <desrt> but you parse it back in again in the form "yyyy-mm-dd" always
[14:45] <mterry> desrt, let me look at code again
[14:45] <desrt> ya.... it fails to parse US-formatted times
[14:45] <desrt> and in canada it works but.... the result is not nice
[14:46] <mterry> desrt, it works here...
[14:46] <desrt> mterry: are you seeing a mm/dd/yyyy formatted date?
[14:46] <desrt> when i set LC_ALL=en_US that's what i get
[14:47] <desrt> and when i try to change it i get a g_warning to the effect of "WARNING **: Could not understand 03/07/2013"
[14:47] <mterry> desrt, yeah I do
[14:47] <desrt> and the date does not change
[14:48] <desrt> mterry: reading the code, there is really no way this can work....
[14:48] <desrt> 28.6.15 mike@mt |     scanned = sscanf (text, "%u-%u-%u", &year_in, &month_in, &day_in);
[14:49] <mterry> desrt, I am also confused on that line
[14:50] <desrt> so look here: http://bazaar.launchpad.net/~indicator-applet-developers/indicator-datetime/trunk.13.04/revision/120.1.1
[14:50] <desrt> jjardon: you broke it :)
[14:51] <mterry> desrt, I get those print warnings.  Then my system time changes...  Not sure why yet
[14:51] <desrt> used to be hardcoded to %Y-%m-%d
[14:51] <desrt> so full 4-digit year, month, day
[14:51] <desrt> which would work just fine, always
[14:51] <mterry> desrt, ah yes.   I hard coded it because I could not find a way to parse back a date in a generic locale format
[14:52]  * desrt would be annoyed to still be hunting down y2k bugs in 2013 if this was not actually a y0.1k bug
[14:52] <mterry> desrt, I blame Canada
[14:52] <desrt> mterry: i don't believe you that this works in the USA
[14:52] <desrt> it's not possible :)
[14:53] <desrt> mterry: to confirm: we are talking about manual text edit -- not using the buttons
[14:53] <mterry> desrt, this had been part of my subtle attempts to force ISO 8601 on the world
[14:53] <mterry> desrt, oh.  I was using button
[14:53] <desrt> ah
[14:53] <desrt> that one works
[14:53] <desrt> unless you're me
[14:53] <mterry> desrt, I still got the warning, but then it worked
[14:53] <desrt> because the button causes the formatted string to update which parses successfully as the year 0013
[14:53] <mterry> right
[14:54] <desrt> anyway.. there are two bugs here
[14:54] <desrt> we need to revert jjardon's commit
[14:54] <desrt> but then we probably also need to change the canadian preferred locale datetime to include a 4-digit year
[14:54] <mterry> desrt, good luck changing anything locale related
[14:54] <mterry> desrt, that is an uphill battle from what I've seen
[14:55] <desrt> sigh.
[14:55] <desrt> so revert jjardon's patch?
[14:55] <mterry> desrt, though I agree 4-digit years does seem better in this day and age
[14:55] <mterry> desrt, is there a bug yet?
[14:55] <desrt> nobody in canada writes a 2-digit year in ISO format
[14:55] <desrt> https://bugs.launchpad.net/indicator-datetime/+bug/729056
[14:55] <ubot2`> Launchpad bug 729056 in indicator-datetime "Date setting in the preferences should be not be shown in ISO format" [Low,Fix released]
[14:55] <desrt> if you're a fan of reusing the bug that was used to introduce the regression
[14:55] <desrt> otherwise, no
[15:00] <desrt> seb128: so i think we're ready to go
[15:00] <desrt> except for this (unrelated) issue, everything works as expected
[15:00] <seb128> desrt, ok, great, "just" need systemd MIRed and systemd-shim uploaded, NEWed and MIRed
[15:01] <desrt> lovely :)
[15:01]  * larsu just realized that MIR now means two things...
[15:01] <didrocks> larsu: we have Mir and MIR
[15:02] <larsu> fair enought
[15:02] <larsu> *enough
[15:02] <Laney> [MIR] mir will be my favourite bug
[15:05] <desrt> tedg: did you follow this conversation?  looks like you were the one to approve the merge?
[15:06] <desrt> tedg: probably the easiest fix right now is a revert, unless you want to do a lot of work
[15:06] <mterry> desrt, commented on that bug and filed a new one too
[15:06] <desrt> k
[15:06] <desrt> mterry: you gonna take care of it, then?
[15:06] <jjardon> desrt: A bug come from the past to bite me! ;)
[15:07] <mterry> Laney, now now now, it would be "[MIR] Mir".  All lower-case "mir" is still an available acronym!
[15:07] <Laney> I was thinking of the package name :P
[15:07] <desrt> mterry: you could get fancy...
[15:07] <mterry> desrt, I want to quickly poke mpt about it.  mpt: feel like looking at bug 1149696 ?
[15:07] <ubot2`> Launchpad bug 1149696 in indicator-datetime (Ubuntu) "Manually editing date field results in bogus date" [Undecided,New] https://launchpad.net/bugs/1149696
[15:08] <desrt> mterry: you could try for format january 2nd 2003
[15:08] <mterry> Laney, ah, yeah you're right
[15:08] <desrt> and see if it comes out like 01-02-03 or 01-02-2003 or 02/01/2003 or whatever
[15:08] <desrt> then decide what the format is based on that
[15:08] <mterry> desrt, but there are things like Canadians
[15:08] <desrt> i think it's also possible to query nl_langinfo for the format string corresponding to %x
[15:08] <desrt> so you could use that to scan with
[15:08] <mterry> desrt, oh really?  I don't recall that being the case
[15:09] <desrt> glib does this, i think
[15:09] <desrt> that's how g_date_time_format() works
[15:09] <mterry> desrt, I *believe* I looked into this in the past and couldn't find it.  But maybe I overlooked it
[15:09] <desrt> PREFERRED_DATE_FMT
[15:09] <mterry> Oh, in that case...
[15:09] <Sweetshark> bdrung: http://people.canonical.com/~bjoern/libreoffice4/ updated
[15:09] <desrt> #define PREFERRED_DATE_FMT nl_langinfo (D_FMT)
[15:09] <desrt> ding ding
[15:10] <desrt> it's still a lot of work to write a parser based on this
[15:10] <desrt> and note that you may not even be dealing with ascii digits
[15:10] <desrt> i think in a farsi locale you get the arabic arabic digits
[15:11] <mterry> desrt, wait, farsi doesn't use "western" arabic digits?  I always assumed we got those from them
[15:11] <desrt> mterry: we got the system from them, but not the glpyhs
[15:11] <mterry> desrt, cool
[15:11] <desrt> ٠‎ - ١‎ - ٢‎ - ٣‎ - ٤‎ - ٥‎ - ٦‎ - ٧‎ - ٨‎ - ٩
[15:12] <desrt> ironically, the arabs call these "hindi numbers"
[15:12] <larsu> because they came from india originally, no?
[15:13] <desrt> yes
[15:13] <desrt> but the indians write them like ०.१.२.३.४.५.६.७.८.९
[15:13] <mterry> desrt, hmm.  I don't want to write a generic date parser.  I vote ISO 8601
[15:13] <desrt> mterry: ya.  me too.  glad you agree. :)
[15:13]  * mterry wonders if that was the real reason I bailed way back when
[15:13] <desrt> mterry: this is a job that could easily consume a week of your time dealing with edgecases
[15:13] <desrt> i don't think having locale-specific date formats is worth a week of your time
[15:14] <mterry> desrt, also, are you sure there aren't differences between %x and D_FMT...?
[15:14] <desrt> mterry: well
[15:14] <bdrung> Sweetshark: some changelog comments: there is a typo in "diable help building on armel/armhf" -> it should be "disable"
[15:14] <desrt> mterry: you use g_date_time_format()
[15:14] <desrt> which implements %x using D_FMT
[15:14] <desrt> so.... no.
[15:14] <mterry> fair
[15:14] <desrt> no difference :)
[15:14] <bdrung> Sweetshark: you can drop the "tweak Maintainer field" changelog entry
[15:15] <seb128> desrt, mterry: what does ISO 8601 specify?
[15:15] <desrt> seb128: date and time formats
[15:16] <desrt> 2013-03-06T14:16:00
[15:16] <mterry> seb128, specifically, this is YYYY-MM-DD
[15:16] <desrt> among many many other things
[15:16] <seb128> that seems wrong
[15:16] <desrt> yyyy-mm-dd is the international standard
[15:16] <seb128> we would here DD-MM-YYYY here for example
[15:16] <mterry> seb128, it's the only thing that's right in a world of evil
[15:16] <desrt> because, you know, canada uses it
[15:16] <desrt> seb128: no.  you would not.
[15:16] <desrt> seb128: you would do dd/mm/yyyy
[15:16] <desrt> with /
[15:16] <seb128> works for me
[15:17] <desrt> - is reserved for people with sane systems
[15:17] <seb128> as long as days are first
[15:17] <desrt> ie: canadians
[15:17] <bdrung> seb128: YYYY-MM-DD is the only date format that cannot be mis-interpreted
[15:17] <larsu> if days come first, so should the time: 18:37 05/02/2000
[15:17] <desrt> larsu: you mean 37:18, right?
[15:17] <mpt> mterry, are you going to tell me that GTK still doesn't have a datepicker widgets?
[15:18] <larsu> desrt: :D
[15:18] <larsu> seb128: doing it the other way around (year first) makes it sortable, though
[15:18] <seb128> bdrung, there is no mis-interpretation in a specific locale
[15:18] <desrt> seb128: as much as i love little endian, you europeans have the date thing totally wrong :p
[15:18]  * larsu agrees
[15:18] <seb128> larsu, I'm not arguing in favor, I'm just saying that users expect it this wat
[15:18] <seb128> way
[15:18] <mpt> I'm surprised no-one has cited XKCD yet
[15:18] <desrt> the americans do too, of course
[15:19] <bdrung> seb128: okay. the mis-interpretation can only happen if you don't know the locale
[15:19] <mterry> mpt, I went to that comic to remember the ISO number  :)
[15:19] <seb128> larsu, you can claim that the europeans users are stupid and don't care but they are still our users
[15:19] <desrt> seb128: if users see 2013- out in front they know that they should alter their expectation
[15:19] <bdrung> Sweetshark: why where a build-conflict on gcc/g++ (>= 4:4.7~) [!i386 !amd64 !kfreebsd-i386 !kfreebsd-amd64] added?
[15:19] <desrt> seb128: and this is not some theoretical "this way or that, all the same" discussion
[15:19] <seb128> desrt, or they complain that the format is weird
[15:19] <desrt> this is a "mterry will have to spend a week fixing this for you to have it your way" discussion
[15:19] <larsu> seb128: yeah, sadly. I didn't say users were stupid, only that I prefer it the other way around
[15:19] <Sweetshark> bdrung: finished? if not, can you collect the needed changes when you have all of them so that I dont cycle around endlessly doing trivial changes.
[15:20] <mterry> desrt, yeah but then we fix it real nice for everyone forever  :)
[15:20] <bdrung> Sweetshark: nope. not finished with my review.
[15:20] <seb128> larsu, what we prefer doesn't really matter though...
[15:20] <desrt> mterry: if you write this code, i want it in GDateTime :)
[15:20] <seb128> desrt, mterry, larsu: doesn't seem like spending lot of time on though
[15:20] <Sweetshark> bdrung: because we had them before, I dont recheck the debian delta on each upload. usually I purge the delta as far as possible for the next libreoffice major
[15:21] <larsu> seb128: I know, but I want to state my opinion regardless :)
[15:21] <desrt> seb128: the problem is that we have a library function to format dates according to the current locale, but none to parse them back
[15:21] <mterry> mpt, no, I don't believe they do have a date picker.  Let me double check GTK hasn't added one since I last looked
[15:21] <bdrung> Sweetshark: have you done a testbuild on non-i386/amd64? i am not sure what this new build conflict means for non-i386/amd64
[15:22] <mterry> mpt, just their calendar widget
[15:22] <mpt> ffs
[15:22] <desrt> mterry: you want a calendar attached to a label or something?
[15:22] <desrt> like, airline booking site style?
[15:22] <desrt> i bet writing one of those is easier than writing a generic date parser :)
[15:22] <mterry> desrt, mpt: true, we could adjust the design so it isn't directly editable
[15:22] <mpt> Fifteen years and still no datepicker
[15:23] <desrt> also: wtf is the deal with the spin buttons
[15:23] <desrt> i press up and it changes *minutes*?
[15:23] <mterry> desrt, hold it down and it goes faster
[15:23] <desrt> heh
[15:23] <mterry> I think...
[15:23] <desrt> thank god for ntp
[15:23] <mpt> The spin buttons should increment/decrement the selected bit. Currently they increment/decrement ... something.
[15:23] <mpt> Minutes and days.
[15:24] <bdrung> Sweetshark: the build conflict on gcc/g++ (>= 4:4.7~) is new
[15:24] <mterry> mpt, hah, I missed that part of the spec (to increment the selected bit)
[15:24] <desrt> selected?  as in 'the one the cursor is inside of'?
[15:25] <mpt> mterry, I didn't specify it, because it's a standard part of a datepicker :-]
[15:25] <larsu> mpt: isn't a datepicker that lets you choose a date from a calendar much more helpful than a spin box?
[15:26] <desrt> larsu: that's kinda what we're bitching about just now
[15:26] <mpt> larsu, it's much slower, especially if the date is way off, e.g. 1970.
[15:26] <mpt> But other than that, yes. :-)
[15:27] <larsu> but that's an edge case. Who ever sets their time 40 years into the past?
[15:27] <desrt> larsu: happened to me today, quite a few times :)
[15:27] <mpt> larsu, it's one of the most likely wrong years, being Unix year zero
[15:27] <larsu> I knew someone would say that :D
[15:27] <Sweetshark> bdrung: checking ... somebody did suggest whitespace changes to debian, making merges a real pain ...
[15:27] <larsu> mpt: ah, good point
[15:27] <Sweetshark> ;)
[15:28] <larsu> in that case, a text field is probably best...
[15:28]  * larsu prefers NTP anyway
[15:28] <desrt> ya.  thank god for ntp.
[15:28] <mpt> mterry, so, how do you feel about implementing the datepicker if I specify it in detail?
[15:28] <bdrung> Sweetshark: these changes made reading debdiff more easily :)
[15:28]  * desrt is amazed that in all of the option-removing zeal, GNOME hasn't stripped away the option to disable network time
[15:28] <desrt> because, seriously... who actually wants their time to be wrong?
[15:28] <larsu> people who aren't connected to the internet
[15:29] <larsu> oh.  Nevermind.
[15:29] <desrt> actually... i know a lot of people who set their alarm clocks fast
[15:29] <mpt> mterry, basically a text field, where you can navigate between its segments with Left+Right keys, increment/decrement with Up/Down, and type a complete replacement date without having to tab or type separators.
[15:29] <mterry> mpt, I'm fine with it.  But the priority is a different question.  It's not mobile related, so...  :)
[15:29] <mpt> true
[15:29] <desrt> mterry: just commit the revert
[15:29] <mterry> mpt, also it'd be difficult to get right due to the variety of parsing back locale-specific formats, so it would take some time
[15:30] <seb128> it seems non trivial work for little benefit in the big picture
[15:30] <seb128> e.g very low priority
[15:30] <seb128> let's go with the easier fix
[15:30] <mterry> mpt, how much do you hate going back to ISO 8601?
[15:30] <seb128> e.g revert the commit?
[15:30] <desrt> seb128: yes
[15:30] <desrt> we can leave the old bug open in case some day someone wants to make the effort
[15:31] <mterry> This time I'm going to leave a comment, pointing at these bugs
[15:31] <desrt> mterry: good idea :)
[15:31] <Sweetshark> bdrung: sure, I hear you want to do the merges there now.
[15:31] <Sweetshark> ;)
[15:31] <mpt> mterry, I love ISO 8601 with a passion. I use ISO 8601 on all my design sketches. But I usually have to explain it if I dare use it with a non-geek.
[15:32] <desrt> mpt: you should move to canada
[15:32] <desrt> we live and breathe iso 8601 here
[15:32] <bdrung> Sweetshark: the whitespace change should have only created a one time merge complication
[15:33] <mpt> desrt, or Lithuania. The locale settings in Lithuania are awesome.
[15:34]  * desrt would have assumed they used the same as the rest of europe
[15:34] <mterry> desrt, your locale says otherwise, two-digit-year man
[15:34] <desrt> mterry: i told you this is another bug
[15:35] <Sweetshark> bdrung: yep, that is a merge error, moving the Build-Conflicts: from debian to us.
[15:35] <mterry> desrt, :)
[15:35] <mterry> desrt, in my opinion, it's a bug with all the locales that they aren't just iso8601
[15:35] <mterry> But that's the programmer in me talking
[15:36] <desrt> mterry: this is the kind of bug that would be closed 'Opinion' :)
[15:36] <desrt> mterry: let's next move on to how daylight savings time is only used by morons and how we should all be on UTC as well :)
[15:36] <mpt> mterry, perhaps a cheap way of improving the situation would be to add a calendar button next to the date field.
[15:37] <Sweetshark> bdrung: since gcc-4.6 is in universe that would likely result in a component mismatch. Ill remove that conflict again.
[15:37] <mterry> https://code.launchpad.net/~mterry/indicator-datetime/iso8601/+merge/151989 for review
[15:38] <mterry> desrt, pfft, UTC is so Earth-centric.  I bet there are all sorts of cool systems that work in space and at different velocities
[15:39] <mterry> Ubuntu could be a real leader here!  :)
[15:39] <mpt> mterry, I doubt it, because relativity
[15:39] <desrt> mterry: i cite our motto as an appropriate scope
[15:39] <desrt> linux for HUMAN BEINGS
[15:41] <mterry> mpt, stupid relativity making it hard to fix bugs
[15:42] <cyphermox> mterry: approving...
[15:43] <mterry> cyphermox, ooh thnks
[15:43] <cyphermox> desrt: if there's a lot of prospective martian users, we might want to include them too
[15:43] <cyphermox> but then we'll have to rename the distro
[15:43] <cyphermox> or at least change the tag line
[15:44] <mterry> Yeah, seems specist right now (specie-ist?)
[15:44] <cyphermox> haha
[15:44] <Sweetshark> bdrung: 99c0770a6c5033f39649716f353cdefdf55b9379 removed conflicts against 4.7 so we had quantal on 4.7, so it should be good.
[15:44] <cyphermox> my cat even tends to favor walking on my key
[15:44] <desrt> GNOME had a participant in the womens outreach programme who was offended by this
[15:44] <cyphermox> *keyboard rather than others
[15:44] <cyphermox> desrt: by what?
[15:44] <desrt> 'linux for human beings'
[15:45] <desrt> she was also offended by the term 'human rights'
[15:45] <cyphermox> ah
[15:45] <bdrung> Sweetshark: so this change got lost in the merge
[15:46] <cyphermox> would have loved to hear the reasons why, but this is *so* off topic for here
[15:47] <Sweetshark> bdrung: yep, I already removed the conflicts again, but wont push until you completed your review.
[15:49] <bdrung> Sweetshark: you seem to have lost the ttf-sil-gentium-basic -> fonts-sil-gentium-basic change in the merge
[15:55] <Sweetshark> bdrung: fixed
[16:02] <bdrung> Sweetshark: wrap-and-sort change: paste.debian.net/240140/
[16:02] <bdrung> http://paste.debian.net/240140/
[16:03] <bdrung> you can recreate it (on raring) with: wrap-and-sort  -d . -v && for i in control*.in; do echo >> $i; done
[16:10] <Sweetshark> bdrung: hmm, I did a wrap-and-sort bluntly on ./debian. It also touched ./debian/copyright ...
[16:10]  * Sweetshark checks if that is sane.
[16:10] <bdrung> Sweetshark: just revert the copyright change
[16:10] <bdrung> it trims of trailing spaces
[16:11] <bdrung> Sweetshark: the copyright file should be fixed in the experimental branch and then merged
[16:12] <bdrung> it follows an old format specification and it doesn't follow the guidelines
[16:13] <bdrung> it should use Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
[16:17] <bdrung> Sweetshark: control.in: libreofficeVER-writer has a trailing comma in Recommends
[16:17] <bdrung> Sweetshark: "integration  and a GConf backend" -> two spaces instead of one after "integration"
[16:18] <bdrung> Sweetshark: i finished the review of the debian/ diff. now i will check lintian and do an install+using test
[16:21] <Sweetshark> bdrung: fixed (trailing , was already fixed by wrap-and-sort)
[16:27] <Sweetshark> me wonders what happened to the builders -- 9 hours delay before amd64 starts building ...
[16:44] <micahg> amd64 	21 	277 jobs (7 hours 20 minutes)
[19:12] <seb128> desrt, http://youtu.be/VTlPLZfJDVc
[19:12] <seb128> desrt, migration to logind session if you want to listen in
[19:12] <seb128> desrt, #ubuntu-uds-client-1 on IRC
[19:48] <seb128> desrt, you missed it
[19:49] <bryce> Sweetshark, yeah amd64 has been getting swamped now and then for me
[19:57]  * didrocks waves good evening
[21:59] <attente> thomi: for autopilot, i can't type into gedit when launching it using launch_test_application, while doing start_app_window works fine
[22:01] <thomi> attente: Hi - I wonder if alesage can help you with this - I need to catch up on sleep :-/
[22:01]  * thomi quits IRC
[22:02] <attente> thomi: no worries, thanks
[22:02] <alesage> you're stuck with me attente :)
[22:02] <attente> aw drat :)
[22:05] <attente> alesage: maybe i should first ask what the difference between the two are
[22:06] <alesage> attente I believe one uses the Unity native bindings and the other the autopilot-gtk bindings
[22:06] <alesage> and I believe that typing is possible via autopilot-gtk, just trying to demonstrate to myself
[22:08] <alesage> attente, which tests are you working on?
[22:10] <attente> a test i haven't pushed yet
[22:17] <notgary> I'm attempting to install egg-list-box using jhbuild and am making it as far as the build phase before I get the error "/bin/bash: --pkg: command not found". The full output from that phase can be found at http://paste.ubuntu.com/5591640/. I can't find any package called 'pkg' (unless someone's misspelled dpkg). Can anyone help me out with this?
[23:21] <xnox> is there a desktop beer hangout? =)
[23:21] <jbicha> notgary: you should ask in a GNOME channel about that
[23:32] <notgary> jbicha, thanks. I've managed to figure it out anyway. I was missing the Vala build tools. I'll pester the gnome people next time about it :P