[12:08] <ogra-cb_> lamont, infinity, could someone take a look at celbalrai ? it seems to be completely dead
[12:08] <cjwatson> 11:16 <ChrisS> cjwatson: Hmm, it's not happy - lots of I/O errors.  I think it may be out of action for a while.
[12:08] <cjwatson> FWIW
[12:08] <cjwatson> (yesterday)
[12:09] <ogra-cb_> oh, well, i thinnk we should replace the HW
[12:09] <ogra-cb_> the last builds that actually produced logs had very weird gzip decompression errors
[12:09] <cjwatson> mm
[12:12] <ogra-cb_> oh, and on a sidenote.... i would REALLY appreciate if some archive admin could let linux-nexus7 out of NEW, it is blocking images building and stuck since nearly a week now (though in the current situation with the builder it might be less pressing)
[12:12] <ogra-cb_> *image
[12:13] <ogra-cb_> i think infinity had agreed to give it a review, but he seemingly didnt get to it
[14:26] <xnox> so glew got reverted, but the britney block is still in place.
[14:27] <seb128> xnox, which is not so much of an issue because the revert is basically the raring version with an extra changelog
[14:27] <xnox> true =)
[14:59] <Laney> oh I see, block doesn't actually take a version
[15:20] <stgraber> I'll be doing a fair bit of code shuffling in a branch of ubuntu-archive-tools and the cdimage branch to rebase all the tools on the "official" qatracker python module and make sure our code supports dealing with multiple trackers (to support the chinese builds).
[15:20] <stgraber> I'll be testing some of the changes directly on nusakan and will trigger a few manual builds
[15:30] <cjwatson> seb128: I've dropped the glew block now, anyway
[15:36] <cjwatson> infinity: Any chance you could have a look over my secure boot stuff in precise-proposed/{NEW,UNAPPROVED}?
[16:56] <infinity> cjwatson: Can do.
[16:57] <infinity> cjwatson: As soon as me three laptops settle down and turn into one again.
[16:57] <ogra-cb> infinity, jani claimed you wanted to look at linux-nexus7 too
[16:57] <ogra-cb> would be helpful to have that in the archive soon
[16:57] <infinity> ogra-cb: Same caveat.  Let me find some coffee or something. ;)
[16:58] <ogra-cb> yeah, well, as long as the live builder is broken its less urgent :)
[16:58] <ogra-cb> celbalrai.buildd still isnt reachable from nusakan, so i guess it will still take a while
[16:59] <infinity> Is IS aware that it's sad?
[16:59] <cjwatson> Yeah, apparently it's producing I/O errors and failing to get past the initramfs.
[16:59] <infinity> Oh, "fun".
[16:59] <cjwatson> ChrisS had a brief look for me yesterday.
[16:59] <cjwatson> Before that it was just randomly corrupting builds.
[17:00] <ogra-cb> well, as i said above it also produced pretty weird gzip errors over the last week or so
[17:00] <infinity> I wonder if it's loose or in the box.
[17:00] <ogra-cb> i would blame memory or disk and suggest to just replace it
[17:00] <infinity> ogra-cb: I'd be more inclined to blame power, actually.
[17:01] <ogra-cb> http://www.embedded.rs/products/ti-omap5430-pico-itx-sbc
[17:01] <ogra-cb> with one of these :)
[17:01] <infinity> I wonder if, going back through history, we'd discover that every one of the weird corruption errors we've seen on Pandas has been on the ones in the PandaBox (which celbalrai is, I just looked), and that PSU just isn't delivering enough power.
[17:01] <ogra-cb> (it claims software compatibility with the panda, i wonder if thats true for kernel and bootloader)
[17:02] <ogra-cb> hmm
[17:02] <infinity> ogra-cb: It's an OMAP5, it can't possibly be compatible at the bootloader and kernel level.
[17:02] <ogra-cb> it started pretty much out of the blue though
[17:03] <ogra-cb> infinity, yeah, thats why i was wondering about that SW compatibility claim
[17:03] <infinity> I suspect they just mean userspace, since not all hobbyist dev boards are A-series cores.
[17:03] <ogra-cb> yeah
[17:03] <infinity> And I'm betting some people have been burned by switching between A and M and realising nothing works.
[17:04] <ogra-cb> well, in any case it looks like a chromebook with sata :)
[17:04] <ogra-cb> though the usb 3.0 is breezing fast on the cb :)
[17:08] <bdmurray> does a regression test for an SRU for bug 938670 seem sufficient to anyone else?
[17:08] <ubot2> Launchpad bug 938670 in Unity Videos Lens "Remote scope should use libsoup" [Undecided,Fix released] https://launchpad.net/bugs/938670
[17:08] <bdmurray> er, bug 936870
[17:08] <ubot2> Launchpad bug 936870 in unattended-upgrades (Ubuntu Precise) "unattended upgrade failing due to incorrectly detected conffile prompt due to "newconffile" line" [Medium,Triaged] https://launchpad.net/bugs/936870
[18:20] <infinity> cjwatson: All accepted.  I goofed the overrides on the NEW stuff, but fixed as of :33
[18:22] <cjwatson> Great, thanks
[18:23] <infinity> cjwatson: I take it we've opted to just hand-wave past the fact that all the -signed stuff probably actually belongs in restricted, not main?
[18:24] <cjwatson> I had a discussion with slangasek about that a while back.  I forget our exact justification.
[18:24] <cjwatson> I think as long as the user can produce a signed version that would fit if they installed their own keys on the firmware, we decided that was good enough for us
[18:25] <infinity> Sure, the source is absolutely free, but the binaries aren't reproducible, which is the icky part.  But I'm not going to be picky about it either.
[18:27] <cjwatson> If we used signed .debs, I wouldn't consider those non-free
[18:27] <cjwatson> e.g. signed with the archive key
[18:27] <cjwatson> shim-signed is skating on the edge a bit, I'll admit
[18:28] <infinity> cjwatson: Yeah, I'm not sure that's quite the same thing, but I can see the extension of the argument.
[18:28] <infinity> cjwatson: More convincing if we can reliably strip the signatures and replace them (can we?)
[18:28] <cjwatson> I believe that's even tested, at least in shim-signed
[18:28] <infinity> Shiny.
[18:28] <cjwatson> sbattach does it
[18:29] <infinity> I thought there were some issues with that not returning one to a pristine unsigned binary, but maybe that was resolved.
[18:29] <cjwatson> AIUI that was the case but was fixed
[20:27] <stgraber> cjwatson: any chance you're still around? :)
[20:28] <stgraber> I submitted https://code.launchpad.net/~stgraber/ubuntu-archive-tools/various-qatracker-improvements/+merge/134192 for inclusion in ubuntu-archive-tools
[20:30] <stgraber> ^ or anyone in ~ubuntu-archive-tools who has a few minutes to review the merge proposal
[20:31] <stgraber> the diff is pretty massive as that's porting all the code to using the upstream python-qatracker module. Rest of the changes are mostly cleaning up, python3 support and a bunch of bugfixes I found while testing
[20:32] <stgraber> the cdimage code will need a couple of matching changes once that one lands but those are trivial and I have commit access :)
[20:53] <stgraber> Note to nusakan users: I merged that branch manually in the copy that's on nusakan so I can land the cdimage bits
[20:53] <stgraber> (running a test now)
[20:57] <slangasek> infinity: even if it doesn't return you to the pristine unsigned binary, it returns a functional equivalent, which is about all we get from package rebuilds anyway (if we're lucky ;)
[20:57] <infinity> slangasek: Yeah, I thought there may have been concerns at one point that it wasn't even quite doing that.
[21:00] <slangasek> ah, nope
[21:13] <bdmurray> looking at ubuntu-dev-tools in the precise-proposed queue there is an undocumented (in the changelog) change to requestbackport
[21:13] <bdmurray> http://launchpadlibrarian.net/122313290/ubuntu-dev-tools_0.141_0.141ubuntu0.1.diff.gz
[21:13] <bdmurray> I'd approve it but wanted a second opinion
[21:14] <bdmurray> infinity, slangasek?
[21:15] <slangasek> doesn't look like a change that needs SRU validation, so yeah, I'd accept as-is
[21:55] <stgraber> and success! we now have the Chinese builds automatically posted on http://localized-iso.qa.ubuntu.com
[21:56] <stgraber> infinity: while playing on nusakan I noticed there's a non-commited change to bin/wait-for-package is that one of yours?
[21:56] <stgraber> I also reverted your release time etc/default-arches change and updated the edubuntu entry for raring while I was at it
[21:57] <infinity> stgraber: Not mine, no.  I've been ruthlessly hunting and committing production changes when I see them.
[23:32] <cjwatson> rejected nexus7-dev-tools at mterry's request
[23:32] <cjwatson> (uploader)


[06:15] <lordievader> Good morning.
[06:26] <ngaio> good morning! Where can I find a list of packages in the current daily image? I'm interested to know if it includes Qt 5.4 and PyQt 5.4, because I'm developing an application using them
[06:30] <lordievader> ngaio: http://cdimage.ubuntu.com/kubuntu/daily-live/20150204/vivid-desktop-amd64.manifest
[06:30] <lordievader> ngaio: It has Qt5.3.2.
[06:31] <lordievader> ngaio: And Python3-PyQt5 5.4
[06:32] <ngaio> my application is with python 3
[06:32] <ngaio> but I guess I will not be able to target any of the Qt 5.4 features
[07:07] <ScottK> ngaio: I think it's likely we'll move to 5.4 before release.
[07:08] <ngaio> ScottK, thanks very much, that's good to know :-)
[07:17] <soee> good morning
[07:40] <sitter> engage disco logging http://people.ubuntu.com/~apachelogger/screencasts/vokoscreen-2015-02-04_08-32-06.mkv
[07:47] <joern> hi everyone
[07:48] <joern> I'm trying to generate LXQt techpreview isos and I'm using SDDM. The problem is that the current configuration of casper/SDDM defaults to plasma.desktop... https://bazaar.launchpad.net/~ubuntu-branches/ubuntu/utopic/casper/utopic/view/head:/scripts/casper-bottom/15autologin
[07:48] <joern> How could this be fixed?
[07:53] <sitter> joern: as seen in line 78 perhaps
[07:54] <joern> that could be an interim solution, but for the future it would be good to have a better solution
[07:55] <joern> as far as I know, there is nothing like a /etc/sddm.conf.d/ folder where I could just drop in a config to override the /etc/sddm.conf?
[07:55] <sitter> joern: nope
[07:55] <sitter> there is a feature request for that though
[07:56] <joern> sounds fine
[07:56] <sitter> https://github.com/sddm/sddm/issues/217
[07:56] <sitter> d_ed: ^ :P
[07:57] <joern> that would be pretty awesome
[07:59] <joern> so I will copy/symlink the .desktop file for vivid, but I hope that a better solution will exist in 15.10 series :D
[08:05] <ovidiu-florin> can someone please fix GRUB in vivid? and let it know we are Kubuntu, and NOT Ubuntu?
[08:05] <ovidiu-florin> or tell me where to fix it myself
[08:06] <valorie> ovidiu-florin: as I understand it, if we change the hard-coding, Bad Stuff ensues
[08:06] <valorie> :(
[08:06] <valorie> I hate seeing that too
[08:07] <ovidiu-florin> where are the settings for this found?
[08:07] <ovidiu-florin> I'd like to take a look
[08:13] <sitter> GRUB_DISTRIBUTOR
[08:14] <sitter> the problem is that the distributor as such is in fact ubuntu, what is needed is a way to override the displayname and only the displayname
[08:15] <sitter> e.g. one of the worst fallouts of changing GRUB_DISTRIBUTOR was that install/update-grub wanted to use the UEFI firmware for the distributor, alas, there is no firmware for kubuntu but only ubuntu
[08:16] <sitter> so really what is needed is a completely different system to say that the name of the installation is XY while leaving the actual distribution type untouched
[08:16] <sitter> anyway, cjwatson is the guy to talk to about this
[08:18] <joern> just another thing: is there a way to get more informations about Ubiquity? ubiquity kde_ui isn't starting, apport doesn't complains about a crash, --debug doesn't make a difference
[08:19] <sitter> joern: /var/log/installer or some such
[08:19] <joern> the only error message after a lot of mount points: "umount: /run/udisks/inhibit-polkit: not mounted
[08:19] <sitter> also --debug possibly only prints to that log file there (or syslog at the most), it certainly doesn't use stderr/stdout
[08:20] <ovidiu-florin> sitter: this guy? http://en.wikipedia.org/wiki/C._J._Watson
[08:20] <joern> there is not even a log file :-/
[08:20] <sitter> ovidiu-florin: yes :P...
[08:20] <sitter> ovidiu-florin: he idles in #ubuntu-devel
[08:20] <joern> ah okay
[08:59] <Riddell> morning
[09:05] <ovidiu-florin> Morning
[09:12] <Riddell> whee I'm famous http://www.mylinuxrig.com/post/109989807768/the-linux-setup-jonathan-riddell-kubuntu
[09:13] <Riddell> answered that about 4 months ago
[09:41] <sitter> Launchpad encountered an error during the following operation: copying a package.  qtwebkit-opensource-src 5.4.0-0ubuntu1~utopic1~ppa10 in utopic (qtwebkit-opensource-src_5.4.0.orig.tar.xz already exists in destination archive with different contents.)
[09:57] <claydoh> will there be 4.14.3  (or 14.12 if  that is even possibe?) for Utopic?
[09:59] <Riddell> 14.12 is nearly there needs someone to finish it off, it's in kubuntu-ppa/next-staging (I think)
[09:59] <Riddell> but that's for utopic-next users
[09:59] <Riddell> sitter said it should be split for utopic plasma 4 users
[09:59] <Riddell> alas I'm currently busy on another project so don't have much time
[10:00] <Riddell> Mirv, mitya57: is there an packaging for qtwebengine or is that todo?
[10:01] <Mirv> Riddell: I think no-one is working on that, lisandro mentioned (if I recall correctly) a huge amount of bundled libraries et cetera that would need work and he wouldn't be doing it. so packaging for it welcome to Debian.
[10:03] <Riddell> thanks Mirv
[10:04] <sitter> Riddell: wrt to stage guessing ... I propose that we move forward with 3 named stages stage-frameworks stage-plasma stage-apps
[10:14] <Riddell> sitter: that shoulds nicer, but somehow I don't think we should spend too long setting it up since it'll all be unnecessary for vivid
[10:24] <claydoh> Riddell: thanks!
[10:34] <sitter> Riddell: we'll be staging for vivid
[10:36] <lordievader> Hey Riddell, ovidiu-florin. How are you guys?
[10:36] <ovidiu-florin> wet
[10:36] <ovidiu-florin> I got a flat shoe
[10:36] <ovidiu-florin> and it's raining
[10:37] <Riddell> sitter: but we can go back to the normal staging ppa for that, no need to have next ppas
[10:38] <Riddell> hi lordievader, get back ok?
[10:38] <Riddell> "He’s also the least fiddle-y KDE user I’ve ever interviewed." I wonder what that means http://www.mylinuxrig.com/post/109989807768/the-linux-setup-jonathan-riddell-kubuntu
[10:38] <ovidiu-florin> Riddell: that you only use Konsole
[10:38] <sitter> Riddell: no we can't because we still might be staging apps and frameworks and plasma all at the same time with different target destinations
[10:38] <ovidiu-florin> and don't over customize your KDE
[10:39] <sitter> the benefit of having multiple stages is that we can a) control the dependencies more tightly, e.g. build against archive frameworks rather than whatever we are staging at the same time b) copy everything from a stage to the destination even when the destinations are different
[10:39] <lordievader> Riddell: I did. FOSDEM was very nice :)
[10:40] <lordievader> ovidiu-florin: Rain ain't good.
[10:40] <ovidiu-florin> lordievader: we didn't take a picture together :(
[10:41]  * Riddell blogs http://wire.kubuntu.org/?p=210
[10:41]  * sitter whines about qtwebkit building forever and ever
[10:41] <lordievader> ovidiu-florin: True, next year better?
[10:42] <sitter> or ya know, akademy
[11:26] <ovidiu-florin> sitter: are you comming to Akademy?
[11:27] <sitter> https://www.youtube.com/watch?v=MnoJdK8cmwQ
[11:29] <sitter> svn info   0.000000   0.000000   0.050000 (  1.391895)
[11:29] <sitter> svn up   0.000000   0.010000   0.060000 (  1.670043)
[11:29] <sitter> ..
[11:29] <ovidiu-florin> sbivol_: are you around?
[11:29] <sitter> Riddell: releaseme caching is gonna be a major pain in the bum
[11:29] <ovidiu-florin> sitter: are you using KMail?
[11:29] <sitter> no
[11:30] <sitter> haven't used it since the 4.x port
[11:47] <Riddell> sitter: d_ed wonders if you can turn on the apt settings that allows file overwrites when using kubuntu-ci, it's what we do for release-upgrades, and kubuntu-ci is going to have file overlaps by design
[11:52] <sitter> I dont think you can turn it on per apt origin, so we'd have to enable it globally which seems a bit meh
[11:52] <sitter> on a related note we'd then have to explicitly disable it again as part of the overwrite checks xD
[11:52] <sitter> anyway, overwrites should not happen in daily or weekly
[11:52] <sitter> if they do that's a bug that needs sorting in the packaging anyway
[11:58] <Riddell> sitter: he just found some
[12:01] <sitter> Riddell: reportttttttttt
[12:03] <Riddell> sitter: where?
[12:04] <sitter> there is a flaw in the current way things work though, say an overwrite arises from 1git1  to 1git2 where git is master and in fact tracking 2 not 1, so the relationship at the time of the conflict is <<1git2, now if there is a tarball release 1.1 that'd be greater than 1git1 but still carry the conflict rendering the relationship pointless as now the relationship would need to be << 1.1gitN which we can't represent
[12:04] <sitter> Riddell: in here, or the list or somewhere
[12:09] <Riddell> sitter: https://paste.kde.org/pu3z7pmmu
[12:09] <Riddell> sitter: https://paste.kde.org/pbgwvndkq
[12:10] <sitter> ah yes
[12:10] <sitter> Riddell: those need legitimate force overwrites
[12:10] <sitter> fallout from buggy packaging
[12:12] <Riddell> tsk, silly packagers
[12:12] <sitter> all ur fault anyway
[12:16] <Riddell> kfunk: ScottK: I verified the fixes for bug 1415451 now it needs someone to move it to -release
[12:17] <Riddell> kfunk_: ↑
[12:19] <kfunk_> uhm, wut?
[12:19] <kfunk_> was disconnected the last minutes
[12:22] <kfunk> Riddell: ^ -- what do you want to show me? :)
[12:25] <yofel> kfunk: [13:16:42] <Riddell> kfunk: ScottK: I verified the fixes for bug 1415451 now it needs someone to move it to -release
[12:25] <kfunk> awsm
[13:00] <BluesKaj> Hiyas all
[13:04] <sgclark> hiyas
[13:04] <BluesKaj> hi sgclark,  what's up today?
[13:07] <sgclark> not much
[13:07] <lordievader> Hey sgclark, how are you doing?
[13:08] <BluesKaj> looking at installing 15.04 on this old desktop, but I think I'll wait til the VDs and activity problems are fixed
[13:09] <sgclark> hi lordievader, doing ok, yourself?
[13:10] <lordievader> sgclark: Okayish, having some problems with Plasma5 + an ancient nvidia chip.
[13:10] <sgclark> hehe I have been having issues with plasma5 and a newer nvidia chip
[13:11]  * sgclark curses at nvidia
[13:11]  * lordievader curses nvidia too
[13:12] <soee> sgclark: nvidia-prime does not work at all atm if you have optimus :)
[13:12] <soee> im on default intel gpu liek a month now i think
[13:13] <lordievader> Intel GPU's are lovely. sure they don't pack any real power but they do ~allways work.
[13:13] <sgclark> I am using nvidia but I can no longer live on the edge. booting to black screens on production machine is not good :(
[13:14] <lordievader> With the Nvidia driver I get a black screen + mouse cursor.
[13:14] <santa_> hi all
[13:14] <sgclark> yeah
[13:14] <lordievader> Luckily it ain't my "work" machine.
[13:14] <santa_> Riddell: no libnm release in plasma 5.2.0
[13:14] <santa_> ?
[13:17] <Riddell> santa_: it's moved to frameworks#
[13:17] <BluesKaj> this old and 2 core with 6G ram and nvidia 8400gs pcie runs very nicely on 14.10 and plasma 4 , on second thought, why do i want to muck that up ? :)
[13:17] <Riddell> now called networkmanager-qt
[13:17] <BluesKaj> and=amd
[13:17] <santa_> Riddell: ah, thanks
[13:19] <lordievader> BluesKaj: Because plasma5 is new and fancy. And you want to test it out and find bugs to improve the KDE software?
[13:20] <BluesKaj> lordievader, I'm already testing 15.04 on yje laptop
[13:20] <BluesKaj> the
[13:23] <Riddell> you know it's 10 years since kubuntu started, I can't help but feel we should do something to mark it, like a series of interviews or a history story or something
[13:24] <lordievader> Riddell: Nice interview (the hacker public radio one) :)
[13:25] <sgclark> Riddell: wow nice
[13:25] <Riddell> oh thanks, I still need to work on my public speaking, I'm too fast and not pronounced enough
[13:26] <lordievader> Is it mentioned on the website?
[13:26] <Riddell> is what mentioned on what website?
[13:26] <lordievader> The 10 year birthday of Kubuntu.
[13:27] <sitter> Riddell: svn caching ... we could maintain a cache that is linked through svn (i.e. recursive checkout): this has the advantage of only needing to do one svn up in any run of tarme (and some random repo queries), it does have the disadvantage that the initial cache needs to be created sequetially which takes about 10 seconds per language for kde/workspace so that's somewhere around 20 minutes for the initial cache run (no time stats on updates yet)
[13:28] <Riddell> sitter: it currently takes 3-4 hours to run the plasma release script so 20 minutes if it saves a couple of hours off that is super
[13:29] <Riddell> lordievader: nope, I've not throught of any way to mark it
[13:29] <lordievader> Some kind of a banner?
[13:30] <lordievader> Perhaps ahoneybun can design something nice.
[13:30] <Riddell> artist skills
[13:30] <sitter> Riddell: the other option is to have the cache directories not linked (i.e. maintain them as invididual checkouts per language): this has the advtange of being able to massively thread the initial cache generation, disadvantage being that we'd need multiple svn ups. one svn up takes apparently somewhere between 1 second and 2 seconds (just the query) so all in all that'd be some 2 minutes spent svn upping for each run of tarme, initial caching is
[13:30] <sitter> pretty much as fast as the network IO is as we'd simply checkout on some >=5 threads at the same time such that the query slowness of svn doesn't matter anymore
[13:30] <sitter> oh, actually, on second thought we'd also thread the svn ups
[13:30] <sitter> totally hadn't thought of that
[13:30] <sitter> so I think that option actually might be better
[13:31] <sitter> it reenforces my point though that the plasma meta script should be written in ruby and used as a highlevel replacement for tarme rather than ontop of tarme
[13:32] <sitter> that way one run of the plasma meta script will do the massively threaded svn up, instead of having it done once per tarme call, of which there appear to be a few
[13:33] <Riddell> could you make a python library to access tarme please
[13:33] <sitter> you really don't want to be happy do you? :P
[13:34] <sitter> anyway, as I was saying in my mail it might be very much a possibility to not have you write anything in the script because what your script does is call tarme with different arguments
[13:34] <sitter> one could just as well define a config format for that
[13:35] <Riddell> it also does some stuff like remove unnecessary tars
[13:35] <Riddell> so it would need the right arguments to be available
[13:35] <sitter> so you'd have a config somewhere that goes... release kde/workspace from trunk && release frameworks/kittens from trunk && release kde/playground/jellyfish from stable
[13:36] <sitter> Riddell: where does it meddle with tars?
[13:36] <sitter> the script is just one giant hack on insufficient feature backing, that's all :P
[13:36] <sitter> it's an abomination before god, that's what it is
[13:37] <Riddell> rm kwindowsaddons* -rf
[13:37] <Riddell> sed -i '/kwindowsaddons/d' $VERSION-release-data
[13:37] <Riddell> it just asks for kde/workspace then it removes kwindowsaddons cos we don't want it, and it removes baloo cos it has a different version number
[13:37] <sitter> ah
[13:37] <sitter> well
[13:37] <Riddell> I agree with you
[13:37] <sitter> without any code one could do the opposite :P
[13:37] <sitter> but yeah, excluding things also sounds like a sensible thing
[13:38] <Riddell> it just needs the arguments to be able to do all that
[13:38] <sitter> yeah, that's cheap though
[13:38] <sitter> svn based releases also work with the stuff I landed 2 weeks ago btw
[13:38] <sitter> needs manual config definition though
[13:38] <Riddell> and then god will be happy and can go and care about more useful things like sorting out those waring religions
[13:39] <sitter> http://paste.ubuntu.com/10053648/
[13:39] <sitter> not quite sure about the DSL, but that's the general concept anyway
[13:43] <Riddell> lovely
[13:49] <soee> Riddell: any info about 14.12.2 apps ?
[13:49] <soee> *for vivid
[13:50] <Riddell> soee: sorry I'm too busy to make packages currently, it'll need someone else to step up for them
[13:51] <soee> Riddell: ok, thanks
[13:51] <soee> BluesKaj: ping
[13:52] <santa_> Riddell: hm, just another simple question: if I want to offer you my siduction specific changes (if any is interesting) whats's the better branch to make my packages kubuntu_unstable or kubuntu_vivid_archive?
[13:55] <BluesKaj> soee, pong
[13:56] <soee> BluesKaj: can you confirm that in current Plasma 5 in Vivid, notifications show up liek ~250px from bottom of the screen not like before in lower right corner ?
[13:58] <Riddell> santa_: I guess it depends if the change is for released software or master branches, kubuntu_vivid_archive is probably best in general
[13:58] <BluesKaj> soee, hang on, need boot the laptop
[14:01] <santa_> Riddell: released software, so kubuntu_vivid_archive? if see my change is already included in kubuntu_unstable, should I refrain to send you back my changes?
[14:03] <BluesKaj> soee, , notifications here show a large dialog box on the lower right that is quite readable , if that's what you mean
[14:04] <soee> BluesKaj: im not usre why but for bye they are on the right side (screen edge) but not newar bottom edge but moved to top like 250px
[14:05] <Riddell> santa_: if they're needed for the stable software then I guess you can still give us the patch or tell us to merge it from kubuntu_unstable
[14:06] <sitter> s/merge/cherry-pick
[14:07] <santa_> great, I will do another rebuild and try to send you back the changes if I have time
[14:08] <BluesKaj> soee, could be a difference in gpu behaviours , mine's an intel 4000 with i915 driver on a laptop
[14:08] <soee> strange
[14:09] <santa_> another thing, could any of you log into alioth and symlink the libnm-qt repository?
[14:10] <santa_> ...so it would be available in git://anonscm.debian.org/pkg-kde/frameworks/libnm-qt.git
[14:10] <shadeslayer> is libnm-qt a framework?
[14:10] <shadeslayer> huh, I guess
[14:11] <shadeslayer> sitter: halp http://dci.pangea.pub/job/plasma/job/kservice_source_unstable/8/console
[14:12] <sitter> santa_: it's not called libnm-qt
[14:12] <sitter> shadeslayer: 01:02:57 patch: **** Can't rename file src/kbuildsycoca/CMakeLists.txt to .pc/kubuntu_rename-application-menu-file.diff/src/kbuildsycoca/CMakeLists.txt : Operation not permitted
[14:12] <shadeslayer> yus
[14:13] <shadeslayer> dafuq is that
[14:14] <shadeslayer> oh
[14:14] <shadeslayer> ohh
[14:14] <shadeslayer> I think I know
[14:14] <shadeslayer> stupid schroot fstab probably
[14:15] <santa_> sitter: oh, I see, thanks
[14:21] <shadeslayer> sitter:  14:20:25 up 96 days, 22:33,  1 user,  load average: 0.48, 0.60, 0.68 :D
[14:21] <shadeslayer> but I had to reboot the bugger
[14:21] <sitter> Riddell: ../tarme.rb --origin stable --version 1 kde/workspace/plasma-desktop  22,92s user 2,99s system 44% cpu 57,663 total
[14:22] <sitter> shadeslayer: there's been like 300 security updates in that time frame :O
[14:22] <shadeslayer> probably
[14:22] <shadeslayer> I just never bothered rebooting it
[14:22] <shadeslayer> but now I have
[14:24]  * sitter throttles bandwith
[14:26] <sitter> you know, I should have threaded l10n sooner, even without cache it's like 300 times faster
[14:26] <sitter> shadeslayer: u my hero for suggesting that
[14:26] <shadeslayer> :3
[14:27] <shadeslayer> out of curiosity, how is it faster with GIL in place? or are you using something else
[14:27] <sitter> Riddell: for comparision this is at 400kib/s without cache ../tarme.rb --origin stable --version 1 kde/workspace/plasma-desktop  36,66s user 15,99s system 25% cpu 3:28,41 total
[14:28] <sitter> shadeslayer: svn is forked anyway
[14:28] <sitter> all the threading does is allow for 5 concurrent svn checkouts
[14:28] <sitter> well, svn info/ svn ls / svn checkout / svn update
[14:28] <sitter> and the establishing of svn connections is the costly thing
[14:29] <sitter> any of those without content transfer takes between 1 and 2 seconds on my system
[14:29] <shadeslayer> sitter: wait so, when you thread svn info and svn ls , it establishes 2 parallel connections running at the same time?
[14:29] <sitter> theres' 108 languages, so even if there were just svn ups and nothing else that'd be some 2 minutes doing sequential update calls
[14:29] <santa_> no kubuntu_vivid_archive branch for kpackage
[14:29] <shadeslayer> wait, no, that's obvious
[14:29] <sitter> shadeslayer: yes, well, see backlog
[14:30] <shadeslayer> ok
[14:30] <shadeslayer> will do
[14:30] <sitter> that of course only works if the actual cache artifacts are unconnected
[14:30] <sitter> i.e. not part of the same checkout
[14:30] <sitter> otherwise svn would lock the repo preventing you from threading access
[14:30] <shadeslayer> mmm
[14:31] <santa_> ugh, nevermind
[14:44] <BluesKaj_> ok , installing 15.05 on a partition beside 14.10 on the old desktop, now we'll see if there are any nvidia probs after reboot...in about 10mins
[14:45] <BluesKaj_> err 15.04...never get used to this laptop KB , it's offset somehow
[14:46] <lordievader> BluesKaj_: Good luck ;)
[14:46] <BluesKaj_> when I'm using the desktop it's wireless KB that sits in my lap
[14:47] <BluesKaj_> oh my finished installing already , that was quick
[14:47] <ovidiu-florin> Kdevelop 4.7.1 was released 2 days ago. I don't see it in https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/next-backports/+packages?field.name_filter=kdevelop&field.status_filter=&field.series_filter= how does it get added? Manually by a human? or automatic by some bot?
[14:48] <Riddell> ovidiu-florin: it would need to be done manually
[14:48] <Riddell> needs packaged in vivid then backported to kubuntu-ppa/backports (not next-backports, it's not kf5)
[14:49] <ovidiu-florin> Riddell: packaged and uploaded manually? or just click on something that makes it available there?
[14:49] <BluesKaj_> that's something new, the installer asked for my password before continuing/finishing the installation
[14:52] <Riddell> ovidiu-florin: packaged and uploaded manually
[14:52] <Riddell> ovidiu-florin: it's not part of kubuntu ci (which is only for kf5 stuff)
[14:53] <Riddell> BluesKaj_: oh? what are you installing?
[14:53] <ovidiu-florin> is there a wiki page on Kubuntu CI?
[14:53] <ovidiu-florin> Riddell: ^
[14:53] <ovidiu-florin> on/about*
[14:54] <Riddell> I don't think so, it's all in harald's head
[14:57] <BluesKaj_> Riddell, 15.04 on my old desktop from last wednesday's daily image
[14:58] <BluesKaj_> and I have a desktop ...now to configure everything
[14:58] <BluesKaj_> bbl
[16:21] <BluesKaj> ok , 15.04 on the desktop, so far so good
[16:21] <Riddell> yay
[16:21] <Riddell> assuming you managed to unlock it during the install :)
[16:23] <BluesKaj> Riddell:  is that why it asked for my pwd?
[16:24] <BluesKaj> ubiquity that is
[16:24] <Riddell> BluesKaj: maybe, was it a full screen request?
[16:24] <BluesKaj> yes
[16:25] <BluesKaj> iirc :)
[16:28] <Riddell> that'll be it then
[16:28] <Riddell> simple to fix just needs someone to add the settings to kubuntu-settings
[17:18] <sgclark> Riddell: I am working on the kdepim items now.. What else needs to be done?
[17:28] <Riddell> sgclark: kdelibs
[17:28] <Riddell> and kde-runtime I think
[17:29] <Riddell> all the same as kdepim
[17:29] <Riddell> new versions with kde applications
[17:29] <sgclark> ok
[17:29] <Riddell> thanks :)
[18:07] <BluesKaj> would be nice if the theme/colour downloader was fixed in system settings
[18:09] <_Groo_> Riddell: can you test if you cna change date/time in systemsettings _> locale > date/time?
[18:09] <_Groo_> Riddell: it hangs on ci
[18:09] <_Groo_> Riddell: prolly something to do with systemd
[18:10] <_Groo_> Riddell: or a packaging error
[18:15] <Riddell> polkit more like
[18:17] <Riddell> _Groo_: yes I can change the date fine
[18:17] <_Groo_> Riddell: does it ask for a password?
[18:18] <Riddell> nope
[18:18] <_Groo_> humpf...
[18:19] <_Groo_> here is just freezes solid after i click apply
[18:19] <_Groo_> i enable ntp just to test and it freezes
[18:19] <_Groo_> can you try that?
[18:22] <_Groo_> kcmshell5 clock
[18:22] <_Groo_> its broken in ci
[18:22] <_Groo_> cant change the date/time or enable/disable ntp, it just freezes till i kill it
[18:23] <Riddell> kcmshell5 clock works for me
[18:24] <_Groo_> vivid?
[18:25] <Riddell> yep
[18:26] <_Groo_> might be one of those bugs that go away once you upgrade
[18:26] <_Groo_> i cant debug whats wrong :(
[18:27] <Riddell> you could also check if all the polkit packages are instaled
[18:27] <Riddell> https://paste.kde.org/pyf4cg3xq
[18:28] <_Groo_> https://paste.kde.org/p6cudzfwv/j55vat
[18:37] <_Groo_> it works with unity-control-center
[18:37] <_Groo_> so something in kf5 just hangs
[18:37] <_Groo_> oh well
[19:19] <_Groo_> Riddell: ping
[19:19] <_Groo_> https://www.irccloud.com/pastebin/CdfbUJly
[19:20] <_Groo_> Riddell: do you get this ^ in vivid if you run it through krunner?