[07:42] <ShalokShalom> Topic Link (Kubuntu 5 Test ISO http://goo.gl/nn2Zej ) Is dead
[07:42] <ShalokShalom> I want to become a tester for 12.04.5 with 4.14 from backports. :)
[07:44] <valorie> ShalokShalom: I suggest joining #kubuntu-devel or at least the kubuntu-devel mail list
[07:44] <valorie> and make your interest known in either/both
[07:44] <ShalokShalom> this is kubuntu-devel ?
[07:45] <valorie> oh sheesh
[07:45] <ShalokShalom> :)
[07:45]  * valorie blushes
[07:45] <lordievader> valorie: ;)
[07:45] <ShalokShalom> you are the girl from g plus ?
[07:45] <valorie> you're right about that link
[07:45] <valorie> the girl?
[07:45] <ShalokShalom> ok, so no
[07:45]  * valorie is female for sure, but it's been a long time since i was a girl
[07:45] <ShalokShalom> there is a hacker girl from kubuntu on g plus, with a similar nick
[07:46] <ShalokShalom> ah, ok
[07:46] <ShalokShalom> my english is buggy
[07:46] <ShalokShalom> i mean female/woman ofc
[07:46] <lordievader> ShalokShalom: Perhaps you are thinking of sgclark.
[07:47] <valorie> I am the only Valorie on g+, I just checked
[07:47] <valorie> didn't know I had fame there
[07:47] <valorie> lol
[07:48] <ShalokShalom> since most genius person, which i ever meet in the open source scene, is a she, i put more attention on females :P
[07:50] <valorie> the only kernel devel I know is female
[07:52] <ShalokShalom> ah
[07:53] <ShalokShalom> i mean anke/demm, who creates KaOS
[07:56] <valorie> anke -- I think she used to come into the linuxchix chan
[07:56] <valorie> years ago
[07:56] <valorie> loads of people there, all smarter than me
[07:57] <ShalokShalom> :)
[07:58] <ShalokShalom> valorie: we write about wayland 
[08:02] <Riddell> hi ShalokShalom 
[08:02] <ShalokShalom> hi
[08:03] <Riddell> ShalokShalom: I'm not doing backports of 4.14 on Kubuntu 12.04, we only backport to the latest LTS
[08:04] <ShalokShalom> yes, i see, 4.13.2 is ready, yes ? :)
[08:05] <ShalokShalom> http://www.kubuntu.org/news/kde-sc-4.13.2
[08:05] <Riddell> ShalokShalom: yep
[08:06] <ShalokShalom> ok, so i want to test that :P
[08:06] <ShalokShalom> what is important ?
[08:13] <Riddell> in testing 4.13?  test baloo file search and kontact, they're the two most flakey bits
[08:13] <ShalokShalom> ok
[08:14] <ShalokShalom> baloo work ever fine to me
[08:14] <ShalokShalom> kontact was buggy, since i know it 
[08:33] <soee> Riddell: maybe it would be a good idea to have some page for people that want to test for example KDE SC with some steps they should do/check so if someone shows up here ready to do test, we can 
[08:34] <soee> give him such link and he would know what to do, also it would be a good idea to allow comments for testers on such page so they can tell what is good/wrong etc
[08:37] <Riddell> soee: good idea, go ahead :)
[08:40] <valorie> woah, our /topic has shrunk
[08:41] <Riddell> lots of things todo in https://trello.com/kubuntu :)
[08:47] <ShalokShalom> soee: thats exactly, what i search, yes. :)
[08:47] <ShalokShalom> a step by step guide
[09:06] <soee> Riddell: ill try to f
[09:06] <soee> *prepare something
[09:07] <soee> ShalokShalom: where did you get info that testers are needed ?
[09:07] <soee> some social media, other user or ?
[09:07] <ShalokShalom> valorie told me that
[09:08] <soee> ah the girl :D
[09:08] <ShalokShalom> yep
[09:08] <ShalokShalom> :P
[09:08] <valorie> pfff
[09:08] <ShalokShalom> haha
[09:09] <ShalokShalom> by the way: does anyone have saved the deb`s of remastersys or the black lab imager ?
[09:09] <ShalokShalom> both go offline
[09:09] <ShalokShalom> or the source ?
[09:10] <ShalokShalom> valorie: we all have a children in us, please take it as a compliment ;)
[09:11] <valorie> it is not respectful to women to call them girls
[09:11] <valorie> yes, I do have a child in me though, for sure
[09:12] <ShalokShalom> it was a language spellinh mistake 
[09:12] <valorie> anyway, need to go to sleep now, it's after 2am here
[09:12] <valorie> niters
[09:12] <ShalokShalom> ok, gn8
[09:13] <valorie> have fun testing
[10:00] <Riddell> "Arthur Schiwon (blizzz) renewed their own membership in the Kubuntu Members (kubuntu-members) team" yay Blizzz still loves us!
[10:08] <Blizzz> always! have a place in my heart, yo ;)
[10:12] <Riddell> :)  but will you still when I remove all the owncloud blogs from planet as I've been asked to, that would show true love
[10:41] <apachelogger> yofel: whatever is going to happen to frameworks packaging in git?
[10:42] <yofel> got distracted by me being on vacation and raphael's git packaging layout thread on debian-devel a bit
[10:43] <yofel> how would we go about repositories owned by different teams btw.?
[10:43] <apachelogger> yofel: push rights is per team?
[10:44] <yofel> pretty much from what I see on git.debian.org
[10:45] <apachelogger> gives me a headache
[10:45] <apachelogger> yofel: well, either we get add to the team or the repo moves to pkg-kde I'd say
[10:45] <Riddell> surely kubuntu and debian would have to be the same team for it to make any sense?
[10:46] <apachelogger> Riddell: pkg-kde would not have push rights to debian-mm so we couldn't fiddle with qtmultimedia for example
[10:46] <yofel> just mentioning it as AFAIK ScottK said something about putting kapidox in the python team
[10:46] <apachelogger> (assming that is maintained by debian-mm)
[10:46] <apachelogger> Oo
[10:46] <apachelogger> kapidox in python sounds peculiar
[10:46] <yofel> [06:40:45] <ScottK> shadeslayer: kapidox is, from a packaging perspective, a python app, so putting it in the python apps team made more sense.
[10:47] <yofel> you might want to read #debian-qt-kde every now and then, you're even there :P
[10:47] <shadeslayer> ^^
[10:47] <shadeslayer> hurray
[10:47] <apachelogger> I am not at workstation
[10:47] <shadeslayer> I fixed pkg-kde-tools
[10:48] <shadeslayer> no more patching ECM
[10:48] <yofel> shadeslayer++
[10:48] <shadeslayer> though pkg-kde-tools has a shitty workaround for setting ECM__MKSPECS_INSTALL_DIR
[10:49] <shadeslayer> https://github.com/shadeslayer/pkg-kde-tools/commit/2a4175ffa8bdad6c77db56e8553e49d56c8cd983
[10:51] <apachelogger> Oo
[10:51] <yofel> shadeslayer: is github seriously the best way to do feature work on debian branches? :/
[10:51] <yofel> well, $external_git_repo_management
[10:52] <shadeslayer> nope, but it was the easiest :(
[10:52] <yofel> bummer
[10:52] <shadeslayer> yeah, I'll try to figure out alioth on the weekend
[10:52]  * shadeslayer retries tier 1
[10:53] <shadeslayer> I like Quintasan's comment on the ML
[10:53] <shadeslayer> so much time invested in neon
[10:54] <shadeslayer> ;_;
[10:54] <yofel> well, without neon I think we wouldn't be having the CP talk in the first place
[10:54] <yofel> we'll still have the memories :P
[10:56] <shadeslayer> ^^
[10:56] <apachelogger> https://code.launchpad.net/kubuntu-packaging-unstable
[10:57] <apachelogger> FWIW BTW, if github's group management wasn't pretty mental I'd totally support moving our packaging to github should we encounter problems with the move to alioth :P
[10:57] <yofel> shouldn't we - at that point - ask upstream whether we can move there?
[10:58] <shadeslayer> ^^
[10:58] <apachelogger> using another remote (debian) is just as nice as having one repo with many branches, only disadvantage being that the initial setup is more of a pain in the bum
[10:58] <shadeslayer> hurray
[10:58] <shadeslayer> things seem to be building
[10:58] <apachelogger> yofel: upstream has global push rights
[10:58] <shadeslayer> I am awesome
[10:58] <shadeslayer> I conquered perl
[10:58] <shadeslayer> only took me 3 days
[10:59] <apachelogger> and I for one would not be comfortable backing push applications from any random packager considering they can then also accidentially break every kde repo in existance
[10:59] <yofel> doesn't gentoo have their stuff upstream?
[10:59] <apachelogger> nope
[10:59] <shadeslayer> there's also the small issue of team thingies in Launchpad
[11:00] <apachelogger> shadeslayer: what's that?
[11:00] <shadeslayer> so everyone in ubuntu-dev can push things in LP
[11:00] <yofel> what was that emege stuff in kdesupport then?
[11:00] <yofel> *emerge
[11:00] <apachelogger> shadeslayer: marginally uninteresting to be honest :P
[11:00] <shadeslayer> but if we move to KDE git / github, you lose that
[11:00] <shadeslayer> apachelogger: I can see people raising hell about it
[11:00] <apachelogger> one could probably even automate auto-archive-sync
[11:01]  * shadeslayer is hungry
[11:01] <apachelogger> shadeslayer: I'll raise hell about launchpad using a shit vcs then
[11:01] <shadeslayer> heh
[11:01] <yofel> I did talk about team permissions with maxy at some point weeks ago, ended without conclusion
[11:02] <yofel> Riddell: what's up with the minimalistic topic btw.?
[11:03] <Riddell> yofel: I just took out the link to 4.14 (cos it's out) and plasma 5 ISOs (cos they moved)
[11:04] <yofel> hm, ok
[11:04] <apachelogger> that is not true, you also removed the octopii
[11:04] <Riddell> well yes, that joke was getting old
[11:04] <yofel> it was ^^
[11:05] <apachelogger> u just don't appreciate the awesomeness of the octopus 
[11:05] <Riddell> oh when you do SUP Yoga among muchos medusas you learn there are many awesome things in the sea
[11:05] <apachelogger> https://www.youtube.com/watch?v=4Lp5a-r3MJU
[11:08] <Blizzz> Riddell: even removing ownCloud blogs from Planet KDE (this you mean?) will not affecting my love. Though I do not know why they should be removed. But i also heard Qt stuff was about to be removed, no?
[11:14] <shadeslayer> apachelogger: ping
[11:14] <shadeslayer> apachelogger: do we want the l10n stuff for KF5 and friends?
[11:14] <shadeslayer> in pkg-kde-tools
[11:16] <apachelogger> shadeslayer: the l10n stuff?
[11:16] <apachelogger> shadeslayer: extraction you mean?
[11:16] <shadeslayer> the l10n stuff
[11:16] <shadeslayer> yes
[11:16] <apachelogger> yeah, we need that :P
[11:18] <shadeslayer> why?
[11:18] <apachelogger> https://www.youtube.com/watch?v=baBJdKHw-zQ
[11:18] <apachelogger> shadeslayer: for our software
[11:18] <shadeslayer> hm
[11:19] <shadeslayer> ok
[11:19] <Riddell> Blizzz: owncloud isn't part of KDE any more so it's been suggested I should remove people who only blog about owncloud and not KDE
[11:19] <shadeslayer> I'll port it over then
[11:19] <Riddell> Blizzz: the Qt news blog isn't on planet kde
[11:22] <Blizzz> Riddell: I believe the woboq guys are/were on Planet KDE and were mostly blogging about Qt
[11:22] <Blizzz> but maybe my memory just mixes things up
[11:23] <Riddell> Blizzz: hmm, maybe I should zap them down too
[11:24] <Blizzz> mh…
[11:26] <Riddell> and blame it on you :)
[11:28] <Blizzz> such a conspiracy
[11:44] <sgclark> Riddell: seems I can no longer build anything, every package gives me http://paste.ubuntu.com/8105612/
[11:44] <yofel> shadeslayer: ^
[12:08] <BluesKaj> Hiyas all
[12:17] <shadeslayer> sgclark: sorry
[12:17] <shadeslayer> just a moment
[12:20] <shadeslayer> sgclark: fixed
[12:20] <shadeslayer> debs should be published in ~30 minutes
[12:21] <sgclark> what was it?
[12:21] <shadeslayer> I'm working on fixing pkg-kde-tools
[12:21] <shadeslayer> porting it to KF5
[12:21] <shadeslayer> I forgot to disable policy checks for the old scripts
[12:21] <sgclark> ok, thanks
[12:22] <yofel> you'll have to make that accept kubuntu dev too, as not all our new package have the debian team as orig maint.
[12:22] <yofel> *packages
[12:22] <shadeslayer> yofel: I just remove the check
[12:22] <shadeslayer> it's useless for us
[12:22] <yofel> that'll work too :)
[12:22] <shadeslayer> http://paste.ubuntu.com/8105819/
[12:23] <shadeslayer> ok, ki18n failed
[12:24] <shadeslayer> hm
[12:25] <shadeslayer> usr/qt5/imports/kf5/ktranscript.so but should be in usr/lib/*/qt5/plugins/kf5/ktranscript.so
[12:25] <shadeslayer> weird
[12:25] <shadeslayer> ah
[12:25] <shadeslayer> stupid me
[12:27] <shadeslayer> https://github.com/shadeslayer/pkg-kde-tools/commit/981e3381f2d118a0bab14d3d8649ef7d4d1f9bc3
[12:27] <shadeslayer> :p
[12:32] <shadeslayer> yofel: stupid sed/regex question
[12:32] <yofel> that doesn't exist :P
[12:32] <shadeslayer> heh
[12:33] <shadeslayer> I want to match pkg-kde-tools*, and replace it by pkg-kde-tools (>= 0.15.15)
[12:35] <mcstr__> anyone here got a bit of experience with yad?
[12:35] <yofel> shadeslayer: I'm not sure if sed can do that reliably... at least I don't think it has a non-greedy version of *
[12:35] <shadeslayer> what's yad 0.o
[12:35] <shadeslayer> yofel: hm
[12:36] <mcstr__> shadeslayer yad = yet another dialog program
[12:36] <mcstr__> it's supposed to create easy dialogues with checkboxes, buttons, etc. 
[12:36] <yofel> shadeslayer: I'm pretty sure you can do a perl one-liner though if you really need it short
[12:36] <shadeslayer> heh
[12:36] <shadeslayer> yofel: well
[12:36] <shadeslayer> fortunately all pkg-kde-tools build deps are unversioned
[12:36] <shadeslayer> so meh
[12:37] <shadeslayer> lucky me
[12:39] <shadeslayer> tier 1 being pushed now
[12:40] <yofel> I had the same problem with kubuntu-initial-upload, which is why it ended up having a weird regex for that
[12:40] <Riddell> apachelogger: hmm you think upstream me should make daily tars for Plasma?
[12:40] <yofel> python does have non-greedy patterns though
[12:40] <yofel> shadeslayer: where do you need that?
[12:41] <shadeslayer> yofel: all pkg-kde-tools need to have a versioned build depends now
[12:41] <shadeslayer> since I switched to using the 3rd iteration of the debian-qt-kde scripts
[12:42] <shadeslayer> http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging-next/sonnet/revision/40
[12:42] <yofel> ah, I would probably end up writing that with python (maybe playing around with dep822 or how that was called)
[12:44] <mcstr__> so no one then? :(
[12:44] <shadeslayer> dep822 yep
[12:44] <shadeslayer> yofel: sounds a bit overengineered :p
[12:44]  * yofel only knows about zenity and kdailog, never heard of yad
[12:44] <yofel> shadeslayer: probably ^^
[12:45] <shadeslayer> find . -name control | xargs sed -i 's/pkg-kde-tools/pkg-kde-tools (>= 0.15.15)/'
[12:45] <shadeslayer> worked for me ^^ :p
[12:45] <yofel> now hope that nothing had a version :P
[12:45] <shadeslayer> I checked
[12:45] <yofel> ok, that'll do the job then
[12:45] <shadeslayer> find . -name control | xargs grep pkg-kde-tools  gave me nothing
[14:07] <kdeuser56> shadeslayer: how is the x session started in the kubuntu-plasma5 iso? 
[14:07] <shadeslayer> kdeuser56: sddm -> starts x -> starts sddm-helper -> autologin kicks in -> sddm-helper is killed -> startkde
[14:07] <kdeuser56> shadeslayer: that seems to create problems with some boot options
[14:07] <shadeslayer> casper autologin scripts write the config for autologin in sddm
[14:08] <kdeuser56> shadeslayer: "text" should normally not start x ... but on this iso x is started
[14:08] <kdeuser56> shadeslayer: the ubiquity "noninteractive" boot option does not work ... it simply starts the graphical session
[14:08] <shadeslayer> sigh
[14:09] <shadeslayer> kdeuser56: does it work on the kde 4 iso?
[14:09] <kdeuser56> shadeslayer: yeah
[14:09] <kdeuser56> kubuntu utopic works ... kubuntu-plasma5 utopic does not work
[14:10] <shadeslayer> http://cdimages.ubuntu.com/kubuntu-plasma5/daily-live/current/
[14:10] <shadeslayer> Riddell: ^
[14:21] <apachelogger> Riddell: no, what we discussed in randa entails rolling tars via jenkins
[14:21] <apachelogger> in fact possibly to such an extent that you can obtain the actual release tars via jenkins
[14:25] <Riddell> apachelogger: rolling tars using a different method than the final tars are made from defeats the purpose really, if jenkins gets tarme built into it that would be cool
[14:27] <apachelogger> Riddell: the idea is that jenkins would use tarme :P
[14:28] <apachelogger> one of the ideas behind this is that as a random developer you do not have to bother with fiddling around with the release scripting, but you could get a tar from jenkins and use that as your release tar, and possibly even have a button in jenkins that would tag the rev the tar came from as $version
[14:28] <Riddell> yes that would be most lovely
[14:28] <apachelogger> Alex had all sorts of crazy ideas in his pursuite of making releasing things less complicated
[14:30] <shadeslayer> apachelogger: I don't think they were crazy btw
[14:30] <shadeslayer> because all of this already exists on platforms like github
[14:30] <shadeslayer> I even proposed this 6 months back with git next
[14:30] <shadeslayer> i.e. dev just pushes tag, CI generates tar
[14:31] <yofel> don't they currently do thing the opposite way?
[14:31] <yofel> *thingſ
[14:31] <yofel> that's a funny character...
[14:31] <shadeslayer> release tar and tag? yes
[14:32] <apachelogger> tag -> tar is largely disliked
[14:54] <Riddell> should we try to release Kubuntu Plasma 5 along with Beta 1 next week?
[14:57] <Riddell> yo sgclark, how are you getting on with partition manager and kscreen?
[14:58] <BluesKaj> is plasma5 image stable after installation now or is it still hit and miss ?
[14:58] <sgclark> Riddell: I committed my partionmanager change yesterday... I am behind on kscreen as since last night I could not use debuild. Fixed now and working on it...
[15:02] <Riddell> BluesKaj: we don't know until you test it out
[15:02] <BluesKaj> hehe, ok Riddell, fair enough :)
[15:12] <Riddell> here's a really important question, should the cdimage pages for Kubuntu Plasma 5 use Ubuntu Font or Oxygen Font?
[15:13] <BluesKaj> gotta confess I never use Ubuntu font
[15:17] <sgclark> ^ same
[15:18] <Riddell> what do you use?
[15:19] <sgclark> oxygen
[15:20] <kdeuser56> hard decision, both look good
[15:22] <Riddell> sgclark: partitionmanager uploaded!  you can probably move that card to Done now
[15:22] <apachelogger> Riddell: upstream ftw? :P
[15:27] <Riddell> size limit on cdimage is..
[15:27] <Riddell> 1,073,741,824
[15:27] <Riddell> 1,102,970,880  ← our current amd64 size
[15:29] <Riddell> 1,207,959,552  ← current plasma5 image size
[15:29] <Riddell> what size limit shall I set it to?
[15:30] <apachelogger> 5 gig
[15:30] <Riddell> nooo
[15:30] <apachelogger> or you know, someone could clean up 
[15:30] <Riddell> ah, I see, you are using irony
[15:31]  * apachelogger too stupid to use cut
[15:33] <apachelogger> Riddell, yofel, shadeslayer: http://bazaar.launchpad.net/~apachelogger/+junk/recipes/files that's what build recipe definition looks like
[15:34] <apachelogger> I do wonder whether a list with generic recipes would be more fruitful though
[15:34] <shadeslayer> I call symlink
[15:34] <shadeslayer> ah wait
[15:34] <apachelogger> at least in neon we currently have the recipes largely diverging because they also define build deps and whatnot
[15:34] <shadeslayer> apachelogger: empty recipes? :p
[15:34] <apachelogger> shadeslayer: no no they are symlinks alright
[15:34] <shadeslayer> ??
[15:35] <apachelogger> all recipes symlink to _standard
[15:35] <shadeslayer> ah
[15:35] <apachelogger> which in turn specifies the recipe through _common
[15:35] <shadeslayer> then launchpad is being weird
[15:35] <apachelogger> all without params because presently there is no need for any special stuff, and it is this lack of need that makes me wonder whether a text file listing stuff meant to build wouldn't be more useful
[15:36] <shadeslayer> it most probably would
[15:42] <kdeuser56> shadeslayer, Riddell: just tested and recorded again, so that you can be absolutely sure my report was right: https://docs.google.com/file/d/0B-ihXi2hkCPfLVZlLW1zYnVuRWM/edit
[15:43] <kdeuser56> shadeslayer, Riddell: the utopic-desktop-amd64.iso is the kde 4 based iso
[15:44] <kdeuser56> shadeslayer, Riddell: the kubuntu-plasma5 iso simply ignores the "text" and the "noninteractive" boot parameter and boots straight to the desktop, which makes preseeding impossible
[15:44] <shadeslayer> kdeuser56: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/utopic/casper/utopic/view/head:/scripts/casper-bottom/15autologin
[15:44] <shadeslayer> kdeuser56: that's how it autologins
[15:44] <shadeslayer> well hm
[15:44] <shadeslayer> you probably want to grep casper
[15:44] <kdeuser56> shadeslayer: it seems this script is invoked too early
[15:45] <shadeslayer> to see what happens when you pass text
[15:45] <shadeslayer> kdeuser56: no, something is not invoked when you boot with text
[15:45] <shadeslayer> which causes 15autologin to get invoked
[15:46] <shadeslayer> yep
[15:46] <shadeslayer> kdeuser56: I have a fix
[15:46] <kdeuser56> shadeslayer: great
[15:47] <shadeslayer> kdeuser56: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/utopic/casper/utopic/view/head:/scripts/casper-bottom/25configure_init#L31
[15:47] <kdeuser56> shadeslayer: does that also fix the noninteractive boot parameter, which is far more important?
[15:47] <shadeslayer> it should
[15:47]  * shadeslayer is trying to understand the regex there
[15:48] <kdeuser56> shadeslayer: I can report you back tomorrow when the new iso is done
[15:48] <shadeslayer> yep, thx al0t
[15:48] <shadeslayer> *alot
[15:49] <apachelogger> Riddell, yofel: I swear to god, I have to see a package where wrap-and-sort will not touch half the files
[15:49] <apachelogger> it's madness
[15:49] <Riddell> why is that madness?
[15:51] <apachelogger> because like I said when I first complained about it people have, are, and will forget to run it thus making someone else pointlessly polluting the version control history with even more pointless lines moves
[15:52] <apachelogger> ohohoh
[15:52] <apachelogger> shadeslayer: I remember what other problem I saw with versions
[15:53] <apachelogger> I think merging with the same changelog stanza will make the merge tool fall over dead
[15:53] <apachelogger> since stable chanes and unstable changes would be interlaced substantially
[15:53] <shadeslayer> kdeuser56: http://paste.ubuntu.com/8107219/
[15:53] <apachelogger> so I think what needs to happen is that the unstable branch has a dedicated stanza listing the unstable changes ontop of the stable changes
[15:54] <apachelogger> i.e. kwin unstable right now would have 5.0.50 or something
[15:54] <apachelogger> ideally the version stanzas actually should be automated, but since upstream Riddell doesn't enforce one variable to define the version in all workspace repos that is a bit impossible right now :'<
[15:56] <apachelogger> dch really hates me
[15:56] <kdeuser56> shadeslayer: thx, you are amazing! I will test again with tomorrows iso, should be in there right?
[15:56] <shadeslayer> eys
[15:56] <shadeslayer> *yes
[15:56] <kdeuser56> great
[15:56] <shadeslayer> thanks for finding that corner case
[15:57] <Riddell> apachelogger: wait one cotton picking minute, upstream Riddell does enforce one variable in Plasma 5.1 for versions
[15:57] <apachelogger> Riddell: do you?
[15:57] <Riddell> apachelogger: just did that yesterday/today
[15:57] <apachelogger> oh lovely then
[15:58] <apachelogger> so we could ditch changelogs entirely and build automatically from commit messages even xD
[15:58] <Riddell> set(PROJECT_VERSION "5.0.95")
[15:58] <apachelogger> Riddell++
[15:58] <Riddell> although it does need this to get a shipit https://git.reviewboard.kde.org/r/119882/
[15:59] <Riddell> which requires d_ed to take a second look
[15:59] <apachelogger> mister beard
[16:02] <apachelogger> http://paste.kde.org/pmiw5n6k4
[16:03] <apachelogger> I am really not sure about this
[16:03]  * apachelogger shall start a notes page on CP tomorrow
[16:04] <Riddell> why are you not sure about build-dep on libepoxy?
[16:05] <Riddell> apachelogger: how do you expect 5.0.2 to be packaged?
[16:05] <apachelogger> Riddell: that'd be from the stable branch
[16:05] <apachelogger> I am not sure about the changelogging, not about the bdep xD
[16:06] <Riddell> apachelogger: right but then how does the stable branch get merged into the unstable branch?
[16:06] <d_ed> Riddell: see comment before shipping, shout IRL if you disagree
[16:06] <apachelogger> Riddell: bzr merge
[16:06] <apachelogger> Riddell: by hand (although in the mid term that should also be automated in some form or fashion)
[16:07] <apachelogger> the by hand factor is why I argued that bzr is rubbish for this endavor :P
[16:07] <apachelogger> at the end of the day when automated merges fail a human will have to forward merge stable into unstable
[16:09] <apachelogger> there's also the question of how much/if we should automated version bumps in the changelog ... i.e. if the project_version in cmake changes we could have automation that declares the present packaging 5.0.whatever and branches it automatically for a human to then do a release pack
[16:09] <apachelogger> could be iritating though
[16:10] <apachelogger> many options are at hand, most of them raise questions I have no good answer for :(
[16:13] <apachelogger> Riddell: anywho, general workflow is fix up stable ->> forward merge changes into unstable ->> triggers unstable rebuilds ->> fix up unstable
[16:16] <apachelogger> oh noes kwin failed
[16:16] <Riddell> sounds like faff
[16:17] <apachelogger> ohhh wayland
[16:18]  * Riddell sings the wayland song
[16:20] <apachelogger> if one of you wants to toy with the present stuff feel free to, shadeslayer should be able to trigger builds 
[16:20] <apachelogger> otherwise I'll try to beat it into green state tomorrow
[16:55] <BluesKaj> is there no install option the plasma5 image disk...seemed to run ok without any freezes 
[16:55] <BluesKaj> ?
[17:01] <BluesKaj> http://cdimages.ubuntu.com/kubuntu-plasma5/daily-live/current/ .. no ubiquity installer ?
[17:04] <sgclark> Riddell: lp:~kubuntu-packagers/kubuntu-packaging-next/kscreen ready for review.
[17:38] <BluesKaj> ubiquity installer is missing from the image...http://cdimages.ubuntu.com/kubuntu-plasma5/daily-live/current/
[20:27] <apachelogger> shadeslayer: I think you broke kwin building https://launchpadlibrarian.net/182900537/buildlog_ubuntu-utopic-i386.kwin_4%3A5.0.50%2Bgit20140821.2014~5cc66f1_FAILEDTOBUILD.txt.gz
[20:28] <apachelogger> oha
[20:28] <apachelogger> shadeslayer: nevermind
[20:28] <apachelogger> it appears that lib is new
[20:28] <apachelogger> my oh my, the changes in kwin alone
[20:28] <apachelogger> outragous
[20:33] <apachelogger> Riddell, shadeslayer, yofel: https://notes.kde.org/p/kubuntu-cp
[20:33] <apachelogger> random notes as of right now
[20:35] <apachelogger> mh
[20:35] <apachelogger> did we always package kwin as 300 packages?
[20:35] <apachelogger> the libs seem somewhat overzealous considering they are only supposed to be used by other workspace
[20:35] <yofel> usually, even for multiple gl's
[20:36] <apachelogger> yofel: well the gl spliting makes sense
[20:36] <debfx> the more the merrier
[20:36] <apachelogger> in the future even more so along the line of x11 vs. wayland
[20:36] <apachelogger> but libkwin4-effect-builtins1 surely doesn't need or want its own lib package
[20:37] <yofel> added fun if you make sure kwin needs at least 4 build runs until every package is filled
[20:37] <apachelogger> much silly
[20:37] <apachelogger> KISS I say
[20:37] <apachelogger> anywho, I dunno what to do with libkwin
[20:38] <apachelogger> upstream chooses to ignore my suggestion of putting a private in their lib names to make clear that they are private :'<
[20:38] <apachelogger> actually
[20:38] <apachelogger> Riddell: use some upstream release dude powers and make that happen plz ;)
[20:54] <shadeslayer> did not
[20:54] <shadeslayer> I need to be beyond the ballmer curve to achieve that brokenness
[20:56] <shadeslayer> no roommates \o/
[20:56] <shadeslayer> I have all the wifi
[21:22] <soee> latest updates, error when processing /var/cache/apt/archives/libpowerdevilcore2_4%3a5.0.1-0ubuntu1~ubuntu14.10~ppa4_amd64.deb
[23:33] <ShalokShalom> i install a fresh 12.04.5 and load the 4.13.2 ppa - that kills my oxygen window decortion (which reappears after reboot) and dont take any effekt, i am still on 4.8.5