Launchpad is temporarily unavailable

[00:39] yofel: did you upload kde-l10n ? === goddard_ is now known as goddard [01:34] *** FIX ME *** === amichair_ is now known as amichair [06:28] clivejo: are you broken? [07:34] clivejo: my emails say I did [07:34] (l10n) [07:43] clivejo: ffmpegthumbs failed, so oddly still not getting that patch in the release tarballs, but KCI does in it's snapshot? [07:45] fix for that segfault in dpkg it seems, https://launchpad.net/ubuntu/+source/dpkg/1.18.9ubuntu2 so hopefully the YY iso install won't crash at the end soon [07:47] someone rewrite dpkg in rust, that supposedly prevents segfaults by itself ^^ [08:44] I see the folder view patch has been added and updated package landed in proposed \o/ [09:23] yep, you can see/click the install icon easily in the YY daily ISO again :) [09:28] clivejo: some files in marble no longer included, so need to go? [09:30] I 'could' do that later, but it would be MUUUUCH later if so, so I'm not fussed. [09:31] Yes, I just grabbed the latest ISO and am installing in KVM now [09:31] It was great to see a clear desktop install icon, within a folder 😃 [09:32] not sure if the new dpkg went in soon enough to fix the installer crash at the end today? [10:02] sitter: what's the easiest way to disable 'stable' builds in the ci? [10:04] yofel: disable or remove? [10:05] sitter: well, disable preferably. Though removing would work too if I can easily add them back once the branch logic and scalability are fixed [10:06] our pangea-tooling has jenkins_able.rb which has a -d swithc to disable all jobs matching a regex [10:06] also jenkins_delete.rb which does the same thing but deletes the jobs instead [10:06] ok, thanks. I'll look at those [10:06] to prevent the jobs getting added back you'll want to remove the stable build type from your kci.yaml === Blizzzek is now known as Blizzz [10:24] Hiyas all [10:31] Plasma 5.8 is going to be a long term support release but it will require Qt 5.6 as a minimum version. Will Kubuntu 16.04 ship Qt 5.6 at least in backports ppa, maybe as optional renamed package? The reason for more fresh KDE in LTS nowadays is bug fixing rather than new(ported old) features. And plasma also going to be LTS for 18 months just fixin [10:31] g bugs. Its a win win situation for LTS Kubuntu if you'll include it. [10:34] helloz :D [10:42] vKLBG: yes, we plan putting 5.8 into the backports eventually, including Qt 5.6 and we're working on it, but Qt 5.6 and Plasma 5.7 will take a while to get done thanks to the Qt update [10:42] Thank you! [10:54] yofel: I made a lxc container called kde-apps but it seesm I did not do something right [10:54] looked right to me, just the ssh key was missing [10:55] funny as I added both mine and his [10:55] you need to add it *inside* [10:55] I did [10:55] mm [10:55] oh, you added it for 'root', not 'ubuntu' [10:56] well ubuntu kept giving me permission denied when editing anything [10:56] you did change to ubuntu's $HOME, right? [10:56] actually let me improve the howto [10:57] most likely I messed up [10:57] yeah, I think I know what happened [10:57] that's what I was afraid of [10:57] there's a better way to do this [10:58] updated, 'su' leaves you in the directory you are, 'sudo -u ubuntu -i' puts you into the proper one [11:00] technically key-based root login is enabled, so you could've logged in if you had used 'root', but lets use ubuntu as that's what I configured [11:00] I did not you to have to do EVERYTHING if it could be avoided I guess [11:01] *want you [11:02] there should be more than one person that can add containers anyway [11:02] while your here I should try again I think [12:36] Any python fans out here? :D [12:36] http://9gag.com/gag/ae60xLO [12:39] clivejo: I have installed the staged 16.04.3 apps. Looking good so far. :) [12:44] Eakkk [12:44] Not ready for testing yet [12:44] Sorry [12:45] that's what happens if you tell people to test from staging :P [12:45] I won't get mad at any of you if I break my computer though. I know the risks. :) [12:50] brrrrrr http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20160701-yakkety.html#kubuntu [12:51] those depwaits make no sense.. [12:51] how could [12:59] Did I hear new, shiny, and fragile in ppa:kubuntu-ppa/staging-kdeapplications ? [12:59] * mamarley duct-tapes his mouth. [13:00] * yofel goes into "deny what happens in front of you" mode [13:01] I have VMs with YY and XX that I am prepared to break, or are the apps still loading into staging? [13:02] In en.US there is an expression, "Who are you going to believe; me or your own lying eyes?" Originally from fraudsters, now mostly just a joke. [13:02] lol === pavlushka_ is now known as pavlushka [15:11] I done a "quick" staging last night and haven't had time to get back to it [15:30] clivejo: in YY or XX? Both are running too smoothly for me. [15:30] I only uploaded for YY [15:36] 137 to be upgraded; 4 to be newly installed [15:37] there are lot still in the red [15:42] Well, the full-upgrade went smoothly. [15:43] the red ones are showing version 16.04.2? [15:47] Konsole and Dolphin both show 16.04.3 and seem to work normally. [16:09] clivejo: why are there some 16.04.3 apps uploaded to the frameworks staging ppa? alphabetically akonadi to baloo-widgets5? [16:10] because I was very tired last night and didnt check a command I run [16:10] wanna delete them? [16:11] I see. I can? yes, I presume I can now? [16:11] there was about six before I realised I had made a mistake [16:11] yes [16:11] easy to do, believe me [16:11] go into delete moed and select the packages that shouldnt be there [16:12] just as I would in my own ppa [16:12] yup [16:12] forgot you had probably done it before [16:14] plenty of times, but only on my own head be it! [16:15] weird [16:15] I uploaded them, but no ack from LP [16:17] I had a couple of the qt ones do that when I uploaded those. one built but no email. The other uploaded, but just vanished. Had to repeat it. [16:17] LP weirdness [16:17] throwing them at LP again [16:17] hopefully some will stick [16:18] 3rd time lucky [16:20] and the two moved to manual khelp and libkdegames [16:21] ok got accepted emails [16:24] back later. pub lunch and a few beers, and I haven't quite recovered yet [16:24] acheronuk: can you see why ffmpegthumbs is FTBFS [16:26] same as before? rolled tarball is missing the ffmpeg 2.9 changes? [16:26] while KCI pulling from git gets them? [16:27] that is what I assumed anyway. I only looked very very briefly [16:27] back in hour or 2 [16:27] have fun! [16:28] already had the fun. now getting over it! [16:30] funny how every webpage I visit now is trying to sell me hotels and flights to Berlin [16:31] trying to find a part for a washing machine but Google wants me to book a hotel room [16:39] clivejo: you've obviously flown to Berlin recently :-) [16:43] amazon is bombqarding my inbox with raspi accessories now that I finally bought the canakit ...works quite well except the resolution seems hard coded to 1824x984 rather than the full 1920x1080 [16:46] didn't care much for the debian jessie version so I'm using ubuntu mate instead . Wonder if there will ever be a kde/plasma image for raspi3 [18:50] mamarley: how are apps looking now? [18:50] clivejo: Still looking good. :) [18:58] just ffmpegthumbs left? [19:07] oh. a YY update is pulling in apt-xapian-index. that is good to see [19:13] apps updated cleanly in a YY VM :) [19:40] yofel: why are they all failing?? [19:43] dep issues on i386 mostly I think [19:45] hm, maybe we should drop the i386 builds [19:45] not like they have much value [19:47] My system is i386 [19:47] are you using the CI packages? [19:47] trolololo http://www.phoronix.com/scan.php?page=news_item&px=Skype-Linux-Exciting-Next-Week [19:47] Oh sorry, No - completely out of context [19:48] I misunderstood [19:48] There is talk about killing "official" i386 support (iso, desktop) for maybe 18.04. But I don't think it's time for that yet [19:49] My laptop is old 2009, but I learned recently that I believe it can run amd64 [19:51] you can probably just look up the vendor spec for your CPU. I have a 2006 notebook (64bit) and a 2008 netbook (32bit), so year doesn't tell much [19:52] I'm not the biggest fan of dropping i386, but looking at things realistically, building for armhf would probably have more use today than i386... [19:52] and for the CI it would cut our build count in half [19:52] almost [19:52] Oh I agree with that, and I think we'll see that grow quite quickly [19:52] As far as laptop and desktop processors go, anything Core 2 Duo and up is x86_64. Earlier Atoms and later Pentiums can go either way. [19:53] that's what I have [19:53] Though some stupid vendors ship 64-bit processors with 32-bit UEFI, making it difficult to install 64-bit OSes. [19:54] Could I be of any assistance with the CI. [19:54] We use Jenkins at work, I am no expert, more a novice, but I do understand what is trying to be achieved [19:55] wondering.. [19:56] I think most of our issues are currently somewhere in the Ruby tooling [19:56] + some scalability [19:57] (the jobs have to wait for launchpad on successful builds, which takes a long time, but we can't have too many concurrent jobs or the server freezes) [19:57] that's why I want to reduce the build count so we actually return the CI into a useful state [19:57] clivejo: would you be against disabling i386? [19:57] Oops sorry back [19:58] Could we split the Successful builds out into a Submit Queue [19:59] Running it as a seperate Job, so that its orthogonal to the Builds, but still provides the LP submission ? [19:59] dunno, currently I think the jobs poll the LP API to find out whether the builds are published to do the binary checks [19:59] splitting might work, esp. with long queues so that Launchpad can get some work done in the meantime [20:00] I have no idea how that would be accomplished though [20:00] OK.. Maybe I poke about... Well I am not too sure, but my colleague Janet at work is a bit of a wizard [20:00] so I can ask her [20:00] (as in: I have no idea how our tooling would create that follow up job) [20:00] Leave it with me if I come up with something I'll shout [20:02] thanks! [20:02] and FWIW, you can also train your packaging skills by trying to fix builds ;) [20:02] Ive no issues with disabling 386 builds [20:03] ok, then let me do that and lets see what happens [20:04] uhm, and let me enable debug symbols for the PPAs while at it [20:04] that sounds like a useful thing [20:05] Yes that would be useful Xen, trying to fix builds is more flexible than trying to package from scratch, as I am very time constrained. So I can dip in and out, and hopefully add small bits of usefulness [20:07] ok, kubuntu-ci/* updated. Lets see if the CI can handle that or waits forever for i386 builds [20:08] now I can make commits directly, I should get on with doing more of those 'fixes' as well [20:10] oh, there is an architecture list in kci.yaml. Let me remove i386 [20:10] and stable while at it. That's broken anyway [20:13] Launchpad is temporarily unavailable [20:13] brrrr [20:13] I was also getting a lot of timeouts just now :( [20:14] Launchpad is temporarily unavailable [20:14] brrrr [20:14] I was also getting a lot of timeouts just now :( [20:15] and my connection's being funny o.O [20:17] And not funny ha ha [20:35] sitter, actually all the headers in libqt5waylandclient5-dev were private. So now that you dropped them, this package no longer makes sense. I'll drop it. [20:35] (Which makes sense, because this library has no public API and is intended to be used by the QPA plugin only) [20:51] there we go, switch things to amd64-only and builds get fixed :P [21:18] * acheronuk quietly cheers at the 'fixed' CI messages [21:19] is it still working on the apps I staged last night? [21:22] no, the recent ones are new jobs [21:22] ... maybe [21:52] I don't get how this CI is supposed to be managed...... [21:53] clivejo: how did you disable the daily jobs? Remove the schedule for mgmt_merger? [21:53] yup [21:53] did you remove any other schedules? [21:54] no, just on the one job [21:54] ok. I tried adding that back for now... [21:55] the actual package jobs all have "Build periodically" enabled, but none of them has a schedule set o.O [21:55] dunno why that is! [21:58] sitter: where is one supposed to run any of these tooling commands? [22:18] Error on retry_it(unknown) :: Access denied. Please ensure that Jenkins is set up to allow access to this operation. [22:18] I'm making progress [22:19] really?!? [22:20] that's more than "no response at all" [22:56] ok, I had to actually add my user to the admin rule in jenkins for this to work.. [22:56] stable builds removed [22:59] sitter: unping [23:11] Build Queue (399) [23:12] still a lot of jobs :S [23:12] lots and lots [23:14] and why are only 6 executors doing something... [23:16] you must have told it to do that! [23:16] well, *I* didn't [23:21] oh, the project dependencies are blocking each other [23:21] at least that's working properly ^^