[00:30] <sergiusens> slangasek hey there! Mind if we let snapcraft into xenial- and zesty-updates? armhf adt failures are timeouts in different locations and different network failures on different runs
[00:52] <slangasek> sergiusens: I don't want to skip these without an understanding of the failures (and why a retry wouldn't fix).  The most recent test run on both xenial and zesty failed with a ProxyErro; do we have an issue with the proxy in the DC?
[00:59] <slangasek> what is meson and why is it terrible?
[01:00] <sergiusens> slangasek they usually fail randomly like this on armhf, not the first time we bring it up
[01:00] <Ukikie> It's the latest fad to replace autotools as a buildsystem, python based.  debhelper supports it, more or less.
[01:01] <slangasek> sergiusens: "timeout" is not the same thing as "network error"
[01:01] <sergiusens> slangasek is the meson question for me? Everyone is moving to meson these days
[01:02] <slangasek> sergiusens: no, that's a question for the aether in response to yet another autopkgtest failing randomly because meson falls over randomly
[01:03] <Ukikie> (FSVO "everyone", the hip ones like systemd and GNOME are moving at least.)
[01:03] <sergiusens> slangasek meson in artful changed its limitations, targets cannot start with `meson-`
[01:03] <sergiusens> in case it helps
[01:03] <Ukikie> sergiusens: Did you see meson got cross support?  Looks like debhelper is getting it soon too.
[01:03] <sergiusens> slangasek ok, I said timeouts incorrectly, it is things like this that fail "fatal: unable to access 'https://github.com/jocave/simple-make-filesets.git/': Could not resolve proxy: squid.internal"
[01:04] <sergiusens> and "<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0xf6b29d30>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution"
[01:04] <sergiusens> it is very common on armhf for us
[01:05] <slangasek> ok
[01:05] <sergiusens> maybe too many adt tests run on the same machine saturating the network driver (I am just making this up) :-)
[01:05] <slangasek> I know I've seen more name resolution errors for armhf than on other archs
[01:05] <slangasek> I chalked that up to discrete infrastructure events
[01:06] <sergiusens> slangasek fwiw, the tests did pass before we merged and tagged the release
[01:06] <slangasek> if we're seeing that consistently, I want to make sure we are following up on that before I start overriding autopkgtest failure
[01:06] <slangasek> s
[01:06] <slangasek> so, I'll dig into this but it will take me a while this evening; I'm now afk
[01:07] <sergiusens> slangasek fwiw, the armhf adt test that passed I usually run during the weekend
[01:07] <sergiusens> which brings in "load" as a possible root cause
[01:08] <sergiusens> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-snappy-dev-snapcraft-daily/xenial/armhf/s/snapcraft/20170909_191306_ef78d@/log.gz and https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty-snappy-dev-snapcraft-daily/zesty/armhf/s/snapcr
[01:08] <sergiusens> aft/20170910_005841_ef78d@/log.gz fwiw
[03:33] <slangasek> infinity: libhybris is going to need porting for glibc 2.26; it has revdeps, a strict versioned dep on libc6, and ftbfs with 2.26.
[03:34] <slangasek> I see there's still an active upstream at https://github.com/libhybris/libhybris; maybe morphis can help with this
[05:12] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (xenial-proposed/main) [2.408.17 => 2.408.18] (desktop-core)
[05:30] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (zesty-proposed/main) [2.441.7 => 2.441.8] (desktop-core)
[05:38] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (xenial-proposed) [2.408.18]
[05:40] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (zesty-proposed) [2.441.8]
[05:44] <infinity> slangasek: Ugh.  How did we not kill hybris in a fire when phone stuff went away?
[05:46] <infinity> slangasek: Or, more to the point, can we petition for its violent removal on the grounds of it never having been a good idea, and certainly not sanely supportable? :P
[05:50] <slangasek> infinity: hybris is a thing of beauty, you infidel
[05:50] <slangasek> infinity: anyway, it has revdeps, so pick your poison
[05:51] <slangasek> it's possible that the mir team are legitimately still using it
[05:51] <slangasek> hard to tell; but at least, it wouldn't be that quick to chase down
[05:53] <infinity> slangasek: You and I define beauty slightly differently.
[06:19] <LocutusOfBorg> slangasek, you completely right, the problem has been a typo in rmadison
[06:20] <LocutusOfBorg> I was trying to fix undertaker, and libpuma-dev is not provided by src:puma but src:aspectc++
[06:20] <LocutusOfBorg> damn
[06:20]  * LocutusOfBorg goes fixing them now that he is awake
[06:49] <LocutusOfBorg> puma, aspectc++, libsoap-site-perl, libauthen-captcha-perl, undertaker should be all fixed now
[06:53] -queuebot:#ubuntu-release- New binary: puma [ppc64el] (artful-proposed/universe) [3.6.0-1ubuntu1] (no packageset)
[06:54] -queuebot:#ubuntu-release- New binary: puma [s390x] (artful-proposed/universe) [3.6.0-1ubuntu1] (no packageset)
[06:54] -queuebot:#ubuntu-release- New binary: puma [amd64] (artful-proposed/universe) [3.6.0-1ubuntu1] (no packageset)
[06:54] -queuebot:#ubuntu-release- New binary: puma [armhf] (artful-proposed/universe) [3.6.0-1ubuntu1] (no packageset)
[06:54] -queuebot:#ubuntu-release- New binary: puma [arm64] (artful-proposed/universe) [3.6.0-1ubuntu1] (no packageset)
[06:54] -queuebot:#ubuntu-release- New binary: puma [i386] (artful-proposed/universe) [3.6.0-1ubuntu1] (no packageset)
[07:42] <cpaelzer> hi, the current migration of a bunch of dpdk fixes in artful (17.05.2-0ubuntu1) is blocked by bug 1712831
[07:43] <cpaelzer> There isn't an ETA on this issue yet, so I wanted to ask if one could hint the autopkgtest of openvswitch on i386 to be non-gating
[07:43] <cpaelzer> If you can make depends then this is true for kernels >=4.12
[08:00] <acheronuk> kscreenlocker all passed for glibc now
[09:56] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (trusty-proposed/main) [3.13.0-132.181] (core, kernel)
[10:01] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (trusty-proposed) [3.13.0-132.181]
[10:08] <LocutusOfBorg> [12:06:16] <BTS> libgit2 0.26.0+dfsg.1-1.1 uploaded by Ximin Luo (infinity0) https://tracker.debian.org/libgit2
[10:08] <LocutusOfBorg> folks,what is your opinion wrt libgit2?
[10:10] <LocutusOfBorg> maybe we can do it for 18.04
[10:54] <juliank> rbalint: I believe unattended-upgrades.service should gain a Before=apt-daily.service, so that when shutting down, and apt-daily.service is already running, unattended-upgrades.service stops after it.
[10:54] <juliank> oops, wrong channel
[11:10]  * doko goes fixing gcc-3.3 :-/
[11:42] -queuebot:#ubuntu-release- New binary: linux-signed-lts-xenial [amd64] (trusty-proposed/main) [4.4.0-96.119~14.04.1] (kernel)
[11:42] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (xenial-proposed/main) [4.10.0-35.39~16.04.1] (kernel)
[11:50] <cpaelzer> reasking if one could please make dpdk pass migration in artful, blocked on i386 autopkgtest by kown kernel bug since 4.12 (bug 1712831)
[12:05] <LocutusOfBorg> doko, get rid of it? I read debian bug: #855851 do you have examples of reverse-deps?
[12:17] <LocutusOfBorg> doko, you are on a roll :) thanks for the llvm fix!
[13:24] -queuebot:#ubuntu-release- New: accepted linux-signed-lts-xenial [amd64] (trusty-proposed) [4.4.0-96.119~14.04.1]
[13:25] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (xenial-proposed) [4.10.0-35.39~16.04.1]
[13:54] <sergiusens> slangasek so what is the plan of action on those snapcraft armhf failures? Do I have to run until it is green?
[13:55] <sergiusens> I re-triggered earlier today and waiting on the results
[15:19] <chiluk> Hey one of the ubuntu-release guys, to comment on https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1712925 in regards to my FFE?  Today is UI freeze and I do have UI changes.
[15:21] <nacc> heh "updated software is available since 17.10 was released". Excellent!
[15:36] <chiluk> stgraber, laney, langasek ^^ can one of you approve or reject my FFE. I should be ready to upload it today. It's baked enough in our infrastructure at indeed that I feel confident with it now.
[15:39] <Laney> cpaelzer: done
[15:39] <Laney> chiluk: I'd rather one of the others TBH, and you spelt slangasek wrong ;-)
[15:39] <chiluk> woops...
[15:39] <chiluk> I guess it's just been too long.
[15:45] <slangasek> sadly I still got the highlight
[15:45] <chiluk> yet ignored it... I see where I stand.
[15:45] <slangasek> been in a meeting, dude :)
[15:45] <chiluk> I figured ... I just miss being part of all the fun.
[15:49] <bdmurray> sil2100: Could you review my network-manager uploads in the -proposed unapproved queue?
[15:49] <sil2100> bdmurray: sure, I'll do that after the meetings no problem
[15:58] <chiluk> thanks a ton slangasek.
[16:00] <smoser> slangasek, http://autopkgtest.ubuntu.com/packages/o/open-iscsi/artful/amd64 can you let open-iscsi through in artful
[16:01] <smoser> that came in under https://code.launchpad.net/~smoser/ubuntu/+source/open-iscsi/+git/open-iscsi/+merge/330315
[16:01] <smoser> read the description there to see why it is right to let it in.
[16:06] <stgraber> speaking of FFes that would be nice to process soon-ish, can someone take a look at https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1715278 ?
[16:24] <sergiusens> slangasek so there are three runs for each of zesty and xenial on armhf failing due to network errors in different tests, can we consider adding up the three runs and consider it a pass and let them into -updates? Maybe a question for sil2100 as he's on guard. FWIW, this is also not the first time we've asked or done this.
[16:32] <slangasek> smoser: fwiw the quicker path for me to unblock this is pointing out that the hint for the old version (as seen in lp:~ubuntu-release/britney/hints-ubuntu/) still applies
[16:33] <slangasek> smoser: hinted
[16:37] <slangasek> sergiusens: I said yesterday that I wanted to identify a path to resolving these network issues before I was willing to ignore the failures; you are now pressuring me again to ignore the failures, when nothing has changed here.  If you're not going to take the CI gate seriously, why are you wasting compute time running these tests on armhf?
[16:42] <sergiusens> slangasek sorry, I think I just misunderstood what the path was given my first message of the day :-) I'll sit and wait then
[16:56] -queuebot:#ubuntu-release- Unapproved: debian-installer (xenial-proposed/main) [20101020ubuntu451.14 => 20101020ubuntu451.15] (core)
[17:03] <Laney> I'd be much obliged if someone would binNEW review the new wallpapers once they pop up
[17:03]  * Laney is squeezing in on the right side of UIF
[17:04] <Laney> well, assuming I didn't mess up :P
[17:05] <smoser> slangasek, well... that would imply that this "bad test" was in fact bad. when in fact at this point the truth is that the OS is bad.
[17:05] <smoser> but thanks for the link to hints-ubuntu
[17:24] -queuebot:#ubuntu-release- New binary: ubuntu-wallpapers [amd64] (artful-proposed/main) [17.10.0-0ubuntu1] (ubuntu-desktop)
[17:35] -queuebot:#ubuntu-release- Unapproved: accepted network-manager [source] (zesty-proposed) [1.4.4-1ubuntu3.2]
[17:36] <bdmurray> tjaalton: Were you still planning on upload the sssd part of the fix for bug 1641203?
[17:51] -queuebot:#ubuntu-release- Unapproved: kexec-tools (xenial-proposed/main) [1:2.0.10-1ubuntu2.3 => 1:2.0.10-1ubuntu2.4] (core) (sync)
[17:52] -queuebot:#ubuntu-release- Unapproved: accepted nova [source] (zesty-proposed) [2:15.0.6-0ubuntu1.1]
[17:58] -queuebot:#ubuntu-release- Unapproved: crash (xenial-proposed/main) [7.1.4-1ubuntu4.1 => 7.1.4-1ubuntu4.2] (core) (sync)
[18:01] <tjaalton> bdmurray: well, 1.13.5 is not out yet :p
[18:01] <tjaalton> i'll poke upstream
[18:02] -queuebot:#ubuntu-release- Unapproved: accepted libc++ [source] (xenial-proposed) [3.7.0-1ubuntu0.1]
[18:14] <bdmurray> xnox: Can you add some SRU information to bug 1600000?
[18:15] <bdmurray> xnox: Bug 1715131 too
[18:21] -queuebot:#ubuntu-release- Unapproved: accepted mdadm [source] (xenial-proposed) [3.3-2ubuntu7.3]
[18:35] -queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (xenial-proposed) [20101020ubuntu451.15]
[19:12] -queuebot:#ubuntu-release- New binary: ldc [ppc64el] (artful-proposed/universe) [1:1.3.0-2] (no packageset)
[19:14] -queuebot:#ubuntu-release- New binary: ldc [amd64] (artful-proposed/universe) [1:1.3.0-2] (no packageset)
[19:19] -queuebot:#ubuntu-release- New binary: ldc [i386] (artful-proposed/universe) [1:1.3.0-2] (no packageset)
[19:29] -queuebot:#ubuntu-release- New: accepted puma [amd64] (artful-proposed) [3.6.0-1ubuntu1]
[19:29] -queuebot:#ubuntu-release- New: accepted puma [armhf] (artful-proposed) [3.6.0-1ubuntu1]
[19:29] -queuebot:#ubuntu-release- New: accepted puma [ppc64el] (artful-proposed) [3.6.0-1ubuntu1]
[19:29] -queuebot:#ubuntu-release- New: accepted ubuntu-wallpapers [amd64] (artful-proposed) [17.10.0-0ubuntu1]
[19:29] -queuebot:#ubuntu-release- New: accepted puma [arm64] (artful-proposed) [3.6.0-1ubuntu1]
[19:29] -queuebot:#ubuntu-release- New: accepted puma [s390x] (artful-proposed) [3.6.0-1ubuntu1]
[19:29] -queuebot:#ubuntu-release- New: accepted puma [i386] (artful-proposed) [3.6.0-1ubuntu1]
[20:19] -queuebot:#ubuntu-release- Unapproved: accepted gdebi [source] (trusty-proposed) [0.9.5.3ubuntu3]
[20:22] -queuebot:#ubuntu-release- Unapproved: accepted cryptkeeper [source] (trusty-proposed) [0.9.5-5.1ubuntu3.1]
[20:31] -queuebot:#ubuntu-release- New binary: ldc [armhf] (artful-proposed/universe) [1:1.3.0-2] (no packageset)
[20:35] -queuebot:#ubuntu-release- New: accepted ldc [amd64] (artful-proposed) [1:1.3.0-2]
[20:35] -queuebot:#ubuntu-release- New: accepted ldc [i386] (artful-proposed) [1:1.3.0-2]
[20:35] -queuebot:#ubuntu-release- New: accepted ldc [armhf] (artful-proposed) [1:1.3.0-2]
[20:35] -queuebot:#ubuntu-release- New: accepted ldc [ppc64el] (artful-proposed) [1:1.3.0-2]
[20:39] <doko> I'm curious about: Depends: gcc-snapshot glibc (not considered)
[20:39] <doko> because the dependencies don't show a dependency on glibc (>= 2.26)
[21:19] -queuebot:#ubuntu-release- Unapproved: mdadm (xenial-proposed/main) [3.3-2ubuntu7.3 => 3.3-2ubuntu7.4] (core)
[21:28] <infinity> doko: Looks like armhf has a 2.26 dep.
[21:29] <doko> ohh, only looked at amd64 and i386
[21:38] -queuebot:#ubuntu-release- Unapproved: accepted mdadm [source] (xenial-proposed) [3.3-2ubuntu7.4]
[22:15] <xnox> bdmurray, yes.
[22:16] <bdmurray> xnox: thanks, feel free to ping me when its ready for review
[22:17] <xnox> bdmurray, ok, thank you.
[22:28] -queuebot:#ubuntu-release- Unapproved: accepted kexec-tools [sync] (xenial-proposed) [1:2.0.10-1ubuntu2.4]
[22:59] -queuebot:#ubuntu-release- Unapproved: python3.5 (xenial-proposed/main) [3.5.2-2ubuntu0~16.04.2 => 3.5.2-2ubuntu0~16.04.3] (core)
[23:03] -queuebot:#ubuntu-release- Unapproved: python3.5 (zesty-proposed/main) [3.5.3-1ubuntu0~17.04.0 => 3.5.3-1ubuntu0~17.04.1] (core)
[23:06] <infinity> bdmurray: A previous SRU for that bug was rejected for not having a testcase in the bug.
[23:06] <infinity> bdmurray: Any chance of doing a tiny bit o' boilerplate?
[23:07] <bdmurray> infinity: I'm aware and doing that now
[23:07] <infinity> bdmurray: \o/
[23:42] <wxl> hey infinity i've recently cleaned and noticed i've been hiding this PowerMac G5 from myself. i remember you had some interest in it if it runs. is that still the case?