[04:23] <pitti> Good morning
[08:54] <ki7mt> Hello all, I have couple merge proposals (server test cases) any chance one of the commiters can look at them so I can get the bugs closed?
[08:56] <elfy> ki7mt: I'll look at them both in the next hour or so
[08:57] <ki7mt> elfy, Thanks, appreciate that.
[08:59] <elfy> welcome
[09:40] <elfy> ki7mt: there's a few issues with them still
[09:42] <ki7mt> elfy, Yes, I got your emails, I thought I had all those "Should's" out of there I guess I missed one.
[09:42] <elfy> mmm
[09:42] <elfy> wonder if I was looking at the right one then - there were a lot
[09:42] <ki7mt> The KB stuff was kind hard to explain, but going though the installer, it's the selections.
[09:43] <elfy> ok
[09:43] <ki7mt> I'll review them again, no probs and drop you a note tomorrow.
[09:44] <elfy> ok - mark it for review again - you can put elfy in the name - I'll notice that :)
[09:44] <ki7mt> Just to be clear though, I did a push to update the MP's do I need to resubmit the MP as well?
[09:45] <elfy> not as far as I know
[09:46] <ki7mt> Ok, was just checking, been since I did that. Ok will get on it.
[09:46] <ki7mt> been a while since .. ..
[09:46] <elfy> :)
[10:24] <pitti> jibel: OOI, why does adt-virt-ssh need the -H/-l/-p options? isn't that something the setup script needs to know and tell a-v-s?
[10:25] <jibel> pitti, it doesn't for adb, but it does for example is you use an existing ssh host that doesn't need a setup script
[10:25] <jibel> s/is you/if you/
[10:25] <pitti> jibel: aah
[10:25] <pitti> jibel: so in that case we wouldn't have root or revert
[10:26] <jibel> pitti, right
[10:26] <jibel> well, we could have root but not revert
[10:26] <jibel> that's a case where sudo capability must be autodetected
[11:01] <pitti> jibel: ah right, with ASKPASS=/bin/true or so
[14:07] <jibel> pitti, any idea what fails here http://dmz-jenkins.ubuntu-ci:8080/job/hwe-eol-precise-desktop-amd64-lts-raring/5/console ?
[14:07] <jibel> I get this error frequently and a re-run usually fixes it
[14:09] <pitti> jibel: uh, is that a race condition?
[14:10] <pitti> jibel: I suppose this does use the adt-buildvm VM, i. e. it shoudl have a root shell?
[14:11] <pitti> fginther, balloons: yay, I just made autopkgtest's new "apt-get download test deps, unpack into /tmp/ and set $*_PATH" fallback for r/o system capable enough to work for the entire autopilot stack (including libautopilot-qt etc.)
[14:11] <jibel> pitti, yes with adt-buildvm, and another job works fine with the same base vm http://dmz-jenkins.ubuntu-ci:8080/view/HWE%20EOL/job/hwe-eol-precise-desktop-amd64-lts-saucy/2/console
[14:12] <pitti> fginther, balloons: in case we want to stop shipping autopilot on the phone :)
[14:12] <balloons> pitti, ohh, so if I update from your branch I'll get all those goodies?
[14:12] <pitti> balloons: haven't committed yet, but soon :)
[14:12] <balloons> pitti, yes I don't think autopilot should be part of the stack
[14:13] <pitti> balloons: I now have a --setup-commands script for starting an upstart user session, another one for switching apt/dpkg to read-only (to force the fallback to "local unpack"), both together approximates what's happening on a phone quite closely
[14:13] <fginther> pitti, very nice!
[14:13] <pitti> balloons: i. e. click stuff can be tested in a schroot or LXC
[14:14] <pitti> which might be enough for the odd merge proposal or automatic click verification, etc.
[14:14] <balloons> pitti, so what's the one the phone story look like/
[14:14] <pitti> balloons: on the phone we don't need these setup scripts of course, you'd just call adt-run with the click source and binary
[14:15] <pitti> we need the ssh runner for that though, not the lxc/schroot/qemu runner
[14:16] <pitti> jibel: did you ever happen to watch this in real-time? do you have a rough feeling how much time there is between "adt-run: DBG: sending command to testbed: open" and the failure?
[14:17] <jibel> pitti, no only in jenkins. I'll try to run it directly on the host.
[14:17] <pitti> jibel: I'll add some time stamping to that in git, so that this is easier to debug
[14:17] <pitti> jibel: I never saw that for utopic-adt-*, so this is new to me, I'm afraid
[14:18] <pitti> jibel: but this is precise, right? maybe sysvinit/upstart behaved differently there, to start getty on ttyS0 earlier than the autopkgtest init.d script
[14:18] <pitti> jibel: hang on, I need a few minutes to empty my brain state
[14:18] <jibel> pitti, not urgent
[14:19] <jibel> I can press the rebuild button :)
[14:20] <pitti> and for the record, I don't like ubuntu-app-launch for testing.. it's waaaay too indirect and complicated
[14:20] <balloons> pitti, jibel how's the ssh runner coming?
[14:22] <pitti> balloons: all pushed now
[14:23] <pitti> balloons: the remaining bit that I now need to do is to interpret an x-test description "autopilot": "@AUTOPILOT_DIR@" adequately
[14:23] <pitti> balloons: so that we don't need to modify a lot of click packages with the diff I pasted a few days ago
[14:24] <pitti> jibel: how can I get into that VM?
[14:24] <pitti> jibel: I have an idea
[14:25] <jibel> pitti, it's on rabisu.ubuntu.ci, I think you have access.
[14:26] <pitti> jibel: wow, first login; I'm in
[14:26] <jibel> pitti, then /var/lib/jenkins/HWE-EOL/images
[14:27] <jibel> pitti, autopkgtest is in my home dir, but you can git pull it if you need to
[14:27] <pitti> ⟫ kvm -m 2048 -snapshot -drive file=adt-precise-amd64-cloud-server.img,if=virtio -nographic -monitor none
[14:27] <pitti> Could not access KVM kernel module: Permission denied
[14:27] <jibel> grrr
[14:27] <pitti> jibel: anyway, let me build a local one
[14:28] <pitti> jibel: is this just a bog standard adt-buildvm-ubuntu-cloud -r precise ?
[14:29] <jibel> pitti, not really
[14:30] <jibel> pitti, it's $AUTOPKGTEST_BASE/tools/adt-buildvm-ubuntu-cloud -s $DISKSIZE -a $ARCH -r $RELEASE --userdata $HWEDIR/hwe-eol/config/user-data.${RELEASE}.${FLAVOR} -v -o $HWEDIR/images/
[14:31] <jibel> pitti, with this user-data file http://bazaar.launchpad.net/~jibel/+junk/hwe-eol/view/head:/config/user-data.precise.desktop
[14:31] <pitti> jibel: ah, so /etc/init/ttyS0.conf and /etc/init.d/autopkgtest both start for runlevel 2
[14:32] <pitti> jibel: perhaps ttyS0.conf is faster, and it tries to get the shell too early
[14:32] <jibel> pitti, changes in user-data are adding a ppa and some addiotional packages
[14:36] <pitti> jibel: how often does that happen? i. e. after how many runs/days could you say that the problem is fixed?
[14:36] <pitti> jibel: http://paste.ubuntu.com/7700722/ is something which you could apply locally to the git checkout
[14:36] <pitti> jibel: this isn't a real fix of course, but if that works I can turn this into a proper poll loop with timing out
[14:37] <jibel> pitti, it's random but frequent, I need to restart the job like 2 to 4 times before it works
[14:38] <jibel> pitti, another bug http://dmz-jenkins.ubuntu-ci:8080/job/hwe-eol-precise-desktop-amd64-lts-raring/7/console when there is a ppa and proposed enabled
[14:38] <jibel> pitti, we sould probably restrict the rewriting to entries with *.ubuntu.com
[14:38] <jibel> should
[14:39] <pitti> jibel: oh, that's --apt-pocket=proposed?
[14:39] <jibel> pitti, yes + ppa:mvo/hwe-eol
[14:39] <jibel> defined in user-data
[14:39] <pitti> jibel: mind filing a bug about that? I'm running out of time today
[14:40] <jibel> pitti, heh, no problem, thanks for your time on this :)
[14:40] <pitti> jibel: yeah, that fix is a bit more involved, I want to test case this properly etc.
[17:50] <phillw> balloons: FYI, the installer has been changed, the step by step instructions for the test cases are now out dated and need updating.
[18:06] <elopio> balloons or popey: this is ready for a review. It doesn't change anything to make reminders tests more stable, but will give better feedback:
[18:06] <elopio> https://code.launchpad.net/~elopio/reminders-app/fix_with_account/+merge/224221
[18:07] <elopio> balloons: what about your branch with the reordered account manager? Should we merge it too?
[18:07] <elfy> phillw: do a bug report for it - I watch them
[18:09] <phillw> elfy: not too sure if I'm allowed to do official stuff. But, I will flag them up.
[18:09] <elfy> mmm
[18:26] <balloons> phillw, ty for the heads up. I'll echo elfy in that please do a bug report
[18:26] <balloons> the more detail the better ofc, but report it :-)
[18:27] <balloons> elopio, I was planning to make a go / no go decision on it this afternoon. It doesn't work without it for me, but I feel like there is a better way
[18:33] <elopio> balloons: can you merge mine and then see what the log looks for you in case of error?
[18:34] <balloons> elopio, yep that sounds like a plan
[19:12] <ki7mt> elfy, Hello, if your around, think I have all the syntax and other issues resolved on the two proposals. I used the tidy script to test them.  On my desktop it's still crazy, not even passing the account store.
[19:32] <elopio> balloons: before adding the logs, I could reproduce the error on delete like 1/20.
[19:32] <elopio> now with the logs, I haven't been able to reproduce it.
[19:34] <balloons> elopio, I feel it would be helpful to print the account info as a debug print
[19:34] <elopio> balloons: I was looking for that, but I'm not sure where is the oauth token stored.
[19:35] <elopio> I made tests for everything account-console show prints
[19:35] <balloons> elopio, is there not a call we can make?
[19:35] <elopio> which is not really useful, just "evernote"
[19:36] <balloons> elopio, well, you'd end up reading it out a db
[19:36] <balloons> my old branch has the location..
[19:37] <elopio> balloons: which old branch?
[19:37] <balloons> elopio, looks like ~/.config/signond/signon.db and signon-secrets.db
[19:38] <balloons> lp:~nskaggs/reminders-app/oauth-ap
[19:39] <elopio> balloons: and how do I print that file?
[19:40] <balloons> elopio, it's an sqlite db
[19:40] <balloons> elopio,  I was originally meaning just print the account info.. just what account console shows
[19:40] <balloons> but if you want more, you could query the db and print the output
[19:41] <elopio> balloons: I'm not sure what to query. I actually don't want anymore, as setting the oauth token has never failed.
[19:41] <elopio> but it was you that asked for more :)
[19:42] <balloons> elopio, yes I think it's overkill.. I was simply wanting account console to confirm the account was created in the debug log
[19:42] <elopio> with the tests I added, we are making sure that the evernote account is always added and enabled
[19:42] <balloons> show me a little something about it
[19:42] <balloons> I know, I just like to see it :-)
[19:42] <balloons> elopio, mostly I'm asking because your branch still fails for me on the desktop
[19:43] <elopio> balloons: but what does it show on error?
[19:43] <balloons> elopio, nope
[19:43] <elopio> that's what I wanted to see.
[19:44] <balloons> elopio, here's the run: http://paste.ubuntu.com/7702244/
[19:45] <balloons> Notice it *seems* to create ok?, but reminders doesn't see it and it fails to delete but doesn't say why
[19:46] <balloons> it's still building in the chroot, I'll have a run from the device soon
[19:46] <elfy> ki7mt: in fact I just did it now - all merged/synced and fix released now - thanks :)
[19:47] <ki7mt> elfy, Thanks !!
[19:47] <elfy> thank you :)
[19:47] <balloons> elfy, phillw did we get a bug filed? I may have missed it
[19:49] <phillw> balloons: I will bug it tomorrow, it is a grey bug and testing for red bugs is the priority
[19:49] <elfy> I've not seen one yet - am watching for it
[19:53] <elopio> balloons: http://bazaar.launchpad.net/~elopio/reminders-app/fix_with_account/revision/170
[19:53] <elopio> that's what we can gather easily.
[19:53] <elopio> looking at your paste...
[19:54] <phillw> balloons: I've been busy, I'll file the bugs :)
[19:55] <balloons> phillw, :-)
[19:59] <elopio> balloons: can you pull and run again please?
[20:06] <balloons> elopio,  sure.. did you make qml changes
[20:06] <balloons> if not, re-running on device is much easier :-)
[20:06] <elopio> I didn't.
[20:16] <balloons> elopio, nice output :-) The account shows it's not enabled :-)
[20:16] <balloons> 16:16:07.269 DEBUG credentials:152 - enabled: False
[20:18] <elopio> nice.
[20:18] <elopio> now why on earth is that happening.
[20:18] <elopio> balloons: can you run the test_credentials.py ?
[20:19] <balloons> just a sec and yea I'll invesitgate
[20:20] <elopio> balloons: take a look at account.set_enabled(True) on _create_account
[20:20] <elopio> you can put a pdb there, and then inspect what account.get_enabled() returns after that
[20:21] <elopio> it's hard to inspect because it's async. But you could continue putting breakpoints to find where the account is disabled.
[20:21] <balloons> right
[20:23] <balloons> hmm.. no luck on device either.. back to desktop for a moment
[20:25] <balloons> elopio, it indeed shows false after get_enabled.. running set_enabled(True) and get_enabled still shows false
[20:30] <elopio> balloons: are you on desktop now?
[20:30] <balloons> elopio, yes.. looking at account-console it says it's enabled.. interesting..
[20:31] <elopio> balloons: remember to do HOME=/tmp/... before account-consoel
[20:31] <balloons> elopio, I did.. id matches etc
[20:31] <elopio> makes no sense.
[20:32] <balloons> wild..
[20:38] <balloons> elopio, I'm not seeing the method calls in Accounts.py you are using.. I'm missing something
[20:44] <balloons> elopio, could you list what account-console show shows?
[20:45] <balloons> Not that I think it will change anything
[20:45] <balloons> but yes, accounts console and the python are returning different thingds
[20:50] <elopio> yes I can.
[20:50] <elopio> one second.
[20:50] <balloons> elopio, it's odd, but your latests updates makes the app not launch on the device
[20:51] <balloons> the diff doesn't reveal anything.. hmm
[20:54] <balloons> elopio, so I deleted the account, but I can still print it afterwards
[20:55] <balloons> ahh I see the goodies are in account_service.get_auth_data()
[21:02] <elopio> balloons: yes, but that's information that we never set. It's taken from online accounts. Would you like to log it too?
[21:02] <elopio> balloons: pull, and you will see the list of all accounts.
[21:03] <balloons> elopio, I'll pull
[21:04] <elopio> I see something weird here. The ids of the accounts are sequential. They should all be 1, as there's no other account.
[21:04] <balloons> mine show up as 1, and indeed
[21:05] <balloons> elopio, magically I'm seeing things as enabled now
[21:05] <balloons> wtf
[21:05] <elopio> if I put a 10 seconds sleep, they all get the 1 id.
[21:05] <elopio> so I think the account_manager is not getting a new instance.
[21:05] <elopio> we might need to kill signond.
[21:06] <balloons> lookey there, test worked
[21:08] <balloons> elopio, ok, so seems there is a small sleep needed before anabling the service
[21:08] <balloons> the test works and prints enabled if I add a small sleep in _enable_evernote_service
[21:16] <balloons> elopio, that sleep actually is required after the         self._join_main_loop(). I suspect you are correct about signond
[21:16] <balloons> a 1 second sleep is enough..
[21:20] <balloons> elopio, I think I'm happy with a small sleep after you set the credentials and before you start the service
[21:20] <balloons> that seems nicer than stopping and starting things. What do you think?
[21:20] <balloons> I deleted my proposal to merge.. yours has everything we should need
[21:20] <elopio> balloons: even with the sleep I can't make it get all the accounts created to have id = 1
[21:22] <balloons> elopio, you are only creating one account correct? Are you saying the account id isn't 1 when you run it?
[21:23] <elopio> balloons: test_credentials.py creates 4 accounts
[21:23] <elopio> all of them should have id = 1.
[21:23] <balloons> elopio, ohh, lol.. I'm still stuck on reminders ofc :-)
[21:23]  * balloons runs
[21:25] <balloons> ok, I see now.. indeed, they aren't all 1
[21:26] <elopio> two are, two aren't. That's puzzling.
[21:26] <elopio> anyway, I think that you won't need the sleep if I kill the signond.
[21:26] <balloons> yep, I see that. I'll look with you.. my other tests with test_reminders with account look good now
[21:27] <elopio> could you try the branch I'm pushing without the sleep?
[21:27] <balloons> elopio, I agree.. I was arguing in favor of sleeping as opposed to killing the service
[21:27] <balloons> elopio, happy to try whatever
[21:27] <elopio> balloons: well, the service will be killed after 5 seconds of inactivity, according to mardy
[21:27] <elopio> so we are just giving it a quicker dead.
[21:27] <balloons> elopio, :-) ok
[21:31] <elopio> balloons: pushed.
[21:32] <balloons> got it
[21:32] <balloons> elopio, test_credentials run looks the same
[21:34] <balloons> elopio, I'd use subprocess and both check the output of pkill and wait for it to finish
[21:34] <balloons> elopio, can we stop it in a saner manner? it runs with initctl yes?
[21:36] <elopio> hum, you are right. This might not be the way to stop it.
[21:37] <balloons> elopio, so can we say subprocess.call(["stop", "signond"])
[21:37] <balloons> or we can do a pidof kill -9
[21:38] <balloons> and do we want to then start it up, using our environment? we can use initctl reset-env
[21:38] <balloons> or shall we assume it starts ok?
[21:38] <elopio> it will be started when we start calling things from gi.
[21:38] <balloons> yes.. just want to make sure it'll have the proper env when called from gi
[21:38] <elopio> stop signond will not work on desktop
[21:39] <elopio> it doesn't work on the phone either
[21:40] <elopio> $ pkill -9 signond works on the phone
[21:40] <balloons> subprocess.call('kill -9 `pidof /usr/bin/signond`')
[21:40] <balloons> mkay, if pkill works on the phone
[21:42] <elopio> balloons: and the problem with subprocess.check_call is that it will fail if the process doesn't exist.
[21:44] <balloons> elopio, we can use check_output if you want to check
[21:44] <elopio> balloons: I don't want to check. Ah, right, call will work.
[21:44] <balloons> :-)
[21:45] <balloons> however, I'm not getting what I want
[21:46] <balloons> weird.. it runs 1, 1, 2, 3
[21:46] <balloons> heh
[21:46] <elopio> balloons: what do you want.
[21:46] <elopio> ?
[21:46] <balloons> elopio, for all the ids to be 1, as you said :-)
[21:46] <elopio> balloons: yes, I want that too :(
[21:46] <elopio> balloons: but did it work without the sleep?
[21:47] <elopio> my phone doesn't let me run the tests again.
[21:47] <balloons> elopio, no.. it has no effect on anything afaict
[21:50] <elopio> balloons: bah, so I'll just add the sleep between the account creation and the enablement.
[21:51] <balloons> elopio, yea, just after the _join_main_loop seems fine
[21:51] <balloons> but the credentials tests are still concerning
[21:51] <balloons> elopio, no other services running? nothing else that might need to be killed?
[21:52] <elopio> balloons: the other thing that mardy said was that we might be keeping an reference to Accounts.Manager
[21:52] <elopio> that's why we have the weird del statements.
[21:54]  * balloons watches processes
[21:55] <balloons> I'm concerned about initctl isolation
[21:57] <balloons> mm.. strace shows it's good
[21:58] <balloons> you are setting xdg too
[21:58] <elopio> balloons: pushed with the sleep.
[21:59] <elopio> balloons: I'm not sure what do you mean about initctl.
[21:59] <balloons> elopio, my concerns are unfounded.. looking at the trace it's all good
[22:08] <elopio> balloons: so, should I do something else on this branch?
[22:10] <balloons> elopio, it's better than it was
[22:10] <balloons> I'm not seeing anything else being launched
[22:12] <balloons> ohh you added so much more
[22:12]  * balloons pulls
[22:15] <balloons> elopio, I found a sleep(1) to be enough, but I guess the sleep(10) is fine
[22:16] <balloons> I'm happy to land it as-is.. There's still some lingering questions, but nothing to hold on
[22:17] <balloons> perfection isn't required :-)
[22:18] <balloons> are you happy? I'll top-approve if so
[22:18] <elopio> balloons: I'm not happy at all because the accounts are not all 1 :D
[22:18] <elopio> but yeah, if it fixes the issue for you, lets land it.
[22:19] <balloons> elopio, I'm ok with landing it, while continuing the fight on accounts not being 1
[22:19] <balloons> there's some much good logging in it
[22:19] <elopio> balloons: so, just to confirm, now it works for you on the phone and on the desktop?
[22:19] <elopio> you no longer get an account disabled?
[22:19] <balloons> I'm trying the phone again.. it actually broke the phone earlier
[22:20] <balloons> I'm assuming that's fixed and it works again
[22:21] <balloons> bah, it's still happening..
[22:21] <elopio> what? The account disabled?
[22:22] <balloons> http://paste.ubuntu.com/7702960/
[22:22] <balloons> no it doesn't launch
[22:23] <balloons> and its attempting to launch the wrong version, which is why it doesn't launch i'll bet
[22:23] <balloons> ohh, nvm that is the right version
[22:24] <balloons> bah the keyfile
[22:24]  * balloons rebuilds
[22:34] <elopio> balloons: the same happens here. I thought it was my phone going crazy as it works on yours.
[22:34] <balloons> elopio, yea I think the key need to be inserted for phone.. but thats odd
[22:37] <balloons> elopio, yea, see I installed the original pkg back to the device, no dice
[22:37] <balloons> let me try trunk quickly for sanity
[22:40] <balloons> yep trunk starts properly.. I guess we have to blame the branch
[22:40] <balloons> elopio, ^^
[22:44] <balloons> yep new build with trunks tests also work.
[22:44] <balloons> ( I mean the tests fail, but the app launches properly, etc ;-) )
[22:45] <elopio> balloons: right, I can see it. I'll try removing some things.
[22:47] <balloons> elopio, it happened before the patch home fixture change.. really it was weird
[22:49] <balloons> elopio, should probably fix this too :-) BaseTestCaseWithTempHome
[22:49] <balloons> err 22:21:21.112 WARNING emulators:26 - The ubuntuuitoolkit.emulators module is deprecated. Import the autopilot helpers from the top-level ubuntuuitoolkit module.
[22:50] <elopio> balloons: what we are doing differently is that we are patching both then env var and the initctl env var
[22:50] <elopio> and it doesn't like it.
[22:53] <balloons> elopio, hehe, I think that's the problem I had with music then as well
[22:53] <balloons> works on desktop, not on phone
[22:53] <balloons> I also had to patch initctl
[22:53] <balloons> and I had to do it before I launched the app
[22:54] <elopio> balloons: well, it means that the patch home fixture is less ready than what I expected. I'll revert that change.
[23:03] <balloons> elopio, can you approve? https://code.launchpad.net/~nskaggs/reminders-app/fix-new-pep8/+merge/224536
[23:05] <elopio> balloons: done.
[23:15] <elopio> balloons: oh, wait, I read it backwards. Getting color blind here.
[23:15] <elopio> why do you put an empty line between the class and its comment?
[23:24] <balloons> elopio, I noticed autopep8 wants to do that
[23:24] <balloons> i didn't change it back
[23:24] <balloons> I guess I'll undo i
[23:25] <elopio> mmm, no, you are right.
[23:25] <elopio> wait.
[23:25] <elopio> Insert a blank line before and after all docstrings (one-line or multi-line) that document a class
[23:25] <balloons> well the man himself barry doesn't consider autopep8 to be the bible on this
[23:25] <elopio> I didn't know about that one.
[23:31] <elopio> balloons: ok, my branch is ready again.
[23:31] <elopio> app launches, but now I'm getting that libaccounts-glib can't write on tmp.
[23:33] <balloons> ok, let me try it
[23:36] <elopio> (process:31524): accounts-glib-WARNING **: Cannot create directory: /tmp/tmpo52mb_sj/.config/libaccounts-glib
[23:45] <balloons> ok, seems to start just fine
[23:59] <balloons> so elopio on the phone run, the isolation didn't work and thus the app doesn't see the account
[23:59] <elopio> balloons: right. But the account seems to be created properly.


[06:56] <neil_> can you have a client (with a hdd) work like a thin client without needing to netboot?
[16:38] <fr0sted> #xubuntu
[16:38] <fr0sted> sry


[06:36] <pitti> Good morning
[06:40] <hikiko> hello! :p
[06:46] <qengho> hihi
[06:46] <FJKong_> hihihi
[06:47] <Sweet5hark> hohoho
[06:47] <hikiko> test
[06:51] <seb128> good morning desktopers
[06:52] <happyaron> morning
[06:52] <pitti> yak shaving yet? :-)
[07:01] <willcooke> morning desktoppers
[07:02] <Trevinho> morning!
[07:03] <Sweet5hark> seb128: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1574285
[07:05] <dholbach> seb128, is https://bugs.launchpad.net/ubuntu/+source/libqmi/+bug/1562957 something the desktop team would look at or would that be cyphermox or somebody else?
[07:12] <seb128> attente, is that InstallFile?
[07:13] <desrt> hi willcooke :D
[07:13] <willcooke> desrt, hihi
[07:13] <seb128> attente, unping
[07:13] <seb128> Sweet5hark, thanks
[07:13] <desrt> seb128: irc doesn't work this way :)
[07:13] <seb128> Trevinho, morning! italians, always late!
[07:13] <seb128> desrt, it should!
[07:14] <seb128> dholbach, no idea, I don't even know what libqmi is
[07:14] <seb128> dholbach, sorry at a sprint and we are getting started, don't have a lot of focus for IRC
[07:14] <dholbach> seb128, it seems to have to do with {network,modem}manager
[07:14] <seb128> try cyphermox
[07:14] <Trevinho> seb128: to get your love :)
[07:14] <dholbach> seb128, understood, no worries - have a good time at the sprint
[07:14] <seb128> I can put on my list for next week
[07:14] <seb128> thanks!
[07:15] <dholbach> seb128, my ping above included Mathieu, so maybe he'll pick it up later on :)
[07:15] <seb128> yeah
[07:19] <seb128> attente, Laney,
[07:19] <seb128> method call time=1461568730.237483 sender=:1.158 -> destination=org.debian.apt serial=37 path=/org/debian/apt; interface=org.debian.apt; member=InstallFile
[07:19] <seb128>    string "ubuntu-xenial-main"
[07:19] <seb128>    boolean true
[07:24] <pitti> hey desrt, what an unusual hour for you -- are you in Europe again?
[07:24] <desrt> yes.  we're sprinting in prague
[07:24] <desrt> desktop team plus shell/designers
[07:24] <pitti> ah, lovely
[07:24] <desrt> this is why i was in your country for my 'visit' yesterday ;)
[07:25] <pitti> transit zone doesn't even legally count as "in the country", does it? :-)
[07:29] <desrt> i went through FRA
[07:35] <seb128> Laney, attente, robert_ancell, not good enough, "error-unreadable-package-file: gnome-calculator" ... it gets the source name not the full pathname, which I guess is what it needs
[07:35] <robert_ancell> yeah, duh
[07:35] <seb128> :-)
[07:36] <larsu> good morning and have a nice sprint!
[07:36] <desrt> larsu: thanks :D
[07:48] <seb128> hey larsu, we miss you here!
[07:54] <larsu> seb128: I miss you too! Thought about coming down for a day, but have quite a lot of work to do this week
[07:54] <seb128> larsu, good luck with the work, maybe next time! we are going to drink a beer for you
[07:59] <larsu> seb128: I know you will ;) Enjoy Prague!
[07:59] <seb128> larsu, thanks!
[08:01] <dholbach> are you going to look at the appstream stuff in the sponsoring queue at the sprint?
[08:02] <seb128> Sweet5hark, do you know if the dpkg-maintscript-helper bug has steps to trigger it? or do we just reports?
[08:09] <Sweet5hark> havent tried to reproduce yet -- so far all I have is those reports ...
[08:10] <Sweet5hark> seb128: I see they all seem 14.04LTS->16.04LTS updates though
[08:10] <seb128> pitti, ^
[08:14] <willcooke> robert_ancell, https://trello.com/b/hY6fCqbx/convergence-topics
[08:46] <Laney> hai
[08:51] <pitti> hey Laney, how are you meeowing today?
[08:53] <Laney> hey pitti!
[08:53] <Laney> we're meowing from prague
[08:59] <chrisccoulson> how's prague?
[09:00] <seb128> Laney, pitti, do you know about "update-rc.d ... remove" erroring out with  "... exists during rc.d purge"? I've a friend who had his trusty to xenial update failing because ppp.preinst hit that one
[09:00] <pitti> seb128: that doesn't ring a bell with me, sorry
[09:00] <seb128> the pppd-dns one if that case
[09:00] <pitti> what exists during rc.d purge?
[09:01] <seb128> the ppp.preinst errored out with "pppd-dns exists during rc.d purg" which seems to be the preinst call to "update-rc.d pppd-dns remove"
[09:01] <seb128> I don't really understand what the errors means though
[09:02] <Laney> sorry
[09:02] <Laney> try slangasek?
[09:02] <seb128> yeah, a bit early for him
[09:02] <seb128> I'm going to watch out for other reports
[09:03] <seb128> it's possible that my friend deleted some conffile or something
[09:03] <Sweet5hark> Laney, pitti: https://twitter.com/TheLadBible/status/723859679479250944
[09:03] <seb128> the system is like several LTS cycles old with quite some custom changes and upgrades
[09:04] <seb128> easier workaround would be to not fail the preinst on errors from that call, unsure if that would be right though
[09:04] <Laney> Sweet5hark: HEAVEN
[09:05] <pitti> Sweet5hark: *grin*
[09:13]  * seb128 reads recent launchpad bugs, quite boring
[09:13] <seb128> not fun bugs reports in that LTS?
[09:17] <pitti> oh, there are; I'm getting tons of duplicates on upgrade failures :/
[09:21] <seb128> oh? :-(
[09:21] <seb128> some common issues?
[09:21] <seb128> like one bug we can fix to address most?
[09:21] <pitti> bug 1560797 in my world mostly
[09:22] <pitti> we SRUed the fix to trusty and wily, but so far most people don't update their trusty/wily before dist-upgrading to xenial :/
[09:22] <seb128> isn't the dist-upgrader supposed to make you do that?
[09:22] <seb128> like ask you to apply SRUs before upgrading?
[09:22] <pitti> I thought it would upgrade to the new apt first
[09:22] <pitti> (which would work as well)
[09:22] <pitti> but not sure why that happens so often still
[09:22] <seb128> people upgrading manually?
[09:23] <pitti> well, I got maybe 10 or 15 reports after the release
[09:23] <pitti> if several thousand upgraded, that would still count as "few" I guess
[09:23] <pitti> yeah, could be manual apt-get dist-upgrade
[09:39] <hikiko> Trevinho, https://code.launchpad.net/~hikiko/compiz/compiz.trusty-1442728/+merge/292773 I hope it's fine
[10:05] <xnox> seb128, pitti - upgrading apt alone, results in a cycle, with a pre-depends which old apt fails to handle. Hence the bug.
[10:06] <xnox> the best we can do, is SRU a fix to all old apts that we can.
[10:06] <xnox> and hope people upgrade to latest updates, before upgrading further up.
[10:06] <xnox> which we have now.
[10:06] <xnox> does dist-upgrader upgrade people to -updates first, then upgrade apt, then upgrade to next series?
[10:07] <pitti> xnox: we already SRUed it with fast-tracking last week
[10:07] <xnox> right. so that's the best we can do. and wait for everyones mirrors to catch up
[10:07] <xnox> and upgrades =/
[10:51] <pitti> RAOF: are you going to merge colord soon, or want me to? I'm merging gnome-color-manager, and the new version needs a new colord
[11:27] <Sweet5hark> ajar JarJar in a jar in an ajar jar: https://plus.google.com/+KristianK%C3%B6hntopp/posts/MXUmooUdtq2?pid=6277259845447416050&oid=102280518215937463274&authkey=CJOjheLDyPWX-gE
[11:35] <pitti> Sweet5hark: hah, brilliant!
[11:36] <Sweet5hark> pitti: as a bonus, it was required to chop JarJars head off for the illustration.
[11:37] <Sweet5hark> JarJar makes me channel my inner Red Queen.
[12:37] <qengho> Sweet5hark:  Austria 20160425 NEVER FORGET
[12:58] <davmor2> Sweet5hark: see now the question is why they didn't do Ajar jarjar in an ajar jar in an ajar jar and keep it recursive ;)
[13:02] <Sweet5hark> davmor2: to break the rhythm I assume. rhythm makes it to easy.
[13:03] <davmor2> Sweet5hark: :)
[13:04] <davmor2> Sweet5hark: I'll stick with the classics like She sells see shell from the seashore if she sells sea shells from the seashore she'll sell sea shells forever more
[13:05]  * Sweet5hark rides off on a buffalo buffalo.
[13:05] <flocculant> sea shells
[13:05] <flocculant> just saying ...
[13:06] <davmor2> flocculant: meh dyslexic if I get it so you can read it I'm happy
[13:06] <flocculant> davmor2: well in that case - I can read it :)
[13:07] <davmor2> flocculant: I actually worte it as seashells but it didn't look right
[13:07] <flocculant> :)
[13:08] <davmor2> wrote even
[13:27] <hyperair> where does gnome-software in xenial get its appdata information from?
[13:29] <Laney> archive.ubuntu.com
[13:34] <kgunn> hikiko: wanna join kpi?
[13:35] <hyperair> Laney: um where exactly?
[13:35] <Laney> hyperair: /ubuntu/dists/suite/dep11/
[13:36] <Laney> /suite/comopnent/dep11/
[13:36] <hikiko> kgunn, I am in the sprint in Prague, I m going to find a quiet place and join you in a few minutes
[13:36] <hyperair> Laney: oh. i thought the appstream stuff was separate from dep11
[13:38] <hyperair> Laney: so how do i debug why something's missing from the dep11 dump?
[13:40] <Laney> hyperair: look on http://appstream.ubuntu.com usually
[13:40] <davmor2> hyperair: http://mhall119.com/2016/03/help-make-gnome-software-beautiful/
[13:40] <hyperair> ah, thanks
[13:44] <kgunn> hikiko: oops forgot...np
[13:56] <davmor2> hyperair: was my link to mhall119 useful I hope so :)  It's just so I can pass it on in future if it was :)
[13:59] <Laney> depends if the problem is an icon or not :)
[14:51] <hyperair> davmor2: well, somewhat, but i found what i needed from laney's link
[14:51] <hyperair> and yes it was an icon
[14:51] <hyperair> i placed it in the wrong place
[14:52] <hyperair>  /usr/share/icons/hicolor/256x256 instead of /usr/share/icons/hicolor/256x256/apps
[14:52] <trmsu> you should be able to SRU that if you want
[14:52] <trmsu> haha I forgot I change my nick
[14:52] <trmsu> changed
[14:53] <hyperair> ..wut
[15:04] <ximion> Laney: you need to set the dataPriority flag for AppStream metadata in the -updates, -backport, etc. suites to someting >> 0
[15:04] <ximion> otherwise the new data won't override the old one
[15:05] <trmsu> ok
[15:10] <hyperair> ximion: um how do you set that?
[15:15] <desrt> trmsu: mmm
[15:16] <ximion> hyperair: on the server, set the "dataPriority" property for the target suite in dep11-config.yml
[15:16] <desrt> trmsu: i will eat you
[15:16] <trmsu> eat my beans
[15:16] <desrt> *pin drop*
[15:17] <ximion> no giraffes, but tiramisu ;-)
[15:18] <trmsu> ximion: what's the right relative priority for backports?
[15:18] <trmsu> proposed < updates < backports?
[15:21] <ximion> jup, I think that makes sense
[15:21] <trmsu> < updates < security < backports
[15:22] <trmsu> actually proposed should be higher than updates
[15:22] <trmsu> release < updates < security < proposed < backports
[15:22] <trmsu> probably
[15:23] <ximion> right, proposed beats security and updates
[15:35] <trmsu> ximion: ok, will be there next time
[15:35] <ximion> :-)
[15:36] <ximion> if we had versions in AppStream data, we could resolve conflicts by version comparisons...
[15:36] <ximion> but that's likely not a great idea
[15:44] <davmor2> wllck: I see you've gone all hip and textspeak and dropped all the vowel from your nick nice ;)
[15:44] <wllck> wrd
[15:47] <seb128> Laney, attente, robert_ancell, the appstream: handler does
[15:47] <seb128> 			g_action_group_activate_action (G_ACTION_GROUP (app),
[15:47] <seb128> 			                                "details",
[15:47] <seb128> 			                                g_variant_new ("(ss)", path, ""));
[15:57] <seb128> that's can't be done I guess since g-s doesn't know about non desktop binaries
[16:42] <hyperair> ximion: um i guess i'll have to ping someone for that?
[16:43] <ximion> hyperair: not just someone ^^ Laney can do it
[16:43] <ximion> or better: has done it ^^
[16:44] <hyperair> ah
[16:44] <hyperair> naise
[16:44] <hyperair> guess i'll SRU the change
[21:47] <muktupavels_> Trevinho: https://bugs.launchpad.net/compiz/+bug/1574866


[01:04] <DonkeyHotei> Angkor Wat?
[04:22] <philballew> How would I add my current nic to be associated with my main nic and therefor get my member cloak?
[04:23] <pleia2> /msg nickserv help group
[04:23] <philballew> alright!
[04:23] <philballew> thank you pleia2
[04:24] <pleia2> so like /msg nickserv identify philipballew your-password-here
[04:24] <pleia2> then /msg nickserv group
[04:25] <philballew> ah, now it works!
[04:26] <pleia2> there you go :)
[04:26] <philballew> alright, now just gotta reconnect
[05:50] <bkerensa> philballew: I would just have it on loan
[05:57] <philballew> bkerensa, the car or laptop is loan?
[05:58] <bkerensa> both
[05:58] <bkerensa> lol
[05:59] <philballew> HAHA, it seems like a nice car though
[06:00] <philballew> My dell I had at oscon broke yesterday so I wont see it till the warranty people ship it back to mr
[23:59] <jtatum> quiet in here :)


[00:07] -kubuntu-ci:#kubuntu-devel- Project mgmt_merger build #810: SUCCESS in 7 min 18 sec: http://kci.pangea.pub/job/mgmt_merger/810/
[00:15]  * ahoneybun is rocking Plasma 5.9.3
[00:28] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kde-dev-utils build #132: STILL UNSTABLE in 20 min: http://kci.pangea.pub/job/xenial_unstable_kde-dev-utils/132/
[00:29] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kde-dev-utils build #145: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/yakkety_unstable_kde-dev-utils/145/
 Seems a good update :)
[00:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdenlive build #397: STILL FAILING in 30 min: http://kci.pangea.pub/job/xenial_unstable_kdenlive/397/
[00:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #326: STILL FAILING in 32 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/326/
[00:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kproperty build #62: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/xenial_unstable_kproperty/62/
[00:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdb build #63: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/xenial_unstable_kdb/63/
[00:41] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ktexteditor build #191: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/yakkety_unstable_ktexteditor/191/
[00:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdiagram build #91: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/xenial_unstable_kdiagram/91/
[00:41] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kexi build #52: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/zesty_unstable_kexi/52/
[00:53] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_k3b build #46: STILL UNSTABLE in 24 min: http://kci.pangea.pub/job/yakkety_unstable_k3b/46/
[00:53] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdiagram build #90: STILL UNSTABLE in 43 min: http://kci.pangea.pub/job/zesty_unstable_kdiagram/90/
[00:53] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdiagram build #63: STILL UNSTABLE in 44 min: http://kci.pangea.pub/job/yakkety_unstable_kdiagram/63/
[01:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdenlive build #245: FAILURE in 23 min: http://kci.pangea.pub/job/yakkety_unstable_kdenlive/245/
[01:04] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_minuet build #120: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/yakkety_unstable_minuet/120/
[01:04] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kopete build #106: STILL UNSTABLE in 54 min: http://kci.pangea.pub/job/zesty_unstable_kopete/106/
 It's nice so far
[01:20] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kstars build #123: STILL UNSTABLE in 38 min: http://kci.pangea.pub/job/zesty_unstable_kstars/123/
[01:20] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kde-dev-utils build #83: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/zesty_unstable_kde-dev-utils/83/
[01:21] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_okular build #130: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/zesty_unstable_okular/130/
[01:21] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_umbrello build #119: STILL UNSTABLE in 39 min: http://kci.pangea.pub/job/zesty_unstable_umbrello/119/
[01:21] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_okular build #217: STILL UNSTABLE in 25 min: http://kci.pangea.pub/job/yakkety_unstable_okular/217/
[01:38] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_spectacle build #102: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/zesty_unstable_spectacle/102/
[01:38] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_k3b build #37: STILL UNSTABLE in 45 min: http://kci.pangea.pub/job/zesty_unstable_k3b/37/
[01:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kstars build #390: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/xenial_unstable_kstars/390/
[01:38] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_k3b build #38: STILL UNSTABLE in 45 min: http://kci.pangea.pub/job/xenial_unstable_k3b/38/
[01:38] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_spectacle build #166: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/yakkety_unstable_spectacle/166/
[01:39] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_trojita build #57: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/zesty_unstable_trojita/57/
[01:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_minuet build #109: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/xenial_unstable_minuet/109/
[01:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_umbrello build #190: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/yakkety_unstable_umbrello/190/
[01:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_trojita build #57: STILL UNSTABLE in 34 min: http://kci.pangea.pub/job/xenial_unstable_trojita/57/
[01:39] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_trojita build #44: STILL UNSTABLE in 33 min: http://kci.pangea.pub/job/yakkety_unstable_trojita/44/
[01:39] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kpimtextedit build #113: STILL UNSTABLE in 18 min: http://kci.pangea.pub/job/zesty_unstable_kpimtextedit/113/
[01:41] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdenlive build #398: STILL FAILING in 21 min: http://kci.pangea.pub/job/xenial_unstable_kdenlive/398/
[01:44] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdenlive build #246: STILL FAILING in 23 min: http://kci.pangea.pub/job/yakkety_unstable_kdenlive/246/
[01:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kstars build #257: STILL UNSTABLE in 47 min: http://kci.pangea.pub/job/yakkety_unstable_kstars/257/
[01:53] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kproperty build #69: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/zesty_unstable_kproperty/69/
[01:53] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdb build #60: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/zesty_unstable_kdb/60/
[01:53] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ktp-common-internals build #106: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/zesty_unstable_ktp-common-internals/106/
[01:53] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kexi build #72: STILL UNSTABLE in 32 min: http://kci.pangea.pub/job/yakkety_unstable_kexi/72/
[01:53] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_akonadi build #327: STILL FAILING in 33 min: http://kci.pangea.pub/job/yakkety_unstable_akonadi/327/
[01:53] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_umbrello build #214: STILL UNSTABLE in 49 min: http://kci.pangea.pub/job/xenial_unstable_umbrello/214/
[02:06] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_krita build #76: STILL UNSTABLE in 1 hr 25 min: http://kci.pangea.pub/job/yakkety_unstable_krita/76/
[02:06] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktp-auth-handler build #291: STILL UNSTABLE in 27 min: http://kci.pangea.pub/job/xenial_unstable_ktp-auth-handler/291/
[02:34] <DarinMiller> Good evening!
[02:43] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_okular build #149: STILL UNSTABLE in 36 min: http://kci.pangea.pub/job/xenial_unstable_okular/149/
[02:44] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_krita build #102: STILL UNSTABLE in 2 hr 2 min: http://kci.pangea.pub/job/zesty_unstable_krita/102/
[02:44] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_krita build #77: STILL UNSTABLE in 1 hr 40 min: http://kci.pangea.pub/job/xenial_unstable_krita/77/
[02:44] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_marble build #125: STILL UNSTABLE in 1 hr 23 min: http://kci.pangea.pub/job/zesty_unstable_marble/125/
[02:45] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_pim-sieve-editor build #101: STILL UNSTABLE in 38 min: http://kci.pangea.pub/job/zesty_unstable_pim-sieve-editor/101/
[02:46] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_spectacle build #219: STILL UNSTABLE in 39 min: http://kci.pangea.pub/job/xenial_unstable_spectacle/219/
[03:43] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kitemmodels build #202: STILL UNSTABLE in 15 min: http://kci.pangea.pub/job/yakkety_unstable_kitemmodels/202/
[03:43] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_korganizer build #73: STILL UNSTABLE in 16 min: http://kci.pangea.pub/job/xenial_unstable_korganizer/73/
[03:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kguiaddons build #199: STILL UNSTABLE in 13 min: http://kci.pangea.pub/job/yakkety_unstable_kguiaddons/199/
[03:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcompletion build #181: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kcompletion/181/
[03:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcodecs build #271: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kcodecs/271/
[03:51] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kdbusaddons build #274: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kdbusaddons/274/
[03:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kjobwidgets build #256: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kjobwidgets/256/
[03:59] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_calligra build #81: STILL UNSTABLE in 1 hr 14 min: http://kci.pangea.pub/job/zesty_unstable_calligra/81/
[04:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kconfigwidgets build #237: STILL UNSTABLE in 8 min 47 sec: http://kci.pangea.pub/job/yakkety_unstable_kconfigwidgets/237/
[04:13] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kitemviews build #106: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_kitemviews/106/
[04:13] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kwidgetsaddons build #116: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_kwidgetsaddons/116/
[04:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kwidgetsaddons build #275: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/yakkety_unstable_kwidgetsaddons/275/
[04:14] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdbusaddons build #113: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/zesty_unstable_kdbusaddons/113/
[04:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_ki18n build #269: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_ki18n/269/
[04:20] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcoreaddons build #209: STILL UNSTABLE in 14 min: http://kci.pangea.pub/job/yakkety_unstable_kcoreaddons/209/
[04:32] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kconfigwidgets build #70: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_kconfigwidgets/70/
[04:32] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kjobwidgets build #107: STILL UNSTABLE in 19 min: http://kci.pangea.pub/job/zesty_unstable_kjobwidgets/107/
 bloody f*****ng hell https://www.kde.org/info/security/advisory-20170228-1.txt
 grrrrrrrrrrrrrrrrrr
 if DarinMiller or wxl want a task, go fix that CVE
 https://raphaelhertzog.com/2012/08/08/how-to-use-quilt-to-manage-patches-in-debian-packages/
 that's my reference guide ^
 otherwise I'll be awake in the morning to fix it
 create new patch given commit and voila it's done
 maybe I'll even give reward if it's done before I wake up :P
 anyways I'm incredibly sleep deprived, good night all o/
[04:41] <valorie> sweet dreams, tsimonq2
[04:51] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_calligra build #91: STILL UNSTABLE in 1 hr 24 min: http://kci.pangea.pub/job/xenial_unstable_calligra/91/
[04:52] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_korganizer build #81: STILL UNSTABLE in 31 min: http://kci.pangea.pub/job/yakkety_unstable_korganizer/81/
[05:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ki18n build #404: FAILURE in 11 min: http://kci.pangea.pub/job/xenial_unstable_ki18n/404/
[05:05] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_attica build #384: FAILURE in 12 min: http://kci.pangea.pub/job/xenial_unstable_attica/384/
[05:15] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kguiaddons build #383: STILL UNSTABLE in 23 min: http://kci.pangea.pub/job/xenial_unstable_kguiaddons/383/
[06:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ki18n build #405: NOW UNSTABLE in 51 min: http://kci.pangea.pub/job/xenial_unstable_ki18n/405/
[06:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcodecs build #386: STILL UNSTABLE in 1 hr 8 min: http://kci.pangea.pub/job/xenial_unstable_kcodecs/386/
[06:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdbusaddons build #410: STILL UNSTABLE in 1 hr 8 min: http://kci.pangea.pub/job/xenial_unstable_kdbusaddons/410/
[06:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kitemviews build #377: STILL UNSTABLE in 1 hr 8 min: http://kci.pangea.pub/job/xenial_unstable_kitemviews/377/
[06:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kconfig build #420: STILL UNSTABLE in 1 hr 8 min: http://kci.pangea.pub/job/xenial_unstable_kconfig/420/
[06:01] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_calligra build #81: STILL UNSTABLE in 1 hr 40 min: http://kci.pangea.pub/job/yakkety_unstable_calligra/81/
[06:01] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[06:01] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_attica build #385: FIXED in 50 min: http://kci.pangea.pub/job/xenial_unstable_attica/385/
[06:13] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdelibs4support build #82: FAILURE in 12 min: http://kci.pangea.pub/job/zesty_unstable_kdelibs4support/82/
[06:18] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_calendarsupport build #93: FAILURE in 17 min: http://kci.pangea.pub/job/yakkety_unstable_calendarsupport/93/
[06:21] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcoreaddons build #377: STILL UNSTABLE in 1 hr 6 min: http://kci.pangea.pub/job/xenial_unstable_kcoreaddons/377/
[06:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcmutils build #311: FAILURE in 16 min: http://kci.pangea.pub/job/xenial_unstable_kcmutils/311/
[06:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kcmutils build #312: STILL FAILING in 11 min: http://kci.pangea.pub/job/xenial_unstable_kcmutils/312/
[08:09] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:09] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_calendarsupport build #94: FIXED in 1 hr 46 min: http://kci.pangea.pub/job/yakkety_unstable_calendarsupport/94/
[08:09] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[08:09] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdelibs4support build #83: FIXED in 1 hr 50 min: http://kci.pangea.pub/job/zesty_unstable_kdelibs4support/83/
[08:14] <yofel> tsimonq2: did you file a bug for the CVE?
[08:17] <acheronuk> someone did: https://bugs.launchpad.net/bugs/1668871
[08:17] <acheronuk> tsdgeos: sorry not been able to get to thsoe yet :/
[08:17] <acheronuk> tsimonq2: I mean ^^^
[08:18] <acheronuk> damn tab complete on similar nicks, lol
[08:18] <tsdgeos> acheronuk: no kdelibs?
[08:19] <acheronuk> tsdgeos: checking. I literally only saw the email for that bug 2 mins ago :P
[08:19] <acheronuk> dumb bot ^^
[08:22] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kio build #122: FAILURE in 12 min: http://kci.pangea.pub/job/zesty_unstable_kio/122/
[08:22] <yofel> meh, that's double patching for every release except trusty :/
[08:32] <acheronuk> precise is still a thing until April? so kde4libs for that as well
[08:35] <yofel> good point
[08:51] <acheronuk> ok. BBL. PM probably
[10:02] <lordievader> Good morning
[10:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #402: FAILURE in 4 hr 0 min: http://kci.pangea.pub/job/xenial_unstable_kwallet/402/
[10:56] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktextwidgets build #358: FAILURE in 4 hr 0 min: http://kci.pangea.pub/job/xenial_unstable_ktextwidgets/358/
[11:47] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kwallet build #403: STILL FAILING in 45 min: http://kci.pangea.pub/job/xenial_unstable_kwallet/403/
[11:47] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_ktextwidgets build #359: STILL FAILING in 46 min: http://kci.pangea.pub/job/xenial_unstable_ktextwidgets/359/
[11:56] <BluesKaj> Hey folks
[12:09] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_eventviews build #71: FAILURE in 4 hr 0 min: http://kci.pangea.pub/job/yakkety_unstable_eventviews/71/
[12:27] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kio build #123: STILL FAILING in 4 hr 0 min: http://kci.pangea.pub/job/zesty_unstable_kio/123/
[12:33] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kconfigwidgets build #370: FAILURE in 46 min: http://kci.pangea.pub/job/xenial_unstable_kconfigwidgets/370/
[13:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_eventviews build #72: STILL FAILING in 47 min: http://kci.pangea.pub/job/yakkety_unstable_eventviews/72/
 anyone here?
 I'd like to report a bug for plasma 5.9.2 in zesty
 and I can't figure out how
[13:14] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kservice build #96: FAILURE in 46 min: http://kci.pangea.pub/job/zesty_unstable_kservice/96/
[13:19] <tsdgeos> ovidiuflorin: launchpad?
[13:19] <tsdgeos> not that anyone ever looks at launchpad bugs according to the experience of the bugs i've opened
[13:19] <tsdgeos> but that's a different story
 yeah...
 I'll try upstream
 but they'll complain that it's not their fault..
 as usual...
[13:22] <tsdgeos> ....
[13:24] <mamarley> You might also want to check the changelog for 5.9.3 which was recently released and is currently in the staging PPA for Zesty.
 will that be in Beta 2?
 I'll probably try staging as well, but not yet..
 I have to get some work done
[13:44] <mamarley> Not sure, sorry.
 drkonqi and KDevelop crash in Beta 1
 they are barely usable
[13:54] <kfunk> Could not start process Unable to create io-slave:
[13:54] <kfunk> klauncher said: Error loading '/usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kio/fish.so'.
[13:54] <kfunk> under Kate, on 16.10 with backports ppa :\
[13:54] <kfunk> known issue?
[13:54] <kfunk> worked before upgrading to the backports ppa
[13:55] <yofel> does it tell anything else?
 yofel, who are you asking?
[14:02] <yofel> kevin
[14:04] <kfunk> yofel: nope
[14:04] <yofel> :/
[14:04] <kfunk> the fish.so file exists, and ldd reports no missing deps
[14:04] <kfunk> I can debug later, just wanted to know whether it's known...
[14:14] <acheronuk> kfunk: In a VM, I see no such message on kate start via command line on Yakkety with backports. kio-extras is installed so that library is there
[14:15] <acheronuk> ovidiuflorin: are those the kdevelop from the zesty archive, or do you have some ppa ones installed?
 I had the KDevelop PPA before the upgrade
 let me check
 dolphin has no icons when launched with kdesudo
 this has been happening for several releases now
 and I mean no icons, for anything
[14:38] <acheronuk> ovidiuflorin: dolphin has not worked properly with kdesudo for ages AFAIK
[14:39] <acheronuk> but I never run file managers as root, so can't say for sure
[14:40] <tsdgeos> ovidiuflorin: don't shoot yourself in the face with a shotgun, it helps
[14:43] <tsdgeos> i.e. don't use apps as root
 I need it in some specific cases
[14:53] <acheronuk> ovidiuflorin: there should be a root actions service menu for dolphin on the KDE store. some other file managers also better support running in sudo/root mode I think?
[15:03] <BluesKaj-pi> heh, neither has system settings with kdesudo...been trying to make the kate and dolphin toolbars etc large enough to be readable on a large monitor from 3M away , the text inside kate is can be set by it's internal font option , but not the main toolbars etc.for dolphin or kate.
[15:07] <BluesKaj-pi> it does work on kde4 tho, so it could be an oversight in kde/ plasma5
[15:09] <BluesKaj-pi> btw most settings in kdesudo systemsettings5 one tries to change don't change\
 BluesKaj-pi have you tried scaling everything bigger with xrandr?
 So anyone fix that CVE yet, or am I doing that?
 what's CVE?
[15:21] <BluesKaj-pi>  ovidiuflorin, it's fine as normal user , only as kdesudp permissions like editing files in dolphin as kdesudo
[15:22] <BluesKaj-pi> or kate
[15:30] <BluesKaj> ovidiuflorin, like so, http://imgur.com/a/C3yux
[15:49] <yofel> tsimonq2: both CVEs got looked at for yakkety and zesty, but the LTS patches are missing so far
[16:09] <acheronuk> tsimonq2: I have been doing bits and pieces today, but so far not managed to sit down long enough to get stuck into that. feel free
[16:15] <marco-parillo> I think configuration problems running apps (like kate) as root might be a won't fix, until they use Polkit. https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1633748/comments/3
[16:19] <tsimonq2> k
[16:20] <tsimonq2> yofel: Uh what? I only see Yakkety looked at...
 BluesKaj-piyou have a font DPI setting in the Fonts KCM
[16:23] <tsimonq2> clivejo, yofel, acheronuk: Do you guys have a handle on making sure we have all six patches uploaded? (one for each codename of each package, making a total of 6 different uploads)
[16:24] <tsimonq2> I can crank this out when I get home in ~ 5 hours
[16:24] <tsimonq2> (if you guys didn't get to it by then)
[16:36] <yofel> tsimonq2: hm, maybe kio wasn't uploaded to zesty, but check the queue
[16:37] <yofel> tsimonq2: we don't upload those, just add the patches so the security team can push them out through the security channel
[16:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kconfigwidgets build #371: STILL FAILING in 4 hr 0 min: http://kci.pangea.pub/job/xenial_unstable_kconfigwidgets/371/
[16:39] <tsimonq2> yofel: I mean at least adding the patches to the bug report so they can do so
[16:40] <yofel> tsimonq2: right, just check what vishnunaini and Marc already took care of
 I'm on Zesty Beta 1: Random things keep crashing and when I try to use the (what's it's name) app to report them, it opens launchpad and complains that I'm already logged in
 You are already logged in … You are already logged in as Ovidiu-Florin BOGDAN. If this is not you, please log out now.
 https://bugs.launchpad.net/ubuntu/+source/kglobalaccel/+filebug/d4e2f37a-fe9d-11e6-b769-002481e7f48a/+login?field.title=kglobalaccel5+crashed+with+SIGABRT+in+QMessageLogger%3A%3Afatal%28%29
 there are moments when the desktop goes on a crashing spree
 apps keep crashing one after another
 krunner, akonadi resources, plasmashell
 and other names I don't recognize
[16:57] <acheronuk> ovidiuflorin: odd. up to date zesty is rock solid here
 regarding the KDevelop crashes
 I see that if I keep the session caches from one version of Kubuntu to another, things start to go very south
 kdevelop sessions that is
 kfunk ^
 if I delete the local sessions (delete the session folders manualy)
 everything works fine after
 but I have to clear out everything in my $HOME related to KDevelop
 not just sessions, but also configs
 acheronuk do we have separate packages for akonadi resources?
[17:01] <kfunk> ovidiuflorin: backtrace :)
 err....
 I tried...
[17:01] <kfunk> which kdevelop versions are involved?
 drkonqi crashed...
 I lost it
[17:01] <kfunk> we usually clean caches from one version to the other
 KDevelop 5.0.3
[17:02] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcmutils build #200: FAILURE in 4 hr 0 min: http://kci.pangea.pub/job/yakkety_unstable_kcmutils/200/
 I asked in the past, and I think I'll ask again
[17:03] <acheronuk> ovidiuflorin: which ppa is that from?
 I believe KDevelop should have an option, CLI if you'd like to clear all the cache
 I installed if from the KDevelop releases ppa when I was on yakkety
 and then upgraded to zesty
 now the PPA is disabled on my system
 kfunk, the option to clear the cache is very useful for me since I have some enourmous projects loading, that use a very f**ed up makefile system
[17:07] <acheronuk> ovidiuflorin: in that case you should probably do a zesty build in the kdevelop ppa, or try the one in staging-misc.
 I don't know how
 I'd preffer to update the kdevelop ppa for zesty
 and I don't know if I have access to do that
[17:12] <acheronuk> I certainly don't have access. clivejo did the last uploads
[17:12] <clivejo> I did what?
[17:12] <acheronuk> clivejo: https://launchpad.net/~kdevelop/+archive/ubuntu/release/+packages
[17:13] <acheronuk> uploader 'clivejo'
[17:13] <clivejo> yeah
[17:14] <clivejo> was hoping 5.1 would be released before FF
[17:14] <acheronuk> seems not, so I suppose zesty archive should be updated to 5.0.2 as well
[17:14] <acheronuk> 5.0.3
[17:14] <acheronuk> assuming that is all bugfix
[17:15] <clivejo> feel free
[17:16] <acheronuk> I have no clue about kdevelop. but if you have no time I may have a look in the next week or 2 before final beta
[17:16] <clivejo> just fed up wasting my time on it
[17:16] <clivejo> still dont have upload rights for the components
[17:17] <acheronuk> the name change?
[17:17] <clivejo> yes
[17:18] <clivejo> and I requested a package refresh and it never happened
[17:18] <clivejo> so as I say, fed up wasting time on it
 kfunk is the 5.1 release planned? I mean does  it have a release date set?
[17:19] <kfunk> ovidiuflorin: asap
[17:19] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kservice build #97: STILL FAILING in 4 hr 0 min: http://kci.pangea.pub/job/zesty_unstable_kservice/97/
 aham, ok, thank you
[17:19] <clivejo> the packaging is being kept up-to-date in KCI
[17:20] <clivejo> so people can use it from there
[17:20]  * acheronuk shrugs
 has santa_ looked at my MR?
[17:20] <acheronuk> if we can't upload a newer one, then I may not bother
[17:20] <clivejo> can upload the main part
[17:21] <clivejo> its just the components
[17:21] <acheronuk> perhaps if out packageset refresh gets done for PIM we can get those in as well
[17:22] <clivejo> if
[17:22] <acheronuk> if? it damn well better be
[17:22] <clivejo> kdev-php and kdev-python are the components I couldnt upload on last check
[17:23] <acheronuk> oh, I said 'if'...
[17:23] <clivejo> good luck on that one :P
[17:23] <acheronuk> it better be 'when'. as not having upload rights to our own stuff is just ludicrous and indefensible
[17:25] <clivejo> !info kdevelop
 that's old
[17:28] <clivejo> yup
[17:29] <clivejo> and a direct sync with debian
[17:36] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_extra-cmake-modules build #115: FAILURE in 17 min: http://kci.pangea.pub/job/zesty_unstable_extra-cmake-modules/115/
[17:37] <acheronuk> !info kdevelop-php
[17:38] <acheronuk> clivejo: that is synced now ^^^
[17:39] <acheronuk> hmmm. python is no though :/
[17:39] <acheronuk> *not
[17:42] <acheronuk> maybe we can upload the main part and get anything missing sync/merged
 acheronnuk do you need admin on KDevelop group? in LP
[18:52] <acheronuk> ovidiuflorin: don't think so. Phil and anyone KC can admin, so that seems enough?
 who is Jonathan Kolberg?
[19:22] <clivejo> !info kdevelop-python
[19:22] <clivejo> !info kdevelop-python unstable
[19:51] <ahoneybun> https://blogs.kde.org/2017/03/01/plasma-510-folder-view-default-desktop-mode?utm_source=dlvr.it&utm_medium=twitter
[19:52] <clivejo> ahoneybun: acheronuk wants to backport that
[19:53] <ahoneybun> 5.10 to what? clivejo
[19:53] <acheronuk> or at least enable it on the iso live session
[19:53] <ahoneybun> folder view?
[19:53] <clivejo> that folder view feature to 5.9.*
[19:53] <ahoneybun> mm
[19:53] <clivejo> so our installer icon can be seen
[19:54] <ahoneybun> should be no reason you can't just put it on there already tbh
[19:55] <acheronuk> ahoneybun: on the live iso http://i.imgur.com/R70XoJ7.png
[19:55] <ahoneybun> you can disable that icon
[19:55] <ahoneybun> I saw it in that video comparing Neon and Kubutnu
[19:56] <ahoneybun> *Kubuntu
[19:56] <acheronuk> ahoneybun: yes, I know how to do it.
[19:56] <ahoneybun> I must not be seeing the issue then, no worries
[19:57] <acheronuk> just a Q of whether to switch it on just the live session, or completely as the default on our installed desktop
[19:57] <acheronuk> ahoneybun: ok. we may be taking about different things
[19:58] <ahoneybun> mm I think I know now
[19:59] <ahoneybun> you want folder view over desktop view on the iso and as default
[19:59] <acheronuk> clivejo: that article suggests KDE don't think folderview is quite polished enough yet to be the desktop default, if they are asking for feedback on the choice and improvements
[19:59] <acheronuk> ahoneybun: yep
[19:59] <clivejo> acheronuk: whats going on with KCI?
[20:00]  * mamarley has been using it for ages without any issues.
[20:00] <acheronuk> ahoneybun: so we can get rid of the ugly separate containment on top that overlaps the toolbox
[20:01] <ahoneybun> you mean the widget box
[20:01] <acheronuk> clivejo: LP is ****ed
[20:01] <clivejo> oh great
[20:02] <acheronuk> ahoneybun: the box yes. which is a folderview containment itself
[20:02] <ahoneybun> gotcha
[20:02] <acheronuk> ahoneybun: but if the whole desktop is one, as KDE want to switch to, that invisibly vanishes ;)
[20:03] <ahoneybun> well those icons on that 5.10 screenshot look like just normal desktop icons
[20:03] <clivejo> a change we should adopt now in 5.9 instead of waiting on 5.10 IMHO
[20:03] <acheronuk> clivejo: or LP was earlier
[20:03] <ahoneybun> the default widget in Desktop view is an folder view
[20:06] <acheronuk> ahoneybun: https://cgit.kde.org/plasma-desktop.git/commit/?id=151bfb728ce8eed923f8e32ae39e345441af2f7b
[20:06] <acheronuk> the KDE upstream change ^^^^ for 5.10
[20:06] <ahoneybun> just one line to change lol
[20:06] <acheronuk> but I would want to check that such a change would not mess up anything for 5.9
[20:07] <acheronuk> the comment about the drop menu, I'm not sure I understand
[20:07] <ahoneybun> I'm thinking it is that box you were pointing at
[20:08] <acheronuk> have been meaning to ash Eike or notmart. but just not got there yet this week
[20:08] <ahoneybun> wow just made plasma crash
[20:08] <ahoneybun> disabled that box
[20:08] <ahoneybun> enable it
[20:08] <ahoneybun> then click it
[20:09] <ahoneybun> mm seems to be a one time thing
[20:11] <ahoneybun> acheronuk: if you enable the folder view in 5.9.3
[20:11] <ahoneybun> and click both that box on the top left with the 3 lines
[20:11] <ahoneybun> then right click the desktop
[20:11] <ahoneybun> both menus have the same actions
[20:12] <ahoneybun> maybe before they did not match up so you needed the box on the top left to be enabled
[20:13] <clivejo> I have no idea what you are talking about?!
[20:13] <ahoneybun> mm
[20:13] <ahoneybun> http://i.imgur.com/R70XoJ7.png
[20:13] <acheronuk> I don't want to disable the toolbox
[20:13] <ahoneybun> I'm saying that they did in 5.10
[20:13] <ahoneybun> atm
[20:13] <clivejo> we just want the install icon to appear nicely on the desktop
[20:14] <acheronuk> want to get rid of the huge grey desktop folder
[20:14] <ahoneybun> just make it a folder view and add the install icon in the desktop dir
[20:14] <clivejo> they did it in 5.10 by switching the default view
[20:14] <acheronuk> ahoneybun: yep, that is what we want to do
[20:14] <ahoneybun> nice then
[20:15] <santa_> good evening/night everyone
[20:15] <acheronuk> just a case of whether we do that on just the iso, or for the actual installed systems
[20:15] <clivejo> what we are saying, is that this would fix the issues we been having with the installer icon and maybe we should think of backporting that tiny change to 5.9.*
[20:15] <acheronuk> if just the iso, we can change the default with a caster script on the iso
[20:16] <acheronuk> if for both, we backport that 5.10 change completely
[20:16] <santa_> yesterday's night autopkgtests for plasma 5.9.3: http://gpul.grupos.udc.es/buildstatus_ubuntu-exp2/ubuntu-exp2_status_plasma.html
[20:16] <santa_> nothing failing for amd64
[20:16] <clivejo> if its coming anyways and is just a matter of a patch to change that line, I think we should do it
[20:17] <clivejo> ahoneybun: did I hear you are running plasma 5.9.3 on your box?
[20:18] <ahoneybun> I am indeed
[20:18] <ahoneybun> on my desktop and laptop
[20:18] <clivejo> so thats mamarley acheronuk and ahoneybun all thumbs up, anyone else?
[20:18] <ahoneybun> for the patch?
[20:18] <clivejo> no 5.9.3
[20:19] <ahoneybun> rocking pretty well here
[20:19] <mamarley> Yeah, works fine here.
[20:19] <acheronuk> clivejo: http://paste.ubuntu.com/24092241/
[20:19] <mamarley> No problems.  But, then again, I didn't have any problems before, so there wasn't anything to fix.
[20:20] <clivejo> acheronuk: I say do it :/
[20:20] <santa_> acheronuk, clivejo: FYI I have just pushed a quick KA patch for kde's sftp server move
[20:20] <acheronuk> the only real problem I had with 5.9.2, I quickly backported the fix for. so not much change with 5.9.3 here
[20:20] <clivejo> santa_: is that move permanant?
[20:20] <clivejo> I really dont understand what they are doing with that
[20:20] <santa_> it seems so
[20:21] <clivejo> why not just change the DNS and point depot.kde.org to the new machine
[20:21] <santa_> but anyway if they change it back we can change it back too
[20:21] <acheronuk> sitter asked them same question
[20:21] <clivejo> I doubt we are the only ones who use that with automation
[20:22] <acheronuk> why not just point the depot domain to the new server
[20:22] <clivejo> acheronuk:  is there a techie reason why they cant?
[20:22] <acheronuk> clivejo: not a clue
[20:22] <clivejo> strange
[20:24] <acheronuk> clivejo: from neon http://paste.ubuntu.com/24092287/
[20:26] <clivejo> LOL
[20:27] <clivejo> does not compute
[20:27] <acheronuk> I like the last line
[20:28] <clivejo> I thought he would be all for skynet
[20:29]  * clivejo imagines Skynet with Harulds face and voice
[20:35] <acheronuk> ok. setting folderview to default would require (a) backport that patch (b) remove the script from kubuntu-settings that for the iso adds that extra folder containment to the desktop, as the desktop would already be one itself!
[20:36] <acheronuk> santa_: thanks for those tests. that is great :)
[20:38] <clivejo> we need to update -settings anyways
[20:38] <santa_> acheronuk: no prob, let's hope I have time to write that guide so you can do yourselves the thing
[20:38] <clivejo> could you apply that patch and upload 5.7.3?
[20:39] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kxmlgui build #386: FAILURE in 4 hr 0 min: http://kci.pangea.pub/job/xenial_unstable_kxmlgui/386/
[20:40] <acheronuk> clivejo: I would want to make both changes at the same time, otherwise we would end up with a nasty looking containment + icon on top of another icon on the live session
[20:52] <acheronuk> clivejo: i.e. we would drop https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kubuntu-settings/tree/desktop/usr-share/layout.js?h=kubuntu_zesty_archive
[20:52] <acheronuk> and let plasma do it's default thing instead
[20:53] <clivejo> does plymouth-theme-kubuntu-logo work?
[20:55] <acheronuk> not sure. I see it sometimes on virtualbox shutdown, but on real hardware plymouth is one of the first things I disable
[21:02] <acheronuk> clivejo: we could make that small change now, and update the rest of the kubuntu-settings in the next week or so? or leave both for changes for another time?
[21:04] <acheronuk> clivejo: LP publisher seems to have died BTW, so not sure about uploading much tonight anyway!
[21:07] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_kcmutils build #201: STILL FAILING in 4 hr 0 min: http://kci.pangea.pub/job/yakkety_unstable_kcmutils/201/
[21:08] <acheronuk> timed out at 4hrs ^^^
[21:29] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:29] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[21:29] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kxmlgui build #387: FIXED in 44 min: http://kci.pangea.pub/job/xenial_unstable_kxmlgui/387/
[21:29] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_extra-cmake-modules build #116: FIXED in 3 hr 47 min: http://kci.pangea.pub/job/zesty_unstable_extra-cmake-modules/116/
 can someone please confirm if we ship the winbind package preinstalled?
 or tell me how I can find out
 besides doing a fresh install
[21:34] <acheronuk> :) http://www.kdigest.com/2017/02/kde-community-publishes-video-showing.html
[21:35] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libksieve build #91: FAILURE in 6 min 13 sec: http://kci.pangea.pub/job/zesty_unstable_libksieve/91/
[21:45] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_libksieve build #92: STILL FAILING in 4 min 47 sec: http://kci.pangea.pub/job/zesty_unstable_libksieve/92/
 if that's the same video I saw...
 it's good that the video exists...
 but the production and demo is not so great IMO
[21:49] <santa_> clivejo: a couple of days ago you asked me about apps 16.12 I presume you want to know the current status?
[21:49] <clivejo> yeah, mainly the autotests
[21:50] <santa_> allright I have the results here, and I'm working on fixing them
[21:50] <santa_> "here" = http://gpul.grupos.udc.es/buildstatus_ubuntu-exp2/ubuntu-exp2_status_applications.html
[21:51] <santa_> the akonadi failures are specially scary and I couldn't dig into it properly, but I have been fixing several ones easier to do
[21:52] <santa_> for instance I'm testing right now a stop-in-gap for kpimtexedit
 santa_ I'd like to stress you to take a look at my MR
[21:52] <santa_> I'm documenting any stop-in-gap or dubious solution here: https://phabricator.kde.org/w/kubuntu/autopkgtests/working_notes/
 😃
[21:53] <santa_> so we could deal with it @ kde properly later
 to poke you actually
[21:53] <santa_> ovidiuflorin: sure I have that in today's todo list
 ok, awesome
[21:54] <santa_> actually I'm going to re-check the thing while kpimtexedit builds
 then I'm off to bed
 it's quite late for me
[21:54] <santa_> ok, no pro
[21:54] <santa_> * prob
 nini
 Mm can't start X11 now
 Since my power went out for a second
[22:13] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-desktop build #132: STILL FAILING in 2 min 35 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-desktop/132/
[22:19] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-desktop build #133: STILL FAILING in 38 sec: http://kci.pangea.pub/job/yakkety_unstable_plasma-desktop/133/
[22:26] <acheronuk> clivejo: if LP is behaving in the morning, I could maybe upload plasma and tweaked setting then?
[22:26] <acheronuk> kubuntu-settings I mean
[22:27] <acheronuk> clivejo: qtcurve will be official kde, so think that should get added to KCI
[22:28] <acheronuk> also need to review our meta, along with settings and seeds
[22:30] <clivejo> ok with me
[22:33] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:33] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-integration build #111: FIXED in 1 hr 3 min: http://kci.pangea.pub/job/zesty_unstable_plasma-integration/111/
[22:33] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_k3b build #47: STILL UNSTABLE in 1 hr 25 min: http://kci.pangea.pub/job/yakkety_unstable_k3b/47/
[22:34] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_oxygen build #89: FIXED in 1 hr 4 min: http://kci.pangea.pub/job/zesty_unstable_oxygen/89/
[22:34] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:34] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kmenuedit build #90: FIXED in 1 hr 5 min: http://kci.pangea.pub/job/zesty_unstable_kmenuedit/90/
[22:35] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:35] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kscreen build #104: FIXED in 1 hr 5 min: http://kci.pangea.pub/job/zesty_unstable_kscreen/104/
[22:35] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:35] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:35] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_powerdevil build #57: FIXED in 1 hr 5 min: http://kci.pangea.pub/job/zesty_unstable_powerdevil/57/
[22:35] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_ksysguard build #77: FIXED in 1 hr 5 min: http://kci.pangea.pub/job/zesty_unstable_ksysguard/77/
[22:35] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:35] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kdeplasma-addons build #117: FIXED in 1 hr 5 min: http://kci.pangea.pub/job/zesty_unstable_kdeplasma-addons/117/
[22:36] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:36] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-desktop build #127: FIXED in 1 hr 7 min: http://kci.pangea.pub/job/zesty_unstable_plasma-desktop/127/
 Mm got sddm after an update to Nvidia drivers
[22:46] <tsimonq2> !info ktnef zesty
[22:46] <tsimonq2> Hmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm
[22:48] <acheronuk> hummmmmmmmmmmmmm
[22:49]  * tsimonq2 hugs yofel
[22:49] <tsimonq2> bug 1668552]
[22:50] <clivejo> ummmmmmmmmmmm
[22:52] <acheronuk> yummm?
[22:53] <acheronuk> !cookies
[22:53] <acheronuk> yummm ^
[22:55] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:55] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_khotkeys build #82: FIXED in 20 min: http://kci.pangea.pub/job/zesty_unstable_khotkeys/82/
[22:55] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_k3b build #39: STILL UNSTABLE in 21 min: http://kci.pangea.pub/job/xenial_unstable_k3b/39/
[22:56] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[22:56] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_plasma-desktop build #134: FIXED in 32 min: http://kci.pangea.pub/job/yakkety_unstable_plasma-desktop/134/
[22:57] <yofel> !yum
[22:57] -kubuntu-ci:#kubuntu-devel- Project merger_kpimtextedit build #614: FAILURE in 10 sec: http://kci.pangea.pub/job/merger_kpimtextedit/614/
[22:57] <yofel> oh come on, why did they change that :/
[23:00] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libksieve build #111: FAILURE in 4 min 9 sec: http://kci.pangea.pub/job/yakkety_unstable_libksieve/111/
[23:00] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libksieve build #123: FAILURE in 4 min 36 sec: http://kci.pangea.pub/job/xenial_unstable_libksieve/123/
[23:08] <ahoneybun> and I got Plasma to start again
[23:09] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kpimtextedit build #114: STILL UNSTABLE in 12 min: http://kci.pangea.pub/job/zesty_unstable_kpimtextedit/114/
[23:10] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_libksieve build #124: STILL FAILING in 4 min 36 sec: http://kci.pangea.pub/job/xenial_unstable_libksieve/124/
[23:11] -kubuntu-ci:#kubuntu-devel- Project yakkety_unstable_libksieve build #112: STILL FAILING in 6 min 7 sec: http://kci.pangea.pub/job/yakkety_unstable_libksieve/112/
[23:42] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:42] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_plasma-workspace build #167: FIXED in 31 min: http://kci.pangea.pub/job/zesty_unstable_plasma-workspace/167/
[23:59] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed!
[23:59] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_plasma-desktop build #126: FIXED in 1 hr 3 min: http://kci.pangea.pub/job/xenial_unstable_plasma-desktop/126/


[00:08] <slangasek> infinity: fixed wrt what?
[00:20] <infinity> slangasek: Oh, it's been FTBFS for a while, he has it fixed in bzr, just not uploaded.
[00:25] <slangasek> infinity: ah
[04:36] <Niraj_> hi, I am not sure if this is right channel to post packaging related doubts, but can someone help me package bash source for oneiric?
[07:22] <tjaalton> shouldn't dh pass --datadir automatically?
[07:22] <tjaalton> the default which is /usr/share
[07:27] <slangasek> tjaalton: it doesn't pass --datadir by default because the autoconf built-in default is fine
[07:29] <tjaalton> slangasek: ah, it comes from there.. well for some reason it doesn't seem to work right for sssd, the __init__.py file has "${prefix}" where the .in file had @datadir@
[07:30] <tjaalton> passing --datadir makes it right, but that shouldn't be necessary
[07:30] <slangasek> the default value of --datadir is ${prefix}/share
[07:30] <tjaalton> heh, ok
[07:30] <slangasek> so that seems like a malformed substitution somewhere
[07:31] <slangasek> the .py probably needs to be generated from a Makefile instead of directly by autoconf, to get the necessary expansion
[07:31] <tjaalton> ok, I'll try that
[08:59] <nn0101> hello!
[08:59] <nn0101> is anyone aware of lvm+luks setup failing on 12.10?
[09:00] <nn0101> i dont understand why the option exists during the installation.
[09:01] <nn0101> i know luks is lvm+luks works because i liveusb'ed it, put passphrase and mounted them successfully.
[09:02] <nn0101> yet when i boot, my laptop just keeps blanking the screen (as if it's trying to boot off my luks'ed partition but failing to do so because of no passphrase prompt or whatever).
[09:04] <nn0101> trying these: /boot is unencyrpted, MBR in /dev/sda, /dev/sda5 is LVM+LUKS. would be great if anyone know if this setup worked on theirs.
[09:05] <trijntje> nn0101: this is probably not the right channel to ask, try #ubuntu
[09:07] <Niraj_> bump: can someone help me package bash source for oneiric?
[10:26] <zykes-> how can I build a package in a directory that has a debian folder ?
[10:26] <ion> debuild -b -us -uc
[11:04] <GunnarHj> slangasek: ping?
[17:08] <jtaylor> why was python-imaging changed?
[17:08] <jtaylor> it breaks a bunch of other packages
[19:01] <xxiao> BenC: no kvm
[19:01] <xxiao> somehow i can not send msg to mklinux
[19:01] <BenC> xxiao: Nick not registered with nickserv?
[19:02] <xxiao> then why can I msg here
[19:02] <xxiao> used to work fine
[19:02] <BenC> xxiao: Are you using qemu-system-ppc64?
[19:02] <BenC> xxiao: Each channel can forbid unregistered nicks from messaging the channel
[19:02] <BenC> Perhaps #mklinux does and this channel doesn't force that
[19:02] <xxiao> hmm but i used to talk on mklinux just fine, will check
[19:36] <BenC> Any ideas why the buildd's can't install packages (unmet deps) that I am able to install locally (raring)?
[19:38] <BenC> https://launchpadlibrarian.net/130223052/buildlog_ubuntu-raring-powerpc.haskell-lens_<IP_ADDRESS>-2_FAILEDTOBUILD.txt.gz
[19:38] <BenC> Specifically this
[19:44] <ev> infinity: ja
[19:44] <ev> probs monday
[20:07] <quadrispro> !regression-alert
[20:10] <quadrispro> bug #1110326 incorrect linking order led to "undefined symbols" errors
[20:11] <quadrispro> I gotta go now, I already uploaded a fix to precise though, I'll work on other releases within few hours
[20:31] <Quacky2200> Hello
[20:32] <Quacky2200> is anyone doing ubuntu development at canonical?
[21:02] <Quacky2200> Does anyone here work at canonical?
[23:48] <infinity> BenC: Are you taking -proposed into account before you ask that question?