=== ahoneybun_ is now known as ahoneybun
[01:42] -queuebot:#ubuntu-release- Unapproved: xorg-server-lts-xenial (trusty-proposed/main) [2:1.18.3-1ubuntu2.2~trusty3 => 2:1.18.3-1ubuntu2.3~trusty1] (no packageset)
[03:02] -queuebot:#ubuntu-release- New: accepted graphene [source] (zesty-proposed) [1.5.4-0ubuntu1]
[03:03] -queuebot:#ubuntu-release- Unapproved: python-os-brick (xenial-proposed/main) [1.2.0-2ubuntu0.1 => 1.2.0-2ubuntu0.2] (openstack, ubuntu-server)
[03:07] -queuebot:#ubuntu-release- New binary: graphene [ppc64el] (zesty-proposed/universe) [1.5.4-0ubuntu1] (no packageset)
[03:07] -queuebot:#ubuntu-release- New binary: graphene [amd64] (zesty-proposed/universe) [1.5.4-0ubuntu1] (no packageset)
[03:08] -queuebot:#ubuntu-release- New binary: graphene [s390x] (zesty-proposed/universe) [1.5.4-0ubuntu1] (no packageset)
[03:09] -queuebot:#ubuntu-release- Unapproved: accepted xorg-server-lts-xenial [source] (trusty-proposed) [2:1.18.3-1ubuntu2.3~trusty1]
[03:09] -queuebot:#ubuntu-release- New binary: graphene [arm64] (zesty-proposed/universe) [1.5.4-0ubuntu1] (no packageset)
[03:11] -queuebot:#ubuntu-release- New binary: graphene [powerpc] (zesty-proposed/universe) [1.5.4-0ubuntu1] (no packageset)
[03:11] -queuebot:#ubuntu-release- Unapproved: python-os-brick (yakkety-proposed/main) [1.6.1-0ubuntu1 => 1.6.1-0ubuntu1.1] (openstack, ubuntu-server)
[03:28] <tjaalton> slangasek: what happened to xorg-server-lts-xenial? 1.18.4 was already pretty much verified but it got replaced with an older version?
[03:29] <slangasek> tjaalton: there were a significant number of bugs linked from the changelog which had not been verified; I was discussing it with bdmurray because this was blocking fixing snapd installability on the desktop, and as we couldn't see any immediate path to getting this one verified to his satisfaction, we decided to swap in just the packaging fixes and reupload 1.18.4 afterwards
[03:30] <tjaalton> ok
[03:30] <tjaalton> well
[03:31] <tjaalton> I don't see anyone actually verifying all those bugs
[03:31] <tjaalton> on trusty
[03:32] <slangasek> then it didn't really seem to be following the SRU process?
[03:32] <tjaalton> aren't these backports special?
[03:33] <slangasek> tjaalton: bdmurray expressed concern about the test case in bug #1619142
[03:33] <ubot5> bug 1619142 in xorg-server-lts-xenial (Ubuntu Trusty) "[MRE] Update to 1.18.4" [Undecided,Fix committed] https://launchpad.net/bugs/1619142
[03:34] <slangasek> I didn't review the SRU bugs myself in any detail, I'm just the messenger here
[03:34] <tjaalton> sure
[03:36] <slangasek> tjaalton: anyway, the SRU had certainly stalled out already by having a bunch of other, non-verified bugs linked from the changelog / .changes file... hwe backports aren't special for that
[03:36] <tjaalton> should've uploaded with just the mre/snapd bugs?
[03:36] <tjaalton> in .changes
[03:37] <tjaalton> that'd take care of the process ;)
[03:46] <bdmurray> It wouldn't improve the test case / results in bug 1619142 though
[03:46] <ubot5> bug 1619142 in xorg-server-lts-xenial (Ubuntu Trusty) "[MRE] Update to 1.18.4" [Undecided,Fix committed] https://launchpad.net/bugs/1619142
[03:48] <tjaalton> that bug didn't actually have any test case when the upload was acked ;)
[03:49] <tjaalton> then someone requested it yesterday and I put something
[03:52] <tjaalton> added some
[09:10] <philroche> Hi, would anyone be able to do accept gce-compute-image-packages in to trusty-proposed? This is a new package and exists in zesty, yakkety and xenial already. lp bug - https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1643585 Package in upload queue - https://launchpad.net/ubuntu/trusty/+queue?queue_state=0&queue_text=gce-compute-image-packages.
[09:10] <ubot5> Ubuntu bug 1643585 in gce-compute-image-packages (Ubuntu Trusty) "Backporting gce-compute-image-packages " [Undecided,New]
=== marcusto_ is now known as marcustomlinson
[10:33] <apw> philroche, other than the version number being inconistent with those in the other backports it looks ok
[10:35] <ginggs> apw: would you please add 'force-badtest ocrmypdf/4.3.5-2/s390x' to your hints?
[10:36] <ginggs> and 'force-badtest freecad/0.16+dfsg2-3/ppc64el freecad/0.16+dfsg2-3/s390x' in p.itti's hints
[10:36] <philroche> apw. Updating version number now
[10:38] <ginggs> apw: and lastly, please 'force-badtest python-pysam/0.10.0+ds-1ubuntu1/armhf python-pysam/0.10.0+ds-1ubuntu1/i386' - it doesn't actually build on those, not sure why its trying to run tests there
[10:42] -queuebot:#ubuntu-release- New: rejected gce-compute-image-packages [source] (trusty-proposed) [20160930-0ubuntu3~14.04]
[10:43] <apw> ^ rejecting to get a new version number
[10:51] -queuebot:#ubuntu-release- New source: gce-compute-image-packages (trusty-proposed/primary) [20160930-0ubuntu3~14.04.0]
[10:52] <philroche> apw: Version number for gce-compute-image-packages updated and reuploaded https://launchpad.net/ubuntu/trusty/+queue?queue_state=0&queue_text=gce-compute-image-packages
[10:59] <apw> philroche, it just told me above :)
[11:05] <philroche> :)
=== marcusto_ is now known as marcustomlinson
[11:12] -queuebot:#ubuntu-release- New: accepted gce-compute-image-packages [source] (trusty-proposed) [20160930-0ubuntu3~14.04.0]
[11:12] <apw> philroche, ^
[11:14] -queuebot:#ubuntu-release- New binary: gce-compute-image-packages [i386] (trusty-proposed/universe) [20160930-0ubuntu3~14.04.0] (ubuntu-cloud)
[11:17] -queuebot:#ubuntu-release- Packageset: 160 entries have been added or removed
[11:32] -queuebot:#ubuntu-release- Packageset: 111 entries have been added or removed
[11:53] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (yakkety-proposed) [2.22.2+16.10]
[11:54] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (xenial-proposed) [2.22.2]
[11:55] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (trusty-proposed) [2.22.2~14.04]
[12:02] <apw> Laney, have you seen cases where britney run tests for packages which are in depwait ?
[12:05] <Laney> apw: no, but I've never looked for such a thing - you can check th elogs to see what it did
[12:05] <Laney> also that's the kind of thing you could write a testcase for and then fix ;-)
[12:05] <apw> Laney, :-p
[12:06] <apw> ginggs, look sensible, done.
[12:06] <Laney> Although I suppose it might be valid to run testsuites in the case of arch:all binaries
[12:06]  * apw thinks about that ... maybe
[12:06] <Laney> Maybe
[12:07] <apw> it really feels if we have builds in a faliure state that we cannot know if we have what we need to run tests
[12:07] <apw> we may have, but we do not know
[12:09] -queuebot:#ubuntu-release- New: accepted libopenshot [i386] (zesty-proposed) [0.1.2+ds1-1]
[12:09] -queuebot:#ubuntu-release- New: accepted libopenshot [i386] (zesty-proposed) [0.1.2+ds1-3]
[12:09] -queuebot:#ubuntu-release- New: accepted libopenshot [amd64] (zesty-proposed) [0.1.2+ds1-3]
[12:13] <Laney> Looks like in this case it used to work on those arches and then stopped with an update
[12:13] <Laney> otherwise it wouldn't be a regression
[12:15] <Laney> And the source does build an arch:all binary package which could be tested
[12:17] -queuebot:#ubuntu-release- Packageset: Removed myspell-ku from personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Removed mythes-it from personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Removed mythes-sv from personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Added fonts-adf to personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Added fonts-atarismall to personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Added fonts-ddc-uchen to personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Added fonts-firacode to personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Added fonts-go to personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Added fonts-liberation2 to personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Added fonts-ocr-b to personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Added fonts-oradano-mincho-gsrr to personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Added fonts-sambhota-tsugring to personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Added fonts-tiresias to personal-gunnarhj in zesty
[12:17] -queuebot:#ubuntu-release- Packageset: Added hunspell-bo to personal-gunnarhj in zesty
[12:26] <ginggs> apw: many thanks!
[13:17] -queuebot:#ubuntu-release- New: accepted gce-compute-image-packages [i386] (trusty-proposed) [20160930-0ubuntu3~14.04.0]
[13:19] <acheronuk> Hi. Can someone please review and accept our sources in the NEW queue please? they are needed before we can our packageset refresh done.
[13:19] <acheronuk> namely minuet, konqueror, kommander, klinkstatus, kimagemapeditor,kfind, kfilereplace, keditbookmarks, kdialog
[13:19] <acheronuk> thanks
[13:19] <acheronuk> most of those are actually OLD packages, but KDE have now split the sources
[13:19] <acheronuk> .
[13:19] <acheronuk> minuet is part of the full KDE applications 16.04.0 release that we were unable to get into yakkety, due to not have some build depends for it in the archive
[13:19] <acheronuk> see: https://www.kde.org/announcements/announce-applications-16.04.0.php
[13:19] <acheronuk> in 16.12 KDE app we are now doing...
[13:19] <acheronuk> kde-baseapps (split into kdialog, keditbookmarks, kfind, konqueror)
[13:19] <acheronuk> kdewebdev (split into kfilereplace, kimagemapeditor, klinkstatus, kommander)
[13:19] <acheronuk> hence these are nothing new per se. just split and some ported to KF5
[13:19] <acheronuk> see: https://community.kde.org/Applications/16.12_Release_Notes#Tarballs_that_we_have_split
[13:19] <acheronuk> thanks :)
[13:37] -queuebot:#ubuntu-release- Unapproved: im-config (xenial-proposed/main) [0.29-1ubuntu12.3 => 0.29-1ubuntu12.4] (input-methods, kubuntu, personal-gunnarhj, ubuntu-desktop)
[13:50] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (zesty-proposed/main) [4.9.0-16.17] (core, kernel)
[13:51] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (zesty-proposed) [4.9.0-16.17]
[13:56] -queuebot:#ubuntu-release- New: accepted kdeclarative [amd64] (zesty-proposed) [5.30.0-0ubuntu1]
[13:56] -queuebot:#ubuntu-release- New: accepted kdeclarative [armhf] (zesty-proposed) [5.30.0-0ubuntu1]
[13:56] -queuebot:#ubuntu-release- New: accepted kdeclarative [powerpc] (zesty-proposed) [5.30.0-0ubuntu1]
[13:56] -queuebot:#ubuntu-release- New: accepted kdeclarative [s390x] (zesty-proposed) [5.30.0-0ubuntu1]
[13:56] -queuebot:#ubuntu-release- New: accepted kdeclarative [arm64] (zesty-proposed) [5.30.0-0ubuntu1]
[13:56] -queuebot:#ubuntu-release- New: accepted kdeclarative [ppc64el] (zesty-proposed) [5.30.0-0ubuntu1]
[13:56] -queuebot:#ubuntu-release- New: accepted kdeclarative [i386] (zesty-proposed) [5.30.0-0ubuntu1]
[14:04] -queuebot:#ubuntu-release- New: accepted knewstuff [amd64] (zesty-proposed) [5.30.0-0ubuntu1]
[14:04] -queuebot:#ubuntu-release- New: accepted knewstuff [armhf] (zesty-proposed) [5.30.0-0ubuntu1]
[14:04] -queuebot:#ubuntu-release- New: accepted knewstuff [powerpc] (zesty-proposed) [5.30.0-0ubuntu1]
[14:04] -queuebot:#ubuntu-release- New: accepted knewstuff [s390x] (zesty-proposed) [5.30.0-0ubuntu1]
[14:04] -queuebot:#ubuntu-release- New: accepted knewstuff [arm64] (zesty-proposed) [5.30.0-0ubuntu1]
[14:04] -queuebot:#ubuntu-release- New: accepted knewstuff [ppc64el] (zesty-proposed) [5.30.0-0ubuntu1]
[14:04] -queuebot:#ubuntu-release- New: accepted knewstuff [i386] (zesty-proposed) [5.30.0-0ubuntu1]
[15:13] -queuebot:#ubuntu-release- Unapproved: landscape-client (trusty-proposed/main) [14.12-0ubuntu0.14.04 => 14.12-0ubuntu4.14.04] (ubuntu-desktop, ubuntu-server)
[15:52] -queuebot:#ubuntu-release- New binary: graphene [ppc64el] (zesty-proposed/universe) [1.5.4-0ubuntu2] (no packageset)
[15:53] <apw> acheronuk, as these new binaries are not yet in debian, do we have confirmation that debian will use the same epoch ?  we do not want to be epoching ahead of them
[15:53] -queuebot:#ubuntu-release- New binary: graphene [amd64] (zesty-proposed/universe) [1.5.4-0ubuntu2] (no packageset)
[15:53] -queuebot:#ubuntu-release- New binary: graphene [i386] (zesty-proposed/universe) [1.5.4-0ubuntu2] (no packageset)
[15:53] -queuebot:#ubuntu-release- New binary: graphene [arm64] (zesty-proposed/universe) [1.5.4-0ubuntu2] (no packageset)
[15:54] -queuebot:#ubuntu-release- Unapproved: im-config (xenial-proposed/main) [0.29-1ubuntu12.3 => 0.29-1ubuntu12.4] (input-methods, kubuntu, personal-gunnarhj, ubuntu-desktop)
[15:55] -queuebot:#ubuntu-release- New binary: graphene [s390x] (zesty-proposed/universe) [1.5.4-0ubuntu2] (no packageset)
[15:56] -queuebot:#ubuntu-release- New binary: graphene [powerpc] (zesty-proposed/universe) [1.5.4-0ubuntu2] (no packageset)
[15:57] -queuebot:#ubuntu-release- New: rejected graphene [amd64] (zesty-proposed) [1.5.4-0ubuntu1]
[15:57] -queuebot:#ubuntu-release- New: rejected graphene [powerpc] (zesty-proposed) [1.5.4-0ubuntu1]
[15:57] -queuebot:#ubuntu-release- New: rejected graphene [s390x] (zesty-proposed) [1.5.4-0ubuntu1]
[15:57] -queuebot:#ubuntu-release- New: rejected graphene [arm64] (zesty-proposed) [1.5.4-0ubuntu1]
[15:57] -queuebot:#ubuntu-release- New: rejected graphene [ppc64el] (zesty-proposed) [1.5.4-0ubuntu1]
[16:11] <acheronuk> apw: keditbookmarks, kdialog are genuinely not yet in debian so the epoch was dropped.
[16:12] <acheronuk> the others ARE in debian, with an epoch, so we cannot drop it for those debs
[16:12] <acheronuk> https://packages.debian.org/sid/konqueror
[16:12] <acheronuk> https://packages.debian.org/sid/klinkstatus
[16:12] <acheronuk> https://packages.debian.org/sid/kimagemapeditor
[16:12] <acheronuk> https://packages.debian.org/sid/kfind
[16:12] <acheronuk> https://packages.debian.org/sid/kfilereplace
[16:13] <apw> acheronuk, bah why do they not show up in rmadison
[16:14] <apw> oh ... there are already binary packages of those names ... right
[16:15] <acheronuk> yes, so where there were not, we dropped epoch. where there was, we could not for now
[16:16] <apw> i guess they cannot do anything other than what you have done
[16:23] -queuebot:#ubuntu-release- Unapproved: rejected im-config [source] (xenial-proposed) [0.29-1ubuntu12.4]
[16:25] -queuebot:#ubuntu-release- Unapproved: accepted im-config [source] (xenial-proposed) [0.29-1ubuntu12.4]
[16:28] -queuebot:#ubuntu-release- New binary: graphene [ppc64el] (zesty-proposed/universe) [1.5.4-0ubuntu3] (no packageset)
[16:29] -queuebot:#ubuntu-release- Unapproved: accepted lxd [source] (xenial-proposed) [2.0.9-0ubuntu1~16.04.1]
[16:29] -queuebot:#ubuntu-release- New binary: graphene [arm64] (zesty-proposed/universe) [1.5.4-0ubuntu3] (no packageset)
[16:29] -queuebot:#ubuntu-release- New binary: graphene [armhf] (zesty-proposed/universe) [1.5.4-0ubuntu3] (no packageset)
[16:30] -queuebot:#ubuntu-release- New binary: graphene [amd64] (zesty-proposed/universe) [1.5.4-0ubuntu3] (no packageset)
[16:30] -queuebot:#ubuntu-release- New binary: graphene [s390x] (zesty-proposed/universe) [1.5.4-0ubuntu3] (no packageset)
[16:30] -queuebot:#ubuntu-release- New binary: graphene [i386] (zesty-proposed/universe) [1.5.4-0ubuntu3] (no packageset)
[16:32] -queuebot:#ubuntu-release- New binary: graphene [powerpc] (zesty-proposed/universe) [1.5.4-0ubuntu3] (no packageset)
[16:34] -queuebot:#ubuntu-release- Unapproved: accepted lxc [source] (yakkety-proposed) [2.0.7-0ubuntu1~16.10.1]
[16:37] -queuebot:#ubuntu-release- Unapproved: accepted lxcfs [source] (yakkety-proposed) [2.0.6-0ubuntu1~16.10.1]
[16:40] -queuebot:#ubuntu-release- Unapproved: accepted lxcfs [source] (xenial-proposed) [2.0.6-0ubuntu1~16.04.1]
[16:41] -queuebot:#ubuntu-release- Unapproved: accepted lxc [source] (xenial-proposed) [2.0.7-0ubuntu1~16.04.1]
[16:49] -queuebot:#ubuntu-release- Unapproved: accepted os-prober [source] (xenial-proposed) [1.70ubuntu3.3]
[16:52] <apw> jbicha, are you going to fix that graphene armhf ftbfs ?
[16:53] <apw> jbicha, that is intended as a query, as it is stuck in New on all other arches
[17:26] <jbicha> apw: it's fixed now :) https://launchpad.net/ubuntu/+source/graphene/1.5.4-0ubuntu3
[17:27] <apw> jbicha, heh
[17:30] -queuebot:#ubuntu-release- New: rejected graphene [amd64] (zesty-proposed) [1.5.4-0ubuntu2]
[17:30] -queuebot:#ubuntu-release- New: rejected graphene [i386] (zesty-proposed) [1.5.4-0ubuntu2]
[17:30] -queuebot:#ubuntu-release- New: rejected graphene [ppc64el] (zesty-proposed) [1.5.4-0ubuntu2]
[17:30] -queuebot:#ubuntu-release- New: rejected graphene [arm64] (zesty-proposed) [1.5.4-0ubuntu2]
[17:30] -queuebot:#ubuntu-release- New: rejected graphene [s390x] (zesty-proposed) [1.5.4-0ubuntu2]
[17:30] -queuebot:#ubuntu-release- New: rejected graphene [powerpc] (zesty-proposed) [1.5.4-0ubuntu2]
[17:31] -queuebot:#ubuntu-release- New: accepted graphene [amd64] (zesty-proposed) [1.5.4-0ubuntu3]
[17:31] -queuebot:#ubuntu-release- New: accepted graphene [armhf] (zesty-proposed) [1.5.4-0ubuntu3]
[17:31] -queuebot:#ubuntu-release- New: accepted graphene [powerpc] (zesty-proposed) [1.5.4-0ubuntu3]
[17:32] -queuebot:#ubuntu-release- New: accepted graphene [s390x] (zesty-proposed) [1.5.4-0ubuntu3]
[17:32] -queuebot:#ubuntu-release- New: accepted graphene [arm64] (zesty-proposed) [1.5.4-0ubuntu3]
[17:32] -queuebot:#ubuntu-release- New: accepted graphene [ppc64el] (zesty-proposed) [1.5.4-0ubuntu3]
[17:32] -queuebot:#ubuntu-release- New: accepted graphene [i386] (zesty-proposed) [1.5.4-0ubuntu3]
[17:33] <jbicha> thanks
[17:34] <acheronuk> apw: exactly, debian will have to do the same if they want to keep those apps
[17:36] <santa_> I have a question which is slightly offtopic here but I need to ask
[17:36] <santa_> we got recently a new testcase added to the kio testsuite which apparently needs to access the network
[17:37] <santa_> so it's failing on the official autopkgtest ubuntu infra
[17:37] <apw> santa_, i believe the lxc and docker.io tests do do that kind of thing
[17:38] <santa_> doing it by the book the correct solution would be adding the isolation-container restriction to the testsuite
[17:38] <nacc> santa_: i believe you can specify the isolation-container restriction ... yeah :)
[17:38] <santa_> however I'm concerned that this would result in the testsuite being skipped on the official infra
[17:39] <santa_> so I'm wondering if it would be better to just disable the test case which access the network
[17:40] <santa_> so we would get the tests running even if the official infra doesn't provide the stuff needed for isolation-container
[17:40] <santa_> so the million dollar question is: does the official infra provide support for that?
[17:40] <santa_> any other toughts?
[17:41] <santa_> apw: thanks for the info btw
[17:41] <nacc> santa_: could you break up the tests in d/t/control to have the tests that don't need network in one stanza and the one that does in another?
[17:41] <nacc> santa_: not sure if that's possible or not
[17:41] <apw> that indeed
[17:41] <apw> though all are at least containers
[17:42] <santa_> well I think i could break up the tests
[17:43] <santa_> calling the cmake thing to execute the one needing network, and another one to call the remaining tests
[17:43] <santa_> I would need to dig into that
[17:43] <nacc> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/d/docker.io/20170201_211202_f4e3c@/log.gz seems to imply docker.io is going to the network for something ("Pulling from library/hello-world")?
[17:43] <santa_> I have the impression it would be possible with enough time
[17:44] <santa_> nacc: indeed
[17:45] <apw> i suspect those have complex proxy management in them to make it work
[17:45] <apw> as i believe all arches are network capable but needing proxy
[17:46] <nacc> apw: ah good point
[17:46] <nacc> santa_: yeah, i'd look at what docker.io actually has to do to make it work
[17:48] <santa_> ok, I will try to dig into this if I have time
[17:48] <santa_> apw, nacc: thank you very much for the info :)
[18:43] -queuebot:#ubuntu-release- New: rejected snapd-glib [amd64] (zesty-proposed) [1.5-0ubuntu1]
[18:43] -queuebot:#ubuntu-release- New: rejected snapd-glib [s390x] (zesty-proposed) [1.5-0ubuntu1]
[18:43] -queuebot:#ubuntu-release- New: rejected snapd-glib [arm64] (zesty-proposed) [1.5-0ubuntu1]
[19:10] -queuebot:#ubuntu-release- New: accepted snapd-glib [amd64] (zesty-proposed) [1.6-0ubuntu1]
[19:10] -queuebot:#ubuntu-release- New: accepted snapd-glib [armhf] (zesty-proposed) [1.6-0ubuntu1]
[19:10] -queuebot:#ubuntu-release- New: accepted snapd-glib [powerpc] (zesty-proposed) [1.6-0ubuntu1]
[19:10] -queuebot:#ubuntu-release- New: accepted snapd-glib [s390x] (zesty-proposed) [1.6-0ubuntu1]
[19:10] -queuebot:#ubuntu-release- New: accepted snapd-glib [arm64] (zesty-proposed) [1.6-0ubuntu1]
[19:10] -queuebot:#ubuntu-release- New: accepted snapd-glib [ppc64el] (zesty-proposed) [1.6-0ubuntu1]
[19:10] -queuebot:#ubuntu-release- New: accepted snapd-glib [i386] (zesty-proposed) [1.6-0ubuntu1]
[19:27] <cyphermox> fossfreedom_: why does budgie-wm need to be run with --replace for ubiquity-dm? Seems wrong and likely to look bad (ie. you need this if some other WM starts, and in that case, you'll see some flickering as the first wm dies and budgie-wm starts; it looks clunky)
[20:04] -queuebot:#ubuntu-release- Unapproved: flash-kernel (xenial-proposed/main) [3.0~rc.4ubuntu62.1.1 => 3.0~rc.4ubuntu62.2] (core)
[21:25] -queuebot:#ubuntu-release- New sync: linux-hwe (xenial-proposed/primary) [4.8.0-35.40~16.04.1]
[21:26] -queuebot:#ubuntu-release- New: accepted linux-hwe [sync] (xenial-proposed) [4.8.0-35.40~16.04.1]
[21:28] -queuebot:#ubuntu-release- New sync: linux-signed-hwe (xenial-proposed/primary) [4.8.0-35.40~16.04.1]
[21:38] <apw> infinity, the meta is in unstable
[21:51] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [sync] (xenial-proposed) [4.8.0-35.40~16.04.1]
[22:01] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (xenial-proposed/main) [4.8.0-35.40~16.04.1] (no packageset)
[22:05] -queuebot:#ubuntu-release- New sync: linux-meta-hwe (xenial-proposed/primary) [4.8.0.35.7]
[22:06] -queuebot:#ubuntu-release- New: accepted linux-meta-hwe [sync] (xenial-proposed) [4.8.0.35.7]
[22:06] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (xenial-proposed) [4.8.0-35.40~16.04.1]
[22:50] -queuebot:#ubuntu-release- Unapproved: bind9 (trusty-proposed/main) [1:9.9.5.dfsg-3ubuntu0.11 => 1:9.9.5.dfsg-3ubuntu0.12] (core)
[22:52] <lamont> tbf, ^^ the bind9 SRU was targeted at trusty-updates 4 march 2016.  /me is slow sometimes.
[23:08] <infinity> lamont: Well, to be fair, you are really, really, really old, so we expect things to sometimes slip your mind.
[23:08] <infinity> (Did I miss a "really"?)
[23:09] <lamont> I'm not old yet.  old is totally in the mind.  and I had other things on my mind that month.
[23:09] <lamont> :p
[23:09] <infinity> s/month/year/
[23:09] <lamont> infinity: does that mean you'll let it into proposed to percolate. :p
[23:10] <lamont> I'd offer to hug you, but I'm not sure which behavior that would incent.
[23:10] <lamont> doko: ever feel like you walked into the middle of a very awkward conversation?
[23:11] <infinity> You can hug doko, it's cool.
[23:12] <lamont> lol
[23:15] -queuebot:#ubuntu-release- Unapproved: accepted bind9 [source] (trusty-proposed) [1:9.9.5.dfsg-3ubuntu0.12]
[23:32] <lamont> ta