[00:06] -queuebot:#ubuntu-release- New binary: otb [amd64] (bionic-proposed/universe) [6.4.0+dfsg-1] (no packageset) [00:57] -queuebot:#ubuntu-release- Unapproved: gcc-7 (artful-proposed/main) [7.2.0-8ubuntu3 => 7.2.0-8ubuntu3.1] (core) (sync) [00:59] -queuebot:#ubuntu-release- Unapproved: gcc-5 (xenial-proposed/main) [5.4.0-6ubuntu1~16.04.6 => 5.4.0-6ubuntu1~16.04.8] (core) (sync) [01:20] Laney: do you know if there's a particular reason for using ssmtp (from universe) in the autopkgtest hooks? It may simply not be smart enough to send mail to multiple recipients, and it certainly doesn't do any useful logging [01:25] -queuebot:#ubuntu-release- New: accepted otb [amd64] (bionic-proposed) [6.4.0+dfsg-1] [01:25] Laney: hmm no, it's not that [01:25] Laney: i.e. strace shows it dtrt at the smtp level [02:13] -queuebot:#ubuntu-release- Unapproved: accepted gcc-7 [sync] (artful-proposed) [7.2.0-8ubuntu3.1] [02:36] -queuebot:#ubuntu-release- New: accepted rsyslog [amd64] (bionic-proposed) [8.32.0-1ubuntu1] [02:36] -queuebot:#ubuntu-release- New: accepted rsyslog [armhf] (bionic-proposed) [8.32.0-1ubuntu1] [02:36] -queuebot:#ubuntu-release- New: accepted rsyslog [ppc64el] (bionic-proposed) [8.32.0-1ubuntu1] [02:36] -queuebot:#ubuntu-release- New: accepted rsyslog [arm64] (bionic-proposed) [8.32.0-1ubuntu1] [02:36] -queuebot:#ubuntu-release- New: accepted rsyslog [s390x] (bionic-proposed) [8.32.0-1ubuntu1] [02:36] -queuebot:#ubuntu-release- New: accepted rsyslog [i386] (bionic-proposed) [8.32.0-1ubuntu1] [04:59] flocculant: that is great, glad I could help [05:11] -queuebot:#ubuntu-release- New binary: dino-im [ppc64el] (bionic-proposed/none) [0.0.git20180130-1] (no packageset) [05:11] -queuebot:#ubuntu-release- New binary: dino-im [s390x] (bionic-proposed/none) [0.0.git20180130-1] (no packageset) [05:12] -queuebot:#ubuntu-release- New binary: dino-im [arm64] (bionic-proposed/none) [0.0.git20180130-1] (no packageset) [05:12] -queuebot:#ubuntu-release- New binary: dino-im [i386] (bionic-proposed/none) [0.0.git20180130-1] (no packageset) [05:12] -queuebot:#ubuntu-release- New binary: dino-im [armhf] (bionic-proposed/none) [0.0.git20180130-1] (no packageset) [05:13] -queuebot:#ubuntu-release- New binary: python-josepy [amd64] (bionic-proposed/none) [1.0.1-1] (no packageset) [05:14] -queuebot:#ubuntu-release- New binary: dino-im [amd64] (bionic-proposed/none) [0.0.git20180130-1] (no packageset) === lotuspsychje_ is now known as lotuspsychje [06:50] -queuebot:#ubuntu-release- New: accepted python-josepy [amd64] (bionic-proposed) [1.0.1-1] [06:53] -queuebot:#ubuntu-release- New: accepted dino-im [amd64] (bionic-proposed) [0.0.git20180130-1] [06:53] -queuebot:#ubuntu-release- New: accepted dino-im [armhf] (bionic-proposed) [0.0.git20180130-1] [06:53] -queuebot:#ubuntu-release- New: accepted dino-im [ppc64el] (bionic-proposed) [0.0.git20180130-1] [06:53] -queuebot:#ubuntu-release- New: accepted dino-im [arm64] (bionic-proposed) [0.0.git20180130-1] [06:53] -queuebot:#ubuntu-release- New: accepted dino-im [s390x] (bionic-proposed) [0.0.git20180130-1] [06:53] -queuebot:#ubuntu-release- New: accepted dino-im [i386] (bionic-proposed) [0.0.git20180130-1] [07:05] what is wrong with http://people.canonical.com/~ubuntu-archive/component-mismatches.txt golang-1.8? [07:06] why is it pulled into main? [07:20] Laney: autopkgtest for lintian/unknown: amd64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ any idea why that fails? already gave it back [07:45] Laney: nm, lintian was not yet built :-/ [08:01] doko: Possibly snapd Built-Using: golang-1.8 [08:02] Hi, I wanted to ask again for src:ipxe-qemu-256k-compat on bionic new queue to be considered [08:02] I even have a security ack in a mail thread for a MIR right afterwards, but I can't file the MIR before the accept on new is done [08:02] also it blocks qemu proposed-migration [08:02] I'm here for discussions on src:ipxe-qemu-256k-compat if needed [08:03] cpaelzer: I'll have a look. [08:03] thanks in advance [08:05] infinity: ahh, and ftbfs in proposed [08:07] given back [08:18] and giving back all failed builds in -proposed [08:53] -queuebot:#ubuntu-release- Unapproved: accepted fwupdate [amd64] (bionic-proposed) [10-1] [08:53] -queuebot:#ubuntu-release- Unapproved: accepted fwupdate [i386] (bionic-proposed) [10-1] [08:54] -queuebot:#ubuntu-release- Unapproved: accepted fwupdate [amd64] (bionic-proposed) [10-2] [08:54] -queuebot:#ubuntu-release- Unapproved: accepted fwupdate [armhf] (bionic-proposed) [10-2] [08:54] -queuebot:#ubuntu-release- Unapproved: accepted fwupdate [arm64] (bionic-proposed) [10-2] [08:54] -queuebot:#ubuntu-release- Unapproved: accepted fwupdate [i386] (bionic-proposed) [10-2] [09:03] -queuebot:#ubuntu-release- New binary: openttd [s390x] (bionic-proposed/universe) [1.7.1-1] (no packageset) [09:08] -queuebot:#ubuntu-release- New binary: openttd [amd64] (bionic-proposed/universe) [1.7.1-1] (no packageset) [09:09] -queuebot:#ubuntu-release- New binary: openttd [i386] (bionic-proposed/universe) [1.7.1-1] (no packageset) [09:11] -queuebot:#ubuntu-release- New binary: openttd [armhf] (bionic-proposed/universe) [1.7.1-1] (no packageset) [09:13] -queuebot:#ubuntu-release- New binary: openttd [arm64] (bionic-proposed/universe) [1.7.1-1] (no packageset) [09:24] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-fan [source] (artful-proposed) [0.12.9~17.10.1] [09:24] -queuebot:#ubuntu-release- New binary: fmtlib [s390x] (bionic-proposed/universe) [4.0.0+ds-2] (no packageset) [09:27] -queuebot:#ubuntu-release- New binary: openttd [ppc64el] (bionic-proposed/universe) [1.7.1-1] (no packageset) [09:27] -queuebot:#ubuntu-release- New binary: qoauth [s390x] (bionic-proposed/universe) [2.0.1~1-3] (no packageset) [09:28] sil2100: Can we ignore the ruby2.3 failure on arm64 blocking readline? It happened before, it's not readline specific. [09:28] -queuebot:#ubuntu-release- New binary: qoauth [armhf] (bionic-proposed/universe) [2.0.1~1-3] (no packageset) [09:29] It's some weird path thing [09:29] -"/var/lib/gems/2.3.0" [09:29] +"/tmp/test_rubygems_895/default" [09:29] -queuebot:#ubuntu-release- New binary: qoauth [arm64] (bionic-proposed/universe) [2.0.1~1-3] (no packageset) [09:30] oh, there are more [09:32] hmm some obscure time zone failures [09:32] Failure: count is the same as for openssl, though, so I guess both are fine :) [09:33] don't ask me why it works in 50% of the cases - I don't know [09:34] -queuebot:#ubuntu-release- New: accepted openttd [amd64] (bionic-proposed) [1.7.1-1] [09:34] -queuebot:#ubuntu-release- New: accepted openttd [armhf] (bionic-proposed) [1.7.1-1] [09:34] -queuebot:#ubuntu-release- New: accepted openttd [ppc64el] (bionic-proposed) [1.7.1-1] [09:34] -queuebot:#ubuntu-release- New: accepted openttd [arm64] (bionic-proposed) [1.7.1-1] [09:34] -queuebot:#ubuntu-release- New: accepted openttd [s390x] (bionic-proposed) [1.7.1-1] [09:34] -queuebot:#ubuntu-release- New: accepted openttd [i386] (bionic-proposed) [1.7.1-1] [09:34] -queuebot:#ubuntu-release- New binary: fmtlib [arm64] (bionic-proposed/universe) [4.0.0+ds-2] (no packageset) [09:35] juliank, sil2100: I would support ignoring all ruby2.3 related failures now. ruby2.5 will be in bionic, and ruby2.3 will go away [09:35] +1 [09:36] -queuebot:#ubuntu-release- New binary: fmtlib [armhf] (bionic-proposed/universe) [4.0.0+ds-2] (no packageset) [09:37] doko: I assume you wanted to sync readline (since you merged the changes into Debian and put out two bugfixes after that), but forgot it, hence I did last week. [09:40] hm, ok [09:45] -queuebot:#ubuntu-release- New binary: fmtlib [i386] (bionic-proposed/universe) [4.0.0+ds-2] (no packageset) [09:51] -queuebot:#ubuntu-release- New binary: fmtlib [amd64] (bionic-proposed/universe) [4.0.0+ds-2] (no packageset) [09:51] juliank: done [09:51] sil2100: thanks [09:55] -queuebot:#ubuntu-release- New binary: qoauth [amd64] (bionic-proposed/universe) [2.0.1~1-3] (no packageset) [09:56] -queuebot:#ubuntu-release- New binary: qoauth [i386] (bionic-proposed/universe) [2.0.1~1-3] (no packageset) [10:00] -queuebot:#ubuntu-release- New binary: fmtlib [ppc64el] (bionic-proposed/universe) [4.0.0+ds-2] (no packageset) [10:08] -queuebot:#ubuntu-release- New binary: qoauth [ppc64el] (bionic-proposed/universe) [2.0.1~1-3] (no packageset) [10:08] Please remove libssl1.0.0-dbg binaries from bionic, migrated to dbgsyms packages. [10:09] -queuebot:#ubuntu-release- New: accepted qoauth [amd64] (bionic-proposed) [2.0.1~1-3] [10:09] -queuebot:#ubuntu-release- New: accepted qoauth [armhf] (bionic-proposed) [2.0.1~1-3] [10:09] -queuebot:#ubuntu-release- New: accepted qoauth [ppc64el] (bionic-proposed) [2.0.1~1-3] [10:09] -queuebot:#ubuntu-release- New: accepted qoauth [arm64] (bionic-proposed) [2.0.1~1-3] [10:09] -queuebot:#ubuntu-release- New: accepted qoauth [s390x] (bionic-proposed) [2.0.1~1-3] [10:09] -queuebot:#ubuntu-release- New: accepted qoauth [i386] (bionic-proposed) [2.0.1~1-3] [10:12] juliank, doko, does not help that ruby2.5 does not pass its tests either. [10:15] -queuebot:#ubuntu-release- New: accepted fmtlib [amd64] (bionic-proposed) [4.0.0+ds-2] [10:15] -queuebot:#ubuntu-release- New: accepted fmtlib [armhf] (bionic-proposed) [4.0.0+ds-2] [10:15] -queuebot:#ubuntu-release- New: accepted fmtlib [ppc64el] (bionic-proposed) [4.0.0+ds-2] [10:15] -queuebot:#ubuntu-release- New: accepted fmtlib [arm64] (bionic-proposed) [4.0.0+ds-2] [10:15] -queuebot:#ubuntu-release- New: accepted fmtlib [s390x] (bionic-proposed) [4.0.0+ds-2] [10:15] -queuebot:#ubuntu-release- New: accepted fmtlib [i386] (bionic-proposed) [4.0.0+ds-2] [10:27] xnox: it does not? [10:27] seemed fine for readline [10:28] xnox: um, ok, it's allways failed [10:28] xnox: but always failed does help :D [10:49] -queuebot:#ubuntu-release- Unapproved: accepted gcc-5 [sync] (xenial-proposed) [5.4.0-6ubuntu1~16.04.8] [10:54] xnox: It's not bionic that's causing that error, it's bionic-proposed. [10:55] xnox: If NBS in the release pocket needed manual intervention every time, nothing would ever migrate. :P [10:56] infinity, ah [10:56] xnox: Fixed in proposed. [10:57] Err, by someone else before me, apparently. :P [11:09] -queuebot:#ubuntu-release- New binary: libixion [s390x] (bionic-proposed/main) [0.13.0-2] (kubuntu) [11:13] -queuebot:#ubuntu-release- New binary: libixion [ppc64el] (bionic-proposed/main) [0.13.0-2] (kubuntu) [11:13] -queuebot:#ubuntu-release- New binary: libixion [i386] (bionic-proposed/main) [0.13.0-2] (kubuntu) [11:15] -queuebot:#ubuntu-release- New binary: libixion [amd64] (bionic-proposed/main) [0.13.0-2] (kubuntu) [11:18] -queuebot:#ubuntu-release- New binary: libixion [armhf] (bionic-proposed/main) [0.13.0-2] (kubuntu) [11:20] -queuebot:#ubuntu-release- New binary: libixion [arm64] (bionic-proposed/main) [0.13.0-2] (kubuntu) [11:33] -queuebot:#ubuntu-release- New: accepted libixion [amd64] (bionic-proposed) [0.13.0-2] [11:33] -queuebot:#ubuntu-release- New: accepted libixion [armhf] (bionic-proposed) [0.13.0-2] [11:33] -queuebot:#ubuntu-release- New: accepted libixion [ppc64el] (bionic-proposed) [0.13.0-2] [11:33] -queuebot:#ubuntu-release- New: accepted libixion [arm64] (bionic-proposed) [0.13.0-2] [11:33] -queuebot:#ubuntu-release- New: accepted libixion [s390x] (bionic-proposed) [0.13.0-2] [11:33] -queuebot:#ubuntu-release- New: accepted libixion [i386] (bionic-proposed) [0.13.0-2] [12:00] infinity, could you please RM qesteidutil 0.3.1-0ubuntu3 from bionic-proposed? no longer needed, as the libp11-3 soname bump is reverted for now (we do not have the new ssl yet, derp) [12:01] plus it FTBFS anyway [13:04] doko, is there anything blocking the promotion of poppler now? [13:05] hi, is bind9 stuck in migration? It's been like this (everything green or ignored) for about 12h now: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#bind9 [13:05] oSoMoN: same as yesterday: mpfr4, binutils, and all the depending stuff, including net-snmp and perl [13:06] oSoMoN: and see the new libixion. not sure what rebuilds are needed [13:26] -queuebot:#ubuntu-release- New binary: liborcus [s390x] (bionic-proposed/main) [0.13.2-1] (kubuntu) [13:28] -queuebot:#ubuntu-release- New binary: liborcus [ppc64el] (bionic-proposed/main) [0.13.2-1] (kubuntu) [13:30] -queuebot:#ubuntu-release- New binary: liborcus [i386] (bionic-proposed/main) [0.13.2-1] (kubuntu) [13:33] ahasenack: bind9 is a transition, it can't migrate until all its rdeps are rebuilt and ready. [13:33] I see [13:33] do I need to do anything about it, or are these other builds kicked off automatically? [13:34] ahasenack: They are not. [13:34] so I need to hunt them down? [13:34] ahasenack: I'll set up a transition tracker to find them for us. [13:35] ok [13:37] ahasenack: Actually, it may be a short enough list to not bother with that. [13:37] -queuebot:#ubuntu-release- New binary: liborcus [amd64] (bionic-proposed/main) [0.13.2-1] (kubuntu) [13:38] bind9 has an annoyingly large number of library packages [13:38] ahasenack: Yeah, but almost nothing uses them. [13:38] -queuebot:#ubuntu-release- New binary: liborcus [arm64] (bionic-proposed/main) [0.13.2-1] (kubuntu) [13:39] ahasenack: isc-dhcp, bind9-dyndb-ldap, libnss-lwres... Looks like the whole list. [13:39] ahasenack: And bind9-dyndb-ldap was already uploaded. [13:39] ahasenack: So, just isc-dhcp and libnss-lwres need rebuilding, AFAICT. [13:39] libnss-lwres will be dropped, as we are not shipping lwresd anymore [13:39] it might build, but won't be installable [13:40] ahasenack: Define "not shipping"... Looks like it's in the archive. [13:40] for bind9 9.10, not this 9.11 one [13:40] I sent an email to ubuntu-server@ and ubuntu-devel@ about it [13:40] debian dropped it [13:40] -queuebot:#ubuntu-release- New binary: liborcus [armhf] (bionic-proposed/main) [0.13.2-1] (kubuntu) [13:42] ahasenack: lwresd is dropped, yes, but not liblwres, which is what libnss-lwres depends on. [13:42] right [13:42] but libnss-lwres depends on lwresd (runtimE) [13:43] ahasenack: But it doesn't. [13:43] really? [13:43] It recommends it, but doesn't depend on it. Which would imply that either it can work without the daemon, or it's packaged incorrectly. :P [13:43] ah, I hadn't noticed that it's a recommends [13:44] it can work by not breaking, without the server bit (lwresd) [13:44] but won't do anything useful I think [13:44] anyway [13:44] we can kick a rebuild I suppose [13:45] maybe it can point at a different ip instead of localhost [13:45] there was no manpage for its config file, nor a sample one [13:45] ok then [13:45] ahasenack: Well, I think lwresd in bind9 was actually just some symlinks to the named binary. :P [13:45] it is [13:46] I was just looking up my mp where I summarized it [13:46] infinity: https://code.launchpad.net/~ahasenack/ubuntu/+source/bind9/+git/bind9/+merge/336719/comments/882890 [13:46] there [13:46] tl;dr: [13:46] root@bionic-bind9-merge:~# md5sum /usr/sbin/lwresd /usr/sbin/named [13:46] 5d1fbcc8583f732b50c2b8a4c3946223 /usr/sbin/lwresd [13:46] 5d1fbcc8583f732b50c2b8a4c3946223 /usr/sbin/named [13:46] that's why liblwres is still packaged, as the /usr/sbin/named will still behave as lwresd (and need the lib) if it's called like that [13:47] ahasenack: So, does the new package ship lwresd as a symlink/hardlink? [13:47] no [13:47] it's really gone [13:47] ahasenack: If not, that seems like a regression. [13:47] no lwresd package, no /usr/sbin/lwresd blob [13:47] that's what was dropped by debian, and we followed [13:47] And a pointless one. [13:48] upstream dropped the lwres code entirely in 9.12 [13:49] Ahh, if it's gone in 9.12, fair enough. [13:49] yes, see my email to ubuntu-devel: https://www.mail-archive.com/ubuntu-devel@lists.ubuntu.com/msg08445.html [13:50] ahasenack: In that case, I'm all for removing libnss-lwres entirely. [13:50] \o/ [13:50] ahasenack: isc-dhcp, on the other hand, can you test and make sure it works with a straight rebuild (and, if not, find a way forward)? [13:50] I will [13:50] get bionic-proposed, make sure bind is 9.11, rebuild isc-dhcp [13:50] that it? [13:51] and that it works, of course [13:51] ahasenack: Yeah. Or toss it at a PPA with proposed enabled, if you're lazy. [13:51] ok, thx [13:51] will ping back with results [13:52] ahasenack: libnss-lwres removed. [13:52] thanks [13:54] -queuebot:#ubuntu-release- New: accepted liborcus [amd64] (bionic-proposed) [0.13.2-1] [13:54] -queuebot:#ubuntu-release- New: accepted liborcus [armhf] (bionic-proposed) [0.13.2-1] [13:54] -queuebot:#ubuntu-release- New: accepted liborcus [ppc64el] (bionic-proposed) [0.13.2-1] [13:54] -queuebot:#ubuntu-release- New: accepted liborcus [arm64] (bionic-proposed) [0.13.2-1] [13:54] -queuebot:#ubuntu-release- New: accepted liborcus [s390x] (bionic-proposed) [0.13.2-1] [13:54] -queuebot:#ubuntu-release- New: accepted liborcus [i386] (bionic-proposed) [0.13.2-1] [13:55] oSoMoN: ^^^ once that is build, we need a LO no-change upload. or do you want to upload a new package? [14:05] LocutusOfBorg: could you summarize the status of the current ghc transition? [14:07] doko, I don't have new changes to push, so a no-change upload is fine [14:07] doko, ready to go, as soon as hoogle fixes the test on arm64 [14:07] I did a no change rebuild half an hour ago [14:07] to see what changes [14:07] -queuebot:#ubuntu-release- Unapproved: preseed (artful-proposed/main) [1.71ubuntu5 => 1.71ubuntu5.1] (core) [14:08] -queuebot:#ubuntu-release- Unapproved: preseed (trusty-proposed/main) [1.62ubuntu1.1 => 1.62ubuntu1.2] (core) [14:08] -queuebot:#ubuntu-release- Unapproved: preseed (xenial-proposed/main) [1.71ubuntu1.1 => 1.71ubuntu1.2] (core) [14:08] LocutusOfBorg: looks like it's entangled with perl / mpfr4 [14:14] doko, I don't agree, sorry! [14:14] Trying easy from autohinter: gitit/0.12.2.1+dfsg-2build1 haskell-aeson-qq/0.8.2-1build4 haskell-asn1-encoding/0.9.5-1build7 [14:15] look for this hint [14:15] it is blocked only by a single autopkgtest failure [14:17] -queuebot:#ubuntu-release- Unapproved: debian-installer (artful-proposed/main) [20101020ubuntu523.1 => 20101020ubuntu523.2] (core) [14:20] -queuebot:#ubuntu-release- Unapproved: debian-installer (xenial-proposed/main) [20101020ubuntu451.18 => 20101020ubuntu451.19] (core) [14:23] -queuebot:#ubuntu-release- Unapproved: debian-installer (trusty-proposed/main) [20101020ubuntu318.42 => 20101020ubuntu318.43] (core) [14:28] -queuebot:#ubuntu-release- Unapproved: accepted lxpanel [source] (xenial-proposed) [0.8.2-1ubuntu2.1] [14:29] -queuebot:#ubuntu-release- Unapproved: accepted menu-cache [source] (xenial-proposed) [1.0.1-1ubuntu0.2] [14:29] -queuebot:#ubuntu-release- New binary: linux-signed-oem [amd64] (xenial-proposed/universe) [4.13.0-1020.21] (kernel) [14:31] -queuebot:#ubuntu-release- Unapproved: accepted cloud-utils [source] (xenial-proposed) [0.27-0ubuntu25] [15:13] -queuebot:#ubuntu-release- New: accepted linux-signed-oem [amd64] (xenial-proposed) [4.13.0-1020.21] [15:15] -queuebot:#ubuntu-release- New: accepted uvp-monitor [source] (xenial-proposed) [2.2.0.316-0ubuntu1~16.04.1] [15:16] -queuebot:#ubuntu-release- New: accepted uvp-monitor [source] (trusty-proposed) [2.2.0.316-0ubuntu1~14.04.1] [15:20] -queuebot:#ubuntu-release- New binary: uvp-monitor [armhf] (xenial-proposed/none) [2.2.0.316-0ubuntu1~16.04.1] (no packageset) [15:21] -queuebot:#ubuntu-release- New binary: uvp-monitor [arm64] (trusty-proposed/none) [2.2.0.316-0ubuntu1~14.04.1] (no packageset) [15:21] -queuebot:#ubuntu-release- New binary: uvp-monitor [armhf] (trusty-proposed/none) [2.2.0.316-0ubuntu1~14.04.1] (no packageset) [15:22] -queuebot:#ubuntu-release- New binary: uvp-monitor [arm64] (xenial-proposed/none) [2.2.0.316-0ubuntu1~16.04.1] (no packageset) [15:29] -queuebot:#ubuntu-release- New binary: uvp-monitor [i386] (xenial-proposed/none) [2.2.0.316-0ubuntu1~16.04.1] (no packageset) [15:31] -queuebot:#ubuntu-release- New binary: uvp-monitor [amd64] (trusty-proposed/none) [2.2.0.316-0ubuntu1~14.04.1] (no packageset) [15:31] -queuebot:#ubuntu-release- New binary: uvp-monitor [amd64] (xenial-proposed/none) [2.2.0.316-0ubuntu1~16.04.1] (no packageset) [15:34] -queuebot:#ubuntu-release- New binary: uvp-monitor [i386] (trusty-proposed/none) [2.2.0.316-0ubuntu1~14.04.1] (no packageset) [16:57] infinity: hi, my test with isc-dhcp-server built with bind 9.11.2: https://pastebin.ubuntu.com/26496073/ [16:58] took a while because I wanted to use maas for this test, but turns out maas in bionic is broken, and the snap is useless for this test since it ships its own isc-dhcp-server [18:39] -queuebot:#ubuntu-release- Unapproved: grub2 (bionic-proposed/main) [2.02-2ubuntu5 => 2.02-2ubuntu5] (core) [20:11] slangasek: I think phpunit and phpunit-mock-object may need a bootstrap [20:12] slangasek: would you be able to do that or would you rather I upload packages that will build without test and then replace them with the test versions? [20:13] nacc_: I'm a bit strapped for time currently, the fast path is probably for you to do it in-archive [20:13] slangasek: ok, thanks [20:13] slangasek: np [20:33] -queuebot:#ubuntu-release- New source: heat-dashboard (bionic-proposed/primary) [1.0.0-0ubuntu1] [20:40] -queuebot:#ubuntu-release- Unapproved: cockpit (artful-backports/universe) [158-1~ubuntu17.10.1 => 160-1~ubuntu17.10.1] (no packageset) [20:44] -queuebot:#ubuntu-release- Unapproved: cockpit (xenial-backports/universe) [158-1~ubuntu16.04.1 => 160-1~ubuntu16.04.1] (no packageset) [20:48] -queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (artful-backports) [160-1~ubuntu17.10.1] [20:49] -queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (xenial-backports) [160-1~ubuntu16.04.1] [21:01] if an AA could demote the php binaries mentioned at http://people.canonical.com/~ubuntu-archive/component-mismatches-proposed I think that will allow the eventual removall of php7.1 and clear upt he current unsatisfiable depends in excuses for 7.2 [21:17] oh I did not know there was a html page too [21:31] -queuebot:#ubuntu-release- New binary: firefox [amd64] (bionic-proposed/main) [58.0.1+build1-0ubuntu1] (kubuntu, mozilla, ubuntu-desktop) [21:52] juliank: yeah it's a bit easier to read sometimes :) [22:06] -queuebot:#ubuntu-release- New: accepted uvp-monitor [amd64] (trusty-proposed) [2.2.0.316-0ubuntu1~14.04.1] [22:06] -queuebot:#ubuntu-release- New: accepted uvp-monitor [armhf] (trusty-proposed) [2.2.0.316-0ubuntu1~14.04.1] [22:06] -queuebot:#ubuntu-release- New: accepted uvp-monitor [amd64] (xenial-proposed) [2.2.0.316-0ubuntu1~16.04.1] [22:06] -queuebot:#ubuntu-release- New: accepted uvp-monitor [armhf] (xenial-proposed) [2.2.0.316-0ubuntu1~16.04.1] [22:06] -queuebot:#ubuntu-release- New: accepted uvp-monitor [arm64] (trusty-proposed) [2.2.0.316-0ubuntu1~14.04.1] [22:06] -queuebot:#ubuntu-release- New: accepted uvp-monitor [arm64] (xenial-proposed) [2.2.0.316-0ubuntu1~16.04.1] [22:06] -queuebot:#ubuntu-release- New: accepted uvp-monitor [i386] (trusty-proposed) [2.2.0.316-0ubuntu1~14.04.1] [22:06] -queuebot:#ubuntu-release- New: accepted uvp-monitor [i386] (xenial-proposed) [2.2.0.316-0ubuntu1~16.04.1] [22:07] -queuebot:#ubuntu-release- New binary: lubuntu-artwork [amd64] (bionic-proposed/universe) [0.70] (no packageset) [22:09] I would appreciate it if lubuntu-artwork could get a Binary NEW review as soon as possible. [23:13] -queuebot:#ubuntu-release- New binary: node-fn-name [amd64] (bionic-proposed/none) [2.0.1-2] (no packageset) === nacc_ is now known as nacc [23:36] -queuebot:#ubuntu-release- New binary: firefox [i386] (bionic-proposed/main) [58.0.1+build1-0ubuntu1] (kubuntu, mozilla, ubuntu-desktop) [23:45] Laney: https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/bionic/ubuntu/+build/122424 we need to revert this livecd-rootfs change; it breaks all builds because people.c.c is not reachable from LP. [23:47] you could just http://people.canonical.com/~ubuntu-archive -> http://archive-team.internal [23:48] I mean by all means revert for process reasons if you'd rather but that'd be the obvious fix [23:48] oh heh, that last change basically did the opposite of that. never mind me :-) [23:50] hmm, does it? there's a *.buildd -> SEEDMIRROR=http://archive-team.internal/seeds/ in there [23:54] I bet that just needs to be *.buildd|*.ppa|*.scalingstack [23:58] cjwatson: a revert lets me fix the release pocket a lot more quickly in the face of current autopkgtest queues, at least in theory