/srv/irclogs.ubuntu.com/2014/06/03/#kubuntu-devel.txt

ahoneycuttvalorie: our session is Wed June 13 at 1700 UTC00:04
ahoneycuttdo we have all three domains for docs.kubuntu?00:11
ahoneycutt.com, .org, .co.uk00:11
apacheloggerin theory we could anyway00:12
apacheloggerovidiu-florin, jose: where are we on website business btw?00:12
joseapachelogger: ask ovidiu-florin!00:13
ovidiu-florinwe're still having issues with the child theme.00:13
ovidiu-florinWe have some suggestions from someone on how to implement that, but I haven't had the time to try them out00:14
ovidiu-florinalso, someone promissed to make an sketch for the Team page00:15
ovidiu-florinbut no feedback since00:15
ovidiu-florinI don't remember his name00:15
apacheloggersgclark: status page adjusted for next http://qa.kubuntu.co.uk/kf5-status/build_status_4.100.0_trusty.html 00:15
apacheloggerovidiu-florin: check logs and poke? :)00:16
sgclarkapachelogger: ok thanks, power went out :(00:16
ovidiu-florinwill do, in the morning00:16
ovidiu-florinin ~9 to 10 hours00:16
ovidiu-florincan someone poke me around then to remind me please?00:17
apacheloggerkubotu: whats the plugin for that?00:17
apacheloggerkubotu: remind ovidiu-florin to poke people in 10 hours00:18
kubotuapachelogger, you don't have 'remind::other::about' permissions here00:18
apacheloggerkubotu: you are being very rude today00:18
ovidiu-florin:)00:19
ovidiu-florinI'll just look over the TODO tomorrow and remember to do that00:19
apacheloggerkubotu: whoami00:19
kubotuyou are my boss00:19
apacheloggerthat's right00:19
apacheloggerkubotu: remind ovidiu-florin to poke people in 10 hours00:19
kubotuokay00:19
apacheloggerthx sweetie :*00:19
ovidiu-florinnice00:20
ahoneycuttlol00:20
ahoneycuttkubotu: whoami00:21
kubotuyou are *ahoneycutt6989616492634000:21
ovidiu-florinkubotu: whoami00:21
kubotuyou are *ovidiu_florin6989616485032000:21
apacheloggerclearly you are nobodys :P00:21
ovidiu-florinwhat's with the numbers?00:21
apacheloggerrandom number00:21
apacheloggersupposed to make the uid unique I guess ^^00:22
apacheloggersince they are autogenerated00:22
apacheloggersgclark: I am going to rename the last branches with -kf5 suffix unless you still need them00:23
apacheloggerkwallet/kactivitites/kdnssd00:24
* apachelogger reports out of coffee and runs circles00:24
sgclarkI am done with bzr if thats what you mean00:24
apacheloggerrenamed00:25
* sgclark impatiently waits for all these copied packages to build00:26
apacheloggershall I trigger neon5 retries to delay things a bit? :P00:27
* sgclark cries out nooooo00:27
apacheloggerbut it's also terribly red :'<00:27
apacheloggeroh right00:28
* apachelogger writes another mail00:28
apacheloggerpft santa_ is blocking our builds00:44
* ScottK considers starting to merge Qt5 5.3 from Debian. 00:44
apacheloggerplease do00:44
* apachelogger wants plasma next with wayland by the end of the week :O00:44
ScottKJust got to my hotel. Need some dinner first. 00:45
sgclarkapachelogger: wait what?!? how. I need to finish at some point ... 14 hours ugh00:46
apacheloggerhttps://launchpad.net/~panfaust/+archive/kubuntu-kf5-experiments00:46
apacheloggerassuming they were uploaded before the copy they will get processed first as they supposedly have the same upload score00:47
* sgclark grumbles00:47
santa_apachelogger: I can remove the packages and do my experiments other day if that helps00:48
sgclarkI still have to apply all my changes files..00:48
apacheloggeralready queued now, I don't mind much :P00:48
sgclarkyes please. ^^00:48
apacheloggersanta_: why do you need to build the entire packageset anyway?00:49
apacheloggerjust make your ppa dep on next and reuse the existing packages to build from00:49
apacheloggeryofel: did you ever reach any sort of conclusion on continuous builds btw?00:50
santa_apachelogger: I'm just getting familiar with your ppa's stuff00:50
santa_never used it before00:50
santa_gonna remove everything then00:50
apacheloggersanta_: http://i.imgur.com/8BJzoXE.png00:52
apacheloggerif you add another ppa as a dep it will basically add that ppa to the sources.list of the builders00:53
apacheloggerso it will simply resuse the existing packages from kubuntu next00:53
santa_yep, the thing is I started that ppa to fix the various ftbfs'es in the previous version, so I needed to rebuild everything00:54
apacheloggerah, please coordinate ftbfs fixes 00:55
santa_but now I guess I could re-use your stuff, yes00:55
apacheloggerotherwise work gets duplicated because I think sgclark is also working on that00:55
santa_it's everything merged now00:55
* sgclark is00:55
santa_I don't have any pending work right now00:56
apachelogger4.100 will have compat issues with the released workspace01:00
* apachelogger rolls eyes01:00
apacheloggerRiddell: btw, did you understand how tarme works yet?01:01
ScottKapachelogger: Of course not.  It'll be perfectly compatible.  In the brave new world of KF5/Plasma Next anyone can release anything whenever they feel like it and it'll be wonderful.  No matter what.  No need for coordination.01:10
ScottKI'm sure of it because both Aaron and KDE promo said so.01:10
apacheloggerwell, frameworks api isn't entirely frozen yet ^^01:12
* sgclark giggles01:13
apacheloggeroh01:15
apacheloggerScottK: fear not, next month binary interface freeze kicks in01:15
apacheloggerif shit breaks after that we get to throw dirt ^^01:15
ScottKAnd then throw dirt again a month later.01:16
ScottKOh, wait.  I forgot.01:16
ScottKKevin Ottens promises no regressions ever in KF5 so we can just blindly update whenever.01:17
ScottKWhat could possibly go wrong.01:17
* apachelogger wonders when devs will remember that qreal != float && qreal != double01:28
ScottKNever since in Qt5 they aren't required to care.01:30
apacheloggerI see a ftbfs :P01:32
apacheloggernot on kubuntu though01:33
* apachelogger squints02:15
apacheloggerwell, it's official lunchpad hates me02:23
apacheloggeroh, actually the buildpackage thing hates me02:24
apacheloggerRiddell: data packages for l10n doesn't compute for me02:30
apacheloggerwhat's the point of that?02:30
apacheloggeroh multiarch02:32
apacheloggermany a kittens have to die because of the frameworks packaging02:32
apacheloggersimplest of frameworks would have an exciting amount of 4 packages in control02:33
apacheloggerand why does the lib binary:version dep on the data02:57
apacheloggerlconvert: could not find a Qt installation of ''03:01
apachelogger...03:01
apacheloggerneon is eating the builders03:33
apacheloggermuch rude.03:33
apacheloggerRiddell, yofel, ScottK, shadeslayer: how about we drop the debian subdirs in bzr branches?03:39
ScottKapachelogger: Please don't.03:39
apacheloggerScottK: why?03:39
ScottKIt would seriously mess up my workflow.03:39
apacheloggerhow so?03:40
ScottKThe .bzr dir is only in the top level dir.03:40
ScottKso with the debian directory under the top level, I can diff the debian dir in the package and the bzr very nicely.03:40
ScottKIf there was no debian dir, the .bzr ends up in my diff.03:40
ScottKReally annoying.03:41
apacheloggerScottK: -x .bzr?03:41
ScottKWhat problem are you trying to solve by changing it?03:41
apacheloggerhaving to type more than I can be bothered to03:42
ScottKAlso then when I diff and patch in and out of the bzr branch (and I do that) then the -p levels get screwed up.03:42
ScottKd <tab> isn't much03:42
apacheloggertoo much considering there's some 80 branches just for frameworks and workspace right now03:42
apacheloggerbut, really the issue is probably more the fact that the packages are too splity03:43
apacheloggerbunch of frameworks now got localization so one now gets to hop into every other framework branch, copy and paste the same stanza, adjust the description create the very same install file and commit that03:44
ScottKSounds like it's dieing to be scripted.03:44
apacheloggerit is exactly the kind of thing I was talking about yesterday WRT having to batch edit stuff03:44
yofelapachelogger: continuous builds?05:41
yofeland please don't drop debian/05:42
yofelit would be rather inconvenient for things like wrap-and-sort, dch, etc...05:42
yofelRiddell FYI about our wrap-and-sort breakage:06:12
yofel"The merged package definitions were separated by one line containing a06:12
yofelspace (line 20 of your control file), but they should be separated by06:12
yofelone empty line. That's the reason why the package definitions were06:12
yofeljoined."06:12
yofelfrom debian 75024706:12
ubottuDebian bug 750247 in src:python-debian "devscripts: [wrap-and-sort] removes package definitions when wrapping control file" [Normal,Open] http://bugs.debian.org/75024706:12
soeegood morning06:17
yofelapachelogger: what was your plan wrt kubuntu-packaging-next and kbzr?07:33
=== vinay is now known as Guest94768
Riddellyofel: hmm, quite likely09:34
yofelRiddell: is there a release schedule for kf5 anywhere? I can find a schedule for plasma, but not for kf509:41
Riddellyofel: http://community.kde.org/Frameworks/Epics is the best we've got10:03
Riddellalthough it tends to be whenever dfaure is free10:03
BluesKaj'Morning folks10:17
ovidiu-florinkubotu: where's my reminder?10:25
ovidiu-florinit's been 10 hours10:25
yofelhm10:26
yofelkubotu: whoami10:26
kubotuyou are yofel10:26
Riddellapachelogger: I'm not too sure on the point of moving those kf5 branches, we'll still need to rename the source package for ones with overlapping names10:31
ovidiu-florinapachelogger: kubotu forgot about my reminder10:34
yofelweird10:35
yofelkubotu: remind ovidiu-florin to poke people in 10s10:35
kubotuyofel, you don't have 'remind::other::about' permissions here10:35
yofelaha10:36
yofelremind me about foo in 10s10:36
yofelkubotu: remind me about foo in 10s10:36
kubotuokay10:36
yofelPM'd me, curious10:36
ovidiu-florinso the reminder is PM?10:37
ovidiu-florindid not expect that10:37
yofelRiddell, apachelogger: if we go with a seperate image for plamsa next for now, do they really have to be co-installable?10:48
yofelI don't particulary see the point in supporting two workspaces in parallel10:50
yofelif anything, I see version clashes regarding the epoch10:51
Riddellyofel: they're not coinstallable10:52
yofelso why rename?10:53
Riddellyofel: kdelibs and kde-runtime equivalents should be co-installable10:53
Riddellkde-workspace doesn't matter10:53
Riddellbut there's some bits of kdelibs which have the same name in kf5 and plasma10:53
Riddellkdnssd, kwallet, kactivities10:54
Riddellattica10:54
yofel:/10:55
yofelhow about renaming everything kf5-<module> so it's at least consistent? Or would that be too messy again10:55
Riddellseems messy an unnecessary to do all, I've been renaming the ones that clash <module>-kf510:56
yofelwhich will need script special casing :/10:56
Riddellright, such is life10:56
Riddellin plasma baloo kfilemetadata and milou will need renamed10:57
Riddellwhich I can do being upstream10:57
Riddellsuggestions welcome for what to call them10:57
yofelRiddell: I think you're uploading to the wrong PPA?11:24
Riddellyofel: so I've just seen11:24
yofel^^11:24
=== joshwambua_ is now known as joshwambua
ovidiu-florinyofel: I've replied to a volunteer that offered to help with a few things with the new kubuntu website. I've CC'd the kubuntu-devel mail list, so you guys can see the thread. Aparently it needs aproval because the message is to big. :|11:36
yofelRiddell: ^11:37
apacheloggerRiddell, yofel: source name has nothing to do with the branch, it never has11:38
apacheloggeras for the renaming11:38
apacheloggerI'll argue that the kde4 sources should be renamed11:38
yofelyou would still have to special case epochs then, or add an epoch to everything11:39
apacheloggeryofel: why? all frameworks will be version 5.x and soversion 511:40
yofelbaloo 4:4.13.0 >> baloo 5.011:41
apacheloggeryofel: so?11:41
apacheloggereverything gets epoch 5? :P11:42
yofelwell, 4 would suffice, current is 011:42
apacheloggerthat's confusing, should be 511:42
yofelwhy, the version is 5, epoch has nothing to do with that11:42
apacheloggeryou need the epoch in the apps space anyway, since they do not change name and they do not need to be coinstallable11:42
apacheloggeryofel: yes, because apps need it11:44
yofelhow? where? why?11:44
apacheloggerVersion: 4:4.13.0-0ubuntu111:45
apachelogger!info gwenview11:45
ubottugwenview (source: gwenview): image viewer. In component universe, is optional. Version 4:4.11.5-0ubuntu0.1 (saucy), package size 2815 kB, installed size 4366 kB11:45
yofel...?11:45
apacheloggeryofel: it has an epoch11:46
yofelwhat's wrong with 4:5.011:46
apacheloggeryofel: it's confusing11:46
yofelwell, it's debian...11:46
Riddellyofel: mind and keep https://notes.kde.org/p/kubuntu-ninjas-frameworks updated when you're working on a KF5 package11:46
apacheloggeryofel: 4:5.1.3+dfsg+really5.1.211:46
yofelRiddell: yeah sorry, forgot to do that for the first 211:47
yofelapachelogger: looks fine to me ^^11:47
Riddellyofel: instead of just writing "done" I've been writing ~ppa2 up so we know that if ~ppa2 fails then it needs to be done again12:07
yofelok12:07
Riddellhola sgclark 12:18
sgclarkRiddell: morning :)12:23
ScottKCoordinate the epoch thing with Debian. If we get to a higher epoch than them it really sucks. 12:43
shadeslayerhi12:47
yofelmoin shadeslayer ^^13:05
shadeslayerhello13:05
shadeslayerhow's it going13:05
shadeslayerapachelogger: I hear you're giving a talk about builder @ UOS :P13:06
shadeslayerScottK: do we want a Qt5 sync up session at UOS?13:08
Riddellbuilder?13:09
apacheloggershadeslayer: that's news13:09
shadeslayer^_^13:09
apacheloggeryofel: whatever happened to the maintainenance on aliaoth notion13:10
yofelnothing, at least not from my side. 13:15
yofelLet me dump our last proposal into the channel and see what happens13:15
yofelmight as well discuss the epoch too13:15
ScottKshadeslayer: we want 5.3 to go in asap. 13:18
ScottKIf that needs a session, fine. 13:18
shadeslayerI'll ask around I guess13:19
ScottKMy trying to get someone from Canonical to discuss it via email isn't going very well. 13:19
shadeslayerok13:19
ScottKFrankly though the whole KDE upstream pov that IMO amounts to screw the distros they're on there own causes me to be even more demotivated about being involved in KDE packaging.13:24
shadeslayerI still have a different view tbh ....13:25
yofelshadeslayer: take that up with the techboard, until then I'm with scott13:26
yofelapachelogger: ok, so sune is against renaming sources13:27
yofel(old ones I mean)13:27
yofelso the epoch is moot I believe as we can keep 0 for now13:27
apacheloggeryofel: not epoching makes scripting more work because you need to parse the epoch out of the changelog before doing things13:29
apacheloggerunless there is a dch argument that automatically reuses the epoch13:29
ScottKapachelogger: dch -i does what I think you're suggesting. 13:33
apacheloggerScottK: no, I mean like dch -v 5.1.013:34
ScottKOh.13:34
yofelwell, currently *nothing* in kf5 has an epoch13:34
apacheloggeryofel: applications will13:34
ScottKYeah you need to include it. 13:34
apacheloggergwenview has epoch 413:35
yofelthat's not kf5, that's plasma and applications13:35
apacheloggerunless we rename all applications we will have an epoch13:35
yofeland you can just keep the 4 there13:35
apacheloggeryofel: so you want two different scripts?13:35
yofelscripts no, different package lists yes13:35
apacheloggeryofel: my point is that to keep the epoch in one part but not the other you then have to script epoch parsing in13:35
apacheloggersomething you could entirely avoid if you say everything core kde (whatever that will be in the future) has epoch X13:36
ScottKFWIW, if someone goes to the TB to ask for an MRE for KF5, I'll probably be arguing against it.13:36
yofelwhat's so hard about string.split(':') ?13:36
apacheloggeryofel: you first need to get the version13:37
apacheloggerso we are talking something like parsechangelog | grep Version | sed13:38
apacheloggerwhich is entirely avoidable by simply not insisting on having no epoch because there is zero benefit to not having an epoch13:38
apacheloggerthere however is a benefit to retaining the epoch and that benefit is to not have to worry about the fact that some automated bits have an epoch and others don't13:39
yofelIMO, I would rather special case stuff for now until we have worked out with debian what they want to do13:39
yofelif we can put our stuff on alioth, and run our scripts over that, and they're fine with it, I'm ok13:39
apacheloggerwell yeah, the epochs should be aligned13:40
yofelI'm not disagreeing that using one epoch on everything is easier, but they have to be in sync then13:40
apacheloggerI am arguing that the epochs should also be aligned across all bits we need to mass automate13:40
shadeslayerapachelogger: yofel https://bitbucket.org/unit193/trellobot13:43
apacheloggerbitbucket still exists?13:44
shadeslayeryes, I use it13:44
shadeslayerfor sekrit repos13:44
yofelfun13:44
apacheloggersekrit repos he said13:45
apacheloggerdon't be lazy, write an rbot plugin13:45
apacheloggerthen you can trello off of kubotu instead of having to run a dedicated bot13:45
shadeslayerhmm13:46
apacheloggerI personally fail to see the point fwiw13:46
* yofel would rather have commit notifications back :S13:52
apacheloggerlol13:53
apacheloggerI just thought the same and am currently looking into that :P13:54
apacheloggernot quite sure how to do that though13:54
yofelyou could probably do it by having the bot subscribed to the mail notifications from launchpad13:54
apacheloggerthat's all sorts of complicated13:55
apacheloggerrss seems more useful13:55
apacheloggerbut automatically subscribing to things is a bit rubbish theree13:55
apacheloggerthat's also why the bug notifications are not active on everything13:56
yofelwell, if launchpad had rss, sure :S13:56
apacheloggeryofel: it does13:56
apacheloggerwell, loggerhead has13:56
apacheloggeroh, actually lunchpad has as well13:56
apacheloggerhttp://feeds.launchpad.net/~kubuntu-packagers/kubuntu-packaging-next/plasma-workspace/branch.atom13:56
yofel*blink* I did not know about that13:56
apacheloggerit's all very well hidden13:57
apacheloggerohohoh13:57
apacheloggerI found a team level feed13:58
apacheloggerhttp://feeds.launchpad.net/~kubuntu-packagers/branches.atom13:58
apacheloggermsg kubotu13:58
apacheloggereh13:58
apachelogger^^13:58
apacheloggermsg kubotu13:58
yofel@_@14:00
apacheloggerthe feed content is a bit pointless14:03
apacheloggerkubotu: rss show branches 114:03
kubotulemme fetch it...14:03
kubotuChannel : Branches for Kubuntu Packagers14:03
kubotu2014/06/03 13:11 :: lp:~kubuntu-packagers/kubuntu-packaging-next/kdbusaddons @ https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging-next/kdbusaddons (by Kubuntu Packagers)14:03
yofelthat's missing the interesting part -.-14:04
apacheloggeroh, maybe by project would work better14:04
apacheloggerkubotu: rss show branches 114:05
kubotulemme fetch it...14:05
kubotuChannel : Latest Revisions for kubuntu-packaging14:05
kubotu2014/06/02 19:58 :: [khtml] r28 Fix remain wrap-andsort breaks... (by Scarlett Clark)14:05
apacheloggerthat one doesn't have links ^^14:05
yofellink might be a bit long IMO14:06
yofelwe know where it is anyway (as long as the project is shown)14:06
apacheloggernot if one takes next into the picture14:06
apacheloggerwell, when there's branch with equal name in both projects anyway14:06
yofelhence my point about the project14:07
yofelFWIW, that's already more useful than the bug notifications...14:08
apacheloggerwhat's wrong with the bug notification :O14:08
yofeluhm, that it always shows the same message each time...?14:09
apacheloggerso?14:09
apacheloggeryou know the bug has changed14:09
yofelI can let kmail notify me about that...14:10
yofelok, nevermind14:10
apacheloggerjust like with branches :P14:10
yofelI'm just used to having *content* in such messages14:10
apacheloggerby that standard irc notifications make no sense altogether because you could simply sub by mail :P14:10
apacheloggeryofel: well, tell launchpad that14:10
apacheloggercan't do much about the title the feeds give14:10
yofelyeah, I got that the second after I finished writing -.-14:11
apachelogger^^14:11
apacheloggerI think I found a way to track all bug reports btw14:11
apacheloggerit's much more straight forward once one realizes that teams have feeds ^^14:11
shadeslayerhidden features, hidden features everywhere14:12
yofelapachelogger: I'm not arguing about launchpad, I'm just arguing that the title isn't really sufficient to tell me anything :/14:13
apacheloggermh14:14
apacheloggerit appears one can write custom filters for the feed plugin14:14
apacheloggernot that I know or understand how that would work14:14
apacheloggereean or markey would apparently since they hold authorship :P14:15
yofelI'm not really sure though if the posts warrant a like 7 line bot message in here though14:15
yofeleven if I like the long kde commit notifications14:15
apacheloggerlooking I say, looking14:16
apacheloggerwell14:17
apacheloggeryofel: as far as the atom is concerned I don't think filtering is an option either14:17
apacheloggerthe actually useful data is html content14:17
apacheloggerextracting meaningful things from that seems nigh impossible14:18
shadeslayeroh oh oh14:18
shadeslayerScottK: yofel apachelogger reckon I should schedule a session for Frameworks releases in ubuntu?14:18
yofelurgh, yeah, that content looks awful14:19
yofelshadeslayer: to discuss it with whom?14:20
shadeslayerTB14:20
yofelwell, go ahead if you want, you're not going to have me on your side unless I've seen a couple releases without any breakage14:21
apacheloggerI'll say that unless there have been actual releases a discussion would involve 99% handwaving14:21
shadeslayerI see14:21
shadeslayerso whats the plan for 14.10 then14:22
apacheloggerland in ppa14:22
yofel^14:22
yofelwe could put it in the archive, but it would be essentially unsupported14:22
yofeldepends on demand really I think14:23
apacheloggerwhich is not in the interest of anyone as that prevents upstream to quickly iterate initial bugs out of the way14:23
shadeslayer^^14:23
apacheloggerone could make an argument for landing it all the same as even with intial bugs it makes it easier for devs to transition to frameworks14:24
apacheloggerbut truth be told right now I actually feel that even then they'd be better served with using the PPA to get the latest and greatest asap14:24
shadeslayerI think landing is pointless unless we can keep updating monthly14:24
yofeladding a PPA isn't that hard, IMO it only makes sense if someone comes up and says that package X that he wants in the archive uses kf5 module Y, then it might make sense14:25
shadeslayeryeah, basically, not having KF5 in the archive blocks KF5 apps in the archive for 9 months14:26
yofelshadeslayer: we can put it in as soon as we put something in the archive that needs it, currently that's nothing, so no point in having it there14:27
yofeland it's not like we can put applications in the archive post-release14:28
shadeslayerbut then if random-app requires a tier 3 framework, what then14:29
yofelshadeslayer: as I said, then we can talk about it, but if random app isn't ready by 14.10 FF, I'm against including it14:34
yofelkubotu: newversion calligra 2.8.314:38
kubotuhttps://bugs.launchpad.net/bugs/132600214:38
shadeslayerooh14:40
shadeslayerhttp://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html14:40
shadeslayerhas autopkgtest output now14:40
shadeslayersweet14:40
yofelwow, how colorful ^^14:41
shadeslayer:D14:41
yofelautopkgtest for kde4libs 4:4.13.1-0ubuntu1: Always failed14:41
yofelgreaaaaat14:41
yofelshadeslayer: do you think it's sensible to add autopackagetest to our kf5 stuff? So far dh_test is being run, but not autopkgtest14:42
shadeslayeryofel: that kdelibs part failing is because of dh-acc not depending on debhelper14:43
yofelah k14:43
shadeslayerworkaround would be to add it manually to our test14:43
shadeslayeras for autopkgtest for KF5, yeah, I think so, plus we can add dh-acc checks to make sure ABI doesn't break14:44
yofelright, still need to read up on that14:44
ScottKshadeslayer: I think we already decided about frameworks in our session.  No need for something at UOS.14:46
shadeslayerScottK: roger14:46
shadeslayerwhole bunch of stuff is blocked on non installable maxima14:47
shadeslayerhm14:47
sgclarkok so I dput ktextwidgets v3 to ppa:kubuntu-ppa/next but seems to have vanished into space, any ideas?14:52
yofelshouldn't happen unless you didn't sign it14:54
sgclarkSuccessfully uploaded packages.14:54
yofelto the right ppa?14:54
apacheloggershadeslayer: there's not much leeway when we land frameworks, we propose an update exception to TB, they either approve or not and then we have to deal with that14:54
apacheloggerthe only real alternative is to then seek approval for allowing a ppa to be enabled by default as to deploy updates outside the scope of the archive (which really amounts to the same problem domain anyway) or worst case have a checkbox somewhere to enable updates for frameworks14:56
apacheloggerenable updates for frameworks would then add the PPA14:56
apacheloggerso short of getting update approval it's either ppa by default or opt-in ppa14:56
sgclarkyofel: used wrong key, thank you14:56
ScottKThat sort of thing has been turned down before.14:56
ScottKapachelogger: I say we update to feature freeze and then start cherry picking.14:57
apacheloggerwell regardless of the outcome of a TB decision we don't have that many options really14:58
shadeslayerScottK: except that cherry picking might result in confusing backtraces for upstream14:58
apacheloggerScottK: that can only be done if the big distros band together and put up a maintenance system14:58
apacheloggeri.e. that cherrypicking would have to be implemented upstream with more than one party involved otherwise that calls for screwuppery14:59
apacheloggeralso that potentially is a lot of work with some 60 potential frameworks that need watching14:59
ScottKshadeslayer: Upstream bought that confusion when they declined to support their releases.  Not my problem.14:59
ScottKapachelogger: Agreed.  If only upstream cared about maintenance.15:00
yofelshadeslayer: Ben made that point, and was completely ignored, so I guess they're fine with it15:00
apacheloggerScottK: that's where our perception differs I think we can be upstream just as much as upstream is upstream, in fact I think we should be upstream ;)15:00
ScottKObviously cherrypicking will be manpower limited, so it'd only be for severe issues.15:00
apacheloggerit's a lot like the dead upstream discussion we had a while back, distros patch k3b, but no one actually bothers enough to pick up maintenance (whatever that may mean) and roll a tarball of new fixes15:01
=== rdieter_ is now known as rdieter
ScottKAIUI upstream objected to stable branches even existing.15:03
apacheloggerhaven't seen that15:05
kubotufeed branches had 4 updates, showing the latest 315:06
kubotu::branches:: [kaccessible] r106 Release... (by Rohan Garg)15:06
kubotu::branches:: [kaccessible] r107 Fix control file to have proper fields... (by Rohan Garg)15:06
kubotu::branches:: [kaccessible] r108 Release... (by Rohan Garg)15:06
yofelIMHO, 'upstream' in this case should really be someone that knows the code. If $distro_dev becomes stable branch maintainer upstream without knowing what he's doing I'm not sure I'll happily use a point release coming from there15:07
* shadeslayer has a headache15:07
yofelI've seen plenty of breakage where someone from $distro1 upstreamed a patch which caused breakage in $distro215:07
yofelso a cherry-pick that's safe in $distro1 doesn't have to be safe in $distro215:08
yofel(not that upstream is in a much different position, just less likely to mess up)15:09
apacheloggeryofel: that's why it needs to be a joint effort15:09
shadeslayeroohh15:10
shadeslayerdebian/libkactivities-models1.abi.tar.gz.amd6415:10
yofelwat15:11
shadeslayeryofel: that's the base abi file for dh-acc to work15:11
shadeslayerto compare things against15:11
yofel*blink*15:11
yofeland where's that o.O?15:11
shadeslayerdebian git15:11
apacheloggereh15:12
kubotu::branches-next:: [ktextwidgets] r26 Bump depends versions (by Scarlett Clark)15:12
kubotu::branches-next:: [ktextwidgets] r27 Fix control file... (by Scarlett Clark)15:12
yofelwait, are we now adding binary files to the source o.O?15:12
shadeslayeryofel: in the debian packaging, supposedly, yeah 15:13
yofelI'm sorry, but that's crap -.-15:13
apacheloggergit likes binary files a lot :P15:13
sgclarkRiddell: plasma-workspace in bzr needs review when you have time15:15
yofelshadeslayer: that looks like a gzipped tar with a single json file in it to me...15:17
shadeslayermhm15:20
yofeland ofc. .abi.tar.gz is hardcoded in dh_acc15:22
yofelsupreme fun15:22
Riddellsgclark: I'll take a look if I get a chance but I think it's worth just going back to KF5 for now as that's got the new release and plasma will do later this week15:47
sgclarkRiddell: sorry what? upstream is going back to kf5? bzr revert should work then right?15:49
yofelRiddell: why is libkf5pty-data arch:any?15:53
kubotu::branches:: [kactivities] r121 * Merge with debian, no remaining changes... (by Rohan Garg)16:06
kubotu::branches:: [calligra] r98 * New upstream release (LP: #1326002)... (by Philip Muškovac)16:06
=== haudegen_ is now known as haudegen
sgclarkRiddell: I reverted to pre- name change so don't worry about reviewing it. I have name change backed up if that is not what you meant.16:08
shadeslayerActual votes cast thus far: 1616:11
shadeslayer~40% voting done16:11
kubotu::branches-next:: [plasma-workspace] r6 Rename - drop kf5... (by Scarlett Clark)16:12
kubotu::branches-next:: [knotifications] r35 Fix description-synopsis-starts-with-article for the binary ... (by Philip Muškovac)16:12
Riddellyofel: sounds like a mistake16:18
Riddellsgclark: just looked, that rename to drop the kf5 looks good16:20
Riddellsgclark: where did you get the idea to use libpkgs_addsubst_allLibraries ?16:20
sgclarksaw all those merges with it16:24
sgclarkRiddell: so go back to dropping the kf5?16:24
sgclarkRiddell: also the merges I have done , the debian version all have allLibraries16:26
ScottKThe problem with libpkgs_addsubst_allLibraries is that if you have one lib installed once you install the -dbg it pulls all the other libs too.16:30
ScottKInstalling a -dbg shouldn't pull in other libs.16:31
Riddellsgclark: ah so must be a new feature debian has got into using16:36
santa_Riddell: the allLibraries is something widely used in the debian packaging for packages which have a lot of libraries .e.g. kdepimlibs16:37
RiddellScottK: I'm also not convinced it's any easier to maintain or clearer to read16:37
santa_I mean imagine the control file of kdepimlibs without using that variable16:37
santa_perhaps the frameworks libs are too small to use this feature16:37
santa_in any case if we don't use it for frameworks it's not a big loss imo16:38
sgclarkworkspace is rather big compared to the rest of kf516:39
ScottKKF5 ~= kdelibs, so no surprise.16:39
sgclarkdoesn't matter to me :) I just recall we are trying to get debian to adopt our kf516:39
santa_well sometimes they use ${allLibraries} sometimes they don't16:40
santa_the main point of using that in my opinion is16:40
santa_1. not forgetting to add libs when a new one appears16:40
santa_2. not having to change everything when a library breaks abi and the packages have to be renamed16:41
santa_about 2 it would make sense to use it in okteta, for instance16:41
santa_however debian doesn't, but it should16:42
ScottKMy objection is only for -dbg depends.  Installing -dbg shouldn't pull in more libs.16:42
ScottKFor other things, it may be fine.16:42
santa_that's a different story16:42
santa_we could downgrade the -dbg depends to suggests16:42
santa_in any case that's a different issue, which exists with our without ${allLibraries}16:43
santa_I think you guys have a point when you say it shouldn't pull everything16:44
lordievaderGood evening16:45
santa_evening16:46
lordievaderHey santa_, how are you?16:46
santa_good, fine thanks16:47
santa_sgclark: ktexteditor has a dupe changelog entry16:51
sgclarkok16:55
kubotu::branches-next:: [kjobwidgets] r27 Fix -dev depends... (by Scarlett Clark)17:12
shadeslayeryofel: any idea why /usr/share/kde4/apps/kajongg/kajongg.py does something like from qt import QObject, usingQt417:25
shadeslayerinstead of from PyQt4 import QObject17:25
yofelno17:26
shadeslayerajj17:27
shadeslayer    new: qt.py and qt4.py bundling all Qt imports17:27
shadeslayerhurray17:27
yofelo.O17:27
shadeslayer28a90a9d58d44c2b229355cd82599d1b9b4256f8 in kajongg17:27
shadeslayeralso has a debian.control in the source code17:27
shadeslayer\o/17:27
yofeldo I smell qtchoosery17:27
shadeslayeryofel: yes17:28
* yofel runs17:28
shadeslayer:'(17:28
shadeslayerhttp://paste.ubuntu.com/7581733/17:30
yofel...17:32
shadeslayerand ofcourse it's not installed17:33
shadeslayer\o/17:33
shadeslayerI'm trying not to kill myself right now, because I can't figure out why the freaking qt.py file is not installed17:46
* yofel stares at his kmail window that has pkg-kde-talk@lists.alioth.debian.org as recipient and a huge white space in it...17:47
shadeslayer:D17:47
shadeslayerah17:48
shadeslayerahaha17:48
* shadeslayer needs a drink now, even though I still have a hangover from last night17:48
shadeslayerhttps://projects.kde.org/projects/kde/kdegames/kajongg/repository/revisions/985bf653088e53483722009f6277dd439423fbfa17:49
yofellol17:49
shadeslayerhow was this not freaking picked up17:49
santa_<kubotu> ::branches-next:: [kjobwidgets] r27 Fix -dev depends... (by Scarlett Clark)17:50
santa_where is this branch, I don't see it in launchpad17:51
santa_?17:51
shadeslayerwhich branch17:51
santa_that one of kjobwidgets having that commit "r27 Fix -dev depends..."17:52
shadeslayerpad.lv/~kubuntu-packagers17:52
shadeslayeroh yay17:53
yofelsanta_: lp:~kubuntu-packagers/kubuntu-packaging-next/kjobwidgets17:53
santa_so how is your workflow with those branches are you going to merge them into this ones https://code.launchpad.net/kubuntu-packaging or what?17:55
yofelnot quite sure yet, apachelogger will know more17:57
sgclarkafaik no, all kf5 will now go into the next18:01
kubotu::branches:: [calligra] r99 Fix syntax of not-installed ... (by Philip Muškovac)18:06
yofelsanta_: TBH, the ultimate goal would be to move all the packaging to alioth before it becomes a question whether to move it back or not, not sure how that'll work out for you18:10
kubotu::branches-next:: [kbookmarks] r28 * Refresh libkf5bookmarks5.symbols ... (by Philip Muškovac)18:12
kubotu::branches-next:: [kio] r34 Patch symbols... (by Scarlett Clark)18:12
santa_yofel: that would mean I wouldn't be able to work on it, but that's [k]ubuntu's business18:13
yofelshadeslayer, apachelogger, Riddell, ScottK, sgclark: anything you want to add before I send this? http://paste.kde.org/p87y1jgp718:46
shadeslayer+118:47
sgclark+118:54
santa_so, farewell to any kubuntu's contributions from me I'm afraid18:54
sgclarkdon't believe I have access to pkg-kde though18:54
yofelsanta_: well, we're not moving everything immediately, and we could still merge changes from anongit clones18:54
yofelsgclark: they're fairly reasonable if you have people backing you, so adding you shouldn't be a problem18:55
sgclarkok18:55
santa_yofel: yes, the question is, will they allow you to merge any change from me? because I don't think so18:56
yofelyou could start out by hanging out in #debian-qt-kde@irc.oftc.net18:56
yofelsanta_: I don't think it's a problem as long as the change is sane and we review it18:56
sgclarkok in there18:59
santa_yofel: http://paste.kde.org/p0orufxa219:02
santa_and he was just asking for advice, not actually forwarding anything from me19:02
yofelI read that when it happened.. maybe not using names would help that -.-19:03
kubotufeed branches had 4 updates, showing the latest 319:07
kubotu::branches:: [kajongg] r82 * Merge with debian, no remaining changes... (by Rohan Garg)19:07
kubotu::branches:: [kamera] r123 * Merge with Debian, no remaining changes... (by Rohan Garg)19:07
kubotu::branches:: [kanagram] r119 * Merge with debian, no remaining changes... (by Rohan Garg)19:07
kubotu::branches-next:: [kio] r35 Remove MISSING i386 ... (by Scarlett Clark)19:13
kubotu::branches-next:: [kio] r36 Fix broken -dev depends ... (by Scarlett Clark)19:13
Riddellyofel: only 1 master branch? no kubuntu branch?19:18
yofelRiddell: 1 master and the series branches, you can have unreleased stuff in the utopic branch if it's specific to us19:19
yofelu+1 would then start off as a branch of utopic19:19
yofelor as  a merge of utopic and master19:20
Riddellmm, ambitious, I like it19:23
geniiDoes Kubuntu ppa use some different version of os-prober or something? Prior to 14.04 release, grub listed my Kubuntu as actually Kubuntu, then after release, it goes to saying Ubuntu.19:27
ScottKgenii: It's a known change in 14.04.19:27
* ScottK doesn't recall why.19:27
geniiScottK: I just found it extremely odd, and was curious :)19:28
yofelme neither, but I remember the UEFI issues in 13.10, maybe related to some more 'ubuntu' hardcoding in the stack19:28
santa_sgclark: are you working on the kf5 ftbfs'es? may I help?19:37
yofelsanta_: who's working on what is tracked at https://notes.kde.org/p/kubuntu-ninjas-frameworks19:38
shadeslayeryofel: genii ScottK it was because the uefi entry said ubuntu and looked for ubuntu in GRUB, and keeping the delta was just too much work19:39
shadeslayerbecause it could cause issues in the future19:39
yofelok, so it was that19:39
geniiAaaaah, OK19:39
shadeslayeratleast that's what I recall apachelogger saying19:39
* yofel will send the mail in 20min if there's no more response19:40
santa_yofel: so mind if I add myself for kactivities?19:43
yofelsanta_: sure, instead of ppaX just post your merge request or the bzr branch with your changes so we can find it19:45
yofelonce you're done, until then put WIP19:45
santa_allright19:45
yofelmail sent20:01
kubotu::branches:: [calligra] r101 release to utopic (by Philip Muškovac)20:07
santa_frameworkintegration amd64 build should be retried20:31
sgclarkdone20:34
kubotu::branches:: [kactivities-work] r33 Remove duplicate changelog entry.... (by Jose Manuel Santamaria Lema)21:07
kubotu::branches:: [kactivities-work] r34 Add kf5-kio-dev build depend. (by Jose Manuel Santamaria Lema)21:07
kubotu::branches:: [kactivities-work] r35 Update symbols file. (by Jose Manuel Santamaria Lema)21:07
kubotufeed branches-next had 12 updates, showing the latest 321:12
kubotu::branches-next:: [kparts] r24 * Refresh libkf5parts5.symbols ... (by Philip Muškovac)21:12
kubotu::branches-next:: [knewstuff-work] r22 Fix control file, re-adding the -dev package. (by Jose Manuel Santamaria Lema)21:12
kubotu::branches-next:: [knewstuff-work] r23 Install the *.pri file in the -dev package. (by Jose Manuel Santamaria Lema)21:12
=== PaulW2U_ is now known as PaulW2U
josethanks for the highlights, kubotu...21:45
sgclarkI reviewed santa_ merges and they look good, I just don't know how to do a merge, anyone available to do that? Holding up the works.22:08
yofelsgclark: go to your local checkout/branch of the branch you want to merge, then run the command the merge page shows at "To merge this branch:"22:09
yofelIIRC you'll then have to commit the merge, push and you're done22:10
shadeslayersgclark: can you point me to the url?22:10
yofelshadeslayer: frameworks pad has the urls22:10
sgclark^22:11
shadeslayer^^22:11
shadeslayerah ok22:11
* shadeslayer throws a keyboard at his internets22:11
soee:o22:14
yofeljose: do you mind? I'm sure apachelogger can hide the names...22:14
yofellaunchpad now has inline diff comments for merges o.O?22:15
yofelwow22:15
joseyofel: not a problem :)22:16
joseyeah, I'm in Beta and find that awesome!22:16
shadeslayerdidn't realize people were still working on Launchpad22:33
santa_sgclark: thank you22:40
sgclarksanta_: np, and thank you22:41
valorieshadeslayer: I've not gotten a ballot yet22:51
valorieat least searching for "ballot" I get nothing22:55
valorieafk for a bit to run22:59
kubotufeed branches-next had 6 updates, showing the latest 323:13
kubotu::branches-next:: [kdelibs4support-work] r32 Update kio metainfo install path. (by Jose Manuel Santamaria Lema)23:13
kubotu::branches-next:: [kdelibs4support-work] r33 Update symbols file. (by Jose Manuel Santamaria Lema)23:13
kubotu::branches-next:: [kdelibs4support-work] r34 Rename libkf5kdelibs4support5.lintian-overrides as libkf5kde... (by Jose Manuel Santamaria Lema)23:13

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!