[00:00] nothing. the epoch is never part of the filenames. [00:01] it seems to have been a few days ago :/ [00:01] no, the accept messages print the package version, the reject messages tell the change filename [00:02] those are 2 different things [00:02] ah [00:02] there was an email about the source code of ark being updated [00:02] maybe thats why its rejected? [00:03] well, the email content tells you why it's rejected [00:03] Hi Albert, any chance to have a respin for the Ark tarball? We need to [00:03] > include this commit [1] in order to have a functioning Ark on Plasma [00:03] > 5.7 [00:04] what should I version the respun orig tarball? [00:04] a? [00:04] yep [00:05] * yofel fixed the docker deployment be reshuffling code whose oder shouldn't matter at all......... [00:06] I'll put the CI in production mode again [00:06] or maybe not...... [00:07] oh conflicts, that's ok [00:08] why does it always blame me :( [00:08] Yippppe [~kubuntu-ppa/ubuntu/staging-kdeapplications/yakkety] ark 4:16.04.3a-0ubuntu1~ubuntu16.10~ppa1 (Accepted) [00:09] see the epochs in that filename [00:09] weirdness [00:10] that is not a filename ^^ [00:10] and you uploaded ffmpegthumbs to yakkety, so dont need to worry about it being missing [00:10] yep [00:11] so its just kde4libs and kde-110n need looking at now [00:14] kde4libs you did manually last time [00:14] ? [00:15] yes [00:15] to get that as part of the auto run you have to set the correct version somewhere [00:21] you didnt backport it? Is it ok to do that? [00:21] create the branch etc [00:22] yofel: ^ [00:22] eakk kubuntu-ci left us! [00:23] hm, changing a global setting seems to reset the bot [00:23] clivejo: well, it should get backported. I didn't have it finished though [00:24] Ill leave it then [00:24] o/ [00:24] how are you all? [00:24] but Ill create the branch [00:24] hi Simon [00:25] o/ [00:25] we are having fun, breaking stuff [00:25] tired :P [00:25] yofel has killed and brought KCI back to live a few times now [00:25] well, I *think* I have it down now. But we'll see when the build jobs start running [00:26] hey clivejo, can you give me something more to do than fix build errors? :D [00:26] Im afraid fixing build errors is the main job at the moment! [00:28] ok, LVM survived the forkbomb of launching 40 builds at once [00:28] clivejo: alright :)( [00:28] *:) [00:28] * clivejo cheers and pours himself a drink in celebration [00:28] anything specific I can do at the moment or should I just go nuts? :) [00:29] well yofel and I wont be about for much longer I reckon [00:29] getting very near bed time [00:29] I understand [00:30] what does Rejected:'Description' mean [00:31] on a LP email [00:31] uh, no idea o.O [00:31] [~kubuntu-ppa/ubuntu/staging-kdeapplications] cantor_16.04.3-0ubuntu1~ubuntu16.10~ppa10_i386.changes (Rejected) [00:31] weird emails [00:33] yet the actual build looks fine to me - https://launchpadlibrarian.net/274724546/buildlog_ubuntu-yakkety-i386.cantor_4%3A16.04.3-0ubuntu1~ubuntu16.10~ppa10_BUILDING.txt.gz [00:33] oh thats much better :P [00:34] :P [00:34] lol [00:34] 00:30:56 Host key verification failed. [00:34] 00:30:56 [00:34] 00:30:56 Unable to connect to SSH host ppa.launchpad.net; EOF during negotiation [00:34] what?!? [00:38] actually, why are we using dput over sftp... [00:39] for me regular ftp stalls out on large files :/ [00:40] hm, there is that, true [00:41] like breeze [00:42] calligra [00:46] finally, I no longer have a red screen :P [00:46] theres time yet [00:48] now with more executors you can have even larger red screens than before! [00:49] 32 at once! [00:49] thats fun! [00:49] put it full screen and it gives the illusion of falling into a pit of doom [00:51] yofel: whats it trying to do? [00:51] XD yofel [00:51] does it dput the build to LP if it builds ok? [00:52] it dputs the source. And it tries that twice and fails then [00:52] I think we need a couple more tries with longer sleeps in between [00:53] ive noticed with mass uploads LP sometimes ignores some of them :/ [00:53] yofel: wth? bug queue and there's IDLE builders? [00:53] lol [00:54] you increased linode executors to 40? [00:54] tsimonq2: the builds are ordered to prevent depwait / dep mismatch as possible. So e-c-m waits on the current jobs, and everything else waits on e-c-m as that's the frameworks root [00:55] I see yofel [00:55] they gonna love us! [00:55] yofel: just giving you a hard time ;) [00:55] clivejo: well, it survided launching most of those at once. So that'll stay like that [00:56] is it ok to max the resources out on it? [00:56] that's not max resources, just high peak I/O. But it could probably handle even more [00:57] I think memory wise it used 3G at most, now using ~1G [00:57] CPU? [00:58] peaks occasionally at 100% when it's building lots of sources. But as the builders spent most of the time waiting for launchpad, average cpu usage is like 10% or so [00:58] oh, its not actually building on the Linode machine? [00:59] it's building the sources, not the binaries [00:59] ah [00:59] binaries are built in the PPA [00:59] I thought it was building binaries too [00:59] building those would require a considerable amount of CPU power [01:02] have you solved the LP not available messages? [01:02] no [01:02] need a retry/sleep [01:03] hm.... [01:03] did kde4libs build for you? [01:03] failed on symbols [01:04] same here [01:05] was there a problem with the symbols? [01:05] or will a batchpatch fix it? [01:06] I think it's fine, but there was something fishy about it so I wanted to check it later [01:09] #MISSING: 4:4.14.22# _ZTIN6Strigi14BufferedStreamIcEE@Base 4:4.14.16 [01:09] looks fishy to me [01:12] I think it's fine in practice because we haven't been using strigi in a long time, but that's a bit tricky to guarantee [01:12] Ive removed them and will upload again [01:24] weeeee [01:24] so much work going on! [01:24] \o/ [01:25] o/ valorie :) [01:27] greetings [01:28] gosh if we get things fixed so quickly early, release will be a breeze [01:28] instead of a nail-biter [01:28] knock on wood..... [01:29] valorie: when's the next release? [01:29] and what are we releasing? lol [01:30] s/we/the Kubuntu team/ [01:30] !releases [01:30] Ubuntu releases a new version every 6 months. Each version is supported for 9 months (non-LTS) or 5 years (LTS). More info at https://wiki.ubuntu.com/Releases & http://wiki.ubuntu.com/TimeBasedReleases [01:30] oh dear, the wiki..... [01:30] oh you mean like Yakkety and Xenial [01:30] I see [01:31] https://wiki.ubuntu.com/YakketyYak/ReleaseSchedule [01:31] applications beta 16.08 (16.07.80) was released yesterday I think. But for that 16.04.3 needs to be done, and we need a plan what we do with kdepim without qtwebengine [01:31] right, we just released 16.04.1 the other day [01:31] but that was just bugfixes [01:32] yofel: we've given up on qtwebengine? [01:32] sgclark started it, but didn't get far enough that someone can finish it? [01:33] valorie: from what I gathered on oftc, hefee might be taking another shot at that. But that might not be in time for us [01:33] does hefee have the work sgclark did? [01:33] yes, at least what's in git [01:33] good [01:34] well, I guess we can decide at some point before feature freeze [01:34] aug. 18 [01:34] coming pretty soon [01:34] :( [01:35] there is another mail client [01:35] but it's no PIM [01:35] trojita [01:35] !info trojita [01:36] Package trojita does not exist in yakkety [01:36] hmmm [01:36] I wonder why that isn't in the archive [01:37] noone has packaged it yet? [01:39] right [01:39] lol [01:39] we might consider packaging that if PIM can't be provided [01:40] theres a nightly for xenial here - https://launchpad.net/~lubuntu-dev/+archive/ubuntu/lubuntu-daily/+packages?field.name_filter=trojita&field.status_filter=published&field.series_filter= [01:41] looks like the last build failed..... [01:42] no, all green check marks, right? [01:42] but trojita-nightly - 0.7.0+201607230446~ubuntu16.04.1, none for 16.10 [01:43] nope, but that shouldnt be a huge problem [01:43] how does it render the emails [01:44] might also use qtwebengine [01:44] hm... [01:45] oh dear [01:46] failing to dput again [01:48] oh its a KDE project - git://anongit.kde.org/trojita [01:48] yes, but like, why?!? [01:48] http://kci.pangea.pub/view/yakkety%20FIX/job/xenial_unstable_kplotting/192/console -> works [01:48] http://kci.pangea.pub/job/xenial_unstable_ki18n/204/console -> fails [01:48] End of File of course [01:48] both linode [01:50] and now all the ones I look at work [01:51] and master is crapping out again [01:51] 01:49:29 make: *** Cannot allocate memory. Stop. [01:54] yes, trojita has been a KDE project for quite awhile [02:00] my internet is sooooo slow [02:01] and LP is soooooo slow [02:03] meh, and my slave permissions are soooooo wrong [02:07] well kde4libs finally build and Im poked rebuilds, so on that note Im going to zzzzZZZZZzzzzzZZZZzzzzZZZ [02:08] nini [02:08] and Ive downloaded 16.04.1 to install on a Windows 10 laptop sometime in the next few days! [02:08] only took 2 hours! [02:10] BTW do you mind if I create a LP git repo for trojita? I might look at that tomorrow if I get a chance [02:10] go ahead [02:10] ok, I think I worked around the permissions... [02:11] would you mind putting that epoch email out? [02:12] opened up a new mail window with a subject. I'll write the rest in a bit [02:39] * tsimonq2 fixes problems [03:00] where do I go to report a bug in a package in that Plasma Staging PPA? [03:52] sorry I couldn't work on more today, I was out of the house, but at least I got to a fix for xenial_unstable_discover [04:01] PR here if anyone wants to take a look: https://code.launchpad.net/~tsimonq2/kubuntu-packaging/+git/kubuntu-plasma-discover/+merge/300983 [04:02] I'm off for the day [04:02] o/ [07:08] hey hey hey I spot a acheronuk merging my MPs! :D [07:08] * tsimonq2 couldn't sleep [07:09] I just saw the email [07:09] damn Verizon phone hacking [07:09] hey it's night owl ahoneybun :D [07:09] heyo [07:09] yeah :( [07:09] trying to break into a phone atm [07:09] or was about to sleep [07:09] oh jeez [07:09] you were going to sleep? [07:09] :P [07:09] and... [07:09] the people made the phone go into FRP [07:10] your phone got hacked?!?!?!?!? [07:10] :( [07:10] well not mine [07:10] my dad bougt one off somepeople [07:10] *bought [07:10] oh okay [07:14] morning :) [07:14] acheronuk: how are you? :) [07:15] tsimonq2: I would say that commit message was a bit long.. [07:15] but that is my pref [07:15] tsimonq2: good thanks. :) [07:19] wow long [07:19] acheronuk: I literally copied the message I put in debian/changelog lol [07:23] tsimonq2: yes, for readability on that, a little less is more IYSWIM [07:23] acheronuk: I see [07:24] acheronuk: I'll make it more basic in the future [07:24] so acheronuk, I see you're a ninja? [07:25] tsimonq2: yes, I got ambushed with that [07:25] or was a nice surprises a week or 2 ago I should say [07:26] acheronuk: is it sort of like Ubuntu Membership where you have to show significant and sustained contribution, or is it like yellow belts, where I just had to convince ahoneybun I knew what I was talking about (I do, but all I had to do was talk to him) [07:26] :P [07:26] lol [07:26] tsimonq2: I still owe in bribes for it though. [07:26] lol [07:27] acheronuk: I mean, what experience did you have beforehand? [07:27] tsimonq2: see https://community.kde.org/Kubuntu/Policies#.7Ekubuntu-ninjas [07:28] acheronuk: I'm aware of that, I'm just wondering what *your* experience was :) [07:28] tsimonq2: I had been helping on here testing things for a few months, then submitting packaging fixes as you are doing. just generally helping out [07:29] alright [07:29] acheronuk: how long did you submit packaging fixes? [07:30] (before becoming a ninja) [07:30] * acheronuk looks at irc logs [07:32] ummm... hard to find. lol [07:33] acheronuk: do you have just a casual estimate, I don't need exact dates :) [07:33] tsimonq2: weeks/month or so rather than many months anyway [07:33] acheronuk: month being singular? [07:34] tsimonq2: month and a bit? maybe? [07:34] great thanks :) [07:34] tsimonq2: point is there is going to be no set time. you could be quicker. depends when the powers that be think you are ready [07:34] seeing as ninjas have access to the PPA's we should trust them enough [07:35] also we need 2 developers to vouch [07:35] ^^^ exactly [07:35] as that page that acheronuk links to kinda explains [07:35] yep :) [07:35] at least with the 2 developer part [07:36] I think I can do that :) [07:36] since the PPAs also include the backports too [07:36] I see [07:36] not sure we have 2 official devs right now [07:36] I was a bit caught by surprise being added to that! [07:37] the dev list or PPA? [07:37] if I'm reading this description right, my best bet would be to work on something other than just yakkety/xenial failures :P [07:37] If yofel asks "Are you evil?.... then" [07:37] ahoneybun: ninjas [07:37] ahoneybun: all of it [07:38] well the 2 devs left are yofel and scarlett [07:38] and scarlett is on a break atm [07:39] I would say that yofel would want a KC vote on it as a backup maybe [07:39] which I think is fair as well [07:39] tsimonq2: yep, broaden it. help test iso when needed, how new releases in ppas etc upgrade, report bugs we find in LP or upstream, and on and on [07:39] *not putting words into yofel's mouth here [07:40] I can upload to the PPA's as a KC member I believe [07:40] or Documentation :) [07:40] plenty to do [07:40] alright acheronuk [07:40] acheronuk: fixing a merge right now [07:41] since he knows the deb packaging maybe once he get's a KDE Identity account he can help with: https://notes.kde.org/p/kubuntu-packaging [07:43] * acheronuk goes looking for coffee [07:47] that's better :) [07:51] valorie: what;s up with this: https://trello.com/c/uvJp5i9t/126-add-content-to-the-blank-wiki-pages-for-upgrades-to-xenial [07:51] since you got me on trello [07:52] mm I'll look at it tomorrow/today [07:52] need sleep [07:52] o/ ahoneybun [07:52] night tsimonq2 and acheronuk [07:52] well, I made the pages and asked for feedback but never got any [07:53] my fault for not adding you to the card I guess [07:53] ahoneybun: night :) [07:53] since I'm on the card [07:53] niters ah [07:53] my bad [07:53] I'm just waking up! [07:53] weird, ark's merge seems to be clean yet it's reporting an error [07:53] since my dad died I find a lot of details have sort of slipped through my fingers [07:53] well it's 4am here [07:54] acheronuk: do ninjas have access to rebuild on Jenkins? [07:54] valorie: :( [07:54] tsimonq2: can retrigger a build, yes [07:54] acheronuk: if so, could you rebuild the ark merger? [07:54] \o/ [07:54] tsimonq2: he was 89, so it was expected [07:55] but it still changed things [07:55] I see valorie [07:55] tsimonq2: let me look whats going on [07:55] acheronuk: well the thing that's puzzling me is when I do it locally, I'm not getting the same errors as CI [07:55] * tsimonq2 does it command-by-command [07:56] tsimonq2: what is the difference [07:57] eyes are glazing over here too [07:57] niters all [07:57] acheronuk: that's what I'm trying to find out, I can't see it [07:57] o/ valorie [07:58] yofel: it was started by you, what's up? [07:58] tsimonq2: I mean what error do you get that KCI doesn't, or vice vera? [07:58] *versa [07:59] [I] merger: Merging kubuntu_stable into kubuntu_unstable. [07:59] /var/lib/jenkins/.rvm/gems/ruby-2.2.0@merger/gems/git-1.3.0/lib/git/lib.rb:937:in `command': git '--git-dir=/var/lib/jenkins/workspace/merger_ark/.git' '--work-tree=/tmp/KCIMerger20160724-5086-1tmzfgr' merge '-m' 'Merging kubuntu_stable into kubuntu_unstable.' 'kubuntu_stable' 2>&1:Auto-merging debian/changelog (Git::GitExecuteError) [07:59] CONFLICT (content): Merge conflict in debian/changelog [07:59] Automatic merge failed; fix conflicts and then commit the result. [07:59] I get a clean merge [08:00] oh, an actual merge! [08:00] http://paste.ubuntu.com/20716960/ [08:00] that's my output ^ [08:01] yeah, http://kci.pangea.pub/job/merger_ark/lastFailedBuild/consoleFull [08:01] I thought you meant a build triggered by a merge request you did [08:01] no no no [08:01] acheronuk: I'm expanding my skills ;) [08:02] wait I think I'm doing it wrong locally, hold on here [08:02] * tsimonq2 checks the commits in the logs [08:04] tsimonq2: https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/ark/+ref/kubuntu_unstable [08:04] acheronuk: it did the merge, I know [08:06] acheronuk: I just don't know why the merge failed because it was already successful [08:08] acheronuk: from all the merges I'm seeing, it's global [08:08] acheronuk: which really makes me wonder what's up [08:11] tsimonq2: well, yofel's comment in this channel in response to the failure message last night was "oh conflicts, that's ok" [08:11] alright, then I'll stop trying to fix it ;) [08:14] KCI was being "adjusted/fixed" a lot again last night it seems [08:16] acheronuk: can you do a rebuild of yakkety_unstable_modemmanager-qt please? there's no code changes and it's failing because of running out of memory [08:17] yakkety_unstable_sddm-kcm needs a rebuild, Launchpad error [08:17] yakkety_unstable_polkit-kde-agent-1 needs a rebuild, Launchpad error [08:18] yakkety_unstable_libkeduvocdocument needs a rebuild, Launchpad error [08:18] yakkety_unstable_libkexiv2 needs a rebuild, Launchpad error [08:19] same with yakkety_unstable_bluez-qt [08:19] hiho [08:19] o/ soee [08:19] same with yakkety_unstable_baloo [08:20] memory error on yakkety_unstable_bovo , needs rebuild [08:21] last one was already queued [08:21] alright thanks acheronuk [08:27] acheronuk: what [08:27] *what's the deal with https://launchpadlibrarian.net/274322048/buildlog_ubuntu-xenial-amd64.kdepimlibs_4%3A16.04.3+p16.04+git20160721.1704-0_BUILDING.txt.gz ? [08:27] sorry [08:27] needs the dev files for Qt5WebEngine [08:28] which is not even packaged in debian yet, let alone in our KCI [08:28] acheronuk: what work has been done so far to fix it? [08:28] that is an ongoing thorny problem [08:29] what work is going on to package Qt5WebEngine then? [08:30] tsimonq2: from last night http://paste.ubuntu.com/20719203/ [08:31] alright cool [08:31] scarlett is packaging it here for debian https://anonscm.debian.org/cgit/pkg-kde/qt/qtwebengine.git/ [08:32] but she has a new job (or 2) and I don't think really has the time [08:34] acheronuk: hmm, does this take the tarball from the PPA mentioned? [08:35] seems like it [08:36] wait no, nevermind [08:37] * tsimonq2 rambles to himself now [08:37] huh? [08:38] oh. lol [09:13] acheronuk, tsimonq2: My 'conflicts, ok' was related to me thinking I had broken the slave again [09:13] everything on http://kci.pangea.pub/view/merge%20FIX/ should get fixed, except oxygen-fonts, that's obsolete I think [09:13] \o/ [09:14] and for you not getting conflicts. The merger does a merge cascade, so you need to do the same to get the conflicts [09:14] yofel: how does it do that? [09:15] I must admit, I had not looked that closely at what it does with those [09:16] lets take http://kci.pangea.pub/job/merger_rocs/475/console for an example [09:16] the green merges are the ones actually executed [09:16] xenial is not the problem so we can ignore that [09:17] but it then merged kubuntu_yakkety_archive into kubuntu_stable, *and then* kubuntu_stable into kubuntu_unstable. So the actual conflict is probably from the indirect kubuntu_yakkety_archive -> kubuntu_unstable merge [09:17] * tsimonq2 takes a look [09:17] yofel: that should really be more verbose [09:18] true, I also tend to wonder what it really does. sitter_ made is a bit too short.. [09:18] *this [09:18] lookign at it, that does make sense [09:18] yofel: is the source code for the build process public? [09:19] tooling is on github? [09:19] not anymore [09:19] tsimonq2: https://git.launchpad.net/~kubuntu-ci-admins/kubuntu-ci/+git/pangea-tooling/tree/kci/merger.rb [09:20] thanks [09:20] oh I see the issue, at least with rocs [09:21] yofel: do I make an MP for the conflict resolution on kubuntu_yakkety_archive or kubuntu_unstable? [09:21] the former I'm assuming? [09:21] kubuntu_unstable [09:22] oh okay [09:22] you're getting a conflict because _unstable has changes that are not yet in _archive, and shouldn't yet be [09:23] yofel: so I shouldn't fix it? [09:23] or should I? [09:24] you should [09:24] okay [09:24] otherwise _unstable won't get any fixes from _archive [09:24] yeah [09:25] conflict != undesired changes? [09:25] yofel: should I make a dch entry as well>? [09:25] s/>// [09:25] just conflicting ones.. [09:26] tsimonq2: rather not [09:26] alright yofel [09:26] try to edit the changelog in _unstable only for important changes [09:26] okay [09:26] * tsimonq2 does a test rebuild and remerge locally [09:26] the changelog is *the* biggest source for merge conflicts [09:27] * acheronuk git skills still need polish [09:28] I am winging it a bit on git, but getting there. [09:28]