[00:01] don't recall testing them. maybe the main (official) ubuntu does [00:02] I think some people test them sometimes [00:03] but in general if they boot and can be successfully installed, not much changes until closer to the alpha [00:03] I see. Back to packaging then :) [00:11] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [00:11] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kopete build #13: FIXED in 22 min: https://kci.pangea.pub/job/xenial_stable_kopete/13/ [00:12] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [00:12] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_kopete build #45: FIXED in 23 min: https://kci.pangea.pub/job/zesty_stable_kopete/45/ [00:13] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [00:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kopete build #198: FIXED in 24 min: https://kci.pangea.pub/job/xenial_unstable_kopete/198/ [00:14] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [00:14] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kopete build #134: FIXED in 25 min: https://kci.pangea.pub/job/zesty_unstable_kopete/134/ [00:14] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kstars build #91: NOW UNSTABLE in 24 min: https://kci.pangea.pub/job/artful_unstable_kstars/91/ [00:17] Regardind kstars, one issue is that the software b-d requires a higher version number than what exists and there's a patch in VCS but not llisted in VCS. These are both upstream fixes right? [00:18] The version number of libindi-dev should be properly written maybe. And the patch might have been deleted [00:23] increasing the libindi depends version to 1.4 would cause kstars to fail to build at the moment, and as it's only optional don't really want to do that. it will fix itself if/whe we get a new libindi into artful [00:25] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kopete build #33: STILL UNSTABLE in 37 min: https://kci.pangea.pub/job/artful_unstable_kopete/33/ [00:26] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [00:26] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kopete build #24: FIXED in 37 min: https://kci.pangea.pub/job/artful_stable_kopete/24/ [00:26] clivejo: why was the stars patch disabled? [00:31] Well, increase the version number would fail because the think doesn't exist yet :) [00:32] The patch I worked on was on dolphin, not kstars, so I have no clue about that [00:32] I thiink I'll migrate to pbuild for good. God dammit, sbuild is always troublesome installing [00:35] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [00:35] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kdenlive build #63: FIXED in 27 min: https://kci.pangea.pub/job/xenial_stable_kdenlive/63/ [00:39] eek! 1:40 am here [00:39] Goodnight all I think :) [00:40] Good night [00:46] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [00:46] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kdenlive build #494: FIXED in 38 min: https://kci.pangea.pub/job/xenial_unstable_kdenlive/494/ [00:56] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [00:56] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kopete build #34: FIXED in 28 min: https://kci.pangea.pub/job/artful_unstable_kopete/34/ === santa is now known as Guest34375 === Guest36807 is now known as lordievader [07:35] Good morning [07:49] morning [08:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1583: SUCCESS in 1 min 3 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1583/ [08:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1583: SUCCESS in 1 min 3 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1583/ [08:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1583: SUCCESS in 3 min 56 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1583/ [08:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1583: SUCCESS in 4 min 13 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1583/ [09:09] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [09:09] -kubuntu-ci:#kubuntu-devel- Project zesty_stable_kscreenlocker build #80: FIXED in 20 min: https://kci.pangea.pub/job/zesty_stable_kscreenlocker/80/ [09:09] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [09:09] -kubuntu-ci:#kubuntu-devel- Project xenial_stable_kscreenlocker build #21: FIXED in 20 min: https://kci.pangea.pub/job/xenial_stable_kscreenlocker/21/ [09:10] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [09:10] -kubuntu-ci:#kubuntu-devel- Project artful_stable_kscreenlocker build #51: FIXED in 20 min: https://kci.pangea.pub/job/artful_stable_kscreenlocker/51/ [09:13] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [09:13] -kubuntu-ci:#kubuntu-devel- Project zesty_unstable_kscreenlocker build #192: FIXED in 23 min: https://kci.pangea.pub/job/zesty_unstable_kscreenlocker/192/ [09:13] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [09:13] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [09:13] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kscreenlocker build #389: FIXED in 23 min: https://kci.pangea.pub/job/xenial_unstable_kscreenlocker/389/ [09:13] -kubuntu-ci:#kubuntu-devel- Project artful_unstable_kscreenlocker build #65: FIXED in 23 min: https://kci.pangea.pub/job/artful_unstable_kscreenlocker/65/ [12:18] Hello all o/ [12:27] good morning/afternoon everyone [12:27] acheronuk: ping? [12:29] pong? [12:29] akonadi? [12:29] not yet [12:29] * acheronuk got sidetracked [12:30] I would like in the first place to move frameworks 5.35 to the regular backports ppa [12:30] right now landing also provides krita [12:30] do you mind if I copy -landing to the regular backports ppa including krita? [12:31] and plasma 5.10.2 in there as well [12:31] for xesty [12:31] *zesty [12:31] yes, may I copy everything then? [12:32] krita is a bugfix on what is already in there, so seems ok to me [12:32] I'm using -landing on my laptop for the record [12:32] zesty with -landing I mean [12:33] acheronuk: so, proceed (y/n)? [12:33] yeah, so you have test the plasma update somewhat then [12:33] I would say so [12:34] copying then. we can always fix issues later if we find any [12:34] To be honest, I was wondering whether to ping you and ask if it worked ok for you, then copy this weekend. so you more or less just beat me to it [12:35] if there are no anguished screams of breakage on forums and social media, I'll do a website post later [12:37] I'm going to copy frameworks 5.35 for xenial too (which was already tested, by me and got positive feedback from mparillo) [12:39] santa_: yes. there is additional stuff in landing for xenial. apps like konversation, krita again, krusader, kdevelop [12:39] from brief testing I *think* they are ok [12:40] ok [12:40] I can help testing (I think) if needed :+1: [12:41] I just built digikam 5.5 for xenial in staging-misc, but may want to test that and maybe wait for digikam 5.6. the release of which is imminent, as was tagged in git a few days ago [12:42] gsilvapt: thank you. this is copying stuff in the backports-landing PPA to backport PPA for both Zesty and Xenial. If you have an install or VM of those, testing would be great [12:43] What can we do regarding those packages that are now failing because we changed b-d and they do not exist in previous releases? kajongg, kmag, kstars for instance [12:43] I have space for a VM, yes. I can install, test and uninstall if needed. However, I might need some guidance as I never did any testing [12:43] faling where? yellow is not a 'fail' [12:44] Depends which one you're looking at. kajongg only has yellow warnings but kstars is actually failing because the b-d does not exist in Xenial. [12:45] Actually it's the other way around [12:45] Link to the 'failure' please? [12:46] 1 second, I'm trying to find them [12:48] kmag has a different b-d in xenial: https://launchpadlibrarian.net/324314065/buildlog_ubuntu-xenial-amd64.kmag_4%3A17.04.2+p16.04+git20170616.2252-0_BUILDING.txt.gz [12:49] We discussed this last night. I was told the package had a different name for previous releases and thus it can't find the package in previous releases other than artful [12:49] Now I'm looking at kajongg because there's clearly missing a dependency. Not sure if it exists in xenial or if I missed it [12:49] oh. unstable kajongg needs a new twisted only found in artful. not going to mess with backporting that for now [12:50] Exactly, that's my problem. most of the game packages I've helped porting have packages that either do not exist in previous builds or had different names before. [12:50] backporting may be hard but there's no way to figure out the name of the packages (AFAIK) [12:51] most exist. and can be found from cmakelists or the build output and a bit of detectivework [12:56] gsilvapt: want to refresh the patches for kstars? [12:57] clivejo: looking at it, I think it may need a bit more than a 'refesh'. but no harm looking [12:57] kmag is oddly still looking for some Qt4. weird [12:58] have you guys already fixed the thing with my dolphin patch? [12:58] I "think" I just disabled them to get it to build [12:58] fixed the thing? [12:59] it was failing to apply in unstable because I got an upstream patch to fix a test [12:59] yeah, I removed the patch [12:59] in _unstable [13:00] thanks [13:00] santa_: your fuzzy compare patch for kstars?? [13:01] ? [13:01] would you mind taking a look to see if it is still relevant in unstable? [13:01] how are apps 17.04.2 coming along? [13:02] I fixed ~4 autopkgtrollings yesterday [13:02] santa_: they made some changes to those lines I'm not 100% sure equivalent changes can be substituted in or are needed [13:02] acheronuk: did you look at the seed after those new packages made it it? [13:03] clivejo: they should already be in there from when I last updated the seed from a clone all [13:04] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmag build #219: STILL FAILING in 4 min 0 sec: https://kci.pangea.pub/job/xenial_unstable_kmag/219/ [13:04] clivejo: http://bazaar.launchpad.net/~kubuntu-dev/ubuntu-seeds/kubuntu.artful/revision/1360 [13:05] that commit, when it was apps 16.12 in git [13:05] can we put that link on qa.kubuntu? [13:05] can put what we like on there if it's useful [13:06] be useful to me, as I can never find that link! [13:06] Firefox remembers for me.... [13:14] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmag build #220: STILL FAILING in 5 min 7 sec: https://kci.pangea.pub/job/xenial_unstable_kmag/220/ [13:23] ff is not for remembering links [13:24] but for constant segfauts and crashes :p [13:24] for me it does both [13:24] sometimes..... [13:27] gsilvapt: xenial seems to have an old version of libqaccessibilityclient which I think is too old and not pulling in some of the legacy qt4 depends that kmag seems to oddly need [13:27] going to try building the zesty version for KCI build to test [13:36] Sorry, I was having lunch. I take care of that later, if that's okay. i only need to run quilt refresh in kstars? [13:36] santa_, I've made a merge request recently that should fix that. I'm not 100% certain it is done properly but... [13:43] quilt refresh won't do it, as the code to patch has changed. not just the it's context [13:49] I need to leave for a wile, I'll be back [14:08] -kubuntu-ci:#kubuntu-devel- Yippee, build fixed! [14:08] -kubuntu-ci:#kubuntu-devel- Project xenial_unstable_kmag build #221: FIXED in 12 min: https://kci.pangea.pub/job/xenial_unstable_kmag/221/ [14:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » master build #1584: SUCCESS in 59 sec: https://kci.pangea.pub/job/mgmt_docker/label=master/1584/ [14:46] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » linode-01 build #1584: SUCCESS in 1 min 0 sec: https://kci.pangea.pub/job/mgmt_docker/label=linode-01/1584/ [14:48] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-01 build #1584: SUCCESS in 3 min 49 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-01/1584/ [14:49] -kubuntu-ci:#kubuntu-devel- Project mgmt_docker » swy-02 build #1584: SUCCESS in 4 min 2 sec: https://kci.pangea.pub/job/mgmt_docker/label=swy-02/1584/ [15:19] Hi all [16:21] @CliffordTheBigRedDoggie I assume no meeting? I forgot again :/ [16:41] Sorry wasn't at my computer [16:48] might have to think of alternate times if we want to carry them on [16:59] If there good weather I can't make it [17:00] @CliffordTheBigRedDoggie, you should be fine to be there for most of a UK summer then [17:01] Lovely day today [17:02] yep. nice cold beer is going down well [17:34] To "update" the patch issues in kstars (https://kci.pangea.pub/job/xenial_unstable_kstars/517/parsed_console/) should I remove the patch inside debian/patches? [17:34] It was left out of VCS before [17:34] Regarding the other package, the requirement is actually superior to what currently exists, even in artful. Should we ignore it for the time being? [17:41] My suggestion is we should keep the patch (in case it becomes useful anytime in the future) and propose a patch upstream to set the version number right of INDI package. [17:44] <[Relic]> Hate to interrupt, but is there anyway to make a live usb boot very slowly (item by item?) so I can see where it is causing a kernel panic lock up (happens on 3 different usb drives)? [17:53] gsilvapt: leave the patch for now. we can properly review whether to update it or ditch it. we have months to do that on the versions unstable branch is tracking [18:02] ok acheronuk, thanks! [18:05] Anyone here uses sbuild? i'm having the same error in all packages and, as far as I remember, this is a configuration error: https://paste.ubuntu.com/24882700/ [18:05] gsilvapt: on libindi we just need to update or wait for debian to update the libindi version in the archives. [18:06] But I can't remember what it is and I've done the installation guide twice.... [18:06] Hum, I see. I forgot to check upstream if the package has a higher version number [18:06] 7back [18:07] http://indilib.org/download/source.html [18:07] 1.4.1 [18:09] tried building that the other day, but there were issues with missing symbols compared to 1.2 so would need to see what debian (or pre-empt them) do on any library version bump [18:10] speaking of symbols, I need to read about those [18:10] so since it's only a non-essential optional build depend for kstars, just waiting to see for now [18:11] okay, thanks for the tip! [18:12] Sorry for asking so many things but I just have to ask what's all this to understand what is going on and what can I do :) [18:14] gsilvapt: https://irclogs.ubuntu.com/2017/02/22/%23kubuntu-devel.html#t14:55 [18:15] on symbols ^^^ [18:20] Oh, cool! A guide on this. Thank you, super useful! [18:28] Wow, this is a tad complex [18:30] Yes, it takes the best of us some time to get our heads round that! [18:32] This is also an extensive walkthrough. I'd benefit from one of these as it is a hands-on experience. [19:37] acheronuk, clivejo: https://phabricator.kde.org/T6358 I'm not going to do it yet, since I'm working on apps and the Qt transition which is more urgent. feel free to do it or mentor someone else to do it before I have time for that [19:38] gsilvapt: the symbols files are with huge difference the most complex task you would have to deal wrt kde packaging [19:42] santa_: ack. it's not urgent === mitya57_ is now known as mitya57 [19:45] acheronuk: regarding the akonadi fixing, if possible I will do that tomorrow, if so it's ok if I give you the dsc to upload the package? (I would handle the thing in git) and after that we could work with the release team to unblock the rest of kdepim [19:46] santa_: whichever is easiest for you [19:46] ack [19:47] regarding the qt transition, as you know I'm doing some test rebuilds to assess the thing. so far kdeframeworks is much better than expected only a couple of possible issues [19:49] in addition to the packages which may need some small adjustments (which we will do), this is imho what we should do in the kde packaging scope before artful gets qt 5.9 [19:49] 1. get the current stuff in -proposed out of proposed [19:50] 2. upload kde applications 17.04.2 (if that's possible to do in time) [19:52] note that 17.04.2 will need some binary-only new reviews [19:52] so probably we will have to that after qt 5.9 lands in artful [19:53] and this means that, unfortunately we may need to do some small fixes here and there for apps 16.12, which is not cool, but if there's no other way... [19:54] so to sum up I think the 1. is a "must have" and the 2. a "nice to have but only if it's feasible" [19:54] tsimonq2: ↑ [20:22] santa_: all sounds reasonable [20:43] santa_: Well my goal is to get Qt in and out of proposed ASAP [20:43] santa_: I'd rather not have it stuck in there like glue for a month :/ [20:53] it's traditional. new Qt sets up semi-permanent residence in -proposed [20:56] I'd like to prevent that now that we're shoving Unity 8 out the doot [20:56] *door [21:03] (Document) https://irc-attachments.kde.org/mKQ4P7RF/Screenshot_20170617_170253.png [21:03] Unity8 is still alive btw [21:04] @ahoneybun, ?? [21:04] no idea how that keeps happening [21:05] latte? [21:05] yepp [21:05] looks ok [21:05] it's super small lol [21:06] oh. I usually make panels and docks quite small, so it did not look odd to me [21:06] you could do everything with latte and remove all other panels really [21:07] tsimonq2: I want the same thing, so I'm trying to figure things out to make that hapen [21:07] the same thing = get qt 5.9 into artful as soon as we can [21:08] yes, if it going in, sooner = better [21:08] https://phabricator.kde.org/w/kubuntu/black-operations/qt-5-9-transition/ [21:08] within reason [21:13] @ahoneybun: It's getting removed from the archive. If it ever comes back, it'll be in a different name and it'll be in Universe. [21:13] santa_: Wonderful. Let's accomplish that. :) [21:13] right [21:14] santa_: Also, if you want me to get anything in the PPA (because mitya57 just has to press a button and it's all copied to proposed) that fixes a lot of the KDE * stack (that's broken after the Qt update), let me know. [21:15] santa_: Just upload it to a PPA and I think we'll be able to just review it. [21:15] santa_: But as long as you know that it's a possibility... :) [21:16] Same goes for anyone else with Ninja or Developer status [21:16] If Qt 5.9.0 breaks something and you have a fix, ping [21:17] tsimonq2: sure. wrt test rebuilds frameworks for i386 is about to finish so I'm going to schedule plasma/amd64 tonight, we will have the results in the morning, then I will continue with plasma/i386 tomorrow [21:17] inb4 my night and my morning, it's 23:17 here [21:25] mparillo: ping? [21:25] http://kubuntu.org/news/latest-round-of-backports-ppa-updates-include-plasma-5-10-2-for-zesty-17-04/ [21:28] Pong? [21:29] acheronuk: Good time to spread the good news? [21:31] mparillo: It is :) [21:38] Now which VM and which incognito browser did I use to insulate myself from facebook? [21:44] santa_: ack :) [21:48] acheronuk: Wow, that was a fast turnaround time for backports! Keep up the good work :) [21:48] santa_, clivejo ^ [21:48] huh? [21:49] clivejo: http://kubuntu.org/news/latest-round-of-backports-ppa-updates-include-plasma-5-10-2-for-zesty-17-04/ [21:51] I know, I'm getting pinged about that left, right and center [22:14] acheronuk, santa_, clivejo: Ping, can one of y'all please join #debian-cd on OFTC and help test Stretch KDE images? They're having some errors when booting and I'm not sure how to begin diagnosing some of these things. [22:16] And anyone else who is good at diagnosing Plasma things ^^^ [22:17] @acheronuk, @CliffordTheBigRedDoggie ^^^^ [22:52] Hey all o/ [22:54] hi DarinMiller [22:54] where you been? [22:54] FYI for anyone using apt-cacher NG that also want to use wine staging. Ensure to edit (or create) /etc/apt/apt.conf and add:Acquire::HTTP::Proxy::dl.winehq.org "DIRECT"; [22:56] I have not been far. I mostly have been on in late evening when everyone else is in bed. [22:57] awwww [22:57] stupid time zones [22:58] yes, big spinning rock we live on, hard to stay in sync with everyone.