[01:00] <ScottK> Riddell: That's compared to me.
[04:36] <valorie> http://xkcd.com/1205/
[06:19] <soee> good morning
[06:45] <kubotu> ::runtime-bugs:: [1306377] kwallet not use blowfish (gpg) auth @ https://bugs.launchpad.net/bugs/1306377 (by GoFast)
[07:24] <lordievader> Good morning
[07:37] <Quintasan> > Saucy^WTrusty Tahr
[07:37] <Quintasan> and the header
[07:37] <Quintasan> >[ Another cycle, another shameless copy and paste email... ]
[07:37] <Quintasan> Adam Conrad++
[09:07] <Riddell> all seems to be compiling, powerpc and some arm being slow as usual but no problems
[09:28] <apachelogger> debfx: how does the initial upload script know which builddep versions to bump and which ones to leave?
[09:28] <apachelogger> (perlkde's bdeps on smokekde-dev and perlqt-dev were not bumped to 4.13 for some reason, were still at 4.9)
[09:32] <debfx> apachelogger: idk, the version I wrote just bumped the kde-sc-dev-latest build-dep version
[09:45] <ghostcube> hmm linux headers for 3.13.0-24 cant be installed
[09:50] <kubotu> ::runtime-bugs:: [1306377] kwallet not use blowfish (gpg) auth @ https://bugs.launchpad.net/bugs/1306377 (by GoFast)
[09:53] <ghostcube> yep proposed repo is missing linux-headers-3.13.0-24.46
[10:10] <yofel> apachelogger: it simply doesn't
[10:11] <yofel> apachelogger: well, to be more accurate, it will bump any deps that are in kde-sc-dev-latest-$release.txt AND have a versioned build-dep
[10:12] <apachelogger> mh
[10:13] <apachelogger> yofel: so what'd be the best approach to preventing this in the future? add smokekde-dev to the sc-dev?
[10:13] <Riddell> yay, okular in, that one often catched out lots of packages
[10:14] <yofel> yeah, that's supposed to have the same list of packages that the real kde-sc-dev-latest breaks
[10:14] <yofel> as it's the kinda replacement
[10:17] <apachelogger> right
[10:17] <apachelogger> hooray hooray
[10:17] <apachelogger> on a related note, this shall be much fun with frameworks and plasma next xD
[10:17] <yofel> also note, unversioned build-deps don't get versioned by putting something in that file
[10:21] <apachelogger> right, so all -devs need to be versioned and all devs need to be in the dev list file
[10:22] <apachelogger> that should then speed up build alignment by one or two cycles (~1hour from what I have seen yesterday)
[10:25] <apachelogger> allee: pam-kwallet foo should all be available now
[10:36] <andreaxxx> Hello, since last week I've had a weird problem on 14.04: basically all windows have no titlebar, are maximized by default and can not be resized or moved, also alt+tab doesn't work. Any idea?
[10:37] <apachelogger> andreaxxx: sudo apt-get install kubuntu-desktop kde-window-manager
[10:41] <BluesKaj> 'Morning folks
[10:49] <apachelogger> xnox: when installing today's image I get an exciting dialog titled ??? ??? with an ok button, has anyone else seen that?
[10:51] <apachelogger> (prep page of ubiquity-kde; the one with an overview of ac-adapter-plugged-in & internet access & disk space)
[10:52] <andreaxxx> apachelogger: thank you!
[10:52] <xnox> apachelogger: $HOME is now set, does that affect you? (one line in /usr/lib/ubiquity/bin/ubiquity
[10:52] <xnox> )
[10:54] <apachelogger> xnox: the line is not there
[10:55] <xnox> apachelogger: oh, ok. so probably didn't build with new ubiquity yet.
[10:55] <apachelogger> ok
[12:10] <apachelogger> four more builds and 4.13 landing should be complete
[12:11] <apachelogger> correction, one more ^^
[12:31]  * Quintasan tries saucy -> trusty upgrade
[12:32] <apachelogger> Quintasan: I'd wait with that
[12:33] <apachelogger> until 4.13 landing is complete
[12:33] <Quintasan> mmkay
[12:33] <apachelogger> should only be a matter of hours
[12:33] <apachelogger> powerpc builds so incredibly slow :/
[12:36] <jussi> hrm, doing the trusty upgrade and something has gone wrong: http://paste.ubuntu.com/7234728/
[12:37] <Quintasan> apachelogger: http://qa.kubuntu.co.uk/buildstatus/kubuntu-buildstatus.html all green there
[12:37] <apachelogger> no
[12:38] <apachelogger> kopete still missing
[12:38] <Quintasan> jussi: sudo apt-get update && sudo apt-get -f install doesn't help?
[12:38] <Quintasan> apachelogger: We don't ship Kopete by default anymore do we?
[12:38] <jussi> Quintasan: Im running those now, but that shouldnt happen...
[12:38] <apachelogger> also runtime is apparently blocked by CI on libreoffice
[12:38] <Quintasan> I see.
[12:38] <Quintasan> Well, that can wait.
[12:39] <apachelogger> runtime blocked on libreoffice CI, kopete blocked on building on powerpc, korundum blocked on armhf build
[12:40] <apachelogger> latter should be resolved in the next proposed migration attempt though
[12:41] <apachelogger> also libreoffice CI failed, so I am not sure runtime will get a promotion
[12:41] <Quintasan> apachelogger: CI?
[12:41] <apachelogger> https://jenkins.qa.ubuntu.com
[12:42] <Quintasan> How and why is that related to runtime?
[12:42] <apachelogger> LO-kde depends on kde-runtime
[12:42] <Quintasan> oh
[12:42] <Quintasan> we still ship that?
[12:42] <Quintasan> I thought it was broken
[12:42] <apachelogger> CI on LO failed which now blocks kde-runtime from going to the release pocket
[12:43] <Quintasan> And we decided to drop that.
[12:43] <apachelogger> tho the failure seems to be from the test tooling rather than the actual package
[12:43] <apachelogger> Quintasan: was fixed
[12:43] <Quintasan> I see.
[12:43] <apachelogger> also the Munich guys are working on it
[12:44] <apachelogger> korundum should get promotion shortly
[12:44] <apachelogger> only the other two left then
[12:44] <apachelogger> and kopete should be building(tm)
[12:44] <apachelogger> just very slow ^^
[12:47] <Quintasan> Splendid. The world is almost ours.
[12:51] <apachelogger> ovidiu-florin: I guess we'll not have wordpress before 14.04?
[13:07] <manchicken> apachelogger: I'm going to push this branch now (hopefully, assuming the latest reply on my comment is as awesome as it sounds) and I'll run through the rest of the release steps later.
[13:07] <apachelogger> manchicken: yay
[13:08] <manchicken> I added your stuff to the ChangeLog as best as I could without getting too verbose.
[13:08] <manchicken> I may have missed something...
[13:09] <ghostcube> hmm i cant test kamoso sorry
[13:09] <ghostcube> it just doesnt recogniozes my cam
[13:09] <ghostcube> every other tool does it but not kamoso
[13:09] <manchicken> YES! It worked.
[13:09] <manchicken> apachelogger: So I create a branch, and then tag the master, yes?
[13:13] <Quintasan> apachelogger: 4 Vboxes ready for testing. Guess it's going to be a long night
[13:14] <manchicken> Okay, qapt 2.2.0 is tagged and branched for 2.2.
[13:14] <manchicken> Very cool.
[13:17] <apachelogger> manchicken: you tag a commit, and one commit can be in multiple branches, so it really does not matter what branch you are on when you are tagging
[13:17] <apachelogger> i.e. if you branch master, all comments of the branch are the very same commit objects as they are in master, they also have the very same hash as the commits in master
[13:28] <manchicken> Yeah, but you tag the branch/master at a current point in time, right?
[13:28] <manchicken> So if you check out a certain tag, you go to that point in time?
[13:29] <manchicken> A fixed point in time
[13:29] <manchicken> :)
[13:29] <apachelogger> manchicken: nono, you tag a commit ;)
[13:29] <apachelogger> which is a fixed point in time, except you don't care about the time really ^^
[13:29] <manchicken> But I just did `git tag`…
[13:30] <manchicken> So that just tags the most recent commit?
[13:30] <apachelogger> yeah
[13:30] <manchicken> Okay, I'm okay with that.
[13:31] <apachelogger> which is why you should use git tag $HASH (i.e. so you specify which commit exactly)
[13:31] <apachelogger> with careful checking git tag is just as good though
[13:44] <ghostcube> apachelogger: hmm i didnt get a cam picture so far or any vid
[13:44] <ghostcube> but kamoso doesnt crash anymore if taking a snapshot
[13:44] <apachelogger> ?
[13:45] <apachelogger> well that's something
[13:45] <Quintasan> Does it need testing on 13.10?
[13:50] <apachelogger> Quintasan: what needs testing?
[13:50] <Quintasan> kamoso
[13:50] <apachelogger> no
[13:51] <apachelogger> limited trusty changes
[13:51] <Quintasan> hm
[13:51] <Quintasan> I see.
[13:57] <apachelogger> kopete accepted, only runtime missing now
[14:06] <apachelogger> Quintasan: you could try an upgrade, but maybe make a snapshot first ;)
[14:06] <apachelogger> Quintasan: if it fails find someone in #ubuntu-devel to look at that runtime thing, no one wants to talk to me today :P
[14:06] <apachelogger> also I am not sure who exactly to poke about it anyway
[14:06] <apachelogger> I am a poor lost soul
[14:08] <ScottK> apachelogger: I'll have a look at it.
[14:08] <apachelogger> \o/
[14:14] <ScottK> apachelogger: If I did it right, it'll go on the next britney run.
[14:15] <apachelogger> ScottK: cool thx
[14:15] <apachelogger> Quintasan: ^
[14:16] <jussi> right, so I had that error on upgrade. seem to have fixored it by apt-get install -f and apt-get dist-upgrade. (and confirming kubuntu-desktop  installed...) lets see what happens on reboot...
[14:17] <Quintasan> jussi: Good.
[14:17] <Quintasan> apachelogger, ScottK: noted, reading books till then
[14:22] <apachelogger> I think someone will want to deal with the Kopete Latex plugin thread
[14:22] <apachelogger> IMHO that's a suggests level relationship, which really doesn't help the user all that much to overcome the error message in general
[14:23] <Quintasan> apachelogger: Can't we just tell him to kindly stop using deprecated software?
[14:23] <apachelogger> he's developer of that deprecated software :P
[14:24] <Quintasan> >Can you add imagemagick dependency to kopete package, so Latex plugin will work?
[14:24] <Quintasan> Can we even do that?
[14:24] <apachelogger> not for trusty we can't
[14:25] <Quintasan> I'll do it when trusty+1 is open
[14:32] <ScottK> Quintasan: I'd say split the Latex plugin into a separate binary then (if it's not already - didn't check).
[14:33] <jussi> it works :)
[14:40] <jussi> small "bug"? even after update, I still have the update icon in my system tray. hovering over it gives "An Update is available for your system" 
[14:40] <sgclark> Same here, and it does not seem to want to go away
[14:40] <jussi> sgclark: yeah, exactly
[14:40] <ScottK> What happens if you click on it and check for updates?
[14:41] <jussi> it stays.
[14:41] <sgclark> ^
[14:41] <ScottK> manchicken: ^^^
[14:41] <manchicken> ?
[14:41] <ScottK> That's kind of a big deal.
[14:42] <ScottK> manchicken: Updates available status icon not clearing after updates are applied.
[14:42] <manchicken> Okay, I didn't touch any of the muon stuff.
[14:42] <ScottK> It could be qapt too though.
[14:42] <ScottK> If qapt isn't clearing the status.
[14:43] <manchicken> qapt doesn't clear the status from what I understand. That sounds like it would be all muon, no?
[14:43] <manchicken> qapt only would handle reloading the cache and such.
[14:47] <ScottK> OK.
[14:47] <ScottK> I guess as long as you're confident it's reloading the cache correctly, you're off the hook.
[14:47] <ScottK> Who's been doing the Muon work?
[14:48] <apachelogger> apol
[14:48] <ScottK> Seems not to be here.
[14:48] <apachelogger> ScottK: seems britney needs more convincing
[14:48] <apachelogger> ScottK: #kde-devel
[14:49] <ScottK> jussi: Talk to apol on #kde-devel.
[14:49]  * ScottK looks
[14:49] <apachelogger> ScottK: unless your change didn't make it into the last run
[14:49] <apachelogger> for which the log was generated at 14:18 utc
[14:49] <ScottK> The page didn't update yet since I made the change.
[14:49] <apachelogger> ok
[14:49] <ScottK> Should be any time now.
[14:50]  * apachelogger heads out for coffee and stuff then
[15:17] <ScottK> apachelogger, Quintasan: Looks like it went.
[15:18] <apachelogger> ScottK: aye, thanks for poking it
[15:19] <ScottK> yw
[16:06] <kubotu> ::runtime-bugs:: [1306377] kwallet not use gpg auth @ https://bugs.launchpad.net/bugs/1306377 (by GoFast)
[16:58] <snele> guys after all todays updates i just rebooted 
[16:59] <snele> and grub shows "Ubuntu"
[16:59] <snele> not "Kubuntu"
[17:02] <jacky> you have the GRUB2 KCM?
[17:02] <jacky> if so, you could edit that
[17:03] <snele> jacky: yeah but by default until today it was "Kubuntu"
[17:05] <crissi> hello
[17:05] <jacky> Might be a change somewhere in the defacto Grub config
[17:05] <crissi> m. after upgrading to kde 4.12.97 kwallet is not able to read the password store.
[17:05] <crissi> whats wrong there?
[17:06] <Quintasan> 12.04 LTS with backports ppa -> 14.04 werks
[17:07] <crissi> saucy
[20:52] <ScottK> Upgraded to 14.04 from 13.10 works.  I can confirm the stuck "you have updates" icon issue.
[21:08] <soee_> :)
[21:09] <soee_> also when updating muon list
[21:09] <soee_> there are several notifications about available updates but should be only oen imo
[21:12] <ScottK> soee_: Someone needs talk to apol.
[21:13] <shadeslayer> known issue IIRC
[21:14] <shadeslayer> https://bugs.kde.org/show_bug.cgi?id=331434
[21:15] <shadeslayer> next 2.2 release I guess
[21:17] <soee_> ah nice
[21:18] <ScottK> shadeslayer: Is there a commit we can cherrypick?
[21:18] <ScottK> Seems rather important to me.
[21:18] <shadeslayer> ScottK: in the comments
[21:18] <shadeslayer> I'd recommend talking to apachelogger though
[21:19] <shadeslayer> http://commits.kde.org/muon/a882eeb2574af5fe7931166787911cb09975d12c
[21:19] <ScottK> shadeslayer: Can you upload it?  I can't review it if I do.
[21:19] <shadeslayer> okay
[21:20] <ScottK> He already confirmed it fix it.
[21:20] <ScottK> (in the bug)
[21:20] <ScottK> Thanks for finding/uploading.
[21:20] <shadeslayer> *nod*
[21:23] <shadeslayer> ScottK: already in
[21:24] <ScottK> Already in our packages?
[21:24] <ScottK> If so, then that's not the fix to the current issue several people are seeing.
[21:26] <shadeslayer> vHanda: not sure how much this helps, but krunner is taking up 100% CPU and this is the only thread that seeps to be doing any work http://paste.kde.org/psk8gpadt 
[21:27] <ScottK> shadeslayer: ?
[21:28] <shadeslayer> ScottK: not sure, that's the only issue I saw wrt notifications going bonkers
[21:28] <shadeslayer> soee_: can you run apt-cache policy muon-updater
[21:30] <soee_> shadeslayer: http://paste.ubuntu.com/7236822/
[21:30] <shadeslayer> soee_: and logging out / in still spams you with notifications about upgrades?
[21:31] <soee_> will chek tomorrow :) now i have some work to do
[21:32] <snele> http://www.ubuntuupdates.org/package/core/trusty/universe/base/muon
[21:32] <shadeslayer> ok
[21:32] <snele> it is in :)
[21:32] <snele> but after these latest updates stuck icon appeared
[21:33] <snele> as I described in mailing list
[21:33] <soee_> yes the icon is there all the time :) 
[21:34] <shadeslayer> ahhhhh
[21:34] <shadeslayer> no, I was talking about the notification spam issue, I too have a icon in my systray which indicates(?) I have an update, but there aren't any
[21:35] <shadeslayer> actually
[21:35] <shadeslayer> :O
[21:35] <ScottK> Fix that one for us.
[21:35] <snele> shadeslayer: yeah that icon
[21:35]  * shadeslayer is out of date at the moment
[21:37] <shadeslayer> will upgrade overnight and check tomorrow
[21:39] <snele> shadeslayer: I described here my findings. hope it helps a little ;) https://lists.ubuntu.com/archives/kubuntu-devel/2014-April/008230.html
[21:47] <ScottK> shadeslayer: We're into final freeze, so please don't wait too long.
[21:47] <ScottK> Maybe apachelogger will return.
[22:10] <vHanda> shadeslayer: if only it was reproducible
[23:08] <valorie> restart on todays updates; so far, so good
[23:27] <valorie> since I've successfully restarted after todays upgrades, I was checking trusty bugs
[23:27] <valorie> $ apt-cache policy ktp-common-internals
[23:27] <valorie> N: Unable to locate package ktp-common-internals
[23:28] <valorie> https://launchpad.net/ubuntu/+source/ktp-common-internals/0.8.0-0ubuntu1 shows all green checks