[00:34] -queuebot:#ubuntu-release- Unapproved: gnome-software (yakkety-proposed/main) [3.20.1+git20160923.2.7374bdc-0ubuntu1 => 3.20.1+git20161003.0.7ac7d1b-0ubuntu1] (ubuntu-desktop)
[02:01] -queuebot:#ubuntu-release- Unapproved: gvfs (yakkety-proposed/main) [1.28.2-1ubuntu2 => 1.30.0-1ubuntu1] (ubuntu-desktop)
[03:11] -queuebot:#ubuntu-release- Unapproved: appstream-glib (xenial-proposed/main) [0.5.13-1ubuntu3 => 0.5.13-1ubuntu4] (desktop-core)
[04:33] -queuebot:#ubuntu-release- Unapproved: kde4libs (yakkety-proposed/universe) [4:4.14.22-0ubuntu1 => 4:4.14.22-0ubuntu2] (kubuntu)
[04:36] <tsimonq2> hmmmmmmm ^
[04:38] -queuebot:#ubuntu-release- Unapproved: accepted kde4libs [source] (yakkety-proposed) [4:4.14.22-0ubuntu2]
[04:40] <tsimonq2> slangasek: thanks :)
[04:59] <Mirv> the virtualbox autopkgtest failure happens probably because of 4.8 kernel, and definitely not due to Qt. http://autopkgtest.ubuntu.com/packages/v/virtualbox/yakkety/amd64 - could it be ignored?
[05:06] -queuebot:#ubuntu-release- Unapproved: lxd (yakkety-proposed/main) [2.3-0ubuntu5 => 2.3-0ubuntu6] (edubuntu, ubuntu-server)
[05:08] -queuebot:#ubuntu-release- Unapproved: accepted lxd [source] (yakkety-proposed) [2.3-0ubuntu6]
[05:23] -queuebot:#ubuntu-release- Unapproved: pcl (yakkety-proposed/universe) [1.8.0+dfsg1-4ubuntu1 => 1.8.0+dfsg1-4ubuntu2] (no packageset)
[05:23] -queuebot:#ubuntu-release- Unapproved: sqlmap (yakkety-proposed/universe) [1.0.9-1 => 1.0.10-1] (no packageset) (sync)
[05:24] -queuebot:#ubuntu-release- Unapproved: accepted pcl [source] (yakkety-proposed) [1.8.0+dfsg1-4ubuntu2]
[05:25] -queuebot:#ubuntu-release- Unapproved: accepted sqlmap [sync] (yakkety-proposed) [1.0.10-1]
[05:31] -queuebot:#ubuntu-release- Unapproved: libint2 (yakkety-proposed/universe) [2.1.0-1.1 => 2.1.0-2] (no packageset) (sync)
[05:31] -queuebot:#ubuntu-release- Unapproved: accepted libint2 [sync] (yakkety-proposed) [2.1.0-2]
[07:04] -queuebot:#ubuntu-release- Unapproved: kover (yakkety-proposed/universe) [1:4-9 => 1:4-11] (no packageset) (sync)
[07:05] -queuebot:#ubuntu-release- Unapproved: accepted kover [sync] (yakkety-proposed) [1:4-11]
[08:03] <mardy> Laney: hi! Could you please remove the yakkety s390x packages created by online-accounts-api? https://launchpad.net/ubuntu/yakkety/+source/online-accounts-api
[08:04] <Laney> mardy: nope, can't do that, sorry - you need a member of ubuntu-archive
[08:04] <Laney> mardy: You should fix the package to stop building those though, if you haven't already
[08:04] <mardy> Laney: yep, I've the change silo'd
[08:05] <mardy> cjwatson: hi! could you help with this? ^
[08:05] <acheronuk> [10:27] <jbicha> could kdegraphics-mobipocket be accepted from the yakkety rejected queue? I see that okular depends on the new version
[08:05] <acheronuk> indeed it does ^^^
[08:43] <apw> acheronuk, do we know why it was rejected in teh first place ?
[08:47] <cjwatson> mardy: not this week, slammed
[08:47] <cjwatson> mardy: pick another AA victim :)
[08:47] <mardy> cjwatson: ok, thanks anyway
[08:48] <mardy> didrocks: hi! Want to be a victim? ^
[08:52] <didrocks> mardy: I don't have any official time anymore to do AA work :/
[08:53] <mardy> didrocks: no, thanks anyways :-)
[08:54] <apw> mardy, why do they need removing ?
[08:56] <mardy> apw: because they prevent bileto siloes from building, they get stuck in "dependency wait" state
[08:57] <apw> is this more of your upstart disaster ?
[08:58] <mardy> apw: mine? :-) but yes, I think it's related to upstart
[08:59] <apw> mardy, and i don't th
[09:00] <apw> mardy, and i don't think that those existing is stopping your builds, the depwait there is presumably because you have a dirty build-dep on upstart in s390x
[09:01] <mardy> apw: I've tried with and without build-dep on upstart, and it gets stuck anyway
[09:01] <apw> iirc the build-dep: was recommended to make the binaries not build as they are uninstallable as they have a runtime-dep on upstart, right ?
[09:01] <mardy> apw: yes, that's my understanding too
[09:02] <cjwatson> yeah, from what I remember of your situation, the dep-wait is intentional
[09:02] <cjwatson> but perhaps your binaries need to be pulled out so that this doesn't block
[09:02] <apw> yeah that sounds like what i am expecting, that this is the last time they need removing
[09:04] <mardy> apw: do you have time to help?
[09:05] -queuebot:#ubuntu-release- Unapproved: witty (yakkety-proposed/universe) [3.3.5+dfsg-1ubuntu2 => 3.3.5+dfsg-1.1ubuntu1] (no packageset)
[09:05] <apw> mardy, looking at the ramifications now
[09:06] -queuebot:#ubuntu-release- Unapproved: accepted witty [source] (yakkety-proposed) [3.3.5+dfsg-1.1ubuntu1]
[09:07] <shadeslayer> acheronuk: hm, forwarding all those emails is going to be tricky
[09:07] <shadeslayer> I'll see what I can do
[09:13] <apw> mardy, can i assume storage-framework is one of yours, and you won't care if it no longer works on s390x ?
[09:14] <mardy> apw: yes, no one will care
[09:21] <acheronuk> apw: due to no real changes in the source for this release I think. kde bump their release versions to have a full versioned set for each release for these. reason for no changes in many is that Qt/kde4 dev on those stopped as a Qt5/kf5 port was being done but not ready
[09:21] -queuebot:#ubuntu-release- Unapproved: accepted gnome-software [source] (yakkety-proposed) [3.20.1+git20161003.0.7ac7d1b-0ubuntu1]
[09:22] <apw> mardy, ok removed ... let the publisher run (~1hr) and see if that unblocks your silo
[09:24] <acheronuk> shadeslayer: no worries. whatever you can *reasonably* do
[09:25] <mardy> apw: thanks a lot!
[09:30] <acheronuk> apw: [09:58] <slangasek> acheronuk: if the kubuntu team wants the new version numbers, they can upload later; final freeze is just not a good time for that kind of upload
[09:31] <acheronuk> apw: unfortunately as you can see, some of them block builds if not accepted
[09:34] -queuebot:#ubuntu-release- Packageset: Added im-config to personal-gunnarhj in yakkety
[09:34] <bluesabre> Hello release team, Xubuntu has some late-landing changes for our Yakkety wallpaper, can we please get an ack for the following?
[09:34] <bluesabre> https://bugs.launchpad.net/ubuntu/+source/xubuntu-artwork/+bug/1629650
[09:34] <bluesabre> https://bugs.launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/+bug/1629648
[09:53] <xnox> pitti, could you please hint over http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#libgnupg-interface-perl test suite results. it appears those tests fail in the container runners only.
[09:53] <apw> xnox, why did they work before ?
[09:53] <xnox> apw, never with gnupg2 =)
[09:54] <apw> that really, really does not deserve a happy emogi !
[09:54] <xnox> they do work on bare-metal and kvm.
[09:54] <xnox> (and pass)
[09:54] <xnox> (on s390x at least)
[09:55] <ginggs> would an archive admin remove NBS binaries wine and wine1.4-dev from yakkety, please?
[09:55] <xnox> gpg: can't connect to the agent: File name too long
[09:55] <xnox> gpg: error reading key: No secret key
[09:55] <xnox> not ok 1
[09:55] <xnox> *sigh*
[09:55] <xnox> apw, so first they think it's a good idea to use $GNUPGHOME for sockets, then they complain that filename is too long.
[09:56] <apw> xnox, don't we point HOME somewhere like /DIESCREAMING
[09:56] <xnox> apw, not anywhere in production, just on poor people's default sbuild
[09:57] <apw> ahh
[09:57] <xnox> 'HOME' => '/build/'  & $resolve_alternatives = 1; in my ~/.sbuildrc
[09:57] <xnox> to match launchpad
[10:01] <apw> ginggs, if i am reading this right there is a number of things depping on those that need a rebuild
[10:03] <ginggs> apw: nothing should need a rebuild
[10:04] <ginggs> apw: wine-stable and wine-development both Provides: wine
[10:07] <apw> so that might be NBS being too dumb i guess, hrm
[10:11] -queuebot:#ubuntu-release- Unapproved: mame (yakkety-proposed/multiverse) [0.176-3 => 0.177-1] (no packageset) (sync)
[10:13] -queuebot:#ubuntu-release- Unapproved: accepted mame [sync] (yakkety-proposed) [0.177-1]
[10:15] -queuebot:#ubuntu-release- Unapproved: ubuntu-ui-toolkit-gles (yakkety-proposed/universe) [1.3.2104+16.10.20160919.3 => 1.3.2104+16.10.20160929] (ubuntu-qt-packages) (sync)
[10:15] -queuebot:#ubuntu-release- Unapproved: ubuntu-ui-toolkit (yakkety-proposed/main) [1.3.2104+16.10.20160919.3 => 1.3.2104+16.10.20160929] (ubuntu-desktop, ubuntu-qt-packages) (sync)
[10:21] <mardy> apw: it worked, thanks a lot!
[10:24] -queuebot:#ubuntu-release- Unapproved: prelude-manager (yakkety-proposed/universe) [1.0.1-5.1ubuntu3 => 1.0.1-5.2] (no packageset) (sync)
[10:24] -queuebot:#ubuntu-release- Unapproved: accepted prelude-manager [sync] (yakkety-proposed) [1.0.1-5.2]
[10:26] <apw> ginggs, so yes the NBS report is too dumb, and in theory all those are removable... however I am not convinced that a provides: will trigger package replacement for old installs
[10:27] -queuebot:#ubuntu-release- Unapproved: bugwarrior (yakkety-proposed/universe) [1.4.0+git2016070901-1 => 1.4.0+git2016090101-1] (no packageset) (sync)
[10:27] -queuebot:#ubuntu-release- Unapproved: flask-script (yakkety-proposed/universe) [2.0.5-1 => 2.0.5-2] (no packageset) (sync)
[10:27] -queuebot:#ubuntu-release- Unapproved: accepted bugwarrior [sync] (yakkety-proposed) [1.4.0+git2016090101-1]
[10:27] -queuebot:#ubuntu-release- Unapproved: gnustep-gui (yakkety-proposed/universe) [0.25.0-3 => 0.25.0-4] (no packageset) (sync)
[10:27] -queuebot:#ubuntu-release- Unapproved: accepted flask-script [sync] (yakkety-proposed) [2.0.5-2]
[10:28] -queuebot:#ubuntu-release- Unapproved: ipython-genutils (yakkety-proposed/universe) [0.1.0-1 => 0.1.0-2] (no packageset) (sync)
[10:29] -queuebot:#ubuntu-release- Unapproved: accepted gnustep-gui [sync] (yakkety-proposed) [0.25.0-4]
[10:29] -queuebot:#ubuntu-release- Unapproved: kitchen (yakkety-proposed/universe) [1.2.4-1 => 1.2.4-2] (no packageset) (sync)
[10:29] -queuebot:#ubuntu-release- Unapproved: accepted ipython-genutils [sync] (yakkety-proposed) [0.1.0-2]
[10:29] -queuebot:#ubuntu-release- Unapproved: libjs-jquery-selectize.js (yakkety-proposed/universe) [0.12.2+dfsg-1 => 0.12.3+dfsg-1] (no packageset) (sync)
[10:29] -queuebot:#ubuntu-release- Unapproved: minetest-mod-mesecons (yakkety-proposed/universe) [2016.07.09-1 => 2016.09.13-1] (no packageset) (sync)
[10:30] -queuebot:#ubuntu-release- Unapproved: accepted kitchen [sync] (yakkety-proposed) [1.2.4-2]
[10:30] -queuebot:#ubuntu-release- Unapproved: accepted minetest-mod-mesecons [sync] (yakkety-proposed) [2016.09.13-1]
[10:30] -queuebot:#ubuntu-release- Unapproved: node-text-encoding (yakkety-proposed/universe) [0.6.0-1 => 0.6.1-1] (no packageset) (sync)
[10:30] -queuebot:#ubuntu-release- Unapproved: accepted libjs-jquery-selectize.js [sync] (yakkety-proposed) [0.12.3+dfsg-1]
[10:30] -queuebot:#ubuntu-release- Unapproved: node-simple-fmt (yakkety-proposed/universe) [0.1.0+20130419-1 => 0.1.0+20130419-2] (no packageset) (sync)
[10:30] -queuebot:#ubuntu-release- Unapproved: pygccxml (yakkety-proposed/universe) [1.7.4-3 => 1.8.0-1] (no packageset) (sync)
[10:31] -queuebot:#ubuntu-release- Unapproved: accepted node-simple-fmt [sync] (yakkety-proposed) [0.1.0+20130419-2]
[10:31] -queuebot:#ubuntu-release- Unapproved: accepted pygccxml [sync] (yakkety-proposed) [1.8.0-1]
[10:31] -queuebot:#ubuntu-release- Unapproved: accepted node-text-encoding [sync] (yakkety-proposed) [0.6.1-1]
[10:31] -queuebot:#ubuntu-release- Unapproved: pynac (yakkety-proposed/universe) [0.6.8-1 => 0.6.9-1] (no packageset) (sync)
[10:31] -queuebot:#ubuntu-release- Unapproved: relational (yakkety-proposed/universe) [2.4-1 => 2.5-1] (no packageset) (sync)
[10:31] -queuebot:#ubuntu-release- Unapproved: accepted pynac [sync] (yakkety-proposed) [0.6.9-1]
[10:31] -queuebot:#ubuntu-release- Unapproved: rc (yakkety-proposed/universe) [1.7.2-2build1 => 1.7.4-1] (no packageset) (sync)
[10:32] -queuebot:#ubuntu-release- Unapproved: accepted relational [sync] (yakkety-proposed) [2.5-1]
[10:32] -queuebot:#ubuntu-release- Unapproved: svnmailer (yakkety-proposed/universe) [1.0.9-2 => 1.0.9-3] (no packageset) (sync)
[10:32] -queuebot:#ubuntu-release- Unapproved: timew (yakkety-proposed/universe) [1.0.0~beta1+ds-1 => 1.0.0+ds.1-1] (no packageset) (sync)
[10:33] -queuebot:#ubuntu-release- Unapproved: accepted rc [sync] (yakkety-proposed) [1.7.4-1]
[10:33] -queuebot:#ubuntu-release- Unapproved: accepted timew [sync] (yakkety-proposed) [1.0.0+ds.1-1]
[10:33] -queuebot:#ubuntu-release- Unapproved: accepted svnmailer [sync] (yakkety-proposed) [1.0.9-3]
[10:33] -queuebot:#ubuntu-release- Unapproved: traitlets (yakkety-proposed/universe) [4.2.2-2 => 4.3.1-1] (no packageset) (sync)
[10:34] -queuebot:#ubuntu-release- Unapproved: accepted traitlets [sync] (yakkety-proposed) [4.3.1-1]
[10:34] <ginggs> apw: old installs of wine get removed due to wine-stable and wine-development having Conflicts: wine (>= 1.1)
[10:35] <apw> ginggs, yes, but how to _new_ installs of wine-stable get triggered if you have wine installed already
[10:35] <ginggs> apw: through wine1.6
[10:36] -queuebot:#ubuntu-release- Unapproved: acmetool (yakkety-proposed/universe) [0.0.56-1 => 0.0.56-2] (no packageset) (sync)
[10:37] -queuebot:#ubuntu-release- Unapproved: accepted acmetool [sync] (yakkety-proposed) [0.0.56-2]
[10:37] -queuebot:#ubuntu-release- Unapproved: wsjtx (yakkety-proposed/universe) [1.1.r3496-3 => 1.1.r3496-3.1] (no packageset) (sync)
[10:37] -queuebot:#ubuntu-release- Unapproved: wdq2wav (yakkety-proposed/multiverse) [1.0.0-1 => 1.0.0-1.1] (no packageset) (sync)
[10:37] -queuebot:#ubuntu-release- Unapproved: xpaint (yakkety-proposed/universe) [<IP_ADDRESS>-3.1build1 => <IP_ADDRESS>-3.2] (no packageset) (sync)
[10:37] <ginggs> apw: ubuntu's old wine package was a metapackage that Depends: wine1.6
[10:38] -queuebot:#ubuntu-release- Unapproved: accepted wdq2wav [sync] (yakkety-proposed) [1.0.0-1.1]
[10:38] -queuebot:#ubuntu-release- Unapproved: accepted xpaint [sync] (yakkety-proposed) [<IP_ADDRESS>-3.2]
[10:38] -queuebot:#ubuntu-release- Unapproved: djmount (yakkety-proposed/universe) [0.71-7 => 0.71-7.1] (no packageset) (sync)
[10:38] -queuebot:#ubuntu-release- Unapproved: polyorb (yakkety-proposed/universe) [2.11~20140418-3 => 2.11~20140418-3.1] (no packageset) (sync)
[10:38] -queuebot:#ubuntu-release- Unapproved: accepted wsjtx [sync] (yakkety-proposed) [1.1.r3496-3.1]
[10:38] -queuebot:#ubuntu-release- Unapproved: nast (yakkety-proposed/universe) [0.2.0-6build1 => 0.2.0-6.1] (no packageset) (sync)
[10:38] -queuebot:#ubuntu-release- Unapproved: diffpdf (yakkety-proposed/universe) [2.1.3-1 => 2.1.3-1.1] (no packageset) (sync)
[10:38] <santa_> slangasek: good morning, I would like to work with you on the issues we got with kde packages
[10:39] -queuebot:#ubuntu-release- Unapproved: accepted diffpdf [sync] (yakkety-proposed) [2.1.3-1.1]
[10:39] -queuebot:#ubuntu-release- Unapproved: accepted nast [sync] (yakkety-proposed) [0.2.0-6.1]
[10:39] -queuebot:#ubuntu-release- Unapproved: fractalnow (yakkety-proposed/universe) [0.8.1-1build1 => 0.8.1-1.1] (no packageset) (sync)
[10:39] -queuebot:#ubuntu-release- Unapproved: accepted djmount [sync] (yakkety-proposed) [0.71-7.1]
[10:39] -queuebot:#ubuntu-release- Unapproved: accepted polyorb [sync] (yakkety-proposed) [2.11~20140418-3.1]
[10:39] -queuebot:#ubuntu-release- Unapproved: tachyon (yakkety-proposed/universe) [0.99~b6+dsx-5 => 0.99~b6+dsx-6] (no packageset) (sync)
[10:39] <santa_> first of all I would like to say that we would upload libkexiv2 (we missed that in the massive uploading)
[10:40] <santa_> and we would also need to get drumstick in (it's needed by minuet)
[10:40] -queuebot:#ubuntu-release- Unapproved: accepted fractalnow [sync] (yakkety-proposed) [0.8.1-1.1]
[10:40] -queuebot:#ubuntu-release- Unapproved: accepted tachyon [sync] (yakkety-proposed) [0.99~b6+dsx-6]
[10:53] -queuebot:#ubuntu-release- Unapproved: siege (yakkety-proposed/main) [4.0.2-1ubuntu1 => 4.0.2-1.1] (core) (sync)
[11:05] -queuebot:#ubuntu-release- Unapproved: wsjtx (yakkety-proposed/universe) [1.1.r3496-3.1 => 1.1.r3496-3.1build1] (no packageset)
[11:05] -queuebot:#ubuntu-release- Unapproved: accepted wsjtx [source] (yakkety-proposed) [1.1.r3496-3.1build1]
[11:07] -queuebot:#ubuntu-release- Unapproved: aodh (yakkety-proposed/main) [3.0.0~rc1-0ubuntu2 => 3.0.0~rc1-0ubuntu3] (openstack)
[11:07] -queuebot:#ubuntu-release- Unapproved: python-pymysql (xenial-proposed/main) [0.7.2-1 => 0.7.2-1ubuntu1] (ubuntu-server)
[11:25] <Mirv> ^ (some screens up) ubuntu-ui-toolkit and ubuntu-ui-toolkit-gles no code changes, just arm64 test enablement
[11:28] <apw> Mirv, that seems like a strange reason to upload them ?
[11:29] <Mirv> apw: well QA was insisting they want to have them immediately, but then if they should skip yakkety thats ok and up to you. the bileto is still releasing everything to yakkety and not the PPA.
[11:29] <Mirv> which this week starts to be wrong
[11:30] <Mirv> sil2100: maybe redirecting bileto silos to overlay this week now?
[11:30] -queuebot:#ubuntu-release- Unapproved: ubuntu-system-settings-online-accounts (yakkety-proposed/universe) [0.7+16.10.20160830.2-0ubuntu1 => 0.7+16.10.20160929-0ubuntu1] (no packageset) (sync)
[11:33] <sil2100> Mirv: I guess that's a valid proposal right now
[11:34] <sil2100> Mirv: let me discuss that quickly tomorrow on the RTM status
[11:41] <Mirv> could you ignore virtualbox autopkgtest failures for qtbase-opensource-src and qtbase-opensource-src-gles ? http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#qtbase-opensource-src
[11:42] <apw> Mirv, yeah that is a kernel interaction, we have the same version in the kernel
[11:42] <Mirv> it seems that has constantly been failing since linux 4.8 for introduced
[11:42] <Mirv> apw: right.
[11:42] <apw> Mirv, it is actually about whether the kernel and it are in sync, and if they are it breaks
[11:43] <apw> (which ironically is a good thing)
[11:45] <apw> Mirv, and done
[11:48] <Mirv> apw: thank you!
[11:50] -queuebot:#ubuntu-release- Unapproved: ceilometer (yakkety-proposed/main) [1:7.0.0~rc2-0ubuntu1 => 1:7.0.0~rc3-0ubuntu1] (openstack, ubuntu-server)
[11:50] -queuebot:#ubuntu-release- Unapproved: miral (yakkety-proposed/universe) [0.1.0+16.10.20160919-0ubuntu1 => 0.2.0+16.10.20160930.1-0ubuntu1] (no packageset) (sync)
[11:51] -queuebot:#ubuntu-release- Unapproved: accepted miral [sync] (yakkety-proposed) [0.2.0+16.10.20160930.1-0ubuntu1]
[12:02] -queuebot:#ubuntu-release- New source: ubuntu-kylin-wizard (yakkety-proposed/primary) [16.10.0]
[12:24] -queuebot:#ubuntu-release- Unapproved: libkf5kexiv2 (yakkety-proposed/universe) [15.12.3-0ubuntu1 => 16.04.3-0ubuntu1] (kubuntu)
[12:24] <santa_> hi again
[12:25] <santa_> it would be nice if wee could get this one approved ↑ (libkf5kexiv2) because it's blocking other builds of kde applications
[12:25] <santa_> (we missed it because of a small glich in out automation tools)
[12:26] <santa_> s/wee/we/
[12:26] <santa_> s/out/our/
[12:29] -queuebot:#ubuntu-release- Unapproved: hardinfo (yakkety-proposed/universe) [0.5.1-1.4ubuntu1 => 0.5.1-1.4ubuntu2] (lubuntu)
[12:30] -queuebot:#ubuntu-release- Unapproved: kio (yakkety-proposed/universe) [5.26.0-0ubuntu1 => 5.26.0-0ubuntu2] (kubuntu)
[12:34] -queuebot:#ubuntu-release- Unapproved: plasma-discover (yakkety-proposed/universe) [5.7.5-0ubuntu1 => 5.7.5-0ubuntu2] (kubuntu)
[12:34] -queuebot:#ubuntu-release- Unapproved: plasma-sdk (yakkety-proposed/universe) [4:5.7.5-0ubuntu1 => 4:5.7.5-0ubuntu2] (kubuntu)
[12:35] -queuebot:#ubuntu-release- Unapproved: plasma-desktop (yakkety-proposed/universe) [4:5.7.5-0ubuntu1 => 4:5.7.5-0ubuntu2] (kubuntu)
[12:48] <slashd> Hi SRU vanguard, could you please nominate LP:  #1628279 affecting Xenial ?
[12:48] <apw> slashd, done
[12:49] <slashd> apw, tks
[13:00] <rbasak> slashd: won't that regress Xenial users by definition?
[13:01] <apw> yep, looks like it will ... perhaps we should be offering them under both names in this
[13:02] <rbasak> Yeah, adding symlinks makes sense. Then users can rely on the new names, but users relying on the old names won't break before a release upgrade.
[13:02] <apw> rbasak, perhaps copy that into the bug, i do not believe they have done the work on teh sru yet
[13:02] <rbasak> Will do
[13:04] <slashd> apw, rbasak, the debdiff for Xenial is not done yet, only yakkety to addressed the situation the sooner, but yes I was actually thinking of a symlink approach too, I'm glad you have a +1 on this
[13:06] <apw> slashd, it sounds like there are two pending srus here (following through the bugs) can we get those two together
[13:07] <slashd> apw, merging "1628279" with "1607920" in one single debdiff ?
[13:10] <apw> slashd, as i understnad things they both are blockers for seeding right?
[13:14] <slashd> apw, "1628279" as definitely more impact, caribou is working on the upload, it is fixing a bug, where the renaming is more/less cosmetic but still I think we need to do it.
[13:19] -queuebot:#ubuntu-release- Unapproved: gnome-calculator (xenial-proposed/main) [1:3.18.3-0ubuntu1 => 1:3.18.3-0ubuntu<IP_ADDRESS>] (ubuntu-desktop)
[13:24] <slashd> cking, apw and I would like to combine both LPs in one single SRU : your python2->python3 + the utilities python script renaming (1628279), I'll redo the SRU accordingly
[13:25] <sakrecoer> hi everyone, sorry for nagging about this, but now we have all the missing pieces for our FFe/UIFe ... https://bugs.launchpad.net/ubuntustudio/+bug/1624690 we would be very thankfull if this could land on our ISO before RC...
[13:25]  * sakrecoer crosses fingers and proceeds to nagg a little in #u-dev too :3
[13:27] <slashd> cking, apw disregard my last comment
[13:28] -queuebot:#ubuntu-release- Unapproved: nautilus-image-converter (xenial-proposed/universe) [0.3.1~git20110416-1ubuntu1 => 0.3.1~git20110416-1ubuntu<IP_ADDRESS>] (no packageset)
[13:28] <slashd> caribou, as per my discussion with apw,  I will re-submit a new debdiff for bug (1607920) which will include fix for another bug I worked on as well (1628279) for Xenial.
[13:30] <caribou> slashd: ok
[13:33] -queuebot:#ubuntu-release- Unapproved: xml-core (yakkety-proposed/main) [0.13+nmu2ubuntu1 => 0.15] (core) (sync)
[13:36] -queuebot:#ubuntu-release- Unapproved: ptouch-driver (yakkety-proposed/main) [1.4.2-1 => 1.4.2-2] (desktop-core) (sync)
[13:49] -queuebot:#ubuntu-release- Unapproved: playonlinux (yakkety-proposed/multiverse) [4.2.10-2 => 4.2.10-2ubuntu1] (no packageset)
[13:49] -queuebot:#ubuntu-release- Unapproved: accepted playonlinux [source] (yakkety-proposed) [4.2.10-2ubuntu1]
[13:50] -queuebot:#ubuntu-release- Unapproved: cyphesis-cpp (yakkety-proposed/universe) [0.6.0-6build1 => 0.6.2-2] (no packageset) (sync)
[13:50] -queuebot:#ubuntu-release- Unapproved: accepted cyphesis-cpp [sync] (yakkety-proposed) [0.6.2-2]
[13:59] -queuebot:#ubuntu-release- Unapproved: polyorb (yakkety-proposed/universe) [2.11~20140418-3.1 => 2.11~20140418-3.1build1] (no packageset)
[14:00] -queuebot:#ubuntu-release- Unapproved: accepted polyorb [source] (yakkety-proposed) [2.11~20140418-3.1build1]
[14:02] <slangasek> acheronuk, apw: kdegraphics-mobipocket accepted (though an equally valid fix would have been to have okular un-version its build-dep)
[14:03] <slangasek> ginggs: http://people.canonical.com/~ubuntu-archive/nbs.html says wine, wine1.4-dev aren't ready to be removed
[14:03] <slangasek> ah, apw already addressed this
[14:05] <slangasek> santa_: hi, so I'm several timezones west of you, best to not block on me for things you need; but I'm looking at libkf5kexiv2 now
[14:07] -queuebot:#ubuntu-release- Unapproved: accepted libkf5kexiv2 [source] (yakkety-proposed) [16.04.3-0ubuntu1]
[14:07] <slangasek> acheronuk, santa_: is anyone looking at the kde-runtime autopkgtest failure?  Strangely the tests are not run at build time...
[14:08] -queuebot:#ubuntu-release- Unapproved: ubuntustudio-default-settings (yakkety-proposed/universe) [0.62 => 0.63] (no packageset)
[14:10] <ginggs> slangasek: i think dssi-vst should be removed, it was removed from debian in 2013. will wine1.4-dev then get removed automatically?
[14:11] -queuebot:#ubuntu-release- Unapproved: ubuntustudio-lightdm-theme (yakkety-proposed/universe) [0.9 => 0.10] (no packageset)
[14:14] <slangasek> ginggs: done (and yes, that should make wine1.4-dev a candidate for NBS removal)
[14:15] -queuebot:#ubuntu-release- Unapproved: libpfm4 (yakkety-proposed/main) [4.7.0+git11-gbfb9baf-1 => 4.7.0+git30-gd422ba2-1] (no packageset) (sync)
[14:15] <ginggs> slangasek: thanks! ok, is anything else needed wrt to the wine binary NBS?
[14:16] <slangasek> ginggs: don't know; apw?
[14:16] <apw> so the confusion was whether there was a clean path for existing people with "wine" installed to the new world order
[14:16] <apw> yes if they install wine they will get the new via a provides, but is there a migration for actual old wine metapackages installed
[14:17] <apw> as that currently includes a path through the package we are trying to remove
[14:17] <ginggs> apw: if they had the old wine metapackage, they would have wine1.6 installed
[14:17] <slangasek> this does not ensure that apt chooses to upgrade wine1.6 and remove wine; have you tested?
[14:18] <ginggs> slangasek: yes, we did much testing
[14:18] <ginggs> various upgrade logs in LP: #1558480
[14:19] <apw> ginggs, and wine/1:1.6.2-0ubuntu14 from xenial is already in this form
[14:20] <ginggs> apw: sorry, not understanding
[14:21] <apw> ginggs, i mean we're testing using the xenial base on upgrade to yakkety
[14:21] <ginggs> wine/1:162-0ubuntu14 and -0ubuntu15 are still in the old form
[14:22] <apw> but they are in the form with wine causeing wine1.6 to be installed ?
[14:23] <acheronuk> slangasek: thank you :) downgrading the okular build-deps was a fallback option
[14:23] <ginggs> yes, it is the old form where they are metapackages that Depends: wine1.6
[14:23] <sakrecoer> \o\ Laney /o/ thank you!!!! <3
[14:36] -queuebot:#ubuntu-release- Unapproved: snapcraft (xenial-proposed/universe) [2.18.1 => 2.19] (no packageset)
[14:40] -queuebot:#ubuntu-release- Unapproved: cinder (yakkety-proposed/main) [2:9.0.0~rc1-0ubuntu1 => 2:9.0.0~rc2-0ubuntu1] (openstack, ubuntu-server)
[14:41] <sergiusens> infinity or others in the sru team, mind letting snapcraft ^ in?
[14:44]  * apw has a look ...
[14:44] -queuebot:#ubuntu-release- Unapproved: gnocchi (yakkety-proposed/universe) [2.0.2-7 => 3.0.0-1] (no packageset) (sync)
[14:44] -queuebot:#ubuntu-release- Unapproved: magnum (yakkety-proposed/universe) [2.0.0-6 => 3.0.0-1] (no packageset) (sync)
[14:44] -queuebot:#ubuntu-release- Unapproved: accepted gnocchi [sync] (yakkety-proposed) [3.0.0-1]
[14:44] -queuebot:#ubuntu-release- Unapproved: accepted magnum [sync] (yakkety-proposed) [3.0.0-1]
[14:47] -queuebot:#ubuntu-release- Unapproved: sahara (yakkety-proposed/universe) [1:5.0.0~b2-1 => 1:5.0.0~rc1-1] (openstack) (sync)
[14:47] -queuebot:#ubuntu-release- Unapproved: unity8 (yakkety-proposed/universe) [8.14+16.10.20160922-0ubuntu1 => 8.14+16.10.20160922-0ubuntu2] (ubuntu-qt-packages)
[14:55] -queuebot:#ubuntu-release- Unapproved: designate (yakkety-proposed/main) [1:3.0.0~rc1-0ubuntu1 => 1:3.0.0~rc2-0ubuntu1] (openstack)
[14:56] -queuebot:#ubuntu-release- Unapproved: accepted snapcraft [source] (xenial-proposed) [2.19]
[14:57] -queuebot:#ubuntu-release- Unapproved: glance (yakkety-proposed/main) [2:13.0.0~rc1-0ubuntu1 => 2:13.0.0~rc2-0ubuntu1] (openstack, ubuntu-server)
[15:03] -queuebot:#ubuntu-release- Unapproved: horizon (yakkety-proposed/main) [3:10.0.0~rc2-0ubuntu1 => 3:10.0.0~rc3-0ubuntu1] (openstack, ubuntu-server)
[15:07] -queuebot:#ubuntu-release- Unapproved: nova (yakkety-proposed/main) [2:14.0.0~rc1-0ubuntu2 => 2:14.0.0~rc2-0ubuntu1] (openstack, ubuntu-server)
[15:11] -queuebot:#ubuntu-release- Unapproved: accepted hardinfo [source] (yakkety-proposed) [0.5.1-1.4ubuntu2]
[15:25] <slangasek> pitti: for some reason the autopkgtest requests for a couple of bileto ppas went missing - and I retried them and they still didn't fire.  how do we debug these going missing?  is it possible that triggering for multiple releases in parallel is a problem on the amqp side?
[15:26] <slangasek> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-1988-excuses/2016-10-01_06:35:00/1988_vivid_excuses.html https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-1988-excuses/2016-10-01_06:35:00/1988_xenial_excuses.html
[15:26] <slangasek> actually
[15:27] <slangasek> pitti: nevermind, apparently those URLs are stale (?) and there are different excuses for that ppa that show things completed
[15:28] <slangasek> robru: ^^ why would the excuses url for a ticket change over time?  that's inconvenient
[15:31] -queuebot:#ubuntu-release- Unapproved: accepted unity8 [source] (yakkety-proposed) [8.14+16.10.20160922-0ubuntu2]
[15:32] -queuebot:#ubuntu-release- Unapproved: juju-core (yakkety-proposed/main) [2.0~beta17-0ubuntu<IP_ADDRESS> => 2.0~rc2-0ubuntu<IP_ADDRESS>] (ubuntu-server)
[15:40] <handsome_feng> Laney, hi, are you there? It is has been a while since I updated the ubuntu-kylin-wizard package, Couble you please upload that when you are free, Thank you !
[15:41] <Laney> handsome_feng: did you see https://bugs.launchpad.net/ubuntukylin/+bug/1609207/comments/5 ?
[15:42] <jbicha> handsome_feng: could you make sure Kylin is aware of bug 1618138 ?
[15:42] <handsome_feng> Oh, I just notise that , Thank you , laney.
[15:43] <handsome_feng> jbicha: er, I'm not sure about that, I will ask the people
[15:44] <jbicha> thanks
[15:46] <apw> Laney, that "initial version" bug number looks to be an unrelated hardinfo bug ?  (for ubuntu-kylin-wizard)
[15:46] <Laney> AAAAAAAAAAAAA
[15:47] <Laney> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
[15:47] <Laney> it should be the one I just linked
[15:47] <apw> Laney, it appears to be one i recognise so from a qeueu entry today
[15:47] <Laney> lemme fix that
[15:47] <Laney> I probably copied from the wrong tab
[15:47] <robru> slangasek: it's the nature of swift that you can't overwrite an object once it's been written (at least not reliably), so each new file gets a new time-stamped name
[15:49] <slangasek> robru: well that's unseemly
[15:50] -queuebot:#ubuntu-release- New source: ubuntu-kylin-wizard (yakkety-proposed/primary) [16.10.0]
[15:51] -queuebot:#ubuntu-release- Unapproved: indicator-network (yakkety-proposed/universe) [0.8.0+16.10.20160915-0ubuntu1 => 0.8.0+16.10.20160930.5-0ubuntu1] (no packageset) (sync)
[15:51] <Laney> apw: try that one
[15:51] -queuebot:#ubuntu-release- Unapproved: accepted indicator-network [sync] (yakkety-proposed) [0.8.0+16.10.20160930.5-0ubuntu1]
[15:51] <robru> slangasek: when i was first adding swift support for diffs, i tried overwriting same names, but the old version would get served most of the time because it's a caching distributed file store thing. It was pitti who suggested putting a timestamp in the name so each upload would have a unique name
[15:52] <cjwatson> you could have a frontend server proxy the current file from swift
[15:52] <slangasek> yes
[15:52] <cjwatson> that's the usual approach
[15:53] <robru> Yeah? The current URL is listed on the ticket
[15:54] <slangasek> robru: the end user experience should not require me to go back to the ticket page to find a new URL
[15:54] -queuebot:#ubuntu-release- New: rejected ubuntu-kylin-wizard [source] (yakkety-proposed) [16.10.0]
[15:54] <slangasek> hitting 'refresh' in my browser should Just Work
[15:54] <slangasek> thus, 'frontend'
[15:56] <robru> Hmm
[16:07] <flocculant> slangasek: we're seeing a crash on update manager - I think there's probably a private bug for it, but I reported bug 1629900 which has a branch linked with a fix
[16:08] <flocculant> or rather I know there is a bug which I can't see bug 1623296
[16:17] <tsimonq2> thanks Laney
[16:27] -queuebot:#ubuntu-release- New: rejected ubuntu-kylin-wizard [source] (yakkety-proposed) [16.10.0]
[16:27] -queuebot:#ubuntu-release- New source: ubuntu-kylin-wizard (yakkety-proposed/primary) [16.10.0]
[16:33] -queuebot:#ubuntu-release- New: accepted ubuntu-kylin-wizard [source] (yakkety-proposed) [16.10.0]
[16:34] -queuebot:#ubuntu-release- Unapproved: grub2 (xenial-proposed/main) [2.02~beta2-36ubuntu3.3 => 2.02~beta2-36ubuntu3.4] (core)
[16:38] -queuebot:#ubuntu-release- New binary: ubuntu-kylin-wizard [amd64] (yakkety-proposed/none) [16.10.0] (no packageset)
[16:38] -queuebot:#ubuntu-release- New binary: ubuntu-kylin-wizard [ppc64el] (yakkety-proposed/none) [16.10.0] (no packageset)
[16:38] -queuebot:#ubuntu-release- New binary: ubuntu-kylin-wizard [arm64] (yakkety-proposed/none) [16.10.0] (no packageset)
[16:38] -queuebot:#ubuntu-release- New binary: ubuntu-kylin-wizard [i386] (yakkety-proposed/none) [16.10.0] (no packageset)
[16:38] -queuebot:#ubuntu-release- New binary: ubuntu-kylin-wizard [armhf] (yakkety-proposed/none) [16.10.0] (no packageset)
[16:41] -queuebot:#ubuntu-release- New binary: ubuntu-kylin-wizard [s390x] (yakkety-proposed/none) [16.10.0] (no packageset)
[16:45] -queuebot:#ubuntu-release- New binary: ubuntu-kylin-wizard [powerpc] (yakkety-proposed/none) [16.10.0] (no packageset)
[16:46] -queuebot:#ubuntu-release- Unapproved: gnome-session (yakkety-proposed/main) [3.20.2-1ubuntu5 => 3.20.2-1ubuntu6] (ubuntu-desktop)
[16:49] <slangasek> bdmurray: could you lookt at flocculant's update-manager crash+branch? (https://launchpad.net/bugs/1629900)
[16:52] -queuebot:#ubuntu-release- Unapproved: ubuntu-terminal-app (yakkety-proposed/universe) [0.7.218 => 0.7.218ubuntu1] (no packageset)
[16:53] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-terminal-app [source] (yakkety-proposed) [0.7.218ubuntu1]
[16:54] <bdmurray> slangasek: I've been looking at it already. ;-)
[16:54] <slangasek> bdmurray: \o/
[16:56] <flocculant> thanks guys :)
[17:00] -queuebot:#ubuntu-release- Unapproved: cloud-init (xenial-proposed/main) [0.7.8-1-g3705bb5-0ubuntu1~16.04.2 => 0.7.8-1-g3705bb5-0ubuntu1~16.04.3] (edubuntu, ubuntu-cloud, ubuntu-server)
[17:01] -queuebot:#ubuntu-release- Unapproved: lxd (trusty-backports/universe) [2.0.3-0ubuntu2~ubuntu14.04.1 => 2.0.4-0ubuntu1~ubuntu14.04.1] (no packageset)
[17:03] <lamont> dear archive-admins... please take smosers upload of cloud-init as a replacement for thge one I have sitting in xenial-proposed.
[17:03] <lamont> kthx
[17:04] -queuebot:#ubuntu-release- Unapproved: lxc (trusty-backports/main) [2.0.3-0ubuntu1~ubuntu14.04.1 => 2.0.4-0ubuntu1~ubuntu14.04.1] (ubuntu-server)
[17:05] -queuebot:#ubuntu-release- Unapproved: designate-dashboard (yakkety-proposed/universe) [2.0.0-2 => 3.0.0~rc1-1] (no packageset) (sync)
[17:05] -queuebot:#ubuntu-release- Unapproved: accepted designate-dashboard [sync] (yakkety-proposed) [3.0.0~rc1-1]
[17:08] -queuebot:#ubuntu-release- Unapproved: lxcfs (trusty-backports/universe) [2.0.2-0ubuntu1~ubuntu14.04.1 => 2.0.3-0ubuntu1~ubuntu14.04.1] (no packageset)
[17:11] <slangasek> cjwatson: why does trying to grab ubuntu-ui-toolkit from the yakkety unapproved queue with 'queue fetch' give me an openid login page instead of a .dsc?
[17:11] <slangasek> (instead of any of the files, indeed)
[17:11] <slangasek> ah
[17:11] <slangasek> the source ppa is deleted
[17:11] <slangasek> robru: why is the ppa for https://bileto.ubuntu.com/#/ticket/2019 deleted before the package has landed in yakkety?
[17:13] <slangasek> Mirv: looks like this is your doing.  Did you knowingly override a warning in bileto about the packages not yet having landed in yakkety?
[17:13] -queuebot:#ubuntu-release- Unapproved: accepted lxc [source] (trusty-backports) [2.0.4-0ubuntu1~ubuntu14.04.1]
[17:13] -queuebot:#ubuntu-release- Unapproved: accepted lxd [source] (trusty-backports) [2.0.4-0ubuntu1~ubuntu14.04.1]
[17:13] -queuebot:#ubuntu-release- Unapproved: accepted lxcfs [source] (trusty-backports) [2.0.3-0ubuntu1~ubuntu14.04.1]
[17:14] -queuebot:#ubuntu-release- Unapproved: rejected ubuntu-ui-toolkit-gles [sync] (yakkety-proposed) [1.3.2104+16.10.20160929]
[17:14] -queuebot:#ubuntu-release- Unapproved: grub2-signed (xenial-proposed/main) [1.66.3 => 1.66.4] (core)
[17:15] -queuebot:#ubuntu-release- Unapproved: rejected ubuntu-ui-toolkit [sync] (yakkety-proposed) [1.3.2104+16.10.20160929]
[17:23] -queuebot:#ubuntu-release- Unapproved: rejected gvfs [source] (yakkety-proposed) [1.30.0-1ubuntu1]
[17:23] <robru> slangasek: yep, Mirv force merged. he should be aware that force merging while things are unapproved nukes them (this was true also before ephemeral ppas)
[17:24] <slangasek> robru: why do we still have that button? :-)
[17:25] <robru> slangasek: there are cases where it's warranted, eg if it's in proposed and we're rushing to get an ota out the door or something.
[17:25] <robru> slangasek: I suppose I could make a big red warning for when merging when things are still unapproved
[17:25] <slangasek> force-merging, even if it's just in -proposed, still breaks the archive CI
[17:26] <slangasek> robru: or disallow entirely for that case, since it nukes the packages and leaves the archive admins with a mess?
[17:27] <robru> slangasek: I thought archive admins were aware that queued uploads where the source has been deleted should just be rejected with extreme prejudice?
[17:28] <slangasek> robru: I /have/ rejected it with extreme prejudice.  Figuring out that this was what was supposed to happen took far more time than it should have
[17:31] <robru> slangasek: let's say hypothetically bileto prevented force-merging tickets with unapproved queue packages, what would you prefer to happen? presumably mirv needed that merged so he could rebuild some other silo and include the changes, so you'd want mirv to come here and ask to have the upload rejected, then he can merge? I don't see a lot of point in that,
[17:31] <robru> if un-doing the upload is really what you want to do
[17:31] <robru> "really what HE wanted to do"
[17:32] <robru> slangasek: it sounds to me more like your upload queue software should be smarter/faster about noticing when the source has vanished
[17:32] <slangasek> robru: force-merge does not mean "undo the upload"
[17:32] <robru> slangasek: well, it does for queued uploads, and mirv knows that
[17:33] <slangasek> robru: no, it was a triple-landing, so two of them are landed and the third one is broken off at the hip
[17:33] <slangasek> if you want to abandon a ticket, you abandon a ticket, you don't *merge* it
[17:34] <slangasek> "your upload queue software" - which is Launchpad, which is the existing software that bileto needs to integrate with
[17:34] <slangasek> if you want to provide a patch to Launchpad to auto-reject things from the queue when the source disappears, ok ;)
[17:34] <slangasek> but this still absolutely should not have been force-merged
[17:35] <robru> slangasek: but he didn't want to abandon it, he wanted the changes merged to trunk.
[17:35] <slangasek> robru: then that is the opposite of undoing the upload!
[17:36] <robru> slangasek: I know it's bad practise, but I don't think it's outrageously terrible to want to merge something to trunk without caring if it actually got to the archive. I would assume he just had another ticket he wanted to publish quickly and just wanted to merge one, rebuild the other, then publish, essentially batching up two uploads into one. I don't know
[17:36] <robru> if that's what really happened but it seems like a reasonable scenario.
[17:37] <slangasek> if there is not a committment to follow the process, then these packages should not be using triple landings
[17:37] -queuebot:#ubuntu-release- Unapproved: python-taskflow (yakkety-proposed/main) [2.3.0-1 => 2.3.0-1ubuntu1] (ubuntu-server)
[17:38] <slangasek> and other teams should not be left doing forensics to figure out the mess left behind
[17:38] <tsimonq2> slangasek: what emails are sent out to flavors for anything administrative? also, what about email notifications for package uploads like the Debian archive?
[17:39] <slangasek> tsimonq2: "sent out to flavors" - if you mean the mails you asked to be signed up for, it's image build failures and image oversized
[17:39] <slangasek> and there's not really a way to sign up for notifications of package uploads
[17:40] <tsimonq2> slangasek: well I mean the Debian tracker notifies on that sort of thing, I get those emails all the time!
[17:40] <robru> slangasek: bileto doesn't have permission to remove packages from the upload queue, for the same reason it doesn't have permission to add things to the upload queue, so noticing sources of uploads have been deleted is on LP's end
[17:41] <slangasek> robru: yes, so take out the force-merge option.
[17:42] <tsimonq2> slangasek: is it something in the tooling? the way things are set up? what if I really wanted to receieve those sort of notifications for the lubuntu packageset?
[17:42] <slangasek> landers should not be half-landing and then backing out of yakkety.  If they're not going to use dual/triple landings right, they need to be maintaining separate per-release branches.
[17:42] <robru> slangasek: you want it taken out entirely, or taken out in the case of queued uploads, or can we just limit it's use to a smaller group of trusted people?
[17:42] <robru> slangasek: mirv is technically a train guard
[17:43] <slangasek> robru: IMHO it should be taken out entirely; I would accept a compromise of removing the option for queued uploads; and no it shouldn't be limited to "trusted people", because nobody should be trusted with this ;)
[17:43] <slangasek> tsimonq2: Debian upload management is completely different software to Ubuntu's
[17:44] -queuebot:#ubuntu-release- Unapproved: nova-lxd (yakkety-proposed/main) [14.0.0~b3-0ubuntu1 => 14.0.0~rc1-0ubuntu1] (ubuntu-server)
[17:44] <robru> slangasek: removing it entirely is a scary prospect for me because there are times when proposed is broken but tickets still need to land
[17:44] <slangasek> right
[17:44] <robru> Impedance mismatch between touch and archive
[17:45] <tsimonq2> slangasek: I see, ok, I thought you guys shared a lot more tools
[17:45] -queuebot:#ubuntu-release- Unapproved: helm (yakkety-proposed/universe) [2.1.0-1 => 2.2.0-1] (no packageset) (sync)
[17:45] -queuebot:#ubuntu-release- Unapproved: link-grammar (yakkety-proposed/universe) [5.3.10-1 => 5.3.11-1] (no packageset) (sync)
[17:45] <tsimonq2> slangasek: is it set up different on the servers or is there somewhere I can make a PR against?
[17:45] <slangasek> tsimonq2: er, we use Launchpad? :)
[17:46] -queuebot:#ubuntu-release- Unapproved: accepted siege [sync] (yakkety-proposed) [4.0.2-1.1]
[17:46] <slangasek> tsimonq2: so you can propose a merge against launchpad :)
[17:46]  * tsimonq2 greps for<EMAIL_ADDRESS>[17:46] <robru> slangasek: also, abandoning has the same problem, the source is deleted without removing the queued upload, should i block that too?
[17:46] <tsimonq2> thanks slangasek :)
[17:46] -queuebot:#ubuntu-release- Unapproved: accepted helm [sync] (yakkety-proposed) [2.2.0-1]
[17:47] <slangasek> robru: no, because in that case it's consistent - the package will not land in the archive, and the branch is not merged to trunk
[17:47] -queuebot:#ubuntu-release- Unapproved: accepted link-grammar [sync] (yakkety-proposed) [5.3.11-1]
[17:47] <robru> slangasek: but still you have a queued upload that takes you too long to notice doesn't exist
[17:47] <slangasek> in a dual/triple landing, of course, it will be landed in the overlay ppa still... unless you want bileto to back those out also on 'abandon'
[17:47] <robru> Ugh
[17:48] <robru> slangasek: some time ago i proposed not copying to overlay until after it migrated through proposed but that was shot down
[17:48] <slangasek> robru: yes, the interaction with the queue will still be annoying, but in this case I think it happened only because force-merge was pushed when the right answer was to wait for the review
[17:48] <slangasek> heh
[17:49] <robru> slangasek: ok I'll block merges when uploads are queued
[17:49] <slangasek> robru: thanks :)
[17:50] -queuebot:#ubuntu-release- Unapproved: accepted aodh [source] (yakkety-proposed) [3.0.0~rc1-0ubuntu3]
[17:50] <slangasek> robru: fwiw it seems you're right, there is a new ticket for those packages now https://bileto.ubuntu.com/#/ticket/2035
[17:51] <robru> slangasek: yeah, that makes sense
[17:52] <gQuigs> should I do a separate removal request for src:wine (wine 1.6) which is obsolote due to https://bugs.launchpad.net/ubuntu/+source/wine1.6/+bug/1558480
[17:53] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-system-settings-online-accounts [sync] (yakkety-proposed) [0.7+16.10.20160929-0ubuntu1]
[17:53] <gQuigs> the package "wine" is now a virtual package provided by wine-stable
[17:54] <slangasek> gQuigs: no, this has been discussed in this channel this morning
[17:54] <gQuigs> oh - oops - will check the logs
[18:00] -queuebot:#ubuntu-release- Unapproved: accepted ceilometer [source] (yakkety-proposed) [1:7.0.0~rc3-0ubuntu1]
[18:04] -queuebot:#ubuntu-release- Unapproved: accepted kio [source] (yakkety-proposed) [5.26.0-0ubuntu2]
[18:08] -queuebot:#ubuntu-release- Unapproved: accepted plasma-discover [source] (yakkety-proposed) [5.7.5-0ubuntu2]
[18:10] -queuebot:#ubuntu-release- Unapproved: accepted plasma-sdk [source] (yakkety-proposed) [4:5.7.5-0ubuntu2]
[18:12] -queuebot:#ubuntu-release- Unapproved: accepted plasma-desktop [source] (yakkety-proposed) [4:5.7.5-0ubuntu2]
[18:14] <slangasek> Laney: I see you requested a sync for xml-core; I talked about this with nacc on Friday and I think he concluded we should not sync; why is this wanted now?
[18:20] -queuebot:#ubuntu-release- New binary: libkf5kipi [i386] (yakkety-proposed/universe) [16.04.3-0ubuntu1] (kubuntu)
[18:20] -queuebot:#ubuntu-release- New binary: libkf5kipi [ppc64el] (yakkety-proposed/universe) [16.04.3-0ubuntu1] (kubuntu)
[18:20] -queuebot:#ubuntu-release- New binary: libkf5kipi [amd64] (yakkety-proposed/universe) [16.04.3-0ubuntu1] (kubuntu)
[18:22] -queuebot:#ubuntu-release- New binary: libkf5kipi [arm64] (yakkety-proposed/universe) [16.04.3-0ubuntu1] (kubuntu)
[18:23] -queuebot:#ubuntu-release- New binary: libkf5kipi [armhf] (yakkety-proposed/universe) [16.04.3-0ubuntu1] (kubuntu)
[18:23] -queuebot:#ubuntu-release- New binary: libkf5kipi [s390x] (yakkety-proposed/universe) [16.04.3-0ubuntu1] (kubuntu)
[18:27] -queuebot:#ubuntu-release- New binary: libkf5kipi [powerpc] (yakkety-proposed/universe) [16.04.3-0ubuntu1] (kubuntu)
[18:43] <jderose> cyphermox: so re reverting shim in yakkety... anything i can help with? :)
[18:43] <cyphermox> jderose: not really, I'm just pressing buttons now
[18:43] <jderose> cyphermox: please let me know when you have something to test
[18:48] -queuebot:#ubuntu-release- Unapproved: accepted ptouch-driver [sync] (yakkety-proposed) [1.4.2-2]
[18:52] -queuebot:#ubuntu-release- Unapproved: accepted ubuntustudio-default-settings [source] (yakkety-proposed) [0.63]
[18:55] <smoser> hi. can i get an archive admin to please replace cloud-init in xenial-proposed (0.7.8-1-g3705bb5-0ubuntu1~16.04.2 ) with the version i uploaded to (0.7.8-1-g3705bb5-0ubuntu1~16.04.3)
[18:55] <smoser> i guess maybe that takes sru team member
[18:58] <slangasek> smoser: maybe bdmurray wants to take this one, as he's doing SRU team training today (IIRC)
[18:59] <smoser> that'd be nice. it should be a good example of straight forward
[18:59] <cyphermox> there's also more grub2 / grub2-signed in xenial queue
[18:59] <smoser> shoot. other than i forgot to -v for genchanges correctly
[19:00] <smoser> shall i re-upload for that slangasek ?
[19:00] -queuebot:#ubuntu-release- Unapproved: accepted ubuntustudio-lightdm-theme [source] (yakkety-proposed) [0.10]
[19:00] <slangasek> smoser: yes please
[19:00] <smoser> NACK the one there then ?
[19:02] <slangasek> smoser: done
[19:03] -queuebot:#ubuntu-release- Unapproved: rejected cloud-init [source] (xenial-proposed) [0.7.8-1-g3705bb5-0ubuntu1~16.04.3]
[19:05] <bdmurray> slangasek: The training is tomorrow so if smoser is in hurry I can review it now.
[19:05] <santa_> slangasek: thank you very much for libkexiv, I'm not looking @ kde-runtime so far, right now my priority are some library rejections which I think they are going to block other builds
[19:05] <slangasek> bdmurray: ok, it is a hurry - if you can get it now spiff, otherwise I can
[19:05] <smoser> bdmurray, well, roaksoax will tell you he's in a hurry.
[19:06] -queuebot:#ubuntu-release- Unapproved: cloud-init (xenial-proposed/main) [0.7.8-1-g3705bb5-0ubuntu1~16.04.2 => 0.7.8-1-g3705bb5-0ubuntu1~16.04.3] (edubuntu, ubuntu-cloud, ubuntu-server)
[19:06] <slangasek> santa_: kde-runtime also blocks loads fwiw; I've managed to reproduce the failure, and frustratingly it doesn't reproduce when I run the test case directly, only when I run it under the test harness
[19:07] <cyphermox> jderose: if only shim was to cooperate better with building under gcc 5/6 that would be nice, but I really doubt you can do anything about that ;)
[19:08] <slangasek> cyphermox: building?
[19:09] <cyphermox> slangasek: don't we still want to have the old shim source too?
[19:09] <slangasek> cyphermox: yes, but you can't rebuild it, you'll get a different binary
[19:09] <slangasek> cyphermox: this is copy-package -e territory
[19:10] <cyphermox> oh, right, because shim-signed also goes to check things after
[19:10] <jderose> cyphermox: yeah, i different build would need to be resigned, right?
[19:10] <santa_> slangasek: reagrding the tests, back in the days we were actively disabling them in debian, however that autopkgtests thing arrived and the current maintainer in debian worked on that, and I have the impression he spends the 100% of the time fixing the test themselves or the environment of the tests than fixing any actual bug in the code tested
[19:10] <slangasek> cyphermox: yes, this requires literally downgrading shim in the archive on a provisional basis until the new signed one comes in
[19:10] <cyphermox> yeah
[19:11] <slangasek> santa_: growing pains, resulting from not having testing part of the plan from the beginning
[19:11] <slangasek> cyphermox: so, you do need a new shim-signed source, but the shim source should be a copy-package -b -e [...] of the old one
[19:11] <santa_> slangasek: I know, that's something out of the radar in kubuntu development so far
[19:11] <cyphermox> yeah yeah, I got that now
[19:12] <santa_> I guess we could prepare something to work on that porperly for the next release
[19:12] <slangasek> ginggs: what is the libpfm4 sync fixing?
[19:12] <santa_> * properly
[19:13] <slangasek> santa_: you should not plan on the release team making exceptions to let packages in to 16.10 that fail their tests
[19:13] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (xenial-proposed) [0.7.8-1-g3705bb5-0ubuntu1~16.04.3]
[19:14] <santa_> slangasek: to be honest I didn't plan so much, I got git/ppa permissions very recently and I'm doing the best I can with what we have right now
[19:14] <santa_> there are so much things to improve
[19:15] -queuebot:#ubuntu-release- Unapproved: accepted cinder [source] (yakkety-proposed) [2:9.0.0~rc2-0ubuntu1]
[19:15] <slangasek> santa_: right; my point is, if these packages don't clear proposed-migration on their own merits, chances are they will not make it for release
[19:15] -queuebot:#ubuntu-release- Unapproved: shim (yakkety-proposed/main) [0.9+1465500757.14a5905-0ubuntu1 => 0.8-0ubuntu2] (core) (sync)
[19:16] <cyphermox> slangasek: ^ still looks wrong for the version number to be going down?
[19:16] <cyphermox> -e lets me pick the version, not rename, unless i'm not using the right copy-package
[19:16] <slangasek> cyphermox: oh, you're doing this directly on the archive?  I figured you would still stage it in a ppa so shim-signed could be built and the upgrade tested a bit before landing
[19:17] <cyphermox> oh, sure, we can do that too
[19:18] <infinity> Yeah, with shim-signed depending on shim, we can't really force a downgrade...
[19:18] <cyphermox> my idea really had been to make it so we had 0.9somethingsomething.is.0.8 and not worry about upgrading/downgrading
[19:19] <infinity> I don't suppose shim builds reproducibly? :P
[19:19] <slangasek> infinity: we can "force" a downgrade of shim together with an upgrade of shim-signed; it won't work right for anyone who's been tracking yakkety pre-release but is better than nothing at this point
[19:19] -queuebot:#ubuntu-release- Unapproved: accepted sahara [sync] (yakkety-proposed) [1:5.0.0~rc1-1]
[19:19] <slangasek> infinity: reproducibly> nope sorry
[19:19] <cyphermox> infinity: nope
[19:19] <slangasek> it's close but not quite IIRC
[19:19] <slangasek> and the toolchain has certainly changed since the last build
[19:20] <cyphermox> well, especially now if I need to patch to make it build with gcc 5 or 6
[19:20] <jderose> slangasek: i'm all for better than nothing :)
[19:20] <infinity> slangasek: Yeah, toolchain's changed, but we could fudge that by building it in a PPA that matches.
[19:20] <cyphermox> slangasek: want to reject that shim upload so i can do things better?
[19:20] <slangasek> infinity: well, the whole thing is a hedge against MS not getting the signed binary back to us in time; diminishing returns on how perfect we make this
[19:21] <slangasek> cyphermox: how are you going to make it better?
[19:21] <cyphermox> testing the downgrade in a ppa?
[19:21] <cyphermox> well, I suppose we don't care about shim, only shim-signed
[19:21] <slangasek> cyphermox: it can sit in the queue until then :)
[19:21] <slangasek> still the same binary when you're done ;)
[19:22] <cyphermox> yep
[19:22] <ginggs> slangasek: the libpfm4 update is for enabling support for the latest intel CPUs, there's a papi update i want to sync as well - it was a request from the debian maintainer
[19:22] <Mirv> slangasek: robru: right, forgot about the removal. then again we discussed with apw that the upload is not very needed in yakkety anyway, as it was test related change only to please QA, and that yakkety should be already redirected towards overlay this week. there is new UITK already built and being tested now, wanting to get to that was the goal. it may or may not make sense to get into yakkety as
[19:22] <Mirv> it has Qt 5.6 related changes, depend on how testing looks and time flies.
[19:23] <slangasek> ginggs: well, this is a server-seeded package, dependency of s390-tools; looks to me like it needs a freeze exception and possibly sign-off from server team or xnox, no free pass for Debian maintainers :)
[19:24] <ginggs> slangasek: np, i'll file an FFe
[19:24] -queuebot:#ubuntu-release- Unapproved: accepted designate [source] (yakkety-proposed) [1:3.0.0~rc2-0ubuntu1]
[19:24] <Mirv> slangasek: robru: but I agree it'd make sense to not allow UNAPPROVED status silos to be cleaned, since it removes the package which is probably never really wanted. should ve rejected first.
[19:25] -queuebot:#ubuntu-release- Unapproved: accepted glance [source] (yakkety-proposed) [2:13.0.0~rc2-0ubuntu1]
[19:25] <slangasek> Mirv: ok, then we're on the same page :) and you can always ping a release team member for expedited accept, this is preferable to queue breakage and I'm sure the release team will make time for you
[19:25] <jderose> infinity: slangasek: cyphermox: does the package necessarily need to be rebuilt? i know with the differences in the metadata, the deb itself needs to be signed by the canonical archive key ultimately... but can that be done while retaining the exact same signed shim.efi binary used in xenial?
[19:26] <infinity> jderose: The signed binary indeed can't (and won't) change.
[19:26] <infinity> It's the unsigned package that's a bit trickier.
[19:26] -queuebot:#ubuntu-release- Unapproved: accepted horizon [source] (yakkety-proposed) [3:10.0.0~rc3-0ubuntu1]
[19:27] <jderose> infinity: right
[19:27] <slangasek> infinity, cyphermox: if it came down to it, technically we could reupload shim 0.8-0ubuntu2 source under 0.9+vomit~really.0.8, let it build a different binary, and bodge shim-signed to ignore the binary mismatch just this once
[19:28] <slangasek> we would be no less source-compliant than usual
[19:29] -queuebot:#ubuntu-release- Unapproved: accepted nova [source] (yakkety-proposed) [2:14.0.0~rc2-0ubuntu1]
[19:30] <infinity> slangasek: Given the proper binary will continue to exist in xenial (which will outlive yakkety) and we can point to it in a one-liner in copyright or something, that would be fine by me.
[19:30] <infinity> slangasek: I'd prefer not to break all yakkety->yakkety upgrades if we can work around it with minimal futzing.
[19:31] <cyphermox> I don't mind either way, the Breaks/Replaces isn't very complicated either given there was only ever one version released with that bad shim.
[19:32] <infinity> cyphermox: How would Breaks/Replaces help?
[19:32] <infinity> cyphermox: apt won't let you downgrade without scary force options.
[19:32] <infinity> And update-manager definitely won't.
[19:32] <cyphermox> oh, nevermind, I was thinking of shim-signed itself
[19:32] <cyphermox> but that doesn't need any downgrading.
[19:33] <infinity> Right.
[19:33] <infinity> So, I think Steve's suggestion is the best here, perhaps mixed with mine.
[19:33] <infinity> Bump shim version, ignore the la la la binary mismatch in shim-signed, and add a small note that the shim-signed binary in that specific version is actually the one from xenial.
[19:34] <infinity> (And build in a wily PPA if you're having toolchain issues, that's where the last shim built)
[19:34] <cyphermox> well I already have things patched sufficiently to build in yakkety
[19:34] <infinity> Mmkay.  Though if you didn't patch things and built in wily, it might be almost the same as what we had, ish. :P
[19:35] -queuebot:#ubuntu-release- Unapproved: winff (yakkety-proposed/universe) [1.5.3-7ubuntu1 => 1.5.5-1] (no packageset) (sync)
[19:35] <cyphermox> heh
[19:35] <infinity> Patching things to build a binary we don't intent to use is just extra confusion.
[19:35] <infinity> s/intent/intend/
[19:35] <infinity> If the revert can be nothing but a changelog entry, I'd be happier.
[19:35] -queuebot:#ubuntu-release- Unapproved: accepted winff [sync] (yakkety-proposed) [1.5.5-1]
[19:35] <infinity> (which implies building in a wily PPA and copying, probably)
[19:35] <slangasek> yeah, I'd rather see it built in wily and binary copied to yakkety, than source-patched or built with a different toolchain
[19:36] <slangasek> this is all temporary regardless
[19:36] <jderose> true
[19:36] <infinity> Indeed.  Hopefully it's just a couple of hours of wasted time and we get a newer, shinier, less crap shim before release.
[19:36] <infinity> Hopefully.
[19:37] <slangasek> cyphermox: so, I think infinity wins this one, I'll drop the 0.8-0ubuntu2 from the queue and wait for your 0.9+vomit-really-0.8
[19:37] <cyphermox> so, to reiterate; rebuild 0.8-0ubuntu2 named 0.9+1465500757.14a5905.is.0.8-0ubuntu1 in a wily PPA (with an extra changelog entry "revert to 0.8" on top of the changelog from 0.9) and copy?
[19:38] <slangasek> yes
[19:38] <cyphermox> wfm.
[19:38] <slangasek> in a wily, devirt ppa
[19:38] <infinity> s/0ubuntu1/0ubuntu2/ and yes.
[19:38] <cyphermox> well
[19:38] <infinity> We have a shim-prep PPA for this.
[19:38] <infinity> canonical-foundations/shim
[19:38] <cyphermox> that -0ubuntu1 there is the version of the upload, not the version of the previous shim.
[19:39] <infinity> cyphermox: The ".is" confuses it a bit for me, but I won't be picky and reject if you think I'm wrong. :P
[19:39] <cyphermox> infinity: yep, already use that, and the newer shim is there too.
[19:39] <cyphermox> fair enough; s/is/really/
[19:40] <cyphermox> or really.for.realz.
[19:40] <infinity> cyphermox: No, no.  I don't mind "is", I meant that the is (or really) then implies the next string is the original version you're reverting to. :P
[19:40] <infinity> And ubuntu1 and ubuntu2 weren't the same.
[19:40] <infinity> So...
[19:40] <cyphermox> well then it would have to be -0ubuntu2-0ubuntu1
[19:40] <cyphermox> ;)
[19:40] <infinity> Nah.
[19:40] <infinity> Cause we'll never rev that version.
[19:41] <infinity> If we do, something went extra wrong.
[19:41] <cyphermox> yeah, given that I don't care what it is
[19:41] <infinity> Anyhow.   :P
[19:42] <cyphermox>  0.9+1465500757.14a5905.really.is.0.8dash0ubuntu2.for.infinity-0ubuntu99 it is then.
[19:42] <cyphermox> and I again reclaim my very-long-version-numbers title
[19:42] <slangasek> I want my bikeshed to have points all over
[19:42] <slangasek> like a flail
[19:42] <jderose> haha. yeah, that's the keeper cyphermox :)
[19:43] <ginggs> slangasek: libpfm4 + papi FFe filed LP: #1629989
[19:44] <slangasek> I feel like balloons is trying to troll the release team into fixing bug #1629412 for him
[19:45] <slangasek> really, all he had to do was ask
[19:45] -queuebot:#ubuntu-release- Unapproved: rejected shim [sync] (yakkety-proposed) [0.8-0ubuntu2]
[19:47] <cyphermox> I can see this shim stuff just being totally useless and we'll have the signed new one tomorrow or something
[19:48] <infinity> cyphermox: Better than the inverse scenario.
[19:48] <cyphermox> have the new shim totally useless and do this tomorrow?
[19:48] <infinity> :P
[19:49] <cyphermox> > https://launchpad.net/~canonical-foundations/+archive/ubuntu/shim/+sourcepub/6978941/+listing-archive-extra
[19:50] <infinity> Oh, hrm.  s/wily/vivid/ ?
[19:50] <apw> cyphermox, ftbfs
[19:52]  * cyphermox sighs
[19:52] <lamont> hi
[19:52] -queuebot:#ubuntu-release- Unapproved: ifupdown (yakkety-proposed/main) [0.8.13ubuntu2 => 0.8.13ubuntu3] (core)
[19:52] <infinity> cyphermox: Copied it to vivid instead. :P
[19:52] <lamont> ifupdown is me... can someone review and do the whacky-thump into -proposed?
[19:53] <infinity> cyphermox: Lets see how that goes.
[19:53] <cyphermox> infinity: I was about to do that, reaching for copy-package.
[19:53] <infinity> cyphermox: You're too slow. :)
[19:53] <lamont> sometimes, you two scare me
[19:53] <cyphermox> so I've been told.
[19:53] -queuebot:#ubuntu-release- Unapproved: ifupdown (xenial-proposed/main) [0.8.10ubuntu1.1 => 0.8.10ubuntu1.2] (core)
[19:56] <infinity> lamont: Does that actually work...?
[19:57] <lamont> infinity: verfiied on both xenial and yakkety
[19:57] <lamont> and prior art
[19:57] <infinity> lamont: /lib/lsb/init-functions contains some voodoo wherein running /etc/init.d/service if there's a matching systemd unit will run the unit instead, which leads me to believe you've created an infinite loop...
[19:57] <infinity> But okay...
[19:57] <infinity> Maybe it protects against that. :P
[19:57] <lamont>  /lib/systemd/system/apparmor.service:ExecStop=/etc/init.d/apparmor stop
[19:58] <santa_> slangasek: ok, I have looked @ kmbox abi break. I can justify why we can/should ignore that
[19:58] <lamont> infinity: I don't know how the magic works, but it seems to
[19:58] <jderose> cyphermox: is it possible to take the extact data.tar.xz file from the xenial build, just generate a new control.tar.gz and freshly sign thing whole thing up in .deb goodness?
[19:58] <santa_> 1. it's true its an ABI break
[19:59] <infinity> jderose: Not so much.
[19:59] <santa_> 2. it's reverse dependencies are, if I'm not mistaken, just kdepim-runtime and kf5-messagelib
[19:59] <infinity> cyphermox: Looks like the build in vivid worked, so hand-wavey la la la, we're on our way.
[19:59] <cyphermox> yep, making shim-signed now
[20:00] <jderose> infinity: wonder if it produced the exact same bits though
[20:00] <infinity> jderose: I guarantee it doesn't.
[20:00] <infinity> jderose: But we're not using that binary for anything, so refer back to "hand-wavey la la la".
[20:00] <santa_> 3. kdepim-runtime and kf5-messagelib are a part of kde apps 16.04.3 and as such they are handled by our automation tools
[20:01] <jderose> infinity: okay, gotcha. so is the plan just to place the xenial shim.efi properly on the ISO?
[20:01] <santa_> 4. so kdepim-runtime and kf5-messagelib have a versioned build dependency on libkf5mbox-dev (>= 16.04.3~)
[20:02] <infinity> jderose: More or less.
[20:02] <cyphermox> jderose: not just on the iso, once we're done people will update and get the shim from xenial back.
[20:02] <santa_> 5. therefore even if the abi was broken the reverse dependencies will get rebuilt against the latest version of the library and never the old one
[20:02] <lamont> infinity: I'm seeing magic for upstart, but not for systemd
[20:03] <jderose> cyphermox: which raises a question: in what scenarios (which package upgrades, etc) does the shim.efi file from the actual package get copied onto the ESP?
[20:03] <santa_> slangasek: does it sound as a sane excuse to ignore that abi break? keep in mind that we could bump the abi version using our debian abi manager but that would force us to keep a delta with debian
[20:03] <cyphermox> when you upgrade, grub-install gets triggered and will copy it.
[20:04] <infinity> santa_: None of that is a sane reason to ignore an ABI break, and there also shouldn't be a delta with Debian.  If the ABI broke, it should be fixed everywhere, not just in Ubuntu.
[20:04] <infinity> santa_: ABI tracking is about runtime dependencies, not build-time.
[20:05] <infinity> santa_: If libfoo.so.1 no longer provides all the same symbols that libfoo.so.1 used to, it's not libfoo.so.1 anymore.
[20:07] <infinity> lamont: There's magic somewhere...
[20:08] <lamont> ok
[20:09] <infinity> lamont: eg: http://paste.ubuntu.com/23271705/
[20:09] <infinity> But maybe that magic only trips for automagic sysv-imported units.
[20:09] <infinity> Though not sure how it would tell.
[20:10] <lamont> what does /etc/init.d/exim4 look like?
[20:10] <lamont> most of the upstart jobs had their guts replaced
[20:10] <apw> infinity, it is in the init.d libraries at the top
[20:10] <infinity> lamont: A normal init script, with /lib/lsb/init-functions included.
[20:10] <infinity> apw: Yes, I know, lamont claimed there was no magic in /lib/lsb/init-functions though. :P
[20:10] -queuebot:#ubuntu-release- Unapproved: lxd (yakkety-proposed/main) [2.3-0ubuntu6 => 2.3-0ubuntu7] (edubuntu, ubuntu-server)
[20:10] <apw> oh heh, there cirtainly is :)
[20:11]  * lamont didn't say there wasn't just that hecouldn't find it
[20:11] <lamont> apw: how do apparmor and ebtables avoid the magic?
[20:11] <infinity> Ahh.
[20:11] <infinity> lamont: /lib/lsb/init-functions.d/40-systemd
[20:11] <apw> that
[20:12]  * lamont tears down networking on his desktop, just for testing.. back in a few
[20:18] <lamont> infinity: that was ... interesting.  Please reject both uploads, and I'll get back to you
[20:19] -queuebot:#ubuntu-release- Unapproved: golang-go.crypto (yakkety-proposed/main) [1:0.0~git20160607.0.77f4136-1ubuntu2 => 1:0.0~git20160824.0.351dc6a-1ubuntu1] (kubuntu, ubuntu-desktop)
[20:20] -queuebot:#ubuntu-release- Unapproved: rejected ifupdown [source] (xenial-proposed) [0.8.10ubuntu1.2]
[20:20] -queuebot:#ubuntu-release- Unapproved: rejected ifupdown [source] (yakkety-proposed) [0.8.13ubuntu3]
[20:22] <slangasek> santa_: a versioned build-dependency does not solve the problem that, if the old kdepim-runtime or old libkf5messageviewer5 use the symbols that have been removed, an upgrade of libkf5mbox5 first will break these packages even though the dpkg database says everything's ok.  The library package name is a contract not to break the revdeps, which you can't retroactively revoke
[20:24] <santa_> infinity, slangasek: ok, we are going to bump the soname using the abi manager then. we will get a libfoo5abi1 package for each abi break and a new symbols file
[20:24] -queuebot:#ubuntu-release- Unapproved: accepted juju-core [source] (yakkety-proposed) [2.0~rc2-0ubuntu<IP_ADDRESS>]
[20:25] <slangasek> santa_: that would satisfy the requirements nicely and get cleanly through the queue, thanks
[20:25] <santa_> slangasek: ack
[20:25] <infinity> (And this should happen in Debian too, it shouldn't be a delta)
[20:25] <infinity> Err, unless the ABI break was due to Ubuntu-specific toolchain things.
[20:26] <lamont> infinity: for giggles /etc/init.d/apparmor restart
[20:27] <slangasek> santa_, infinity: so, drilling down into kmbox myself, the only symbol that's been dropped is actually a template instantiation: _ZN5KMBox4MBox13appendMessageERK14QSharedPointerIN5KMime7MessageEE@Base -> "KMBox::MBox::appendMessage(QSharedPointer<KMime::Message> const&)@Base"
[20:27] <lamont> -tigernut(root) 312 : /etc/init.d/ebtables stop
[20:27] <lamont> [ ok ] Stopping ebtables (via systemctl): ebtables.service.
[20:27] <lamont> huh
[20:27] <slangasek> santa_, infinity: in this case, it should *not* be an ABI break, and I should be able to rescue the version from the rejected queue (sorry for not noticing this before)
[20:28] <infinity> slangasek: Oh, heh.  Yay C++?
[20:28] <slangasek> infinity: a bit
[20:28] <santa_> sgclark: hmm, I didn't check the symbols diff, but there was a file rename that suggested an ABI change not properly handled by upstream
[20:29] <santa_> slangasek: ↑
[20:29] <sgclark> oh whew
[20:29] <santa_> sgclark: spurious ping, nvm
[20:29] <santa_> sorry
[20:29] <sgclark> hah np
[20:29] <lamont> infinity: it looks like it just needs to have all of the Execs go there for happiness
[20:29] <lamont> yay more testing
[20:30] <infinity> lamont: That might well completely change what that service does...
[20:31] <infinity> lamont: You might want to get some peer review from pitti regarding his systemd/networking house of cards before reuploading.
[20:32] <slangasek> santa_: so, sorry to waste your time on this one.  Yes, I'm confident that this is not actually ABI-breaking.  Though also, the two reverse-deps of this library in the archive?  I can't find any evidence that they use the library...
[20:33] <slangasek> santa_: ah oops, ignore the last, I was using wrong case
[20:34] <santa_> slangasek: ftr, I just checked using a vm with our staging ppas and doing grep-aptavail -FDepends | grep ^Package: | sort -u
[20:35] <santa_> slangasek: btw how you checked symbols differences, debdiff? something else?
[20:35] <santa_> * how did you check
[20:36] <slangasek> santa_: I looked at the debdiff for debian/lib*.symbols
[20:36] <lamont> infinity: agreed
[20:36] <lamont> though he's EU time, yes/
[20:36] -queuebot:#ubuntu-release- Unapproved: accepted gnome-session [source] (yakkety-proposed) [3.20.2-1ubuntu6]
[20:36] <santa_> k
[20:37] <infinity> lamont: Generally, yes.
[20:37] <lamont> yeah
[20:37] -queuebot:#ubuntu-release- Unapproved: accepted python-taskflow [source] (yakkety-proposed) [2.3.0-1ubuntu1]
[20:41] <slangasek> jbicha: gnome-online-accounts being in main doesn't seem to be a new thing, and yet there are a bunch of component-mismatches for its recommends that I don't remember being there before this week.  Since you TIL, do you want to look at whether realmd and dleyna-server should be demoted to Suggests?
[20:44] <jbicha> slangasek: the binary g-o-a is in universe so I don't think that's necessary
[20:44] <Laney> slangasek: I was fulfilling a sponsorship request and didn't at the time see a reason not to do so. If you have more knowledge, then you can reject and comment on the bug saying such: https://bugs.launchpad.net/ubuntu/+source/xml-core/+bug/1629832
[20:45] <jbicha> component-mismatches seems odd
[20:45] <slangasek> jbicha: interesting, ok
[20:45] <santa_> slangasek: I'm now inspecting kpimtextedit symbol changes from our git, this one looks like a real abi break
[20:45] <xnox> slangasek, a good reason to split out /usr/sbin/cpacfstatsd into separate subpackage to push that dependency out.
[20:45] <jbicha> like gnome-bluetooth recommends unity-control-center | gnome-control-center so I don't think g-c-c should show up there
[20:45]  * xnox opens a bug report for z
[20:45] <santa_> first symbol changed, for example
[20:46] <nacc> Laney: slangasek: that sync is the discussion slangasek and I had last week -- it'd be fine to sync if someone has reviewed the upstream chagnes relative to the freeze. But I believe we've also fixed xml-core in yakkety sufficiently for now
[20:46] <slangasek> jbicha: ah, g-c-c has added a Recommends: on g-o-a so you're probably right that this is a bug
[20:46] <santa_> _ZN12KPIMTextEdit14RichTextEditor14handleShortcutEPK9QKeyEvent
[20:46] <santa_> KPIMTextEdit::RichTextEditor::handleShortcut(QKeyEvent const*)
[20:46] <santa_> ↑ old one
[20:47] <santa_> _ZN12KPIMTextEdit14RichTextEditor14handleShortcutEP9QKeyEvent
[20:47] <santa_> KPIMTextEdit::RichTextEditor::handleShortcut(QKeyEvent*)
[20:47] <santa_> ↑ new one
[20:47] <slangasek> Laney, nacc: thanks, rejecting for now and have followed up to the bug
[20:47] <santa_> slangasek: so proceed to bump the abi with our abi manager for this one?
[20:48] <slangasek> santa_: yes, that's clearly an ABI break (wouldn't be in C, but is in C++ because the symbol lookup would fail)
[20:48] <jbicha> similar for lightdm > kylin-greeter
[20:48] <santa_> allright
[20:49] <slangasek> jbicha: yeah, I will take a stab at tricking germinate later to ignore these
[20:49] <jbicha> lightdm recommends unity-greeter | lightdm-greeter
[20:49] <jbicha> and kylin-greeter provides the virtual package lightdm-greeter
[20:50] <jbicha> but unity-greeter provides that virtual package too
[20:50] -queuebot:#ubuntu-release- Unapproved: rejected xml-core [sync] (yakkety-proposed) [0.15]
[20:51] <santa_> slangasek: libkeduvocdocument seems an ABI break too looking at the diff from our git, proceed with our ABI manager (y/n)?
[20:52] <nacc> slangasek: Laney: i think we can do that immediately with 17.04 though, and was planning on following up with that regardless
[20:54] <slangasek> santa_: yes, libkeduvocdocument is a big ABI break
[20:59] -queuebot:#ubuntu-release- Unapproved: accepted nova-lxd [source] (yakkety-proposed) [14.0.0~rc1-0ubuntu1]
[21:01] -queuebot:#ubuntu-release- Unapproved: open-iscsi (yakkety-proposed/main) [2.0.873+git0.3b4b4500-14ubuntu4 => 2.0.873+git0.3b4b4500-14ubuntu5] (ubuntu-desktop, ubuntu-server)
[21:02] -queuebot:#ubuntu-release- Unapproved: accepted lxd [source] (yakkety-proposed) [2.3-0ubuntu7]
[21:02] -queuebot:#ubuntu-release- New: accepted libkf5kipi [amd64] (yakkety-proposed) [16.04.3-0ubuntu1]
[21:02] -queuebot:#ubuntu-release- New: accepted libkf5kipi [armhf] (yakkety-proposed) [16.04.3-0ubuntu1]
[21:02] -queuebot:#ubuntu-release- New: accepted libkf5kipi [powerpc] (yakkety-proposed) [16.04.3-0ubuntu1]
[21:02] -queuebot:#ubuntu-release- New: accepted libkf5kipi [s390x] (yakkety-proposed) [16.04.3-0ubuntu1]
[21:02] -queuebot:#ubuntu-release- New: accepted ubuntu-kylin-wizard [arm64] (yakkety-proposed) [16.10.0]
[21:02] -queuebot:#ubuntu-release- New: accepted ubuntu-kylin-wizard [i386] (yakkety-proposed) [16.10.0]
[21:02] -queuebot:#ubuntu-release- New: accepted ubuntu-kylin-wizard [ppc64el] (yakkety-proposed) [16.10.0]
[21:02] -queuebot:#ubuntu-release- New: accepted libkf5kipi [arm64] (yakkety-proposed) [16.04.3-0ubuntu1]
[21:02] -queuebot:#ubuntu-release- New: accepted libkf5kipi [ppc64el] (yakkety-proposed) [16.04.3-0ubuntu1]
[21:02] -queuebot:#ubuntu-release- New: accepted ubuntu-kylin-wizard [armhf] (yakkety-proposed) [16.10.0]
[21:02] -queuebot:#ubuntu-release- New: accepted ubuntu-kylin-wizard [s390x] (yakkety-proposed) [16.10.0]
[21:02] -queuebot:#ubuntu-release- New: accepted libkf5kipi [i386] (yakkety-proposed) [16.04.3-0ubuntu1]
[21:02] -queuebot:#ubuntu-release- New: accepted ubuntu-kylin-wizard [powerpc] (yakkety-proposed) [16.10.0]
[21:02] -queuebot:#ubuntu-release- New: accepted ubuntu-kylin-wizard [amd64] (yakkety-proposed) [16.10.0]
[21:04] <santa_> slangasek: same with kidentitymanagement, seems a clear abi break so we would manage it with the abi manager to get a new soname
[21:06] <santa_> slangasek: about libkdeedu, it seems, indeed it's obsolete so I think we could skip that package and let the rejection win
[21:07] <stgraber> slangasek: using sru-review for yakkety uploads now? :)
[21:07] <stgraber> slangasek: got confused by the LP e-mail for a sec when I got it
[21:08] <slangasek> stgraber: yeah, sorry, I have been using it because it's convenient for the reviews, then I usually 'n' out and manually accept - forgot to this time :)
[21:08] <stgraber> ok :)
[21:10] <infinity> slangasek: We could rename it queue-review and have it skip the SRU-specific bits if series == devel.
[21:11] <slangasek> infinity: qiew-review plz
[21:12] -queuebot:#ubuntu-release- Unapproved: rejected libpfm4 [sync] (yakkety-proposed) [4.7.0+git30-gd422ba2-1]
[21:45] -queuebot:#ubuntu-release- New source: gce-compute-image-packages (yakkety-proposed/primary) [20160930-0ubuntu1]
[21:56] -queuebot:#ubuntu-release- Unapproved: accepted open-iscsi [source] (yakkety-proposed) [2.0.873+git0.3b4b4500-14ubuntu5]
[22:20] -queuebot:#ubuntu-release- Unapproved: update-manager (yakkety-proposed/main) [1:16.10.5 => 1:16.10.6] (core)
[22:32] -queuebot:#ubuntu-release- New: rejected gce-compute-image-packages [source] (yakkety-proposed) [20160826-0ubuntu1]
[22:32] -queuebot:#ubuntu-release- New: rejected gce-compute-image-packages [source] (yakkety-proposed) [20160930-0ubuntu1]
[22:34] <infinity> Odd_Bloke: You around, re ^?
[22:34] <infinity> Odd_Bloke: If not, slangasek should be forwarding you my rejection message. :P
[22:34] <infinity> Odd_Bloke: Basically, you missed noting that the two bits in disk_expand/third_party/* are GPL, not Apache, and your attempt to force off old packages with "Conflicts" should be "Conflicts/Replaces" to hint the upgrade/removal.
[22:42] -queuebot:#ubuntu-release- Unapproved: accepted update-manager [source] (yakkety-proposed) [1:16.10.6]
[23:17] -queuebot:#ubuntu-release- Unapproved: ubuntu-release-upgrader (yakkety-proposed/main) [1:16.10.3 => 1:16.10.4] (core)
[23:19] <slangasek> jbicha: gnome-online-accounts binary is pulled into main because of s390x only, where we have no unity-control-center package
[23:20] <slangasek> killing off the desktop seed on s390x would fix this
[23:22] <slangasek> but for the moment, worked around by dropping gnome-bluetooth from the seed on s390x
[23:40] -queuebot:#ubuntu-release- Unapproved: casper (xenial-proposed/main) [1.376 => 1.376.1] (desktop-core, ubuntu-server)
[23:53] <jbicha> slangasek: ok, that looks light lightdm's problem too (pulling in kylin-greeter) because unity-greeter isn't built on s390x
[23:53] <jbicha> s/light/like
[23:56] -queuebot:#ubuntu-release- Unapproved: gnome-chemistry-utils (yakkety-proposed/universe) [0.14.10-2 => 0.14.14-1] (mozilla) (sync)


[12:58] <BluesKaj> Howdy folks
 is there any chance the new menu for Plasma will be available for 5.18?
[20:13] <RikMills> no
 I expected as such. oh well


[01:23] <cjohnston> daker_: et al my comment on bug 793739
[01:23] <ubot4> Launchpad bug 793739 in hall-of-fame "HOF doesn't work with django 1.1.1 (affects: 1) (heat: 6)" [Undecided,Invalid] https://launchpad.net/bugs/793739
[10:02] <daker> cjohnston, ok
[11:21] <nigelb> daker: did you get the ical working on summit?
[11:22] <daker> which ical ?
[11:22] <daker> i was working on the color field
[11:29] <nigelb> daker: yeah, that needed the ical right?
[11:29] <nigelb> well, eventually.
[11:29] <nigelb> I thought you said you were getting an error from the summit ical
[12:09] <daker> nigelb, ah no that's on LD bug #742126
[12:09] <ubot4> Launchpad bug 742126 in dateutil "_thread not available on Python 2.6 (affects: 1) (heat: 2)" [Undecided,Invalid] https://launchpad.net/bugs/742126
[12:09] <nigelb> daker: ahh, ignore me then ;)
[13:03] <daker> skype down again
[17:46] <Ronnie> ping cjohnston, mhall119
[17:46] <mhall119> pong Ronnie
[17:46] <Ronnie> is it already clear which items we want to display on the home page?
[17:47] <mhall119> Ronnie: I'd say 80%
[17:47] <Ronnie> i have not very much time to sort it out and find the info. All the time i have i will spend on designing itself
[17:47] <mhall119> Ronnie: will you be around for tomorrow's call?
[17:48] <mhall119> Ronnie: I'd say that if you can even just get the layout done, nevermind the content, then the rest of us will be able to fill it in
[17:48] <Ronnie> i guess not. maybe on thursday
[17:49] <mhall119> sorry, call is next wednesday, not tomorrow
[17:49] <Ronnie> the layout depends very on the content
[17:50] <mhall119> cjohnston: nigelb: daker: do you guys have a few minutes to get Ronnie our input?
[17:50] <Ronnie> mhall119: next call is 15 june, if im right, not tomorrow
[17:50] <mhall119> Ronnie: that's right, I was thinking it was weekly
[17:51] <Ronnie> next wednesday is still free
[17:51] <mhall119> ok
[17:51] <mhall119> I assume we're still using http://farm6.static.flickr.com/5184/5763041728_9d776baccd_o.jpg as our starting point
[17:52] <nigelb> mhall119: Are we starting with just 25 selected feeds?
[17:52] <mhall119> at this point, I'd say the blog feed, upcoming events and twitter feed are correct
[17:52] <mhall119> nigelb: I don't know how many we'll have to start, Jono and the LC will manage that
[17:52] <Ronnie> i think, the upcoming events part is too small
[17:53] <mhall119> Ronnie: if we just list global events I think we can get it in
[17:53] <Ronnie> if it is global events, its good
[17:53] <mhall119> maybe to 60% width on the blogs and 40% on the events and twitter?
[17:53] <mhall119> that would give more room
[17:54] <Ronnie> i think 70/30 will be good enough
[17:54] <mhall119> I'd like to split the "Slider Images" part into rotating images and a google map of upcoming events
[17:54] <mhall119> again, 60/40 or 70/30 split on that
[17:55] <Ronnie> i think it will look messy if the slider image part is splitted
[17:55] <mhall119> I'm unsure of the 4 bottons + text in between, I think the buttons should be secondary nav links
[17:55] <mhall119> those don't really seem "tab-worthy" to me, since they'll never change
[17:56] <mhall119> Ronnie: any idea where we can cleanly integreate a map of upcoming events?  I would really like to see that on the homepage
[17:56] <mhall119> maybe above the Upcoming Events box?
[17:57] <Ronnie> i think the map should at least span half the content-page
[17:58] <mhall119> hmmm, that doesn't give us anywhere to put it, really
[17:58] <mhall119> why so large?
[17:58] <mhall119> it can be a non-interactive image that just links to the /events/ page
[17:58] <Ronnie> its hard to find places on a small map. i dont like small maps
[17:59] <mhall119> I just want something that, at a glance, will tell visitors "Oh look, there are events coming up all over the world"
[17:59] <mhall119> it doesn't have to immediately tell them if there's one close by
[17:59] <Ronnie> im thinking about a tab system, fo rthe large part of the page (tabs: blogs, map, feeds ... )
[18:00] <mhall119> hmmm, that adds extra steps to see that information, which will mean it won't be seen as often
[18:00] <Ronnie> true
[18:00] <mhall119> I'd rather the homepage serve up teasers of information, with links to pages that have the rest
[18:01] <mhall119> for example, the feed might only show 3 or 5 entries on the homepage, but have a link to another page with the last 50 or so
[18:03] <Ronnie> we should also watch for 'too long' blog feeds. we need to truncate these
[18:03] <mhall119> they're already being truncated, I'm not storing the entire content
[18:04] <mhall119> we'll link to the source for that
[18:05] <Ronnie> great
[18:05] <Ronnie> do you also filter out the images?
[18:06] <mhall119> yeah, I'm stripping out all html tags
[18:06] <Ronnie> good
[19:14] <nigelb> mhall119, cjohnston: Could I mark you both as contact along with me for folks wanting to help with summit?
[19:18] <mhall119> nope, just you
[19:18] <mhall119> :P
[19:18] <cjohnston> +1 for mhall119's comment
[19:19] <nigelb> mhall119: err, seriously?
[19:19] <mhall119> no
[19:19] <mhall119> list us
[19:19] <nigelb> :)
[19:19] <mhall119> 2nd and 3rd
[19:19] <nigelb> HAHA
[19:19] <mhall119> hey, it's your project now
[19:20] <mhall119> it's like a curse, it's yours until you fine someone else to trick into taking over
[19:22] <cjohnston> hahah
[19:23] <cjohnston> mhall119: how did we pull that one off
[19:25] <cjohnston> wtf.. instructor is sending me a .pub file
[19:26] <Guest33238> cjohnston: publisher file?
[19:26] <Guest33238> that's weird.
[19:26] <cjohnston> ya
[19:26] <Guest33238> gimp might be able to open it (if you're lucky)
[19:27] <cjohnston> nope
[19:42] <nigelb> mhall119, cjohnston: http://nigelb.me/ubuntu/2011/06/08/new-domain-and-summit.html
[19:46] <cjohnston> nigelb: clearly you didnt follow all of my tutorials :-P
[19:46] <nigelb> cjohnston: heh, I skipped a bunch ;)
[19:49] <cjohnston> i kinda wish i was still running nginx
[19:49] <YoBoY> cjohnston: do you want an online converter for your .pub file ? ^^
[19:50] <cjohnston> I found one already.. Thanks YoBoY.. worst part of it all.. it provided me with nothing
[19:50] <cjohnston> (the file, not the converter)
[20:06] <Pendulum> nigelb: no, just needed to know where I needed to be :)
[20:06]  * nigelb waves to Pendulum
[20:06] <nigelb> heh
[20:06] <nigelb> ok, so bug 668555 is probably the easiest bug to start with.
[20:06] <ubot4> Launchpad bug 668555 in summit "add blueprint url to ical feed (affects: 1) (heat: 4)" [Undecided,New] https://launchpad.net/bugs/668555
[20:07] <Pendulum> *nods*
[20:07] <nigelb> Do you have bzr installed?
[20:08] <Pendulum> yes
[20:08] <cjohnston> do i see a new contributor?
[20:08] <Pendulum> maybe....
[20:08] <nigelb> mhall119: ^^ ;)
[20:08] <cjohnston> pen.. just a warning.. nigelb isnt happy that he was elected project lead.. so he may try to push that job to you :-P
[20:08] <nigelb> haha
[20:09] <Pendulum> cjohnston: no way he can push it, I'm too new and don't know enough :P
[20:09] <nigelb> Pendulum: so, you can branch the summit trunk with "bzr branch lp:summit"
[20:09] <cjohnston> this is nigelb we are talking about though
[20:10] <Pendulum> plus I want something that gets me hacking experience, not project management. I have enough project management experience as is
[20:10] <Pendulum> nigelb: done
[20:10] <cjohnston> well.. in this case, project management == lead hacker ;-)
[20:11] <Pendulum> yeah, totally not qualified for that :-)
[20:11] <cjohnston> hehe
[20:11] <cjohnston> all you have to do is hack on production like our current project lead and you will be fine!
[20:11] <Pendulum> as I said to nigelb in PM, the point in my doing this is that I am useless at learning things through tutorials and just need to jump in and learn by osmosis
[20:11] <cjohnston> thats how i learn
[20:11] <nigelb> Pendulum: okay, so there is an install file, set up everything until the end of "To run summit:"
[20:12] <nigelb> Pendulum: let me know if you run into any trouble with those steps
[20:13] <Pendulum> but it is warning to the rest of you that I am very beginner at all of this
[20:13] <cjohnston> Pendulum: mhall119 had to walk me step by step to get started
[20:14] <nigelb> mhall119: for the blueprint url, should we be using a custom X-BLUEPRINT field?
[20:22] <Pendulum> sorry, that was a 'Pen does something stupid and has to restart so she can get her mouse back' thing
[20:51]  * Pendulum finds bugs in the set-up instructions ;-)
[20:57] <mhall119> nigelb: in ical?
[20:57] <nigelb> mhall119: yeah
[20:57] <mhall119> for what reason?
[20:57] <nigelb> mhall119: https://bugs.launchpad.net/summit/+bug/668555
[20:57] <ubot4> Launchpad bug 668555 in summit "add blueprint url to ical feed (affects: 1) (heat: 4)" [Undecided,New]
[21:00] <mhall119> I think summit would benefit more from a JSON API than cramming everything into an ical
[21:00] <nigelb> mhall119: hrm, so you're voting that one off the ical?
[21:01] <nigelb> mhall119: (can you comment on the bug? :-))
[21:01] <mhall119> that's my opinion, unless dan has a good reason
[21:01] <mhall119> done
[21:03] <nigelb> ok, I'll tackle bug https://bugs.launchpad.net/summit/+bug/793018 with Pendulum then
[21:03] <ubot4> Launchpad bug 793018 in summit "Pull the summary from the launchpad blueprint and push it out via the iCal to Guidebook (affects: 1) (heat: 6)" [High,Confirmed]
[21:03] <daker> nigelb, is that the bug 793019 report  for the color field ?
[21:03] <ubot4> Launchpad bug 793019 in summit " Make the colors for the track a database field instead of in the css (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/793019
[21:03] <nigelb> daker: yes
[21:03] <daker> ok
[21:07] <Pendulum> nigelb: I think we can probably move back here unless you're worried about confusing other people :)
[21:07] <nigelb> right
[21:07] <Pendulum> I'm done with stupid questions for now ;-)
[21:08] <nigelb> heh
[21:08] <Pendulum> or at least the ones that are so stupid I don't want them in a channel :P
[21:09] <nigelb> Pendulum: okay, we'll first fix bug https://bugs.launchpad.net/summit/+bug/665589.
[21:09] <ubot4> Launchpad bug 665589 in summit "Importing blueprints unreliable (affects: 1) (heat: 6)" [Undecided,Confirmed]
[21:09] <nigelb> This is probably the easiest bug ever :)
[21:10] <Pendulum> ok
[21:10] <daker> nigelb, this the error i am getting when i add the color field http://paste.ubuntu.com/621201/
[21:10] <nigelb> there's a line in the schedule/models.py/summitmodel.py where we use urllib to get data from launchpad.  Occasionally, it times out becuause of a 502 error.
[21:10] <nigelb> So we'll use try, except and catch the error from urllib2
[21:11] <nigelb> daker: do you have data from uds-o in summit?
[21:11] <Pendulum> ok
[21:11] <nigelb> Pendulum: take a moment to read the bug and figure out if you can find the line which needs fixing :)
[21:11] <daker> nigelb, no
[21:12] <nigelb> daker: scroll through your meeting table and see if any of the fields have a . in the name,
[21:12] <nigelb> daker: that's the error i had.
[21:12] <daker> ok
[21:16] <daker> nigelb, if we reached the num of RETRIES what and it didn't respond what the function should do ?
[21:16] <daker> -what
[21:17] <nigelb> daker: which function?
[21:17] <daker> update_from_launchpad
[21:17] <nigelb> daker: that's run manually
[21:17] <nigelb> so if we try and it doesn't work, we'll just fail gracefully
[21:17] <nigelb> instead of a 2 page traceback.
[21:18] <nigelb> s/run manually/run from terminal
[21:19] <Pendulum> nigelb: do you mean in schedule/models/summitmodel.py ?
[21:19] <nigelb> Pendulum: Yes
[21:19] <daker> Pendulum, nigelb http://paste.ubuntu.com/621210/
[21:20] <nigelb> daker: Thanks
[21:22] <daker__> sorry
[21:25] <daker> nigelb http://paste.ubuntu.com/621210/ what do you think ?
[21:26] <nigelb> daker: i got that earlier too.  That's perfect.
[21:31] <daker> Pendulum, do you want to implement it ?
[21:32] <Pendulum> daker: I'm working in PM with nigelb to actually write the code myself so I understand what I'm doing :)
[21:32] <daker> ok
[21:32] <Pendulum> (yes, I know duplicating work, but this is how I learn. I've not actually looked at your paste :) )
[21:44] <daker> :)
[22:03] <cjohnston> mhall119: et al, bp in ical is so that people on their phones or whatever can have easy access to get to the bp.. and i think it might have had to do with what Dan was trying to do last UDS mhall119
[22:07] <daker> mhall119, cjohnston any idea http://paste.ubuntu.com/621247/ ?