[04:51] <pitti> Good morning
[05:24] <larsu> good morning!
[05:34] <didrocks> mornign
[05:34] <didrocks> morning*
[05:34] <larsu> hi didrocks!
[05:34] <didrocks> hey larsu! up early :)
[05:35] <larsu> yep :)
[05:36] <didrocks> how was your week-end?
[05:36] <larsu> good. Went to  climbing park yesterday
[05:36] <larsu> and I pulled something in my back :/
[05:36]  * larsu can't walk properly
[05:37] <larsu> how was yours?
[05:51] <didrocks> urgh :/
[05:51] <didrocks> I hope that you will get better son!
[05:51] <didrocks> soon*
[05:52] <didrocks> we did walk a lot, I guess something like 16kms again for the european days
[05:52] <didrocks> (they open quite a lot of buildings/monuments and orgnanize activities over the week-end for promoting them)
[05:54] <larsu> oh nice!
[05:54] <larsu> how was it?
[05:59] <didrocks> it was great, we avoided the rain ;)
[05:59] <didrocks> we saw a lot of painted walls inside buildings
[05:59] <didrocks> walked from park to park
[05:59] <didrocks> and also visited the local archive which just opened 10 minutes away from our home
[06:00] <didrocks> (it opened 2 weeks ago)
[06:01] <didrocks> you can easily notice the building: http://www.lyonpoleimmo.com/2014/09/16/33284/le-batiment-des-archives-departementales-du-rhone-a-ouvert/
[06:01] <didrocks> (so, seeing how they store the archives, how they manage to get you access to them, and such…)
[06:04] <larsu> sounds very interesting!
[06:04] <didrocks> yeah, it was great
[06:04] <larsu> and that building looks huge :)
[06:04] <didrocks> heh it is, to store all the archive of Lyon and nearby :)
[06:04] <didrocks> archives*
[06:27] <pitti> hey larsu, bonjour didrocks !
[06:27] <larsu> pitti: guten morgen!
[06:27] <didrocks> guten morgen pitti!
[07:01] <JackYu> didrocks, hi
[07:01] <didrocks> JackYu: hey
[07:05] <jack_> didrocks, would please help to upload a package at bug #1371165?
[07:05] <didrocks> jack_: sure, I can handle this, however, you need the FFe to be approved first by the release team
[07:05] <didrocks> (which isn't the case it seems)
[07:06] <didrocks> jack_: you didn't suscribe the release team as per wiki page, that's why they didn't look at it yet
[07:06] <jack_> didrocks, OK, I will do it now:)
[07:06] <didrocks> jack_: mind pinging me back once they approved it? I'll then upload/make a review
[07:07] <jack_> didrocks, sure, thanks.
[07:07] <didrocks> yw! :)
[07:47] <seb128> good morning desktopers!
[07:47] <didrocks> hey seb128!
[07:47] <pitti> it's a Sébastien !
[07:48] <pitti> bonjour !
[07:49] <seb128> lut didrocks, pitti
[08:04] <willcooke> morning all
[08:04] <Laney> hey hey
[08:04] <didrocks> morning willcooke & Laney!
[08:05] <darkxst> hey Laney, didrocks seb128 pitti
[08:05] <pitti> hey darkxst, how are you?
[08:05] <didrocks> hello darkxst
[08:05] <Laney> good day
[08:05] <pitti> hey willcooke
[08:05] <Laney> good weekends?
[08:05]  * pitti waves to Laney, too
[08:06] <darkxst> pitti, good, but been too busy!
[08:06] <seb128> hey everyone
[08:06] <larsu> morning everyone!
[08:06] <didrocks> Laney: excellent, a lot of walking and visiting monuments in the city (it was the week-end were most of monuments normally closed were opened) :)
[08:06] <didrocks> Laney: how about you?
[08:06] <Laney> closed on the weekend
[08:06] <Laney> what witchcraft is this!
[08:06] <didrocks> Laney: not closed on the weekend, just like "closed", no public access :)
[08:07] <willcooke> didrocks, we had a simialr thing "Open London"
[08:07] <Laney> visited baby nephew on saturday, went climbing on sunday & then for a roast at a friend's house :-)
[08:07] <Laney> didrocks: I mean that that's probably one of the days they should definitely be fully open by default?
[08:07] <didrocks> willcooke: yeah, seems it's something european (at least, they call it like this in France)
[08:08] <didrocks> Laney: well, the city town hall for instance isn't opened to the public, and they let people visiting it for those couple of day
[08:08] <didrocks> days*
[08:09] <Laney> oh I get it
[08:09] <Laney> I thought you meant like art galleries
[08:09] <darkxst> Laney, any chance of getting the gnome-desktop transition though still, I've barely been around the computer the last week so havent been able to file a FFe just yet
[08:09] <Laney> darkxst: I emailed poking Robert for it on Friday
[08:09] <darkxst> but I have merges of gnome-desktop, g-s-d and g-c-c
[08:09] <didrocks> Laney: they are opened and free as well (where museum aren't in France), but it's more interesting to visit things you can't usually :)
[08:10] <Laney> for sure
[08:10] <darkxst> Using the 3.10 power plugin/panel to avoid needing upower
[08:10] <didrocks> Laney: willcooke: seems it's called European Heritage Days in your country (http://en.wikipedia.org/wiki/European_Heritage_Days)
[08:11] <didrocks> (and yeah, Open London in London because it shouldn't be named the same :p)
[08:11] <Laney> darkxst: aha, https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1372240
[08:11] <Laney> the problem is that it's beta freeze today
[08:12] <Laney> it would be a good change for us to have in before the beta though I reckon
[08:13] <pitti> Laney:
[08:13] <darkxst> Laney full transition or just the u-s-d/u-c-c changes first?
[08:13] <pitti>     upower: The type of the Device* signal arguments are 'o', not 's'.
[08:13] <pitti>     
[08:14] <pitti> Laney: I just noticed https://launchpadlibrarian.net/185450739/buildlog_ubuntu-utopic-i386.python-dbusmock_0.11.3-1_FAILEDTOBUILD.txt.gz
[08:14] <pitti> Laney: it seems upower 0.9 indeed needs 's', not 'o'
[08:14] <pitti> Laney: I missed that locally as I have upower 0.99 installed in utopic for months (and forgot about it)
[08:14] <pitti> Laney: I take it you only tested that with 0.99, not with 0.9/
[08:15] <pitti> ?
[08:17] <Laney> pitti: Hmm, sorry about that, looks like it but I can't remember for sure
[08:17] <Laney> you want me to fix?
[08:18] <pitti> Laney: nah, I'm on it, I just wanted to ensure that you didn't specifically fix this for 0.9
[08:18] <pitti> Laney: http://paste.ubuntu.com/8401975/ fixes the tests for 0.9 again, verifying with 0.99
[08:19] <Laney> darkxst: I didn't look at the transition itself yet, was focused on this
[08:19] <Laney> do you have a summary of that?
[08:24] <darkxst> Laney, much the same as 3.10, mostly rebuilds, I don't believe there are any api changes outsides of the xrandr/idle monitor code
[08:25] <Laney> okay, file the bug with list of packages please and I'll take a look
[08:32] <jibel> on latest utopic desktop in qemu lightdm doesn't start and I find nothing interesting in the logs. Any idea where to look to find out why this is happening?
[08:33] <jibel> /var/log/lightdm is empty
[08:33] <jibel> this is bug 1371651 btw
[08:45] <darkxst> Laney, Bug 1372346
[08:53] <Laney> darkxst: cheers, subscribed ubuntu-release for you
[09:02] <Sweetshark> moin
[09:04] <Sweetshark> "Someone" (likely a kernel or nvidia-drivers update) broke my nvidia-optimus with an SRU on trusty btw which I pulled in on my first day of vacation ...
[09:06] <Sweetshark> ... xorg just boots into an blank screen but thinks everything is fine. VTs still work and the xorg.log is suggesting a happy start.
[09:07] <Sweetshark> I worked around that by disabling optimus in BIOS (which I am luckily able on this device).
[09:16] <willcooke> Sweetshark, I /think/ popey had the same problem
[09:17] <popey> i dont use optimus
[09:20] <seb128> hum
[09:20] <seb128> we should probably try to get https://packages.qa.debian.org/u/usbmuxd/news/20140913T092542Z.html in utopic
[09:21] <Laney> oh hi seb128 ;-)
[09:21] <Laney> Sweetshark: #ubuntu-kernel maybe, would probably be good to identify the bad package
[09:22] <seb128> hey Laney ;-)
[09:23] <willcooke> seb128, looks like we have 1.0.7 right?
[09:23] <Laney> what's good about that version?
[09:23] <seb128> willcooke, no, https://launchpad.net/distros/ubuntu/+source/usbmuxd 1.0.8
[09:24] <Laney> anyway it's good that we know the uploader
[09:24] <seb128> Laney, it should fix those gvfs-afc segfault we get
[09:25]  * seb128 looks back for the bug
[09:26] <seb128> bug 1355020
[09:26] <seb128> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745844
[09:26] <seb128> Laney, ^
[09:27] <seb128> there is also https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/1363583
[09:27] <Laney> kay
[09:28] <Laney> hyperair: we're talking about your package here
[09:28] <seb128> which states that any program using that lib ^ is going to segfault until we update usbmuxd
[09:28] <hyperair> hmm?
[09:28] <hyperair> yeha i uploaded a snapshot
[09:28] <Laney> seb128 is wondering about syncing it
[09:28] <seb128> should we sync that to utopic?
[09:28] <hyperair> sure
[09:28] <hyperair> but please do the testing
[09:28] <seb128> I don't have the required hardware for that :/
[09:28] <hyperair> nor do i
[09:28] <hyperair> this is a joke
[09:29]  * hyperair is maintaining the libgpod bunch of stuff because nobody else will do it
[09:29] <hyperair> but i haven't an iphone myself
[09:29] <Laney> apply to the dpl for an iphone :-)
[09:29] <hyperair> let the iphone users burn. \o/
[09:29] <hyperair> nothanks, that shit shall stay out of my hands
[09:29] <hyperair> evil devices, those
[09:29] <seb128> well, the bts ticket has a comment from an user saying the update fixes the issue
[09:29]  * hyperair strokes his nexus 5
[09:29] <hyperair> well, that's good enough for me. =p
[09:29] <seb128> let's sync!
[09:29] <Laney> this is all very reassuring :P
[09:29] <hyperair> indeed
[09:30] <hyperair> \o/
[09:30] <hyperair> thing is, usbmuxd hasn't moved for 5 months or so before i packaged that snapshot
[09:30] <hyperair> upstream i mena
[09:30] <seb128> willcooke, do you know of anyone having an iphone around?
[09:30] <hyperair> so i guess it should be okay enough
[09:30] <seb128> yeah, fedora is also shipping a snapshot
[09:30] <hyperair> alright
[09:30] <hyperair> is it the same rev?
[09:30] <hyperair> and eh.. fedora isn't very reknown for its stability, is it?
[09:30] <seb128> http://pkgs.fedoraproject.org/cgit/usbmuxd.git/
[09:31] <seb128> 1.0.9-0.6.c24463e
[09:31] <willcooke> seb128, I have a 5s
[09:31] <seb128> indeed not
[09:31] <hyperair> but debian's doing it, so it must be okay!
[09:31] <seb128> lol
[09:31]  * hyperair coughs
[09:31]  * hyperair hides under the desk
[09:31] <seb128> seems like willcooke can test things on a 5s
[09:31] <seb128> what sort of testing do we need?
[09:31]  * willcooke . o ( the shame)
[09:31] <seb128> like "is it listed/working in rhythmbox"?
[09:31] <hyperair> no idea, plug it in, see if things randomly segfault?
[09:31] <hyperair> try syncing
[09:32] <hyperair> i've heard people complaining that it doesn't work in 14.04 itself
[09:32] <seb128> willcooke, what's current happening if you plug that device on a 14.10 deskto?
[09:32]  * willcooke will have to install a 14.10 desktop
[09:32] <willcooke> I assume this won't work well via a vm
[09:32] <hyperair> so we uh, have 5 more commits over fedora's snapshot
[09:32] <hyperair> mostly bugfixes
[09:32] <seb128> willcooke, not running Ubuntu are you? ;-)
[09:32] <hyperair> ...and a protocol version switch
[09:32]  * seb128 ducks
[09:33] <seb128> hyperair, urg
[09:33] <willcooke> wait, I have to use this strange Linux thing do I?
[09:33] <hyperair> indeed
[09:33] <seb128> not the strange one
[09:33] <willcooke> I stick with LTS
[09:33] <seb128> the one for Ubuntu beings
[09:33] <seb128> Human*
[09:33] <seb128> even
[09:33] <hyperair> THE ONE FOR HOOMINS
[09:33] <willcooke> but I will install 14.10 on my Inspiron
[09:33] <seb128> thanks
[09:34] <hyperair> yay
[09:34]  * willcooke downloads the iso
[09:34] <seb128> good opportunity to try 14.10 daily :p
[09:34] <seb128> willcooke, thanks
[09:34] <hyperair> seb128: in any case, upstream says there shall be another release soon
[09:34] <seb128> hyperair, yeah, but beta freeze is today for us
[09:34] <hyperair> mm
[09:34] <hyperair> just stick it in
[09:34] <hyperair> let the beta testers flush the issues out
[09:34] <seb128> yeah
[09:34] <Laney> do it, we can sync that later if necessary
[09:34] <seb128> Laney, ^ wdyt?
[09:34] <hyperair> indeed
[09:35] <seb128> who want to press the button? ;-)
[09:35] <hyperair> it's probably just moar bugfixes after this
[09:35] <hyperair> go go
[09:35] <happyaron> didrocks: can you have a look at this bug? https://bugs.launchpad.net/ubuntu/+source/fcitx-qimpanel-configtool/+bug/1371912
[09:35] <hyperair> 2014-09-10 04:07:41<nikias> hyperair just spoke to psp250. We'll cook up a release in the next few days.
[09:35] <happyaron> didrocks: seems it's blocking fcitx-qimpanel's proposed migration
[09:36] <hyperair> next few days > (22 - 10) apparently.
[09:36] <seb128> great
[09:36] <Laney> cool
[09:37] <happyaron> attente_: is there any missing bit in the new fcitx release for you?
[09:37]  * Laney acks bug #1372240
[09:37] <seb128> Laney, hyperair, ok so should I do the sync?
[09:37] <Laney> ok
[09:37] <hyperair> http://paste.debian.net/122326/ <-- this is what's changed in usbmuxd since i did that upload
[09:37] <hyperair> seb128: yeah go ahead
[09:38] <seb128> done
[09:38] <hyperair> hmmmm
[09:38] <Laney> OH GOD WHAT HAVE YOU DONE
[09:39] <seb128> lol
[09:39] <hyperair> :D
[09:39] <hyperair> O:D
[09:39] <hyperair> OO:D <-- multiple halos for more credibility
[09:39]  * Laney notices a bitcoin mining process running
[09:39]  * hyperair lols
[09:39] <didrocks> happyaron: sounds good, removing! :)
[09:40] <didrocks> happyaron: you added some Replaces: in the version in proposed if it's installing the same files?
[09:41] <happyaron> yes
[09:42] <seb128> Laney, btw, new gst1.0 bugfix versions, should I sync gst/base?
[09:42]  * didrocks flushes
[09:42] <Laney> jibel: sorry for no reply, I just installed the daily in qemu and it works for me
[09:43] <didrocks> happyaron: next publisher cycle should have the removed
[09:43] <Laney> seb128: already downloading to test build / install / sync
[09:43] <didrocks> removal*
[09:43] <seb128> Laney, great
[09:43] <seb128> Laney, oh, can you get the new glib in rtm btw?
[09:43] <Laney> erm
[09:43] <seb128> Laney, since it fixes the wakeup isue
[09:43] <Laney> the polling thing?
[09:43] <seb128> yes
[09:43] <Laney> I suppose so
[09:43] <seb128> that's important for the phone
[09:43] <seb128> great
[09:43] <seb128> thanks
[09:43] <Laney> it's just the process
[09:44] <jibel> Laney, looks like a race somewhere, sometimes it starts, sometimes it doesn't.
[09:44] <Laney> whatever is the test plan for glib ...
[09:44] <seb128> Laney, "make sure things keep working" :p
[09:44] <Laney> seb128: I would like it if we could upload usd/ucc today too
[09:44] <Laney> do you know if those branches are attached to the bug are it?
[09:44] <seb128> Laney, for gnome-desktop?
[09:45] <Laney> yeah
[09:45] <Laney> think it would be good to be in the beta
[09:45] <seb128> I think they are yes
[09:45] <happyaron> didrocks: thanks
[09:45] <Laney> okay
[09:45] <Laney> would you be able to put it in the train?
[09:47] <seb128> sure
[09:48] <Laney> ty
[09:48] <jibel> Laney, it happens once every 5 boots or so on my machine
[09:49] <Laney> jibel: alright, I'll reboot a few times
[10:00] <happyaron> Laney: do you mind to add ubiquity-slideshow-ubuntu to ubuntukylin packageset? I sent to request to devel-permission just now
[10:01] <seb128> Laney, can I upload a glib with a distro patch to silent those property warnings? ;-)
[10:01] <Laney> yes, that's shared with ubuntu
[10:02] <Laney> if you want, but I'm sad about it
[10:02] <seb128> Laney, well, what else do you suggest so I can work without having my command line spammed with warnings? ;-)
[10:02] <Laney> export G_ENABLE_DIAGNOSTICS=0
[10:03] <seb128> we can spend efforts on GTK, but I see little point doing that when we are going to get the fixes for free next cycle when we update
[10:03] <Laney> :-)
[10:03] <seb128> we are not going to ask every user to export a "UNBUG_MY_DEV_ENV"
[10:03] <Laney> you said 'my'
[10:03] <seb128> well, I'm interested in a solution for utopic
[10:03] <seb128> which I'm using
[10:04] <seb128> so yeah, if we fix utopic, it fixes my case as well :p
[10:04] <seb128> do you think we benefit that much from those warnings?
[10:04] <seb128> it doesn't seem like something that adds value to the release to me
[10:05] <seb128> we are going to get those warning back next cycle, when we get the new GTK and don't get the side effect of having glib/gtk mismatching
[10:05] <didrocks> seb128: +1 for the distro patch
[10:05] <Laney> I think it is gtk's problem, not glib's, so working round it there is bad form
[10:05] <Laney> but go for it if you don't think fixing that is worth it
[10:05] <seb128> Laney, well, as said we can spend efforts on silencing GTK warnings on a version we plan to replace when next cycle opens
[10:05] <happyaron> Laney: then please add it when convenient
[10:06] <seb128> but it doesn't seem a good use of our resources to me
[10:06] <Laney> happyaron: that was "yes I do mind"
[10:06] <seb128> didrocks, thanks
[10:06] <seb128> Laney, thanks as well
[10:06] <happyaron> Laney: ok..
[10:06] <Laney> sorry, but it shouldn't have packages which are shared with Ubuntu
[10:06] <Laney> it's a policy
[10:06] <happyaron> fine to me
[10:07] <seb128> Laney, I'm going to distro patch that for utopic, so we don't waste resources reducing noise on a gtk version which is not buggy for users otherwise, knowing that gtk is already fixed in the new serie so things are sorting themself once we update
[10:07] <Laney> I guess my main problem is that it is targeting one problem with a solution that affects everything
[10:08] <Laney> and if you want to do that thing then it is for upstream
[10:08] <seb128> well, it's not like those warnings were useful in a stable version
[10:08] <seb128> it's the same way we turn off apport for release
[10:08] <Laney> but last time desrt didn't want to add such a thing to glib, so ...
[10:09] <seb128> well, he provided me the patch
[10:09] <seb128> and it said it makes sense rather than spending time "fixing" gtk 3.12
[10:09] <seb128> with the agreement that the patch is only for utopic
[10:09] <seb128> next cycle we have a fixed gtk and we can go back to show warnings during unstable serie
[10:09] <didrocks> I really don't think users must undergo the technical details of why we didn't upgrade some parts when there is no visible effect at all of the cause
[10:09] <didrocks> and we should always keep that in mind for our decisions
[10:10] <Laney> I've made my points, this is circular now
[10:10] <Laney> just do it
[10:11] <darkxst> gah, https://code.launchpad.net/~darkxst/unity-settings-daemon/xkb still not been merged ;(
[10:12] <Laney> that can be in this landing
[10:16] <darkxst> Laney, ok, so land the unity changes pre freeze? and the rest post freeze?
[10:16] <Laney> think so
[10:18] <darkxst> Laney, I just pushed all rebuild to ppa:darkxst/gnome-desktop, so that basically has everything except u-s-d/u-c-c
[10:20] <Laney> darkxst: I'd like it if they were in a copyable form
[10:20] <Laney> ie using distro version numbers
[10:21] <willcooke> seb128, got 14.10 installed.  what do you need me to do?
[10:22] <seb128> willcooke, connect your iphone to usb and see what happens I guess
[10:22] <darkxst> Laney, sure can do, I can repush them after freeze
[10:22] <seb128> like is it listed as a mount
[10:22] <seb128> willcooke, see if rhythmbox lists it/includes music
[10:23] <willcooke> seb128, 1st plugin in = crash of something.  Trying to work out what
[10:23] <seb128> willcooke, gvfs-afcd I guess?
[10:23] <willcooke> seb128, now I've told the phone to "trust" the desktop, and trying again
[10:24] <seb128> willcooke, the "details" in the apport dialog should tell you what process it was
[10:24] <willcooke> seb128, "Unable to mount $iphone_name. Message did not receive a reply (timeout by message bus)"
[10:26] <willcooke> seb128, gvfs-afc-volume-monitor
[10:26] <seb128> k
[10:26] <willcooke> seg fault
[10:26] <willcooke> in strlen()
[10:27] <willcooke> and then
[10:27] <seb128> willcooke, great, now we need to see if the issue is still there with the usbmuxd update from this morning
[10:27] <willcooke> "The problem cannot be reported.  You have obsolete package version installed"
[10:27] <seb128> it should be fixed with the new version
[10:27] <willcooke> seb128, so I should wait a day or so, upgade and try again
[10:27] <willcooke> ?
[10:27] <Laney> darkxst: preferably in a dedicated ppa
[10:27] <Laney> so I can just copy everything from it
[10:28] <seb128> willcooke, no need to wait a day, it's in utopic, run update-manager, upgrade, reboot, try again
[10:28] <Laney> ty
[10:28] <willcooke> seb128, ack
[10:28] <seb128> willcooke, thanks
[10:29] <seb128> willcooke, the package just migrated, it might take another 15 minutes before apt/update-manager sees the update
[10:29] <willcooke> seb128, no worries
[10:30] <darkxst> Laney, what do you mean? that is a dedicated ppa (although it still has trusty packages from last time around)
[10:30] <Laney> darkxst: indeed, there's other things in there
[10:30] <Laney> you can delete those instead if you want
[10:34] <seb128> darkxst, Laney, you want https://code.launchpad.net/~darkxst/unity-settings-daemon/xkb/+merge/224919 to be merged as well?
[10:34] <seb128> that needs to be rebased on top of https://code.launchpad.net/~robert-ancell/unity-settings-daemon/xrandr/+merge/224548 if so
[10:34] <seb128> they conflict on debian/control changes
[10:35] <darkxst> seb128, yes, let me rebase now
[10:35] <seb128> thanks
[10:37] <willcooke> tkamppeter, email from Brother re: IPP. CC'd you on the reply. They're going to test their IPP printers with 14.10 \o/
[10:38] <seb128> nice!
[10:44] <darkxst> seb128, rebased and pushed, but silly bzr ate the history
[10:44] <seb128> k
[10:44] <seb128> the way you do it usually is merge trunk/the other vcs in, resolve the conflict and commit that
[10:45] <seb128> bah
[10:46] <seb128> is bugzilla.gnome.org down?
[10:46] <seb128> oh, no, just slow it seems
[10:51] <darkxst> seb128, that seems kind of backwards but then I mostly work with git more than bzr
[11:22] <Laney> I hope I'm driving this rtm sync right ........
[11:23] <seb128> Laney, can l53 be deleted? https://launchpad.net/ubuntu/+source/indicator-session/12.10.5+14.10.20140919-0ubuntu1 seems to include the change you describe in there
[11:23] <Laney> that landed
[11:23] <Laney> don't know about deleting lines, never done that before
[11:23] <seb128> just delete it if it's deprecated
[11:24] <Laney> ok
[11:25] <darkxst> seb128, repushed branch with fixed history
[11:25] <seb128> darkxst, shrug
[11:25] <seb128> I had it in a silo building
[11:25] <seb128> I guess I can start from scratch again now :/
[11:26]  * seb128 is slightly annoyed
[11:26] <darkxst> seb128, I told you the history was messed up
[11:26] <seb128> well, I didn't care much about that
[11:26] <seb128> as long as the code changes are ok
[11:26] <seb128> but ok, let me see if I can cancel the build
[11:27] <Laney> If you can't I can, give me a PPA link
[11:27] <seb128> I clicked the red cross on the jenkins job
[11:27] <seb128> trying to restart a build
[11:28] <Laney> you might have to cancel the actual build  in the PPA too
[11:28] <seb128> it was still preparing the packages, didn't do the actual dput I think
[11:28] <Laney> oh I don't even see it https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-020
[11:28] <seb128> https://ci-train.ubuntu.com/job/ubuntu-landing-020-1-build/35/console
[11:28] <Laney> yeah
[11:28] <Laney> not much loss then
[11:59] <seb128> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-020/+packages
[11:59] <seb128> has u-s-d/u-c-c to test
[12:52] <willcooke> seb128, do I need to be running proposed in order to get those updates?
[12:52] <seb128> willcooke, no
[12:52] <seb128> they should be available by now, if you are not using a mirror at least
[12:52] <willcooke> just looking to see whats been upgraded
[12:53] <willcooke> some glib networking things
[12:53] <willcooke> ahhh
[12:53] <willcooke> usbmuxd
[12:53] <willcooke> kk
[12:56] <willcooke> hrm now upowerd is segv
[13:03] <willcooke> seb128, ok - it's better.  It mounts the device and it knows its a music player and a camera
[13:04] <seb128> willcooke, great!
[13:04] <willcooke> but I still see an error "unable to mount $iphone_device_name.  Unhandled lockdown error (-256)"
[13:04] <willcooke> that error doesnt seem to break anything though
[13:04] <willcooke> like
[13:04] <willcooke> I can see browse the device
[13:06] <seb128> willcooke, thanks, iphone support is known to be suboptimal, I wanted to see at least the segfault resolved
[13:06] <seb128> which seems to be the case
[13:06] <willcooke> yeah, certainly an improvement
[13:07] <willcooke> seb128,  second boot everything worked fine
[13:07] <seb128> nice!
[13:24] <seb128> Laney, do you want to test that ppa more? or should I just land that to utopic?
[13:25] <Laney> seb128: I didn't test it yet, let me just install and reboot
[13:25] <seb128> Laney, thanks
[13:29] <Laney> seb128: ucc is still building?
[13:30] <seb128> Laney, oh right, I keep forgetting you guys don't use i386 ;-)
[13:31] <Laney> yeah I should upgrade to that at some point
[13:31] <seb128> hehe
[13:34] <seb128> Laney, ok, amd64 built, I guess it's going to take some extra minutes for the index to be updated
[13:34] <Laney> ok, cool, should give me time to prod at this script some more
[13:35] <Laney> what the hell is up with lxc lately
[13:41]  * Sweetshark building LibreOffice 4.3.2~rc2 with fixed mergedlibs, autopkgtests and dropped transitionals
[13:42] <desrt> Laney: btw: i have another glib stable on the way
[13:42] <desrt> which one you package is not really critically important
[13:42] <desrt> but the existing stable misses some semi-important bsd-related fixes
[13:43] <desrt> i got to hear about that all weekend long from some of my new friends :)
[13:43] <Laney> oh well I didn't start on that
[13:43] <desrt> i'll have .2 out the door today some time
[13:43] <desrt> along with the .0
[13:44] <Laney> wouldn't want to upset the ubuntu/freebsd community
[13:44] <desrt> :)
[13:44] <desrt> that's why i say that it doesn't matter much for you :p
[14:39] <seb128> Laney, https://git.gnome.org/browse/shotwell/tree/NEWS ... do you consider shotwell 0.18 -> 0.20 as something that requires a ffe?
[14:42] <Laney> I think so, for those new services, would be good to have it tested
[14:42] <seb128> I've no clue what those services are and no real interest into looking into that
[14:42] <seb128> what if I disable build of those new services? :p
[14:42] <didrocks> seb128: thanks for source NEWing nose-json on Friday btw, mind looking at binNEWing it? :)
[14:43] <JackYu> laney, hi, would you please review the FFe request at bug #1371165?
[14:43] <Laney> then it would probably be fix only
[14:43] <seb128> didrocks, sure, looking
[14:43] <didrocks> thanks
[14:43] <seb128> Laney, thanks
[14:44] <JackYu> Laney, Hi~~
[14:45] <Laney> JackYu: I will do
[14:45] <JackYu> Laney, great, thanks:)
[14:57] <seb128> Laney, ok, so those are plugins which are not enabled by default for non-common services (one of them is a czesh specific one) ... is it worth filing a ffe if I state I can't/don't wantt to spend time trying to get those exotic options tested?
[14:57] <seb128> Laney, or is it better if I try to axe in the build-system to make them not installed at all?
[15:00] <Laney> you mean that you have to go to preferences -> plugins and enable them?
[15:01] <JackYu> Laney, also, could you help to release the "ubiquity-slideshow-ubuntu 87"? we have merged the ubuntu-kylin-slideshow into it.
[15:02] <seb128> Laney, yes
[15:02] <Laney> JackYu: I think that is in https://launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/86
[15:03] <JackYu> Laney, yeap...
[15:05] <Laney> JackYu: it's in the NEW queue for an archive admin to review https://launchpad.net/ubuntu/utopic/+queue?queue_state=0&queue_text=
[15:07] <seb128> Laney, JackYu, slideshow NEWed
[15:08] <seb128> didrocks, nose binNEWed as well
[15:08] <didrocks> seb128: thanks!
[15:08] <seb128> yw!
[15:08] <JackYu> seb128, Laney, that's great, thanks.
[15:09] <seb128> ok, I'm off for some exercice
[15:10] <seb128> Laney, would be nice if you could test the silo ppa so I can publish when I'm back, also please advice what to do for shotwell, I would like to get that update/the bugfixes in utopic
[15:10] <seb128> bbiab
[15:11] <Laney> seb128: I think you can upload shotwell, but I don't much like "I don't want to test the new features" :(
[15:11] <Laney> Fair enough if the Czech one is too hard to do though
[15:11] <Laney> I'll test the silo in parallel with DMB
[15:15] <seb128> Laney, I would test the features if they were things most users would use/exercice or easy to hit, I'm not going to create some accounts on random online services with my email to test some hidden plugin functionality though
[15:16] <seb128> I'm happy to hack the buildsystem/packaging around to drop those plugins though
[15:16] <seb128> thanks for the testing!
[15:27] <Laney> the silo seems good from what I can see
[15:31] <JackYu> Hi Laney, how about bug #1371165?  tomorrow is beta final freeze:).
[15:31] <Laney> I'm just finishing up with a meeting
[15:33] <JackYu> I see. Busy Monday...
[15:36] <Laney> JackYu: there you go
[15:37] <JackYu> Laney,  thanks!
[15:39] <JackYu> didrocks, hi, could you help to upload this package at bug #1371165 ? Laney approved the FFe just now.
[15:39] <didrocks> JackYu: hum, let me have a look
[15:40] <didrocks> JackYu: seems like you already asked and gave to seb128, right?
[15:40] <didrocks> seeing that he commented 5 hours ago)
[15:40] <JackYu> didrocks, seb128 have helped to review it.
[15:41] <didrocks> JackYu: where are the updates? https://code.launchpad.net/~luolei/ubuntu-kylin-sso-client/trunk is from the 19th
[15:42] <didrocks> JackYu: the debian/copyright fix is not in trunk
[15:43] <JackYu> didrocks, let's me check.
[15:44] <didrocks> JackYu: also: bzr: ERROR: Inconsistency between source format and version: version is native, format is not native.
[15:44] <didrocks> debian/source/format should be: 3.0 (native)
[15:45] <Laney> diff the packaging with ubuntu-sso-client? ;-)
[15:45] <didrocks> Laney: yeah, I was doing that, seems similar
[15:45] <JackYu> didrocks, I will update the code asap.
[15:45] <didrocks> Laney: the thing is that I can't even bzr bd :p
[15:48] <didrocks> JackYu: in addition to what seb128 told: W: ubuntu-kylin-sso-client source: missing-license-paragraph-in-dep5-copyright gpl-3 with openssl exception (paragraph at line 3)
[15:48] <didrocks> please add the paragraph
[15:49] <didrocks> JackYu: also debian/tests/control mentions a run-tests file which doesn't exist in debian/tests/
[15:50] <JackYu> didrocks, Sure.
[15:50] <didrocks> JackYu: nitpick, but, please change the date to be a real one in debian/changelog
[15:50] <didrocks> Thu, 19 Sep 2014 -> was a Friday
[15:50] <didrocks> JackYu: a hint, when you build the package, you have lintian warnings in the end, they tell you that :)
[15:51] <JackYu> OK!
[15:51] <Laney> I think the Tests-Directory: . fixes the debian/tests thing
[15:51] <Laney> Makes it look in the root of the package which has such a script
[15:51] <didrocks> Laney: I compared to u-s-c, and it seems that they still have the other file
[15:51] <didrocks> I don't really know and want to risk blocking in proposed though, wdyt?
[15:52] <didrocks> if you are sure it's working that way, fine with me :)
[15:52] <Laney> this is also part of the diff
[15:52] <Laney> +Tests-Directory: .
[15:52] <didrocks> JackYu: and finally (other small things, but not too big):  ubuntu-kylin-sso-client-qt has a too long description line, please wrap in debian/control to 80 characters
[15:53] <didrocks> Laney: ah ok, thanks for the hint, JackYu: please ignore the test comment then
[15:53] <Laney> Looks like all the Ubuntu one does is run that script
[15:53] <JackYu> good:)
[15:53] <Laney> someone's clever, fixing that :P
[15:54] <didrocks> JackYu: oh, and in debian/control -> Priority: extra -> set it to optional please :)
[15:54] <didrocks> no reason to have it extra
[15:56] <didrocks> JackYu: ok, the rest is minor, just do those changes and I'll NEW it
[15:57] <JackYu> didrocks, got it, dong now
[15:57] <didrocks> JackYu: seeing the commit: 7 Files: *
[15:57] <didrocks>  7Files: all others
[15:57] <didrocks> this is wrong :)
[15:57] <didrocks> for the second one, just keep Files: *
[15:58] <didrocks> (this will be "all other files" from the spec)
[16:08] <didrocks> JackYu: do you think you are nearly done? I'm going to EODing soon, but I guess seb128 can finish it once he's back as he will finish later on
[16:09] <didrocks> (I posted my comments on the bug report so that he can continue)
[16:10] <JackYu> didrocks, in 2 minutes:)
[16:12] <didrocks> JackYu: also, in changelog, add the LP: #bugnumber for the FFe so that people aren't suprised by the new package :) (even if it won't close the bug automatically)
[16:13] <JackYu> got it.
[16:17] <JackYu> didrocks, Committed.
[16:18] <didrocks> JackYu: forgot to push? https://code.launchpad.net/~luolei/ubuntu-kylin-sso-client/trunk
[16:18] <JackYu> oh...
[16:19] <JackYu> didrocks, wait a moment
[16:21] <JackYu> didrocks, I got this error: bzr: ERROR: Cannot lock LockDir(chroot-78301392:///%2Bbranch/ubuntu-kylin-sso-client/.bzr/branch/lock): Transport operation not possible: readonly transport
[16:21] <didrocks> JackYu: you stopped a bzr push I guess
[16:22] <didrocks> you need to break the lock
[16:22] <didrocks> JackYu: bzr break-lock lp:ubuntu-kylin-sso-client
[16:22] <JackYu> OK, thanks.
[16:22] <didrocks> then, if it's your lock, answer yes and bzr push again
[16:22] <Laney> I think not
[16:22] <Laney> from that URL it looks like the branch is owned by someone else
[16:23] <Laney> only the owner can push to it, assuming that ~luolei is a person and not a team
[16:23] <didrocks> oh right
[16:23] <didrocks> https://code.launchpad.net/~luolei/ubuntu-kylin-sso-client/trunk
[16:23] <didrocks> it's not a team
[16:23] <didrocks> JackYu: ^
[16:23] <JackYu> Oh...
[16:24] <didrocks> meanwhile, push to your namespace
[16:24] <Laney> you could do bzr push lp:~ubuntukylin-members/ubuntu-kylin-sso-client/trunk
[16:24] <Laney> and switch the trunk branch of that project to point to this team one
[16:24] <didrocks> and I'll push the package from it
[16:24] <Laney> that seems sensible to me
[16:24] <didrocks> yeah
[16:24] <JackYu> OK
[16:25] <JackYu> You both are smart guys:)
[16:25] <JackYu> pushing
[16:25] <Laney> too much time clicking in launchpad over the years
[16:26] <JackYu> lol:)
[16:27] <didrocks> JackYu: the line too long in debian/control is actually " Qt frontend to be used by the desktop service to sign into Ubuntu Kylin services
[16:27] <didrocks> "
[16:27] <didrocks> you removed the line after :)
[16:29] <didrocks> all the rest is fine (for reference, you normally reference launchpad bugs with LP: #bugnumber, but it's not important in that case as the bug can't be closed automatically until the package is in ubuntu
[16:29] <didrocks> JackYu: want me to fix debian/control and push it somewhere?
[16:29] <didrocks> will be quicker
[16:29] <JackYu> didrocks, that's very nice
[16:29] <JackYu> please:)
[16:31] <didrocks> JackYu: yw! you can pull from there: lp:~didrocks/ubuntu-kylin-sso-client/fix-description-wrapping
[16:31] <didrocks> JackYu: uploading it for you now and NEWing
[16:31] <didrocks> W: ubuntu-kylin-sso-client source: missing-runtime-test-file ./run-tests
[16:31]  * didrocks trusts Laney then
[16:31] <didrocks> It will be all your fault dude! :)
[16:31] <Laney> me?
[16:32] <JackYu> didrocks, thanks. I will pull back now.
[16:32] <Laney> you could try running the tests!
[16:32] <JackYu> Laney, lol...
[16:32] <didrocks> Laney: in case the directory trick doesn't work :)
[16:32] <Laney> it's okay, I'll be far away by the time we find that out
[16:32] <Laney> on the beach sipping cocktails
[16:32] <didrocks> Laney: ahah :)
[16:33] <didrocks> JackYu: ok, I'll ping you on #ubuntu-release FYI with the NEWing and source NEW :)
[16:33] <didrocks> and then bin NEW
[16:35]  * didrocks links downstream and upstream project meanwhile
[16:35] <didrocks> hum, building starts in 17 minutes
[16:35] <didrocks> seems the builders are busy
[16:36] <didrocks> seb128: in case I'm not around anymore once ubuntu-kylin-sso-client binary packages are built, mind binNEWing them? I've already reviewed with a local build and I +1.
[16:36] <Laney> looks like a kde flood
[16:36] <didrocks> JackYu: FYI ^
[16:36] <didrocks> Laney: yeah, seems so :p
[16:37] <seb128> didrocks, ok
[16:37] <didrocks> thanks seb128!
[16:38] <seb128> yw!
[17:11] <willcooke> EOD, tata
[17:15] <tsdgeos> seb128: kenvandine: https://code.launchpad.net/~aacid/ubuntu-system-settings/update_pot/+merge/235497
[17:15] <seb128> tsdgeos, we don't do mps for pot update, we just commit to trunk
[17:15] <tsdgeos> i tried
[17:16] <tsdgeos> i have no power
[17:16] <tsdgeos> so you can do it
[17:16] <tsdgeos> maybe
[17:16] <tsdgeos> or approve my mp :D
[17:16] <seb128> well, approving your mp sure
[17:16] <seb128> but that's not going to make that change land
[17:16] <tsdgeos> right
[17:16] <tsdgeos> seb128: so then you can do it or give me moar powers :D
[17:17] <seb128> you want to be added to the team?
[17:17] <tsdgeos> not really, i just want stuff to be translatable
[17:17] <seb128> I'm fine doing it, more reviewers for us, it's always good
[17:17] <tsdgeos> you get to choose how we make it happen :)
[17:17] <seb128> we all do
[17:17] <seb128> but those manual pot updates suck
[17:17] <tsdgeos> agreed
[17:17] <tsdgeos> i've complained to about everyone i could
[17:17] <tsdgeos> probbly not you
[17:18] <seb128> complaining is not providing a solution though
[17:18] <tsdgeos> :D
[17:18] <seb128> tsdgeos, added you to the settings team, feel free to commit
[17:18] <seb128> or to push rather
[17:19] <tsdgeos> seb128: as i've said to lots of people we have a solution that works in KDE land, and we're a bunch of random non paid hackers, if we don't have a solution in canonical is because noone seems to think it's important, not because it's hard
[17:19] <seb128> tsdgeos, we have a solution for years on the Ubuntu side
[17:19] <tsdgeos> doesn't seem to be working ^_^
[17:19] <tsdgeos> pushed
[17:20] <seb128> the Ubuntu solution is working
[17:20] <seb128> it's just that it doesn't work for clicks
[17:20] <seb128> so people decided to translate the upstream components and not the Ubuntu package
[17:20] <seb128> thanks
[17:21] <tsdgeos> yw :)
[17:21] <seb128> also KDE has an easier job (as does GNOME)
[17:22] <seb128> they probably have consistant build tools accross their components
[17:22] <tsdgeos> true, but we don't use the build system to generate the .pot files so that's a non issue
[17:22] <seb128> e.g you have a standard way to update the pot
[17:22] <seb128> well, you probably use standard tools though
[17:22] <seb128> like intltool
[17:22] <seb128> or whatever qt is using
[17:22] <tsdgeos> yep, have a Messages.sh file somewhere that does the work
[17:23] <tsdgeos> daemon will find it, run it and be done with it
[17:23] <seb128> if everything was using intltool it would be easy
[17:23] <seb128> we could call intltool-update automatically
[17:24] <tsdgeos> anyhow, got things to do
[17:24]  * tsdgeos waves
[18:16] <happyaron> seb128: can you also binNEW ubuntukylin-wallpapers-utopic after it's built?
[18:17] <kodiak11> Is there a quick guide on customizing / making the most use of Unity for new users to Unity but obviously not to Linux?  I'm coming from the XFCE world and trying to give Unity a fair shake.
[18:18] <sarnold> kodiak11: hold down the windows key and you'll get a cheatsheet dialog box
[18:19] <kodiak11> so that's how to get the damn thing back lol
[18:20] <kodiak11> I X'd it on the first boot and was like I'll look later...
[18:20] <sarnold> hehe
[18:28] <seb128> happyaron, sure
[18:29] <happyaron> seb128: thanks, and btw both wallpapers and sso client are NEW now, :)
[18:29] <seb128> k
[18:29] <seb128> yw!
[19:09] <seb128> happyaron, NEWed
[19:10] <happyaron> yea!
[19:10] <happyaron> time for bed..
[19:14] <seb128> happyaron, night