[01:18] -queuebot:#ubuntu-release- Unapproved: krb5 (yakkety-proposed/main) [1.14.3+dfsg-2 => 1.14.3+dfsg-2ubuntu1] (core) [02:03] -queuebot:#ubuntu-release- Unapproved: krb5 (xenial-proposed/main) [1.13.2+dfsg-5 => 1.13.2+dfsg-5ubuntu1] (core) [02:10] -queuebot:#ubuntu-release- New binary: exo [ppc64el] (zesty-proposed/universe) [0.11.2-1] (lubuntu, xubuntu) [02:11] -queuebot:#ubuntu-release- New binary: exo [amd64] (zesty-proposed/universe) [0.11.2-1] (lubuntu, xubuntu) [02:12] -queuebot:#ubuntu-release- New binary: exo [arm64] (zesty-proposed/universe) [0.11.2-1] (lubuntu, xubuntu) [02:13] -queuebot:#ubuntu-release- New binary: exo [armhf] (zesty-proposed/universe) [0.11.2-1] (lubuntu, xubuntu) [02:13] -queuebot:#ubuntu-release- New binary: exo [i386] (zesty-proposed/universe) [0.11.2-1] (lubuntu, xubuntu) [02:13] -queuebot:#ubuntu-release- New binary: exo [s390x] (zesty-proposed/universe) [0.11.2-1] (lubuntu, xubuntu) [02:15] -queuebot:#ubuntu-release- New binary: exo [powerpc] (zesty-proposed/universe) [0.11.2-1] (lubuntu, xubuntu) [02:52] -queuebot:#ubuntu-release- Unapproved: krb5 (trusty-proposed/main) [1.12+dfsg-2ubuntu5.2 => 1.12+dfsg-2ubuntu5.3] (core) [05:22] -queuebot:#ubuntu-release- New binary: node-clone-stats [amd64] (zesty-proposed/universe) [1.0.0-1] (no packageset) [05:23] -queuebot:#ubuntu-release- New binary: node-clone-buffer [amd64] (zesty-proposed/universe) [1.0.0-1] (no packageset) [05:23] -queuebot:#ubuntu-release- New binary: node-detect-newline [amd64] (zesty-proposed/universe) [2.1.0-1] (no packageset) [05:23] -queuebot:#ubuntu-release- New binary: node-commondir [amd64] (zesty-proposed/universe) [1.0.1-1] (no packageset) [05:23] -queuebot:#ubuntu-release- New binary: node-find-cache-dir [amd64] (zesty-proposed/universe) [0.1.1-1] (no packageset) [05:24] -queuebot:#ubuntu-release- New binary: node-is-stream [amd64] (zesty-proposed/universe) [1.1.0-1] (no packageset) [05:24] -queuebot:#ubuntu-release- New binary: node-loader-utils [amd64] (zesty-proposed/universe) [0.2.16-1] (no packageset) [05:24] -queuebot:#ubuntu-release- New binary: node-is-valid-glob [amd64] (zesty-proposed/universe) [0.3.0-1] (no packageset) [05:24] -queuebot:#ubuntu-release- New binary: node-pkg-dir [amd64] (zesty-proposed/universe) [1.0.0-1] (no packageset) [05:25] -queuebot:#ubuntu-release- New binary: node-remove-trailing-separator [amd64] (zesty-proposed/universe) [1.0.1-1] (no packageset) [05:25] -queuebot:#ubuntu-release- New binary: node-set-blocking [amd64] (zesty-proposed/universe) [2.0.0-1] (no packageset) [05:25] -queuebot:#ubuntu-release- New binary: node-vali-date [amd64] (zesty-proposed/universe) [1.0.0-1] (no packageset) [05:25] -queuebot:#ubuntu-release- New binary: node-replace-ext [amd64] (zesty-proposed/universe) [1.0.0-1] (no packageset) [05:25] -queuebot:#ubuntu-release- New binary: node-y18n [amd64] (zesty-proposed/universe) [3.2.1-1] (no packageset) [05:25] -queuebot:#ubuntu-release- New binary: node-slash [amd64] (zesty-proposed/universe) [1.0.0-1] (no packageset) === cpaelzer_ is now known as cpaelzer [07:42] pitti: morning! according to update_excuses, blender is still missing a build on ppc64el and is not considered. I was under the impression the removal you did yesterday would make it a valid candidate [07:50] ginggs: oh -- I think I removed 2.77.a+dfsg0-9 binaries, but apparently there's still some 2.77.a+dfsg0-9build1 ppc64el binaries somewhere [07:51] blender | 2.77.a+dfsg0-9build1 | zesty-proposed/universe | ppc64el [07:51] $ remove-package -b -a ppc64el -e 2.77.a+dfsg0-9build1 -m 'unblock glew transition, uninteresting for this arch' blender blender-data blender-dbg [07:51] Could not find binaries for 'blender/2.77.a+dfsg0-9build1' in zesty . Exiting. [07:51] bah, remove-package, what do you want from me [07:52] ah, -s zesty-proposed; killed [07:52] ginggs: ^ should work for realz now, sorry [07:54] pitti: thanks! [08:01] -queuebot:#ubuntu-release- Unapproved: sssd (trusty-proposed/main) [1.11.8-0ubuntu0.2 => 1.11.8-0ubuntu0.3] (ubuntu-desktop) [09:08] -queuebot:#ubuntu-release- Unapproved: libvirt (xenial-proposed/main) [1.3.1-1ubuntu10.5 => 1.3.1-1ubuntu10.6] (ubuntu-server, virt) [09:40] -queuebot:#ubuntu-release- Unapproved: gst-plugins-bad1.0 (xenial-proposed/universe) [1.8.3-1ubuntu0.1 => 1.8.3-1ubuntu0.2] (ubuntustudio) [09:45] -queuebot:#ubuntu-release- Unapproved: gstreamer-vaapi (xenial-proposed/universe) [1.8.2-1~ubuntu2 => 1.8.3-1ubuntu0.1] (no packageset) [10:53] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-drivers-common [source] (trusty-proposed) [1:0.2.91.12] [10:54] -queuebot:#ubuntu-release- Unapproved: libdrm (xenial-proposed/main) [2.4.67-1ubuntu0.16.04.2 => 2.4.70-1~ubuntu16.04.1] (core, xorg) [11:07] -queuebot:#ubuntu-release- Unapproved: accepted nvidia-prime [source] (trusty-proposed) [0.6.2.1] [12:13] -queuebot:#ubuntu-release- Packageset: Added dovecot-antispam to ubuntu-server in zesty [13:49] seb128: Hi! I'm not sure I understand what this is telling me: http://people.canonical.com/~ubuntu-archive/proposed-migration/zesty/update_excuses.html#libertine [13:49] seb128: Is there anything to be concerned about or does it just need a review of an admin? [13:50] hey ChrisTownsend [13:50] seb128: Good afternoon:) [13:52] ChrisTownsend, hum, I need to have a look [13:52] libertine-xmir-tools/amd64 unsatisfiable Depends: matchbox-window-manager [13:52] does that binary needs to be in main? [13:53] that binary = libertine-xmir-tools [13:53] seb128: No [13:53] k, so I guess it needs to be moved to universe [13:53] let me have a look [13:53] seb128: At this time, none of the new packages listed there needs to be in main. [13:54] seb128: I think a few of the libertine binaries are in a main, but most are in universe still. [13:54] seb128: Thanks [13:54] seb128: Ahh, since libertine source package is in main, it assumes any new binaries are targeted to main, right? [13:57] ChrisTownsend, no, it's the archive admin who accepts those who decide where to put them, if nothing in main depends on them they should just go to universe [13:57] -queuebot:#ubuntu-release- New: accepted exo [amd64] (zesty-proposed) [0.11.2-1] [13:57] -queuebot:#ubuntu-release- New: accepted exo [armhf] (zesty-proposed) [0.11.2-1] [13:57] -queuebot:#ubuntu-release- New: accepted exo [powerpc] (zesty-proposed) [0.11.2-1] [13:57] -queuebot:#ubuntu-release- New: accepted exo [s390x] (zesty-proposed) [0.11.2-1] [13:57] -queuebot:#ubuntu-release- New: accepted exo [arm64] (zesty-proposed) [0.11.2-1] [13:57] -queuebot:#ubuntu-release- New: accepted exo [ppc64el] (zesty-proposed) [0.11.2-1] [13:57] -queuebot:#ubuntu-release- New: accepted exo [i386] (zesty-proposed) [0.11.2-1] [13:57] seb128: Ok [13:57] -queuebot:#ubuntu-release- New: accepted googletest [sync] (zesty-proposed) [1.8.0-2] [13:57] -queuebot:#ubuntu-release- New: accepted voctomix-outcasts [amd64] (zesty-proposed) [0.3+git20161119-2] [13:57] -queuebot:#ubuntu-release- New: accepted voctomix-outcasts [amd64] (zesty-proposed) [0.3+git20161119-1] [13:59] pitti, hi, sbuild testsuite is sad, can you please hint it? [14:00] installing buildd with no configuration makes the systemd daemon fail [14:00] -queuebot:#ubuntu-release- New: accepted node-clone-buffer [amd64] (zesty-proposed) [1.0.0-1] [14:00] -queuebot:#ubuntu-release- New: accepted node-commondir [amd64] (zesty-proposed) [1.0.1-1] [14:00] -queuebot:#ubuntu-release- New: accepted node-find-cache-dir [amd64] (zesty-proposed) [0.1.1-1] [14:00] -queuebot:#ubuntu-release- New: accepted node-is-valid-glob [amd64] (zesty-proposed) [0.3.0-1] [14:00] -queuebot:#ubuntu-release- New: accepted node-pkg-dir [amd64] (zesty-proposed) [1.0.0-1] [14:00] -queuebot:#ubuntu-release- New: accepted node-replace-ext [amd64] (zesty-proposed) [1.0.0-1] [14:00] -queuebot:#ubuntu-release- New: accepted node-slash [amd64] (zesty-proposed) [1.0.0-1] [14:00] -queuebot:#ubuntu-release- New: accepted node-y18n [amd64] (zesty-proposed) [3.2.1-1] [14:00] I think this is expected and the same in Debian, I don't see reason for starting buildd without changing the configuration [14:00] -queuebot:#ubuntu-release- New: accepted node-clone-stats [amd64] (zesty-proposed) [1.0.0-1] [14:00] -queuebot:#ubuntu-release- New: accepted node-is-stream [amd64] (zesty-proposed) [1.1.0-1] [14:00] -queuebot:#ubuntu-release- New: accepted node-remove-trailing-separator [amd64] (zesty-proposed) [1.0.1-1] [14:00] -queuebot:#ubuntu-release- New: accepted node-vali-date [amd64] (zesty-proposed) [1.0.0-1] [14:00] -queuebot:#ubuntu-release- New: accepted node-detect-newline [amd64] (zesty-proposed) [2.1.0-1] [14:00] -queuebot:#ubuntu-release- New: accepted node-set-blocking [amd64] (zesty-proposed) [2.0.0-1] [14:00] -queuebot:#ubuntu-release- New: accepted node-loader-utils [amd64] (zesty-proposed) [0.2.16-1] [14:00] hey LocutusOfBorg [14:00] LocutusOfBorg: congrats to your new core-dev badge! [14:01] thanks :) [14:01] -queuebot:#ubuntu-release- New: accepted python-vmware-nsxlib [source] (zesty-proposed) [0.2.0-0ubuntu1] [14:01] LocutusOfBorg: err, I don't just want to ignore this -- if sbuild doesn't work, that's bad, let's fix it [14:02] this isn't sbuild, but buildd [14:02] this is quite obviously a regression in 0.72 [14:02] and installing it, see it starting and than exiting because of no-configuration seems somewhat strange [14:02] isn't better a failure and exit2? [14:02] in any case, the same behaviour is in Debian [14:02] lets ping josh [14:04] -queuebot:#ubuntu-release- New binary: python-vmware-nsxlib [amd64] (zesty-proposed/universe) [0.2.0-0ubuntu1] (no packageset) [14:05] -queuebot:#ubuntu-release- New: accepted python-vmware-nsxlib [amd64] (zesty-proposed) [0.2.0-0ubuntu1] [14:05] -queuebot:#ubuntu-release- New binary: googletest [ppc64el] (zesty-proposed/universe) [1.8.0-2] (no packageset) [14:05] -queuebot:#ubuntu-release- New binary: googletest [s390x] (zesty-proposed/universe) [1.8.0-2] (no packageset) [14:06] LocutusOfBorg: perfectly reproducible in a sid VM, so that's an RC bug against the "buildd" package [14:07] -queuebot:#ubuntu-release- New binary: googletest [amd64] (zesty-proposed/universe) [1.8.0-2] (no packageset) [14:07] pitti, you sure? I mean, what is the point of it being started when there is no configuration? [14:07] LocutusOfBorg: packages must not fail to install [14:07] I admit, I don't know such buildd package [14:07] mmm ok [14:07] it's of course fine to *not start*, but that's not the same as "package fails and breaks apt" [14:07] -queuebot:#ubuntu-release- New binary: googletest [i386] (zesty-proposed/universe) [1.8.0-2] (no packageset) [14:08] LocutusOfBorg: neither do I, but that's a property that's true for all packages [14:08] failure to install -> RC bug [14:08] ack [14:08] going to open an RC [14:08] -queuebot:#ubuntu-release- New binary: googletest [powerpc] (zesty-proposed/universe) [1.8.0-2] (no packageset) [14:09] LocutusOfBorg: thank you [14:10] reopening #842057 [14:15] -queuebot:#ubuntu-release- New binary: googletest [arm64] (zesty-proposed/universe) [1.8.0-2] (no packageset) [14:19] -queuebot:#ubuntu-release- New binary: googletest [armhf] (zesty-proposed/universe) [1.8.0-2] (no packageset) [14:20] hurray googletest is built everywhere :p [14:27] -queuebot:#ubuntu-release- New: accepted googletest [amd64] (zesty-proposed) [1.8.0-2] [14:27] -queuebot:#ubuntu-release- New: accepted googletest [armhf] (zesty-proposed) [1.8.0-2] [14:27] -queuebot:#ubuntu-release- New: accepted googletest [powerpc] (zesty-proposed) [1.8.0-2] [14:27] -queuebot:#ubuntu-release- New: accepted googletest [s390x] (zesty-proposed) [1.8.0-2] [14:27] -queuebot:#ubuntu-release- New: accepted googletest [arm64] (zesty-proposed) [1.8.0-2] [14:27] -queuebot:#ubuntu-release- New: accepted googletest [ppc64el] (zesty-proposed) [1.8.0-2] [14:27] -queuebot:#ubuntu-release- New: accepted googletest [i386] (zesty-proposed) [1.8.0-2] [16:47] -queuebot:#ubuntu-release- New binary: gcc-6-cross [amd64] (zesty-proposed/main) [13ubuntu3] (no packageset) [22:07] -queuebot:#ubuntu-release- Unapproved: cloud-init (yakkety-proposed/main) [0.7.8-15-g6e45ffb-0ubuntu1 => 0.7.8-49-g9e904bb-0ubuntu1~16.10.1] (edubuntu, ubuntu-cloud, ubuntu-server)