[02:14] <rbetzen> phonon-backend-vlc 0.8.2 build fails. pbuilder can't seem to find libvlc-dev and libvlccore-dev.  Logged into pbuilder and tried to install the dependencies, but they're not present.  Any suggestions?
[03:22] <sgclark> rbetzen: make sure universe in apt sources.list
[03:25] <rbetzen> sgclark: hello again!  I'll check. I had it in my head that it was set up when pbuilder created the environment.  That's what I get for assuming.  Duh. ;)
[03:26] <sgclark> rbetzen: yeah I had to add  http://paste.ubuntu.com/9510369/ to my .pbuilderrc file to get dpes to install properly, keep in mind mine is for vivid so adjust accordingly
[03:33] <rbetzen> Ok.  I'm going to try again using your settings.  I'll let you know how it goes.  Thanks a bunch!
[03:52] <rbetzen> sgclark: that took care of my dependency issues.  thanks for the help.  wading through another issue now...
[03:57] <sgclark> rbetzen: np :) good luck!
[13:02] <BluesKaj_> Howdy folks
[13:50] <Mamarok> hm, some error in the Calligra update I got today: 
[13:50] <Mamarok> /var/cache/apt/archives/kexi_1%3a2.8.7-0ubuntu1~ubuntu14.10.1~ppa1_amd64.deb
[13:51] <Mamarok> trying to overwrite '/usr/share/kde4/services/calligra/koreport_chartplugin.desktop', which is also in package calligra-libs 1:2.8.7-0ubuntu1~ubuntu14.10.1~ppa1
[16:24] <sgclark> Mamarok: a code in student did that package, for how you can dpkg --force-overwrite --install /var/cache/apt/archives/kexi_1%3a2.8.7-0ubuntu1~ubuntu14.10.1~ppa1_amd64.deb
[17:22] <yofel> dear phonon, why don't you see any sound devices if I boot with systemd o.O?
[17:23] <yofel> alsa seems to be working....
[17:24] <yofel> ok, it's pulse that sees no devices, fun
[17:31] <yofel> no, it's alsa o.O
[17:35] <BluesKaj_> yofel, sometimes alsa automute is enabled after upgrades 
[17:36] <yofel> nah, my problem is:
[17:36] <yofel> $ aplay -l
[17:36] <yofel> aplay: device_list:268: no soundcards found...
[17:37] <sitter> alsa is very meh
[17:37]  * yofel is just reading init stuff as it works fine with upstart
[17:38] <sitter> seems weird though, our pulse is session bound, so udev and thus alsa should be up and running at that point
[17:38] <sitter> unless you have configured your pulse to be global
[17:39] <yofel> nah, pulse is session bound, and pulseaudio -k doesn't help either
[17:39] <sitter> driver bug maybe?
[17:40] <yofel> how would that break under systemd?
[17:40] <sitter> libalsa has fun issues with reentrancy
[17:40] <yofel> ...
[17:41] <sitter> I keep being told that they are all fixed though :P
[17:41] <sitter> *getting
[17:41] <yofel> ofc ^^
[17:42]  * sitter gets a headache from looking through things to do for 15.04
[17:45] <yofel> er... why does aplay see the devices if I run it with sudo O.O
[17:45] <yofel> how I love permission problems
[17:46] <sitter> yofel: loginctl lists your session?
[17:46] <yofel>          1        148 sddm             seat0           
[17:46] <yofel>          2       1000 yofel            seat0  
[17:49] <BluesKaj_> does F6 in alsamixer show any soundcards?
[17:49] <yofel> if I run it as root yes
[17:49] <yofel> crw-rw----+  1 root audio 116,  3 Dec 14 18:21 controlC0
[17:49] <yofel> hm...
[17:50] <sitter> do note that permission control ought to be handled through logind regardless of what the file system permissions say
[17:50] <yofel> ok
[17:50] <sitter> no clue how that works, but I know ubiquity had a similar situation
[17:50] <sitter> that being said, I think the problem there was sddm
[17:50] <sitter> so it's entirely possible that our sddm profile is still busted
[17:50] <sitter> yofel: try lightdm for good measure maybe
[17:51] <yofel> we don't have a sddm systemd profile, it's starting init.d/sddm
[17:51] <sitter> oh actually
[17:51] <sitter> sddm has tight sytemd integration, since our sddm is not built with sytemd integration for reasons I do not know that could potentially cause problems like these
[17:51] <sitter> so yeah, try lightdm :P
[17:51] <yofel> yeah, good idea. brb
[17:51] <sitter> if it works there try to build a sddm with systemd enabled
[17:56] <yofel> yeah, works with lightdm
[18:05] <sitter> https://www.kubuntuforums.net/showthread.php?67037-Website-quot-stealing-quot-KFN-threads
[18:06] <sitter> lulz
[18:06] <sitter> internet be a weird place
[18:09] <yofel> XD
[18:11] <sitter> also why is there no way to view hottest topics of the past week, web forums are well terrible
[18:11] <sitter> claydoh: has anyone ever thought about using a different forum software?
[18:14] <Mamarok> sgclark: thanks, I already did so :)
[18:20] <yofel> sitter: it indeed was the missing systemd integration in sddm
[18:20] <yofel> works fine now
[18:20]  * sitter blames Riddell
[18:20]  * yofel is getting tired of hplip telling him that he has no system tray -.-
[18:21] <yofel> where's that autostart file..
[18:22] <sitter> what what
[18:22] <yofel> sitter: why *did* we disable that? The git log doesn't give any hint
[18:22] <sitter> I fixed that
[18:22] <yofel> well, not fixed here
[18:22] <sitter> https://bugs.launchpad.net/bugs/1350038
[18:22] <sitter> of course upstream is dead or something
[18:23] <sitter> though I think I uploaded a distro patch for that
[18:23] <sitter> yofel: https://launchpad.net/ubuntu/+source/hplip/3.14.6-1ubuntu1
[18:23] <yofel> yeah, just read the changelog
[18:24] <sitter> hm
[18:24] <sitter> yofel: do you have sni-qt?
[18:24] <yofel> no
[18:24] <sitter> that'd be the problem then
[18:24]  * sitter ponders that maybe plasma-desktop should recommend it
[18:24] <sitter> then again that is a qt thing
[18:25] <yofel> yup, works once that's installed
[18:25] <yofel> thanks
[18:25] <sitter> Mirv: would ubuntu have any problems with promoting sni-qt to recommends/depends on qt4?
[18:25] <sitter> unity that is
[18:28] <sitter> yofel: I added it as recommends to desktop for the time being, for 15.04 this should not be a problem as we need breeze-qt4 for theme convergence anyway
[18:29] <yofel> k
[18:33] <yofel> *sigh*
[18:34] <yofel> Riddell: it's great if you leave packaging tasks to gci students if they're interested, but please a) do some Q/A *before* uploading to the archive and backporting and b) import the packaging into VCS once you're done if you don't use it during the packaging
[18:35] <sitter> ....
[18:35] <yofel> I even stopped complaining about unwritten changelogs -.-
[18:36] <sitter> changelogs are silly
[18:36] <sitter> like anyone cares :P
[18:36] <yofel> indeed
[18:36] <sitter> but yeah... technically when merging unstable people should compile the change sinto debian/changelog
[18:36] <sitter> that was the original proposal anyway, no one does it though, so...
[18:36] <sitter> I personally couldn't care less ^^
[18:37] <yofel> I'm talking about calligra, but yeah, that too
[18:37] <yofel> sitter: why not write the changelog as usual in unstable?
[18:38] <sitter> incredibly hard to get to automerge
[18:38] <yofel> ok, I need to remove something from parley then ^^
[18:39] <sitter> oh, good thing I have not looked at the diff or you'd have gotten a bit of bully me as Riddell put it :P
[18:39] <yofel> there was a way to fill the changelog using the git log right?
[18:40] <sitter> it's a bit meh though, I was actually thinking about making the merger a bit smarter in that changelog conflicts would always yield to 'theirs' which however also can have funny side effects :/
[18:40] <sitter> yofel: probably
[18:40] <yofel> would require people to write proper commit logs though :/
[18:41] <sitter> not really, the thing is... changes are supposed to be so atomic that even with proper commit messages the autogenerated output would be largely pointless noise
[18:41] <sitter> which is why I argued that a human should compile the changelog on merge
[18:42] <sitter> an autogenerated changelog with lots of pointless noise is about as useful as no changelog
[18:42] <yofel> that doesn't really scale with kde though...
[18:42] <sitter> which is probably why no one does it :P
[18:42] <yofel> unless the script actually marks packages that had changes in unstable
[18:42] <sitter> what I would find more useful anyway is documenting patches + the rest of the changelog should be upstream changes
[18:43] <sitter> i.e. post-release you'd document your patches for SRU, as that happens anyway. up until then and for PPA you'd document what changed upstream (under the assumption that our packaging did only adopt what upstream did or improved our structuring)
[18:45] <sitter> packaging changes are not useful to the user and right now muon-updater presents the changelog to the user which is mostly useless because the changelog except for post-release only contains what changed packaging-wise which is (or perhaps ought to) not be relevant for the user
[19:21] <sitter> FWIW other option would be to have a CI-exclusive changelog in debian/changelog.ci or debian/meta/changelog which would only hold the changes relative to $release branch and gets cleared upon merge of CI branch into $release branch
[19:21] <sitter> knowing the team I am reasonable certain that this sort of approach would be too much overhead for people so they wouldn't do it :P
[19:25] <yofel> I'll agree with that
[19:35] <yofel> *sigh* ~130 package copy errors in the updates ppa and nobody seems to care
[19:35] <yofel> I'll admit that cleaning those up is a PITA though
[19:36] <sitter> needs IRC bot
[19:36] <sitter> yofel: how do those happen?
[19:36] <yofel> Copied from: Private PPA for Kubuntu Ninjas. Copied by: Scarlett Clark Target series: Utopic
[19:36] <yofel> konsole 4:4.14.2-0ubuntu1~ubuntu14.10~ppa1 in utopic (same version has unpublished binaries in the destination archive for Utopic, please wait for them to be published before copying)
[19:37] <sitter> anyone fancy wiring my lp client to rbot xD http://anonscm.debian.org/cgit/pkg-kde/ci-tooling.git/tree/lib/lp.rb
[19:37] <sitter> yofel: shouldn't kopypackages do that?
[19:37] <yofel> that's why I prefer to use the deprecated syncSource() instead of copyPackage() as the former is synchronous
[19:38] <sitter> well, IMO there should just be a preliminary check for is-everything-published
[19:38] <yofel> well, with --sync it does, because of ^
[19:38] <sitter> yeah, except that API is supposed to go away at some point so one really shouldn't use it
[19:38] <sitter> plus async is awesomest anyway
[19:39] <sgclark> compile the changelog on merge ? what does that mean?
[19:39] <sitter> so IMO kopy should simply make sure everything is published before doing anything and crap out if everything isn't
[19:40] <sitter> in addition to that one could then possibly have a bot notifiction on failed copies but that shouldn't be needed all that often (i.e. only case where it would kick in is if a new package version is uploaded during copy, which is a bit of an edge case)
[19:41] <sitter> http://anonscm.debian.org/cgit/pkg-kde/ci-tooling.git/tree/ppa-wait.rb#n146
[19:41] <yofel> right, checking whether the version is already there before copying should cover most usually
[19:42] <sitter> sgclark: right now kubuntu_unstable has no debian/changelog, so one would need to look at the changes one merges from kubuntu_unstable and manually write suitable debian/changelog entries
[19:43] <sgclark> ahhh
[19:43] <sgclark> np here
[19:44] <yofel> for you maybe not, for others yes :P
[19:44] <sitter> as I was saying, I don't particularly care, changelogs outside an SRU context mostly just document what would be documented in the git log anyway, so to me it seems like pointless information duplication
[19:44] <sgclark> yeah
[19:45] <sgclark> yofel, what is that about copy errors, what did I not do> or do wrong?
[19:45] <sgclark> I have np cleaning up my stuff if I know what I need to do
[19:46] <yofel> nah, I just did the cleanup. What I think happened is that you did a mass package copy twice without delay in between (script failed in the middle or so?)
[19:47] <yofel> that's pretty much the only thing that would cause over a hundred not-yet-published errors
[19:48] <sitter> for some reason launchpadlib likes to crap out for weird reasons ^^
[19:48] <sgclark> ok
[19:48] <yofel> so package wise, nothing bad happened, but it fills up the launchpad copy package error list - and as the UI for it sucks, it's annoying
[19:49] <sitter> well, package-wise bad things can happen on copy errors ... if A requires B but B is not published and thus fails to copy A becomes uninstallable
[19:50] <sitter> worse yet if A technically requires B but the packaging relationships is screwed and then a maintainerscript assumes B is present and things explode at install-time
[19:50] <yofel> I don't think launchpad does dependency checks on copying?
[19:50] <sitter> yofel: which is why it can explode
[19:50] <sitter> A gets copied, B doesn't, user gets error
[19:51] <yofel> well yeah, but this case here is about copying A, getting an error, then copying A and B - resulting in a copy error for A
[19:51] <yofel> although, NONE of our scripts actually make sure that everything did get copied in the end
[19:51] <sgclark> doh
[19:52] <sitter> I am just saying *technically* this sort of thing can cause errors, they don't necesasrily need to :P
[20:58] <soee_> wow i did noticed the undo function in frameworks it has been added 5.5.0 ?
[20:59] <soee_> *added with
[21:07] <sgclark> undo function?
[21:13] <soee_> sgclark: yes this one http://notmart.org/blog/tag/plasma-5-2/
[21:15] <sgclark> oooh neat