[00:00] are there issues with PPA's tonight? [00:01] E: Failed to fetch http://ppa.launchpad.net/kubuntu-ci/unstable/ubuntu/pool/main/k/kactivities-kf5/libkf5activities5_5.38.0+p17.04+git20170918.0902-0_amd64.deb Unable to connect to ppa.launchpad.net:http: [00:07] clivejo: Do you have a timestamp for that? [00:08] build started at 2350 UTC [00:10] wgrant: buildlog - https://launchpadlibrarian.net/337481506/buildlog_ubuntu-zesty-amd64.peruse_1.2+p17.04+git20170918.2350-0_BUILDING.txt.gz [00:11] Interesting. [00:14] clivejo: Looks like an issue with apache's mpm_event. Investigating -- thanks for the report. [00:32] wgrant: getting worse [00:32] clivejo: It's actually getting better. But it did get worse for a few minutes... [00:32] Nearly there. [00:32] wall of red failures on KCI [00:32] But I've suspended all builds. [00:40] wgrant: don't know if it's coincidence, but only seems to have affected xenial series [00:40] clivejo: Just a coincidence. [00:47] clivejo: Right, we've defeated systemd and it should be fully responsive again. Retries should work, and let me know if you see any further issues. [00:49] thanking you kindly [08:55] Hi, I just created a ppa and uploaded packages to it. Now if I run add-apt-repository I get "gpg: no valid OpenPGP data found." and "Failed to add key." Any hints on what's wrong? [08:56] ail30: it takes a little while for keys to be generated [08:56] it works if I run apt-key adv --recv-key [08:57] does that mean the key has already been generated? [08:57] should do [08:58] gpg: keybox '/tmp/tmp6phwstbk/pubring.gpg' created [08:58] gpg: /tmp/tmp6phwstbk/trustdb.gpg: trustdb created [08:58] gpg: key 57A94721: public key "Launchpad PPA for Adrian I. Lam" imported [08:58] gpg: Total number processed: 1 [08:58] gpg: imported: 1 [08:58] gpg: no valid OpenPGP data found. [08:58] Failed to add key. [08:59] ^ That's what add-apt-repository gives me [08:59] What's the full PPA name? [09:00] ppa:adrianiainlam/indicator-keyboard-led [09:00] Will have a look in a bit, about to have a meeting [09:00] thanks [09:19] cjwatson, I tried it on another computer and it worked. Perhaps it's just something wrong with my gpg. [09:28] cjwatson, apparently it was because I linked /usr/bin/gpg to /usr/bin/gpg2 instead of actually having a gpg1. It's been solved now. [09:28] Aha [09:28] Yes, was just trying it locally (and it was fine) [09:29] That may be something that needs to be fixed in add-apt-repository though [09:30] Probably /usr/lib/python3/dist-packages/softwareproperties/AptAuth.py === chihchun is now known as chihchun_afk [12:44] "Create a new dput configuration section using incoming = ~//ubuntu/ and the suite you specify will override the suite named in the upload changelog when you upload it using the new configuration" [12:44] thats still the case? Cause it doesn't seem to work (~dupondje/dupondje/ubuntu/xenial) [13:07] dupondje_: You didn't follow the directions accurately. [13:08] I think. Let me check. [13:09] dupondje_: Right. Your PPA's *display name* is "dupondje", but its *name* is "ppa". [13:09] https://launchpad.net/~dupondje/+archive/ubuntu/ppa [13:10] dupondje_: Perhaps you meant to change its name; but right now, the form is ~dupondje/ppa/ubuntu/xenial [13:11] dupondje_: That said, that form is deprecated; where do you see it? The preferred form now is ~dupondje/ubuntu/ppa with Distribution: xenial in the .changes file, or ~dupondje/ubuntu/ppa/xenial if you need to override the suite. [13:12] Ah, https://help.launchpad.net/Packaging/PPA/Uploading#Using_packages_from_other_distributions. Will fix. [13:13] cjwatson: aha ok :) Was unclear a bit. Thx === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === dupondje_ is now known as dupondje === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk [21:09] how do i find an official release version og gcc 4.8.1 arm-linux-gnueabihf, the binaries on launchpad.net and linaro archive are all prerelease versions [22:08] is there something wrong with LP builders? [22:09] seems to be a lot of "Cleaning" going on [22:33] i'm having a heck of a time getting lp builders to install stuff from maven.. i can wget stuff from maven during the snap install phase no problem (http://bazaar.launchpad.net/~bigdata-dev/bigdata-data/snap-pig/view/head:/snap/snapcraft.yaml#L198), but every time my snap tries to do it via ant, i get a 403: [22:33] [ivy:resolve] HTTP response status: 403 url=http://repo.apache.maven.org/maven2/xmlenc/xmlenc/0.52/xmlenc-0.52.pom [22:33] [ivy:resolve] CLIENT ERROR: Forbidden url=http://repo.apache.maven.org/maven2/xmlenc/xmlenc/0.52/xmlenc-0.52.pom [22:33] [ivy:resolve] maven2: resource not reachable for xmlenc#xmlenc;0.52: res=http://repo.apache.maven.org/maven2/xmlenc/xmlenc/0.52/xmlenc-0.52.pom [22:33] if it was a proxy issue, i'd expect a 407 or some other auth denied message... the 403 makes me think the lp builders have been blacklisted. anyone else seen this? [22:36] fwiw, i know the ant_opt are legit because i see them exported in the build log (https://launchpadlibrarian.net/337575355/buildlog_snap_ubuntu_xenial_ppc64el_pig_BUILDING.txt.gz), and i have an authenticated proxy on my home machine that works just fine. i'm stumped trying to figure out why it doesn't work on lp.