[04:10] err... in kdeplasma-addons somehow scim stuffs are back [04:11] fixeroo-ing [04:15] done === palasso_ is now known as palasso [11:34] bshah: regarding kdeplasma-addons it had a broken merger due to previous changes [11:34] oh [11:35] clivejo: still broken? or fixed? [11:35] I dont know [11:35] Phil added those files to the install file [11:35] http://anonscm.debian.org/cgit/pkg-kde/plasma/kdeplasma-addons.git/commit/?h=kubuntu_unstable&id=192a9daf4dec90a34391f79c5f4e6fc4f661923d [11:36] this should not be in _unstable for sure.. [11:36] as in master it was removed [11:36] how is it removed? [11:37] was moved to plasma-workspace [11:37] err.. [11:37] plasma-desktop [11:37] clivejo: https://quickgit.kde.org/?p=kdeplasma-addons.git&a=commit&h=c24ceb9eaf11795b750118c68a479da3303de2bd [11:52] sitter, Riddell: does kubuntu care about https://launchpad.net/ubuntu/+source/plasma-widget-mail/0.3.1-0ubuntu9 ? [11:53] doko: no it's kdelibs4 stuff. note neither me nor sitter are spending much time on kubuntu currently [11:57] Riddell, yeah, I noticed :-/ is there still anybody caring? [11:58] doko: you can try sgclark, yofel, clivejo [12:00] doko: what the problem with it? [12:00] that's not even in the packageset, so we "technically" never even supported that? [12:00] would be one reason why we didn't know about it at least [12:01] clivejo, well, see the link above [12:01] ah FTBFS [12:02] clivejo, yofel: there's also a problem with kde4libs (main), wanting some dozen new deps in main ... see http://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg [12:02] bshah, clivejo: FWIW, I have no idea why I added scim back - maybe it got in during the debian merge..? [12:02] maybe... [12:03] yofel: I dont know either, just got fed up with KCI blaming me for it [12:03] I attempted to fix it [12:03] the changelog is a mess [12:04] doko: hm, we'll look at that. That's far too much [12:05] yofel: how come there is so much UNRELEASED stuff? [12:05] we never released it? [12:05] should we not start getting it released? [12:06] sure, find someone that does it [12:06] I'll have time over the weekend - I hope [12:07] I wonder if we should tag frameworks as released so we can work on 5.19 [12:07] I can generate packages from a tag.. [12:09] doko: regarding time, there's at least 3 of us devs left that care. But with all of us doing this in our free time only and working on some 300 packages things are not exactly going well. [12:09] we should be able to reduce that amount next release - I hope... [12:11] doko: and regarding plasma-widget-mail.. kill it please [12:11] yofel, please file a bug report to remove it, and subscribe ubuntu-archive [12:12] ack [12:15] yofel: I dont think I can do anything more with apps, the remaining ones are beyond me. Anything else I can do? [12:15] clivejo: set frameworks to released, tag it and start with 5.19 [12:16] or maybe a rebuild test would be a good idea before that [12:16] I would have to do that anyway [12:17] set framewords to release, and tag it, I dont know how to do that [12:18] ok, I'll do it [12:19] if you walk me through it then Ill know for again :/ [12:19] I can c&p what I do myself at least [12:19] oh right [12:20] yeah please c&p [12:20] testing 14.04 would be a thing - if you can afford the bandwidth [12:20] in kubuntu-automation: /git-clone-all -t /tmp/fwrb/ -r frameworks [12:21] 14.04? [12:21] clivejo: 14.04.4 release is today [12:23] davmor2: I’m dyslexic, numbers mean very little to me, especially remembering them! What is at 14.04.4? [12:24] clivejo: http://iso.qa.ubuntu.com/qatracker/milestones/356/builds [12:24] clivejo: the forth point release for trusty LTS [12:24] ah [12:25] I was wondering why the bot was announcing iso builds [12:25] That explains it [12:26] clivejo: and then next week 16.04 beta1 testing kicks in \o/ [12:26] Im afraid all of my boxes are on Senile [12:27] yofel: fwrb = frame works re build? [12:28] right [12:28] I wish I could watch you [12:28] I bet you have tons of tricks to save time [12:31] not really... or at least nothing I conciously think about. I do a lot of on-the-fly shell scripting if anything [12:34] * highvoltage warps in [12:35] no running in the hallways! [12:35] rules are there to be broken. [12:35] hence the warp? ^^ [12:37] yofel: are you still cloning? [12:37] just finished [12:38] next: cd /tmp/fwrb; do-all git checkout kubuntu_xenial_archive; do-all git-buildpackage-ppa -s 50 [12:38] oh dang, failing on uscan [12:38] highvoltage: davmor2 is looking for 14.04.4 testers :) [12:38] cause 5.19 is out? [12:38] yeah, let me figure out an rsync command [12:39] ppa50 ? [12:39] or is that a special number? [12:39] davmor2: cool, I'm syncing kubuntu 14.04.4 20160217.1 and will give it a spin through its test cases [12:39] $something_that's_definitely_higher_than_anything_in_the_ppa [12:39] = 50 [12:39] highvoltage: awesome [12:39] Id pick 99 [12:39] :P [12:41] yofel: is that a bug in uscan, or designed that way for a reason? [12:41] I think there's a bug report in debian for that [12:42] IIRC [12:43] oh, International Integrated Reporting Council (IIRC) CEO Paul Druckman plans to step down this year. [12:44] lol [12:44] yofel: do you do a package list refresh? [12:44] no, the current one is 5.18, is it not? [12:45] * yofel stares at the screen while oxygen-icons downloads....... [12:45] how did you so the rsync? [12:46] do [12:46] ovidiu-florin: ping? [12:46] teach me master yoda [12:48] I'll tell you that once it's done [12:48] :/ [12:49] ae you cheating? :P [12:50] rsync -avh ftpubuntu@depot.kde.org:/srv/ftp/pub/kde/stable/frameworks/5.18/ build-area; mv build-area/portingAids/* build-area/ [12:50] also fetches the zips though if you're concerned about bandwidth (I'm not) [12:50] how do I edit kubuntu.org? https://www-admin.kubuntu.org/ isn't working [12:51] Riddell: https://kubuntu.org/wp-admin - you'll need to be in the webadmin team on LP [12:52] meh, stupid uscan [12:52] yofel: so you are just grabbing a copy of all the frameworks tarballs? [12:52] yes [12:53] yofel: I think I staged those so should have them all locally [12:53] for me Id just have to pull all changes from debian git [12:54] right, we'll I didn#t [12:54] yofel: just thinking :P [12:54] uscan workaround: cd build-area; for file in *.xz; do ln -s $file ${file%-*}_5.18.0.orig.tar.xz; done; cd .. [12:57] if I do a "do-all git pull"; would that work? [12:58] eak qtbase5 has another update today [13:00] yofel: Im gonna go for lunch, but post the commands so I can see the process [13:00] sure [13:00] I think I see what you are doing [13:02] right now running git-buildpackage-ppa again [13:02] some tarballs need renames though, so I'll do that once the run completes and re-run it [13:08] Hiyas all [14:17] is it normal for kubuntu to have the lock screen enabled in the live session? [14:18] I'm fairly certain that's a bug that we never fixed [14:19] highvoltage, just turn itoff if it bothers you :-) [14:44] morning [15:02] highvoltage: can't be as bad as tanglu which I just discovered has lockscreen and blank password doesn't work [15:02] ximion: how do I get round that? ^^ [15:08] Riddell: on the live-cd? [15:08] blank password should work, but actually, the lockscreen should be disabled [15:09] are you using the development version (dasyatis, T4), or the stable version (chromodoris, T3) [15:09] in the latter case, try "live" as password [15:09] ximion: stable, chromodoris, on virtualbox [15:09] ximion: I see you don't have uefi support in the images, do you get many complaints about that? [15:11] yes, which is the reason why it's a high priority task for the next release: https://tracker.tanglu.org/T159 [15:11] UEFI on the live-cd works well already, but both installers have problems installing Grub correctly [15:13] while most people are fine with disabling UEFI, it's annoying to those who are using it in e.g. multiboot scenarios, and it's generally not nice if it doesn't work - so T4 will have UEFI support, secure boot is a different beast though, and much more complicated to do it right [16:02] clivejo: so, rebuild done and things look fine. Now to the releasing: [16:02] do-all sed -e '1s/UNRELEASED/xenial/' -i debian/changelog [16:02] do-all git commit -am \"Release to xenial\" [16:02] do-all git-tagpkg [16:02] do-all git push origin --follow-tags [16:02] the sed stuff can probably be done with dch -r as well or so [16:04] who broke kio!! [16:04] yofel :P [16:11] I break all the things [16:13] http://qa.kubuntu.co.uk/ppa-status/frameworks/build_status_5.18.0_xenial.html [16:13] looks ok [16:15] clivejo: push done, you can start with 5.19 if you want [16:15] wasn't able to boot into 16.04 after the last upgrade , the recovery kernel and the older kernels fail as well and the journalctl log wouldn't load in the root VT prompt [16:16] clivejo: I wonder if just merging in master for all repositories would make sense? [16:16] should be next to no diff now that we merged already? [16:24] debian already have 5.19 done [16:24] I merged kio as maxy done the new kio gui package better that I did [16:28] then this would be an application of "do-all git merge origin/master" ? [16:28] and figuring out the failures [16:29] + adding changelogs [16:35] oh good lord [16:37] this would be the last time that we would touch frameworks at all, so it might be worth it [16:37] but is it wise to mass merge them? [16:38] I guess try it and see how many conflicts pop up! [16:38] well, you'll have to still read the diff [16:38] but you can also 'do-all git diff' that ^^ [16:39] you want me to do it :P [16:39] give me enough rope and Ill hang myself! [16:41] as I said earlier, I love doing a lot of on the fly scripting :P [16:41] you can just do it by hand if you want [16:41] frameworks is small enough that it's still reasonable [16:49] Ill look later, Im in a bit of a foul mood [16:50] just got all four seasons in the space of an hour [16:53] be happy, here I had grey sky and light mist for 3 days straight now. Kind of depressing -.- [16:56] I was happily enjoying the sunshine, sawing sticks then there was heavy rain, sleet snow and driving wind [16:56] got soaked to my skin [16:57] mparillo: did you mark the iso testdays that you did as passed? [16:59] highvoltage: ^ [17:13] yofel: highvoltage: I did, but I did test on a prior release candidate, so my test is no longer on http://iso.qa.ubuntu.com/qatracker/milestones/356/builds [17:13] ok, thanks for testing [17:13] one of the other QA folks did some testing for the new images [17:14] Basically, it was brief. VMware using their easy install. Tested maybe two apps on each after successful install. [17:53] Trying to run Kubuntu Xenial in a VM using KVM. It reaches the desktop, but won't install. [17:54] Error message: libvirt did not detect any UEFI/OVMF firmware image installed on the host === who_da_fly is now known as superfly [18:32] Somebody solved the not installing problem mentioned earlier. Thank you! Xenial is now installing in KVM! [18:48] yeehi: I thought this was the root cause of the Xenial install bug: https://bugs.launchpad.net/hundredpapercuts/+bug/1529450 [18:48] Launchpad bug 1529450 in ubiquity (Ubuntu) "[master] AttributeError: 'PageKde' object has no attribute 'get_secureboot_key'" [Critical,Triaged] [18:50] Thanks, mparillo Why do you love Plasma / Kubuntu? [18:57] Linux in general is what I need to run inside a VM on my work computer. Linux in general allowed me to recover my son's laptop after the Win7 to Win10 upgrade failed. Kubuntu feels to me the lightest KDE distro, and the folks here and on kubuntuforums.net are the best. So I help with Plasma 5, even though it is only now approaching Plasma 4. [18:58] yeehi: But is sounds as you are successfully installing even though the underlying bug is not solved? [18:59] The daily today installed beautifully, mparillo! [18:59] I was very happy [19:08] TY. I will try myself again soon then. [19:41] clivejo: ping [19:41] ong [19:41] sgclark: pon [19:42] are you working on kdepim-runtime? [19:42] not any more [19:43] ok [19:55] hmmm FTBFS kdesdk-kioslaves [19:59] yofel: I merged master -> xenial_archive and I think all of them have conflicts :( [19:59] :S [20:00] mainly changelog, control and rules [20:01] but a few symbols and install files to make things interesting [20:01] wait, should I stage them first? [20:02] if I bumped to 5.19 that *might* fix a few of the control file conflicts? [20:05] uh what is going on? kf5 was already merged [20:05] clivejo: just stage it normally then. Not worth the trouble [20:06] actually I think if I staged first it would get rid of a lot of these conflicts [20:06] most are : [20:06] <<<<<<< HEAD [20:06] extra-cmake-modules (>= 5.18.0~), [20:06] ======= [20:06] extra-cmake-modules (>= 5.19.0~), [20:06] >>>>>>> master [20:06] I don't think so.. but I wonder what the conflict in rules would be? [20:06] why are you merging kf5 again?!?! [20:07] ah yeah, that'll happen [20:07] sgclark: I thought merging would be easy... [20:07] well, it's not [20:07] I a mso confused, do you mean to sync? [20:07] no [20:08] kf5 merges have already been done, I am so confused ight now [20:08] the other problems are symbols [20:08] apps however still have stuff to be done. [20:08] well yes. So I thought just merging in 5.19 should be easier than doing stuff ourselves [20:08] well, wrong idea [20:08] lets revisit that thought next release [20:08] oh. [20:08] I see. [20:09] ours symbols are labelled 5.18+git.... , debians are 5.19 [20:09] yeah symbol headers always seem to conflict [20:09] and the version bumps will be issue in control [20:10] ah right.. [20:10] I dont mind going through those the fixing manually [20:10] I should not give advice while being absent minded [20:10] haha [20:10] just stage it yourself. Will be a lot less work [20:10] note: I was already wrong once today XD [20:10] yofel: is there a way to undo the merge locally, or should I just clear the folder and git clone again# [20:11] well I merged kdenlive and it has repo in an off infa svn ... that was fun.. NOT [20:11] clivejo: git reset --hard origin/kubuntu_xenial_archive should undo stuff [20:12] should or definitely ?!? :P [20:12] it won't undo untracked stuff, and I'm not a 100% expert on git behavior [20:12] yofel: not sure what to do about kdesdk-kioslaves it is not packaging but and actual build fail. [20:13] HEAD is now at 6604e11 Release to xenial [20:13] file an upstream bug I guess.. and we'll skip it in the upload [20:13] yofel: ok [20:13] sgclark: could that be the debian/tmp thingie again? [20:15] clivejo: mm not sure what you mean. this fails with recipe svn.cpp not sure that has anything to do with debian/tmp [20:15] $(overridden_command) --destdir=debian/tmp [20:16] totally unrelated [20:18] ok [20:18] no product for kdesdk-kioslaves... on kde bugs [20:23] yofel: is there a way to delete a super seceded build in a PPA, I messed up and left an epoch that should have been removed. And now a new release will not publish. [20:24] yes, wait like a random time up to half a day until the janitor deletes the files [20:25] yofel: staging-upload script is failing [20:25] log please [20:26] in bump-build-dep-versions [20:26] Expecting property name enclosed in double quotes: line 75 column 1 (char 2736 === doko_ is now known as doko [20:26] o.O [20:29] did I mention everything seems to be going wrong for me today? [20:30] now you did [20:30] yofel: https://paste.kde.org/pkjl3r4rg [20:33] urgh [20:33] clivejo: remove the comma at the end of dev-package-name-lists/frameworks-xenial.json line 75 [20:33] stupid json being over pedantic [20:40] ok its staging at the moment [20:40] should I push that fix to KA? [20:42] this script doesnt seem to be bumping build depends [20:42] I thought it outputs a diff? [20:45] nope, its not bumping them :/ [20:47] yes, push it [20:47] the new script hardcodes the versions in the json files [20:47] unless you update *that* first, it won't do anything [20:47] and IIRC there's no automatic way to update those yet [20:48] sed is your friend [20:49] what json files? [20:49] the one you just fixed [20:50] "_comment": "This file was generated automatically by dev-package-name-list." [20:50] ah [20:50] does that work *before* you upload stuff yet? [20:50] LOL Ive deleted the workspace folder [20:51] should I bump these all manually? [20:51] as I said, sed is your friend [20:51] I havent pushed the comma fix yet [20:51] or use perl if you're crazy [20:51] find and replace? [20:52] or that [20:53] libkf5identitymanagement-dev is apps [20:53] bump thats to 15.12.1? [20:54] I guess not, we havent finished those yet, so wont be in the staging PPA [20:55] don't [20:55] actually [20:55] we'll have to make sure apps deps are not higher than 15.08 [20:55] or stuff won't build in the archive [21:01] I should probably throw stuff into a clean ppa before uploading.. [21:14] its currently 15.12.0 [21:14] you must have moved that to the staging PPA? [21:14] Ill bump it to 15.12.1 [21:16] and pushed [21:17] lets try the staging script agian [21:17] thats better [21:22] yeah, but that will definiely fail in the archive [21:23] so that's something to be aware of when uploading [21:39] why are we working on new stuff when we have not finished old stuff? [21:40] clivejo: marble needs symbols update. [21:41] so does libkf5kipi [21:41] and again with libkf5kface [21:57] hummmmm Debian only do symbols for amd64? [21:57] ask them? [21:58] clivejo: did you research the lintain error on ktp-text-ui? if not you need to. [21:58] # SymbolsHelper-Confirmed: 4:15.12.0 amd64 [21:58] libmarblewidget-qt5.so.23 libmarblewidget-qt5-23 #MINVER#