[00:02] -queuebot:#ubuntu-release- Unapproved: gnome-todo (zesty-proposed/universe) [3.22.1-1 => 3.22.1-2] (no packageset) (sync)
[00:02] -queuebot:#ubuntu-release- Unapproved: accepted gnome-todo [sync] (zesty-proposed) [3.22.1-2]
[00:03] <slangasek> looks like xjadeo in multiverse is a historical inaccuracy; promoting to universe now
[00:04] <slangasek> piem: that's the first half of it; the second half is that, since this package is seeded on the ubuntustudio image and we're in beta freeze, we should only unblock it now in coordination with the ubuntustudio team
[00:04] <piem> slangasek: i see. so there is something i could do to close #1639409? ... oh, did you just close it? :)
[00:06] <piem> slangasek: understood, thanks. there is a bunch of tests in aubio, and they are run at build time. if i can help convincing someone from ubuntustudio to do that, i'd be glad to help
[00:06] <slangasek> yeah, closing the bug now
[00:09] <slangasek> krytarik: ^^ are you the best person to speak to letting aubio in right now?
[00:09] <jbicha> there's quite a few ~ubuntu-archive bugs for when you get bored, like bug 1601953
[00:16] <krytarik> slangasek: Well, I'm not in any official position in the Studio team - but I don't think we care much about something minor like that, given what all we ship, if it sounds sensible generally. :P
[00:17] <krytarik> And piem just asked in our devel channel too - so Len might be bothered to give an official response.
[00:23] <piem> krytarik: did you mean that you think 'we don't mind doing it' or 'we don't care about it'? certainly not minor to me, upstreamwise :P
[00:25] <krytarik> piem: No, I mean the change might be major or minor to the package - but the package itself isn't something like e.g. Ardour or Krita to us.
[00:26] -queuebot:#ubuntu-release- Unapproved: system-config-printer (zesty-proposed/main) [1.5.7+20160812-0ubuntu6 => 1.5.7+20160812-0ubuntu7] (kubuntu, ubuntu-desktop)
[00:33] <piem> krytarik: sure, i got that, but that doesn't really answer my question. :-)
[00:35] <slangasek> krytarik: except that ardour itself needs to be updated as part of the transition, so...
[00:36] <slangasek> and that's an update from 1:50~dfsg-2 to 1:5.5.0~dfsg-1 which no one handled until now
[00:37] <krytarik> I know - I was at the relevant bug report earlier.
[00:46] <slangasek> infinity: systemd 232-20ubuntu1 is nearly ready to go wrt autopkgtests; how do you want to handle this vis-à-vis final beta?
[01:23] <krytarik> slangasek, piem: Well, the versions of both packages sitting in -proposed currently are in Debian for 3 months now, and I don't see any new bugs reported on them - so I guess we should be good. :P
[01:24] <sbeattie> Hi, not sure if there's an SRU person about. For bug 1668934, the percona-xtradb-cluster-5.6, percona-xtrabackup, and percona-galera-3 packages were promoted to (xenial|yakkety)-updates; they should also be pocket copied to the respective -security pockets; the packages were built in the ubuntu-security-proposed ppa to get binaries built with only -security enabled. (cc jamespage)
[03:23] -queuebot:#ubuntu-release- Unapproved: pidgin-librvp (zesty-proposed/universe) [0.9.7cvs-1ubuntu1 => 0.9.7cvs-1.1] (no packageset) (sync)
[03:23] -queuebot:#ubuntu-release- Unapproved: accepted pidgin-librvp [sync] (zesty-proposed) [0.9.7cvs-1.1]
[03:23] -queuebot:#ubuntu-release- Unapproved: scim-canna (zesty-proposed/universe) [1.0.0-4.2ubuntu2 => 1.0.0-4.3] (no packageset) (sync)
[03:24] -queuebot:#ubuntu-release- Unapproved: accepted scim-canna [sync] (zesty-proposed) [1.0.0-4.3]
[04:12] <tsimonq2> aaaaaa/or
[04:12] <tsimonq2> Argh
[04:25] <infinity> slangasek: Don't unblock anything.  I'll be removing the large block in the morning anyway.
[04:27] <slangasek> infinity: copy
[04:27] <infinity> slangasek: paste
[04:56] <infinity> sakrecoer: Any news on UbuntuStudio Beta testing?
[06:48] -queuebot:#ubuntu-release- Unapproved: ladish (zesty-proposed/universe) [1+dfsg0-5ubuntu3 => 1+dfsg0-5.1] (ubuntustudio) (sync)
[07:28] -queuebot:#ubuntu-release- Unapproved: gitlab (zesty-proposed/universe) [8.13.11+dfsg-3 => 8.13.11+dfsg-7] (no packageset) (sync)
[07:29] -queuebot:#ubuntu-release- Unapproved: accepted gitlab [sync] (zesty-proposed) [8.13.11+dfsg-7]
[08:01] -queuebot:#ubuntu-release- Unapproved: clutter-gtk (zesty-proposed/main) [1.8.2-1 => 1.8.2-2] (kubuntu, ubuntu-desktop) (sync)
[08:33] <tsimonq2> Oh come on, don't interrupt my 3 AM hacking session stupid conflicts >__<
[08:33] <tsimonq2>  build-essential : Depends: libc6-dev but it is not going to be installed or
[08:33] <tsimonq2>                             libc-dev
[08:33] <tsimonq2>                    Depends: g++ (>= 4:5.2) but it is not going to be installed
[08:33] <tsimonq2> This is on Yakkety.
[08:34] <tsimonq2> So I guess I'm using an LXD container. :/
[08:49] <tsimonq2> Ha ha, I forgot to enable -updates, ignore me... :P
[09:04] -queuebot:#ubuntu-release- Unapproved: systemd (zesty-proposed/main) [232-20ubuntu1 => 232-21ubuntu1] (core)
[09:05] -queuebot:#ubuntu-release- Unapproved: python-keyring (zesty-proposed/main) [10.1-1 => 10.3.1-1] (core) (sync)
[09:12] -queuebot:#ubuntu-release- Unapproved: dockerpty (xenial-proposed/universe) [0.3.4-1build1 => 0.4.1-1~16.04.1] (no packageset)
[09:12] -queuebot:#ubuntu-release- Unapproved: dockerpty (xenial-proposed/universe) [0.3.4-1build1 => 0.4.1-1~16.10.1] (no packageset)
[09:13] -queuebot:#ubuntu-release- Unapproved: python-docker (xenial-proposed/universe) [1.8.0-0ubuntu1 => 1.9.0-1~16.04.1] (no packageset)
[09:13] -queuebot:#ubuntu-release- Unapproved: python-docker (xenial-proposed/universe) [1.8.0-0ubuntu1 => 1.9.0-1~16.10.1] (no packageset)
[09:14] -queuebot:#ubuntu-release- Unapproved: docker-compose (xenial-proposed/universe) [1.5.2-1 => 1.8.0-2~16.04.1] (no packageset)
[09:14] <mwhudson> argh those ~16.10 versions for xenial :(
[09:15] -queuebot:#ubuntu-release- Unapproved: python-docker (yakkety-proposed/universe) [1.8.0-0ubuntu1 => 1.9.0-1~16.10.1] (no packageset)
[09:16] -queuebot:#ubuntu-release- Unapproved: docker-compose (yakkety-proposed/universe) [1.5.2-1 => 1.8.0-2~16.10.1] (no packageset)
[09:24] -queuebot:#ubuntu-release- Unapproved: mustang (zesty-proposed/universe) [3.2.3-1 => 3.2.3-1ubuntu1] (no packageset)
[09:25] -queuebot:#ubuntu-release- Unapproved: accepted mustang [source] (zesty-proposed) [3.2.3-1ubuntu1]
[09:26] -queuebot:#ubuntu-release- Unapproved: ubuntukylin-default-settings (zesty-proposed/universe) [1.3.17 => 1.3.18] (ubuntukylin)
[09:37] <caribou> howdy, can someone reject the sssd upload on Trusty made yesterday ? Apparently the fix is failing verification on the other releases in -proposed
[09:52] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Zesty Beta 2] has been marked as ready
[09:52] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop i386 [Zesty Beta 2] has been marked as ready
[10:21] <rbasak> caribou: done
[10:21] <caribou> rbasak: thanks!
[10:21] -queuebot:#ubuntu-release- Unapproved: rejected sssd [source] (trusty-proposed) [1.11.8-0ubuntu0.6]
[10:42] <LocutusOfBorg> will some AA work on remove boost1.61 from zesty?
[10:43] <LocutusOfBorg> the three reverse-deps are 1) fixed in branch 2) runtime deps for mir I can upload but I pinged the maintainer on -devel 3) a package that might probably disappear according to LP: #1640317
[10:44] <LocutusOfBorg> http://people.canonical.com/~ubuntu-archive/transitions/html/boost1.62.html
[10:44] <LocutusOfBorg> currently we have both boost1.61 and 1.62 in main :/
[10:47] -queuebot:#ubuntu-release- Unapproved: gitlab-shell (zesty-proposed/universe) [3.6.6-3 => 3.6.6-4] (no packageset) (sync)
[10:48] -queuebot:#ubuntu-release- Unapproved: accepted gitlab-shell [sync] (zesty-proposed) [3.6.6-4]
[11:03] <mapreri> LocutusOfBorg: I'm working out mir in #ubuntu-mir, 0.26.2-1 will be done through bileto, then we can upload -2 switching the deps (and their next 0.26.3-1 will include the change).
[11:03] <mapreri> or whatever version will be the next
[11:04] <LocutusOfBorg> do you have a sponsor
[11:04] <mapreri> yes, you :P
[11:05] <LocutusOfBorg> lol so, ping in case
[11:05] <mapreri> the other 2 still needs taking care, though
[11:06] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (xenial-proposed/main) [4.4.0-70.91] (core, kernel)
[11:07] <LocutusOfBorg> one is fixed in trunk, so just upload
[11:08] <LocutusOfBorg> the next upload will overwrite it
[11:19] <mapreri> On another matter, why is imagemagick still stuck in proposed?
[11:20] <LocutusOfBorg> emacs25
[11:20] <LocutusOfBorg> arm64
[11:20] <mapreri> emacs25 depends on imagegick
[11:20] <mapreri> also the reverse?
[11:20] <LocutusOfBorg> how can it migrate if reverse-deps can't migrate
[11:21] <jbicha> mapreri: it's a library transition
[11:21] <mapreri> jbicha: oh, didn't spot that.
[11:21] <mapreri> why ubuntu doesn't do smooth transitions :|
[11:23] <jbicha> because we don't want obsolete libraries lying around when we release every 6 months
[11:23] <mapreri> the solution is a 6 months freeze! :>
[11:25] <LocutusOfBorg> sure releasing once a year might be better, we don't have such need of new releases anymore
[11:26] <LocutusOfBorg> I stopped updating my ubuntu twice an year some time ago, specially now that we have LTS
[11:26] <mapreri> ? LTS have always been around
[11:26] <LocutusOfBorg> one normal, one LTS, one normal, one LTS
[11:27] <LocutusOfBorg> yes, but they were less stable than now, and supported for less years
[11:27] <LocutusOfBorg> now that the infra-LTS releases are supported only for 9 months... I think even less users are using them
[11:31] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Zesty Beta 2] has been marked as ready
[11:31] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop i386 [Zesty Beta 2] has been marked as ready
[11:45] <rbasak> One used to be able to jump up multiple non-LTS releases. Now if you go non-LTS you have to be on the treadmill. But that's not so bad; there's still a choice of two treadmills.
[11:45] -queuebot:#ubuntu-release- Unapproved: maliit-framework (zesty-proposed/universe) [0.99.1+git20151118+62bd54b-0ubuntu13~2 => 0.99.1+git20151118+62bd54b-0ubuntu14] (ubuntu-qt-packages) (sync)
[12:37] <Laney> robru: looks like we emailed everyone again, oops
[12:43] -queuebot:#ubuntu-release- Unapproved: network-manager (zesty-proposed/main) [1.4.4-1ubuntu2 => 1.4.4-1ubuntu3] (kubuntu, ubuntu-desktop)
[12:55] <mapreri> tbh, I think it's fine to send a reminder every week or so about stuck packages.
[13:01] -queuebot:#ubuntu-release- Unapproved: qmenumodel (zesty-proposed/main) [0.2.11+17.04.20170110.1-0ubuntu1 => 0.2.12+17.04.20170316.1-0ubuntu1] (ubuntu-desktop) (sync)
[13:01] -queuebot:#ubuntu-release- Unapproved: qtmir (zesty-proposed/main) [0.5.1+17.04.20170307-0ubuntu1 => 0.5.1+17.04.20170320.1-0ubuntu1] (ubuntu-desktop, ubuntu-qt-packages) (sync)
[13:01] -queuebot:#ubuntu-release- Unapproved: qtubuntu (zesty-proposed/main) [0.64+17.04.20170308-0ubuntu1 => 0.64+17.04.20170320-0ubuntu1] (ubuntu-desktop, ubuntu-qt-packages) (sync)
[13:01] -queuebot:#ubuntu-release- Unapproved: qtmir-gles (zesty-proposed/universe) [0.5.1+17.04.20170307-0ubuntu1 => 0.5.1+17.04.20170320.1-0ubuntu1] (ubuntu-qt-packages) (sync)
[13:01] -queuebot:#ubuntu-release- Unapproved: qtubuntu-gles (zesty-proposed/universe) [0.64+17.04.20170308-0ubuntu1 => 0.64+17.04.20170320-0ubuntu1] (ubuntu-qt-packages) (sync)
[13:02] -queuebot:#ubuntu-release- Unapproved: unity-api (zesty-proposed/main) [8.4+17.04.20170223-0ubuntu1 => 8.6+17.04.20170317-0ubuntu1] (ubuntu-desktop) (sync)
[13:02] -queuebot:#ubuntu-release- Unapproved: unity8 (zesty-proposed/main) [8.15+17.04.20170308-0ubuntu1 => 8.15+17.04.20170321-0ubuntu1] (ubuntu-desktop, ubuntu-qt-packages) (sync)
[13:02] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (xenial-proposed/main) [4.8.0-44.47~16.04.1] (no packageset)
[13:02] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (yakkety-proposed/main) [4.8.0-44.47] (core, kernel)
[13:03] <jbicha> mapreri: there was a proposal to send reminder emails every day(!)
[13:04] <mapreri> jbicha: well, that might be a tad too eccessive :)
[13:08] <Laney> mapreri: it was actually due to landing a branch which emails people at intervals :)
[13:08] <mapreri> ^^
[13:09] <Laney> maybe these were just the second reminders then
[13:52] -queuebot:#ubuntu-release- Unapproved: system-config-printer (zesty-proposed/main) [1.5.7+20160812-0ubuntu6 => 1.5.7+20160812-0ubuntu8] (kubuntu, ubuntu-desktop)
[14:25] <jibel> powersj, Hey, could you update the iso tracker with the results for ubuntu server http://iso.qa.ubuntu.com/qatracker/milestones/374/builds
[14:26] <powersj> jibel: sure!
[14:29] <jibel> powersj, thanks!
[14:44] <robru> Laney: yeah i think it's expected to resend mails to everybody as it's been above the threshold time for resending mails anyway. It should settle down after the first round of mails
[14:46] <Laney> nod
[15:07] <davmor2> jibel, powersj: okay second install of server via netboot mini.iso and this is http://people.canonical.com/~davmor2/personal-screenshots/login.png the login I get
[15:07] <davmor2> if I switch tty I get a proper prompt as do I if I login from ssh
[15:12] <powersj> davmor2: let me try the netboot iso I don't normally test that one
[15:13] <Laney> slangasek: bug #1672542 FYI
[15:14] <powersj> davmor2: what is the md5sum of your mini.iso? wanna make sure I'm downloading the same
[15:14] -queuebot:#ubuntu-release- New sync: nama (zesty-proposed/primary) [1.208-1]
[15:15] <davmor2> powersj: b2b5c9beb3512059b2d49af67237da62  Downloads/mini32.iso  d9b91090a6af37f6eb0f77e7a0f90c1e  Downloads/mini64.iso  I added the 32 and 64 or it overwrites the images :)
[15:17] <powersj> davmor2: ok install started; you said 2nd install though, so install once and then install again and see if I get the black screen?
[15:19] <davmor2> powersj: no installed amd64 failed there, installed i386 to double check it and it failed there too
[15:19] <powersj> davmor2: oh ok, thx
[15:21] <slangasek> Laney: ah, so it's genuinely regressed against new kernel?
[15:22] <Laney> slangasek: seems so to me, warrants a deeper look
[15:22] <slangasek> right
[15:28] <powersj> davmor2: I get the blinking cursor was well with two messages about /dev/sda1 recovering journal and clean
[15:29] <powersj> davmor2: file a bug and we can update the test tracker with the #
[15:29] <davmor2> powersj: right and then if you switch tty everything is as expected and you can login as normal right?
[15:29] <davmor2> powersj: will do
[15:30] <powersj> davmor2: and yes changing tty gets me to a prompt that I can interact with and login
[15:31] <powersj> and going back to tty1 then works as expected
[15:31] <davmor2> I'm assuming plymouth isn't being killed
[15:41] <davmor2> powersj: went for the lowest element so we can build up from it https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1675453
[15:43] <powersj> davmor2: thanks for catching this and looking at those ISOs
[15:43] <slangasek> Laney, robru, bdmurray, infinity: 5 minutes here for a coffee refresh, please
[15:43] <robru> Ok
[15:43] <bdmurray> slangasek: hopefully not in a microwave
[15:44] <slangasek> bdmurray: grinding fresh beans
[15:47] <davmor2> powersj: so just done a server install it isn't there so it looks like it is because the mini.iso/netboot will use plymouth and display the ubuntu and dots and that isn't being killed correctly
[15:48] <davmor2> I'll update the bug
[15:52] <slangasek> Laney, infinity, bdmurray: so certainly, for SRUs I think the earliest we want to email would be 10 days... because a Friday publication won't release until Monday
[15:54] <bdmurray> slangasek: Maybe 11 then since it won't happen first thing on Monday
[15:54] <slangasek> ok
[15:54] <slangasek> and beyond that 11 day delay, do we think the same nag rules should apply?
[15:55] <infinity> I'm somewhat lacking an opinion on this one.
[15:55] <bdmurray> 11 + 5, then some more backing off?
[15:56] <slangasek> I think my big concern is whether we're nagging the right person if we go after the uploader/sponsor
[15:56] <slangasek> if the bugs are v-needed, v-failed, and the uploader can't do anything
[15:56] <slangasek> aside from pass on the nag
[15:56] <slangasek> but maybe that's appropriate anyway?
[15:56] <bdmurray> if its v-needed they can act
[15:56] <infinity> They're the one that sponsored it, they're responsible for it.
[15:57] <Laney> I'm wondering if britney's the right thing for SRUs
[15:57] <slangasek> uh
[15:57] <Laney> If they're fixing bugs, then we can nag on bugs
[15:57] <infinity> Well, britney's useful for SRUs, but agreed, maybe the britney MAIL isn't.
[15:57] <Laney> Yes, for emailing
[15:57] <slangasek> oh, for emailing, yes :)
[15:57] <infinity> sru-report already has a bug-nagging facility.
[15:57] <infinity> Which reaches more people than just the uploader.
[15:57] <Laney> Might be that it's better to beef that up
[15:58] <chrisccoulson> slangasek, I just noticed that the flash packages you approved last week are still in proposed. They're good to move to release
[15:58] <Laney> Like, make sure the uploaders are subscribed and nag more often
[16:02] <slangasek> chrisccoulson: remind me the full package name please so I can swap in context :)
[16:03] <slangasek> adobe-flashplugin?
[16:04] <bdmurray> Maybe the uploader is subscribed check should happen before accepting the SRU
[16:04] <infinity> slangasek: yes.
[16:04] <chrisccoulson> slangasek, that's the one :)
[16:04] <bdmurray> That just seems like a reasonable change to the SRU process
[16:04] <slangasek> bdmurray: or driven by the sru-review script itself
[16:04] <bdmurray> Yeah, that's what I meant.
[16:04] <slangasek> as in just subscribe them
[16:04] <Laney> Sure, I'm just thinking that for nagging purposes, that's one way to get them to get the mails
[16:05] <Laney> That part can happen at a few different times
[16:06] <slangasek> so it seems like we should leave britney out of the SRU nagmail business for right now
[16:07] <slangasek> and instead beef up the notifications in the sru tools
[16:07] <slangasek> yes?
[16:07] <robru> So did we agree then? Britney won't send nag mails for SRUs
[16:07] <bdmurray> okay
[16:07] <robru> Ok
[16:07] <infinity> +1
[16:08] <Laney> Ok, so can we talk about the backoff for the development series quickly before robru goes and changes it?
[16:08] <robru> What about it?
[16:08] <slangasek> ok
[16:08] <Laney> you know what; I said on the MP :)
[16:08] <slangasek> Laney: we weren't talking about changing the backoff however
[16:08] <slangasek> only the date of the initial nag
[16:08] <slangasek> s/date/delay/
[16:09] <Laney> well, the algorithm as landed sends mail at 3, 6, 12 days
[16:09] <Laney> the previous proposal was 1, 2, 4, ...
[16:09] <Laney> I was arguing on the MP that this was too aggressive
[16:10] <slangasek> I don't particularly care about the length of the backoff
[16:10] <slangasek> I mean, I have my opinion, but I know there's not a consensus
[16:10] <Laney> Good, because I agree that nagging and backing off is fine
[16:11] <slangasek> but it really should start as soon as the package looks stuck - so 1 day, not 3
[16:11] <Laney> I just don't think sending mail that frequently is fine :P
[16:11] <infinity> I'm not sure how useful the first mail at 1 day is, but meh.
[16:11] <slangasek> infinity: it's the 90% case
[16:11] <infinity> 90% of what?
[16:11] <slangasek> of all the things
[16:11] <Laney> like I would probably say that there should be an interval of at least (say) 3 days between mailing about the same thing
[16:12] <slangasek> 90%+ of uploads that need no intervention will have migrated within 24h
[16:12] <robru> Ok but the thing is that the current algo does not make a distinction between "time of first nag" and "backoff frequency". If you set the first nag to 1 day you get 1, 2, 4, etc. Set it to day 3 and it's 3, 6, 12, etc
[16:12] <Laney> and, that said, I would prefer if someone else reviewed the branch this time. :P
[16:12] <infinity> Of all SRUs stuck for 1 day, how many will unstick without intervention?
[16:12] <slangasek> infinity: not SRUs. we're on the devel series again
[16:12] <slangasek> 90% of packages not migrated after 1 day require intervention
[16:12] <infinity> Err, uploads.  Sorry.
[16:12] <infinity> Didn't mean SRUs.
[16:12] <slangasek> k
[16:13] <slangasek> robru: so then the code needs fixed?
[16:13] <infinity> Your statistics look suspiciously made-up. ;)
[16:13] <infinity> Which might be fine for presidential tweets, but I dunno about here.
[16:13] <robru> slangasek: no, your expectations need fixed because my code is really simple and elegant
[16:13] <slangasek> infinity: that's why I only used one significant figure
[16:13] <slangasek> robru: har
[16:14] <Laney> robru: what do you know? how many days ago you last mailed?
[16:14] <infinity> He knows how long it's been in proposed.
[16:14] <Laney> there's a cache file too
[16:14] <slangasek> chrisccoulson: adobeflashpluginpromoted
[16:15] <robru> Laney: yeah it just compares the day off the last mail to the overall age and it's able to work out the decreasing frequency with a simple comparison. But the "day off first mail" and "frequency between mails" is basically the same number, can't change one without the other being affected
[16:15] <Laney> once in the first year of school I wrote a story and forgot to put any spaces in between the words
[16:15] <Laney> The teacher made me write the whole thing out again
[16:15] -queuebot:#ubuntu-release- Unapproved: content-hub (zesty-proposed/main) [0.3+17.04.20170313-0ubuntu1 => 0.3+17.04.20170317.1-0ubuntu1] (kubuntu, ubuntu-desktop) (sync)
[16:15] -queuebot:#ubuntu-release- Unapproved: indicator-datetime (zesty-proposed/main) [15.10+17.04.20170309-0ubuntu1 => 15.10+17.04.20170322-0ubuntu1] (ubuntu-desktop) (sync)
[16:15] -queuebot:#ubuntu-release- Unapproved: indicator-power (zesty-proposed/main) [12.10.6+17.04.20170210-0ubuntu1 => 12.10.6+17.04.20170322-0ubuntu1] (ubuntu-desktop) (sync)
[16:15] -queuebot:#ubuntu-release- Unapproved: indicator-bluetooth (zesty-proposed/main) [0.0.6+17.04.20170207-0ubuntu1 => 0.0.6+17.04.20170322-0ubuntu1] (ubuntu-desktop) (sync)
[16:15] -queuebot:#ubuntu-release- Unapproved: indicator-network (zesty-proposed/main) [0.9.0+17.04.20170116-0ubuntu1 => 0.9.0+17.04.20170322-0ubuntu1] (ubuntu-desktop) (sync)
[16:16] <chrisccoulson> slangasek, thanks :)
[16:16] <infinity> robru: Make the first one be freqint^0, boom, 1 day.
[16:16] -queuebot:#ubuntu-release- Unapproved: game-data-packager (zesty-proposed/multiverse) [48 => 49] (no packageset) (sync)
[16:16] -queuebot:#ubuntu-release- Unapproved: ubuntu-app-launch (zesty-proposed/main) [0.10+17.04.20170310-0ubuntu1 => 0.11+17.04.20170321-0ubuntu1] (ubuntu-desktop) (sync)
[16:16] -queuebot:#ubuntu-release- Unapproved: url-dispatcher (zesty-proposed/main) [0.1+17.04.20170314-0ubuntu1 => 0.1+17.04.20170318-0ubuntu1] (ubuntu-desktop) (sync)
[16:16] -queuebot:#ubuntu-release- Unapproved: libertine (zesty-proposed/main) [1.7+17.04.20170313-0ubuntu1 => 1.7+17.04.20170320.1-0ubuntu1] (ubuntu-desktop) (sync)
[16:16] -queuebot:#ubuntu-release- Unapproved: ubuntu-system-settings (zesty-proposed/main) [0.4+17.04.20170301-0ubuntu1 => 0.4+17.04.20170317.2-0ubuntu1] (ubuntu-desktop) (sync)
[16:16] <Laney> Omg
[16:16] <Laney> Those packages are the "drop upstart" ones
[16:16] <slangasek> Laney:HISTORICALLYACCURATELATININSCRIPTION
[16:16] <infinity> Laney: !!!
[16:17] -queuebot:#ubuntu-release- Unapproved: accepted game-data-packager [sync] (zesty-proposed) [49]
[16:17] -queuebot:#ubuntu-release- Unapproved: iortcw (zesty-proposed/multiverse) [1.50a+dfsg1-2 => 1.50a+dfsg1-3] (no packageset) (sync)
[16:17] <infinity> Is it my birthday?
[16:17] <slangasek> infinity, robru: freqint^0 implies that we're exponential forever, rather than having a max interval which I believe we said should be 30 days
[16:17] <slangasek> well, maybe it doesn't imply that
[16:18] <robru> infinity: yeah there's no exponent in the code. What you describe would require having one corner case for "is this first mail ever"and then handling the general case differently. What i like about the current code is that there's no corner case, it handles all mails with the same code
[16:18] -queuebot:#ubuntu-release- Unapproved: accepted iortcw [sync] (zesty-proposed) [1.50a+dfsg1-3]
[16:18] <infinity> slangasek: The max interval is configured separately, and is currently 30.
[16:18] <slangasek> robru: why is there no exponent in the code that is supposed to be doing exponential backoff?
[16:19] <Laney> I'll go away and let you argue about the implementation now you know my opinion. :)
[16:19] <Laney> thanks all!
[16:19] <slangasek> Laney: thanks :)
[16:19] <robru> slangasek: because math? I dunno man, somehow dividing by 2 resulted in the exponential frequency we observe. I'm not a mathemagician.
[16:21] <robru> slangasek: seriously though: (age - sent_age) < min(MAX_FREQUENCY, age / 2.0)
[16:21] <robru> I guess it's because age is on both sides of that comparison it has an exponential effect or something
[16:22] <infinity> What you have isn't exponential, it's... Young Adam's math vocabulary failing.
[16:22] <slangasek> right; that explains also why it's 2^n intsead of x^n :)
[16:22] <infinity> But 3, 6, 12 isn't exponential.
[16:23] <slangasek> infinity: exponential with a coefficient
[16:23] <slangasek> a*2^n vs. b^n
[16:23] <infinity> Ahh, fair.
[16:23] <robru> right
[16:23] <slangasek> anyway
[16:24] <slangasek> robru: I don't care about a*2^n vs. b^n, but it does need fixed to start on day 1 :)
[16:25] <robru> slangasek: right, so the easiest way to do that is just have it do 1, 2, 4, 8, 16, etc. if that's ok with you that'd be my preference in terms of simplicity. if you want 1, 3, 6, 12 then that throws a wrench in things
[16:25] <slangasek> robru: and to respect Laney's requirement not to send the second mail right away on day 2
[16:25] -queuebot:#ubuntu-release- Unapproved: landscape-client (yakkety-proposed/main) [16.03-0ubuntu2 => 16.03-0ubuntu2.16.10.1] (ubuntu-server)
[16:26] <slangasek> robru: the code needs to meet both of the requirements that Laney and I have laid out
[16:26] <slangasek> robru: so you'll need to lose the simplicity
[16:27] <robru> slangasek: ok
[16:28] <slangasek> robru: thanks :) still something you can get to today?
[16:28] <robru> Laney: wait, your branch isn't merged?
[16:28] <robru> slangasek: yeah I can do it today, will just take me a bit to figure out how to meet both of those requirements simultaneously
[16:28] <Laney> robru: is now, was waiting for you to review :-)
[16:29] <infinity> robru: After the fun math, if !sent && sent_age=0 && age>=24h, send?
[16:30] <robru> infinity: yeah something like that. I'm going to spend a few minutes trying to think if I can futz the formula to keep it simple though. I hate corner cases
[16:30] <infinity> robru: Then your coeffient just controls the frequency after the 1-day mail, but we always assume that the first is at a day.
[16:31] <infinity> robru: Without rewriting it to let you leverage x^0, I think the corner-case is the simplest path.
[16:31] -queuebot:#ubuntu-release- Unapproved: landscape-client (trusty-proposed/main) [14.12-0ubuntu0.14.04 => 14.12-0ubuntu5.14.04] (ubuntu-desktop, ubuntu-server)
[16:33] -queuebot:#ubuntu-release- Unapproved: transgui (zesty-proposed/universe) [5.0.1-4 => 5.0.1-4.1ubuntu1] (no packageset)
[16:33] -queuebot:#ubuntu-release- Unapproved: accepted transgui [source] (zesty-proposed) [5.0.1-4.1ubuntu1]
[16:50] <flexiondotorg> infinity Do you (someone else) have an ETA for zesty beta 2 release?
[16:50] <infinity> flexiondotorg: Today.
[16:50] <infinity> flexiondotorg: If you're after exact times -- No.
[16:53] <flexiondotorg> If you could release just after I've read betime stories with my daughter, that would be grand. Thanks :-)
[17:07] <robru> slangasek: ok please merge: https://code.launchpad.net/~robru/britney/+git/britney2-ubuntu/+merge/320837
[17:08] -queuebot:#ubuntu-release- Unapproved: curtin (zesty-proposed/main) [0.1.0~bzr470-0ubuntu1 => 0.1.0~bzr479-0ubuntu1] (ubuntu-server)
[17:12] <flocculant> jibel: getting a drupal error at iso.qa PDOException: SQLSTATE[08006] [7] FATAL:
[17:13] <jbicha> me too
[17:14] <jibel> flocculant, jbicha I see it too: too many connections :/
[17:16] <jibel> looking
[17:16] <jibel> too many people testing zesty ;)
[17:19] <davmor2> me too :'(
[17:21] -queuebot:#ubuntu-release- Unapproved: transgui (zesty-proposed/universe) [5.0.1-4.1ubuntu1 => 5.0.1-4.1ubuntu2] (no packageset)
[17:22] -queuebot:#ubuntu-release- Unapproved: accepted transgui [source] (zesty-proposed) [5.0.1-4.1ubuntu2]
[17:24] <jibel> flocculant, davmor2 jbicha it should be better now.
[17:24] <davmor2> yay back in
[17:24] <flocculant> jibel: thanks :)
[17:25] <flocculant> just needed to mark stuff ready - before I got told off :D
[17:25] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Zesty Beta 2] has been marked as ready
[17:25] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop i386 [Zesty Beta 2] has been marked as ready
[17:44] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (zesty-proposed/main) [2.439 => 2.440] (desktop-core)
[17:46] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (zesty-proposed) [2.440]
[17:55] -queuebot:#ubuntu-release- Unapproved: accepted juju-mongodb3.2 [source] (yakkety-proposed) [3.2.12-0ubuntu1~16.10]
[17:57] -queuebot:#ubuntu-release- Unapproved: accepted juju-mongodb3.2 [source] (xenial-proposed) [3.2.12-0ubuntu1~16.04]
[18:06] -queuebot:#ubuntu-release- Unapproved: mediascanner2 (zesty-proposed/universe) [0.112+17.04.20170302-0ubuntu1 => 0.112+17.04.20170322-0ubuntu1] (no packageset) (sync)
[18:13] <bdmurray> slangasek: bug 1637290 is marked v-failed (by you) and rcj uploaded a new livecd-rootfs based upon the livecd-rootfs upload for that bug. Can livecd-rootfs be released even though that bug is v-failed?
[18:14] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Zesty Beta 2] has been marked as ready
[18:14] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop i386 [Zesty Beta 2] has been marked as ready
[18:15] <slangasek> bdmurray: I don't have any recollection of livecd-rootfs being involved in the shim bug.  cyphermox ^^ ?
[18:15] <slangasek> ah this is about a change in the names of the efi executables being installed
[18:15] -queuebot:#ubuntu-release- Unapproved: pencil2d (zesty-proposed/universe) [0.5.4+git20170307.c5d8817+dfsg-1 => 0.5.4+git20170323.ec4712d+dfsg-1] (edubuntu) (sync)
[18:16] <slangasek> bdmurray: looking deeper
[18:16] -queuebot:#ubuntu-release- Unapproved: accepted bind9 [source] (yakkety-proposed) [1:9.10.3.dfsg.P4-10.1ubuntu1.4]
[18:17] <cyphermox> bdmurray: I think the livecd-rootfs is unrelated, and you're looking at an old v-failed. The issue with livecd-rootfs back then was that it was doing extra copies of grub and shim instead of just running grub-install
[18:17] <bdmurray> cyphermox: "old v-failed"? the bug either has the tag or doesn't.
[18:18] <cyphermox> bdmurray: we already reverted the things that were broken
[18:18] <cyphermox> the relevant grub is not in xenial/yakkety/trusty
[18:18] <slangasek> bdmurray: which release are you looking at? xenial has no livecd-rootfs in -proposed currently, and yakkety only has the one I just uploaded
[18:18] <cyphermox> slangasek: https://launchpad.net/ubuntu/+source/livecd-rootfs/2.435.1 ?
[18:19] <slangasek> oh
[18:19] <slangasek> not the one I just uploaded :P
[18:19] <slangasek> right
[18:19] <cyphermox> that package isn't verification-failed AFAICT
[18:19] <cyphermox> (checking)
[18:19] <slangasek> bdmurray: yes, this can be released
[18:20] <slangasek> the code change just drops some redundant cp's that will begin to fail when the new shim package is SRUed
[18:20] <bdmurray> okay, thanks!
[18:20] <cyphermox> we need to re-upload to T and X though
[18:21] <cyphermox> "Deleted in xenial-proposed on 2017-02-08 (Reason: Part of a failed SRU) "
[18:21] <cyphermox> it doesn't need to block on the grub/shim changes of 1637290 though
[18:22] -queuebot:#ubuntu-release- Unapproved: metacity (xenial-proposed/main) [1:3.18.7-0ubuntu0.2 => 1:3.18.7-0ubuntu0.3] (ubuntu-desktop)
[18:24] <slangasek> cyphermox: was that code change landed in the xenial-proposed git branch?
[18:24] <slangasek> looks like... no
[18:24] <slangasek> sorry, I said git but I mean bzr
[18:25] <cyphermox> I think there's been another SRU since in xenial-proposed, so it might have been overwritten?
[18:27] -queuebot:#ubuntu-release- New binary: linux-signed-lts-xenial [amd64] (trusty-proposed/main) [4.4.0-70.91~14.04.1] (kernel)
[18:27] <cyphermox> nah, wouldn't have been overwritten
[18:33] -queuebot:#ubuntu-release- Unapproved: accepted variety [source] (yakkety-proposed) [0.6.2-1ubuntu1]
[18:38] <cyphermox> slangasek: I'm doing to upload livecd-rootfs 2.408.9 again with the extra copies removed.
[18:38] <cyphermox> (there is already a 2.408.9 in the queue)
[18:38] <slangasek> cyphermox: ok.  Please commit it to lp:~ubuntu-core-dev/livecd-rootfs/xenial-proposed/ when you do :)
[18:38] <cyphermox> yep, just about to
[18:43] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64 [Zesty Beta 2] has been disabled
[18:44] <cyphermox> slangasek: done, the upload will still be claimed by rcj given all I really did was copy some changes he had initially done.
[18:45] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (xenial-proposed/main) [2.408.8 => 2.408.9] (desktop-core)
[18:47] <slangasek> and old one rejected
[18:48] -queuebot:#ubuntu-release- Unapproved: rejected livecd-rootfs [source] (xenial-proposed) [2.408.9]
[18:49] <cyphermox> I'll clean up 1637290 to remove the tags and but things back to in progress?
[18:51] <slangasek> sounds good to me
[18:52] <cyphermox> we'll reuse the bug for the shim SRUs
[19:04] <rcj> cyphermox: thanks
[19:05] <cyphermox> rcj: I figure you might want to still list this for upload rights applications; and all I really did was merge things and review them
[19:06] -queuebot:#ubuntu-release- Unapproved: mediaplayer-app (zesty-proposed/universe) [0.20.5+17.04.20161201-0ubuntu1 => 0.20.5+17.04.20170321.4-0ubuntu1] (no packageset) (sync)
[19:06] <rcj> I have to put that together for cloud packages so it really will help
[19:07] -queuebot:#ubuntu-release- Unapproved: accepted mediaplayer-app [sync] (zesty-proposed) [0.20.5+17.04.20170321.4-0ubuntu1]
[19:17] -queuebot:#ubuntu-release- New: accepted linux-signed-lts-xenial [amd64] (trusty-proposed) [4.4.0-70.91~14.04.1]
[19:21] -queuebot:#ubuntu-release- Unapproved: debian-installer (zesty-proposed/main) [20101020ubuntu498 => 20101020ubuntu499] (core)
[19:22]  * tsimonq2 stretches and looks around
[19:26] -queuebot:#ubuntu-release- Unapproved: rejected dockerpty [source] (xenial-proposed) [0.4.1-1~16.10.1]
[19:26] -queuebot:#ubuntu-release- Unapproved: rejected python-docker [source] (xenial-proposed) [1.9.0-1~16.10.1]
[19:28] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi2 [Zesty Beta 2] has been updated (20170323)
[19:32] -queuebot:#ubuntu-release- Unapproved: accepted iscsitarget [source] (xenial-proposed) [1.4.20.3+svn502-2ubuntu4.1]
[19:38] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Zesty Beta 2] has been marked as ready
[19:38] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop i386 [Zesty Beta 2] has been marked as ready
[19:38] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Zesty Beta 2] has been marked as ready
[19:38] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD i386 [Zesty Beta 2] has been marked as ready
[19:41] -queuebot:#ubuntu-release- Builds: Ubuntu Server amd64 [Zesty Beta 2] has been marked as ready
[19:41] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi2 [Zesty Beta 2] has been marked as ready
[19:41] -queuebot:#ubuntu-release- Builds: Ubuntu Server i386 [Zesty Beta 2] has been marked as ready
[19:41] -queuebot:#ubuntu-release- Builds: Ubuntu Server ppc64el [Zesty Beta 2] has been marked as ready
[19:41] -queuebot:#ubuntu-release- Builds: Ubuntu Server s390x [Zesty Beta 2] has been marked as ready
[19:42] <robru> slangasek: if you get a sec: https://code.launchpad.net/~robru/britney/+git/britney2-ubuntu/+merge/320837
[19:43] <Rosco2> infinity, thanks for testing Ubuntu Studio. Real life got in the way for me this time.
[19:43] <Rosco2> Will work on some release notes
[19:44] -queuebot:#ubuntu-release- Unapproved: accepted python-docker [source] (yakkety-proposed) [1.9.0-1~16.10.1]
[19:48] -queuebot:#ubuntu-release- Unapproved: gtk+3.0 (xenial-proposed/main) [3.18.9-1ubuntu3.2 => 3.18.9-1ubuntu3.3] (ubuntu-desktop)
[19:53] -queuebot:#ubuntu-release- Unapproved: cups (zesty-proposed/main) [2.2.2-1 => 2.2.2-1ubuntu1] (core)
[19:54] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Zesty Beta 2] has been marked as ready
[19:54] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Zesty Beta 2] has been marked as ready
[19:54] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Zesty Beta 2] has been marked as ready
[19:54] -queuebot:#ubuntu-release- Builds: Ubuntu Base i386 [Zesty Beta 2] has been marked as ready
[19:54] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Zesty Beta 2] has been marked as ready
[19:54] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Zesty Beta 2] has been marked as ready
[19:56] <infinity> Rosco2: Please make sure you have people test more between now and release, I just did a quick "is it broken?" smoketest.  You'll probably find bugs you want to fix if you test deeper.
[20:00] -queuebot:#ubuntu-release- Builds: 38 entries have been added, updated or disabled
[20:02] <infinity> Beta block dropped in proposed-migration.
[20:02] <infinity> Publishing in progress.
[20:02] -queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (zesty-proposed) [20101020ubuntu499]
[20:04] <tsimonq2> infinity: \o/
[20:04] -queuebot:#ubuntu-release- Unapproved: rejected metacity [source] (xenial-proposed) [1:3.18.7-0ubuntu0.3]
[20:04]  * infinity goes on a short vacation while nusakan publishes the source ISOs.
[20:07] <slangasek> robru: this isn't part of your change, but I question ignoring PolicyVerdict.REJECTED_TEMPORARILY being correct
[20:07] <infinity> Temp rejects are only meant to happen while infra is catching up.
[20:08] <infinity> Is a still-running autopkgtest the uploader's responsibility to chase down?
[20:08] <slangasek> if autopkgtests have been "running" for 5 days, that means a request got lost
[20:08] <infinity> slangasek: Sure, it clearly indicates a problem, but who's problem?
[20:08] <infinity> whose.
[20:08] <infinity> Stupid English.
[20:08] <slangasek> infinity: REJECTED_TEMPORARILY means "we don't have results", not "the test is pending"
[20:09] <slangasek> and test requests do go missing in autopkgtest
[20:09] <infinity> slangasek: Pending and not results are the same thing from an uploader's perspective.
[20:09] <infinity> If the test infra is hung, that's surely on us to investigate, not the uploader?
[20:09] <slangasek> infinity: so are you taking responsibility for retrying all lost requests?
[20:09] <infinity> (Or a request disappeared)
[20:09] <infinity> Retrying lost tests can surely be cronnable.
[20:09] <slangasek> and are you doing that?
[20:10] <infinity> No.  We should.
[20:10] <infinity> I'm just saying that's better managed on the infra side.
[20:10] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (yakkety-proposed) [2.435.2]
[20:12] <slangasek> and in the meantime, things continue to fall through the cracks
[20:17] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (xenial-proposed) [2.408.9]
[20:18] <infinity> I suspect tasking someone with "please cron retries" will close the cracks a lot faster and more efficiently than expecting a few dozen uploaders to know what's gone wrong and who to poke to fix it repeatedly.
[20:19] -queuebot:#ubuntu-release- Builds: 38 entries have been added, updated or disabled
[20:19] -queuebot:#ubuntu-release- Builds: 38 entries have been added, updated or disabled
[20:23] -queuebot:#ubuntu-release- Unapproved: bluedevil (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:24] -queuebot:#ubuntu-release- Unapproved: breeze-grub (zesty-proposed/universe) [5.9.3-0ubuntu1 => 5.9.4-0ubuntu1] (kubuntu)
[20:24] -queuebot:#ubuntu-release- Unapproved: breeze-plymouth (zesty-proposed/universe) [5.9.3-0ubuntu1 => 5.9.4-0ubuntu1] (kubuntu)
[20:24] -queuebot:#ubuntu-release- Unapproved: kactivitymanagerd (zesty-proposed/universe) [5.9.3-0ubuntu1 => 5.9.4-0ubuntu1] (kubuntu)
[20:24] -queuebot:#ubuntu-release- Unapproved: breeze-gtk (zesty-proposed/universe) [5.9.3-0ubuntu1 => 5.9.4-0ubuntu1] (kubuntu)
[20:24] -queuebot:#ubuntu-release- Unapproved: kde-cli-tools (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:24] -queuebot:#ubuntu-release- Unapproved: breeze (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:24] <tsimonq2> KDE bugfix release it looks like ^
[20:25] <acheronuk> tsimonq2: yep
[20:25] -queuebot:#ubuntu-release- Unapproved: kde-gtk-config (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:25] -queuebot:#ubuntu-release- Unapproved: kdeplasma-addons (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:25] -queuebot:#ubuntu-release- Unapproved: khotkeys (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:25] -queuebot:#ubuntu-release- Unapproved: kmenuedit (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:25] -queuebot:#ubuntu-release- Unapproved: kscreenlocker (zesty-proposed/universe) [5.9.3-0ubuntu1 => 5.9.4-0ubuntu1] (kubuntu)
[20:25] -queuebot:#ubuntu-release- Unapproved: ksysguard (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:25] -queuebot:#ubuntu-release- Unapproved: kwayland-integration (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:25] -queuebot:#ubuntu-release- Unapproved: kwrited (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:25] -queuebot:#ubuntu-release- Unapproved: libksysguard (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:25] -queuebot:#ubuntu-release- Unapproved: oxygen (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:25] -queuebot:#ubuntu-release- Unapproved: kdecoration (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:25] -queuebot:#ubuntu-release- Unapproved: kinfocenter (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:25] -queuebot:#ubuntu-release- Unapproved: ksshaskpass (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:25] -queuebot:#ubuntu-release- Unapproved: kwin (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:25] -queuebot:#ubuntu-release- Unapproved: milou (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:25] -queuebot:#ubuntu-release- Unapproved: plasma-discover (zesty-proposed/universe) [5.9.3-0ubuntu1 => 5.9.4-0ubuntu1] (kubuntu)
[20:25] -queuebot:#ubuntu-release- Unapproved: plasma-nm (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:25] -queuebot:#ubuntu-release- Unapproved: plasma-sdk (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:25] -queuebot:#ubuntu-release- Unapproved: kgamma5 (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:25] -queuebot:#ubuntu-release- Unapproved: kwallet-pam (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:25] -queuebot:#ubuntu-release- Unapproved: plasma-desktop (zesty-proposed/universe) [4:5.9.3-0ubuntu3 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:25] -queuebot:#ubuntu-release- Unapproved: plasma-pa (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:25] -queuebot:#ubuntu-release- Unapproved: kscreen (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:25] <robru> slangasek: yeah I'm not sure about that, that was added in by Laney. IIRC one of the last things pitti told me before leaving is that there's actually remarkably little difference between REJECTED_{TEMPORARILY,PERMANENTLY}. I'm not up to speed on what situations result in what types of rejects
[20:25] -queuebot:#ubuntu-release- Unapproved: plasma-integration (zesty-proposed/universe) [5.9.3-0ubuntu1 => 5.9.4-0ubuntu1] (kubuntu)
[20:25] -queuebot:#ubuntu-release- Unapproved: libkscreen (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:25] -queuebot:#ubuntu-release- Unapproved: plasma-workspace (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:26] -queuebot:#ubuntu-release- Unapproved: plasma-workspace-wallpapers (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:26] -queuebot:#ubuntu-release- Unapproved: powerdevil (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:26] -queuebot:#ubuntu-release- Unapproved: systemsettings (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:26] -queuebot:#ubuntu-release- Unapproved: polkit-kde-agent-1 (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:26] -queuebot:#ubuntu-release- Unapproved: user-manager (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:26] -queuebot:#ubuntu-release- Unapproved: sddm-kcm (zesty-proposed/universe) [4:5.9.3-0ubuntu1 => 4:5.9.4-0ubuntu1] (kubuntu)
[20:26] <robru> slangasek: I can drop that condition if you want, makes no difference to me
[20:26] <slangasek> robru: see discussion above w/ infinity
[20:27] -queuebot:#ubuntu-release- Unapproved: accepted aptdaemon [source] (yakkety-proposed) [1.1.1+bzr982-0ubuntu16.1]
[20:28] <robru> slangasek: right, cronning autopkgtest retries sounds like a good idea to me, not clear to me though if that means we should keep the condition of not mailing temp rejects or if we should drop that
[20:29] <robru> slangasek: actually I'd like to drop it, from a code-simplicity perspective
[20:29] <infinity> robru: If retries of temp_fail conditions are handles by "us" (via cron, and occasionally an infra person having to dig deeper), then bugging an uploader with "there's a problem, but someone else will resolve it" is pointless.
[20:29] <infinity> s/handles/handled/
[20:29] <infinity> And it's also noisy and annoying.
[20:30] <infinity> Plus, there's no difference between "in progress" and "it got lost", from your POV, so anyone with a long test list will get bugged early.
[20:30] <infinity> (*cough*me*cough*)
[20:32] <robru> infinity: right, I agree with what you're saying, it's just not clear to me that "autopkgtest results got lost / in progress" is the only possibly temp reject scenario.
[20:32] <slangasek> it's the only policy we have that returns tempfail AFAIK
[20:32] <infinity> If there are other tempfails, I'd expect them to be in a similar "we're waiting on something" boat.  That's sort of the point of a tempfail.
[20:32] <infinity> And telling the uploader "yeah, wait longer" is a good way to get them to ignore all future mails.
[20:32] -queuebot:#ubuntu-release- Unapproved: diaspora-installer (zesty-proposed/multiverse) [0.6.3.0+debian2 => 0.6.3.0+debian4] (no packageset) (sync)
[20:33] <robru> infinity: slangasek: AgePolicy and PiupartsPolicy both reference tempfail. I know we're not using Piuparts, not sure what the story with AgePolicy is
[20:34] <infinity> "This email is to inform you that you've wasted 20 seconds of your day opening and reading this email."
[20:34] -queuebot:#ubuntu-release- Unapproved: accepted qemu [sync] (xenial-proposed) [1:2.5+dfsg-5ubuntu10.10]
[20:34] -queuebot:#ubuntu-release- Unapproved: landscape-client (zesty-proposed/main) [16.03-0ubuntu2 => 16.03-0ubuntu3] (ubuntu-server)
[20:34] -queuebot:#ubuntu-release- Unapproved: accepted diaspora-installer [sync] (zesty-proposed) [0.6.3.0+debian4]
[20:34] <infinity> robru: AgePolicy is what Debian uses to not let things migrate before N days.  A classic case of tempfail used properly, and somewhere you'd not want to tell anyone about it. :P
[20:34] <robru> fair enough
[20:35] <tsimonq2> infinity: (20*200)/60 = Kubuntu people :P
[20:35] <tsimonq2> That's how many wasted seconds
[20:35] -queuebot:#ubuntu-release- New: accepted ibm-java80 [source] (xenial-proposed) [8.0.4.1-0ubuntu1]
[20:36] <robru> infinity: slangasek: so sounds like you guys want to continue not mailing on tempfails? so you'll merge my branch as-is then?
[20:36] <slangasek> still reviewing the branch
[20:36] <robru> ok
[20:36] <robru> thanks
[20:37] <slangasek> +            sent = (age - sent_age) < min(MAX_FREQUENCY, (age / 2.0) + 0.5)
[20:37] <infinity> I think not-mail-on-tempfail is the only sane policy.  I also agree with Steve that this means we need to step up resonsibility on the infra side for actually giving a crap about tempfails that aren't transient.
[20:37] <slangasek> this line is irksomely non obvious in its intent
[20:38] <infinity> Isn't there a global programming rule that any routine involving arithmetic more complicated than "x++" needs a comment to explain the input and expected output?
[20:38] <robru> slangasek: I'm open to ideas for clarification. Do you just want a comment?
[20:39] <slangasek> robru: what I really want is for you to stop trying to cram this into a single math expression
[20:39] <slangasek> your test matches the implementation, but I fail to see why this is what we want
[20:39] <robru> slangasek: I'm not sure what you mean by "cram this in", is there some other way than math to express an exponentially decreasing frequency?
[20:39] <slangasek> +            1.0, 3.0, 7.0, 15.0, 31.0, 61.0, 91.0, 121.0, 151.0, 181.0
[20:40] <robru> slangasek: this is exactly what you asked for. mail on the first day, then not the second day.
[20:40] <infinity> That result seems fine to me.
[20:40] <infinity> I agree that the expression itself is meaningless when read. :P
[20:41] -queuebot:#ubuntu-release- New binary: ibm-java80 [ppc64el] (xenial-proposed/none) [8.0.4.1-0ubuntu1] (no packageset)
[20:41] <robru> slangasek: what if I took the expression and broke it out into a couple variables with meaningful names? would that satisfy you? I'd really rather not change the formula itself at this point.
[20:41] -queuebot:#ubuntu-release- Unapproved: accepted signon-ui [sync] (xenial-proposed) [0.17+16.04.20170116-0ubuntu1]
[20:41] -queuebot:#ubuntu-release- Unapproved: metacity (xenial-proposed/main) [1:3.18.7-0ubuntu0.2 => 1:3.18.7-0ubuntu0.3] (ubuntu-desktop)
[20:41] <slangasek> that's not actually exponentiation
[20:41] <slangasek> well
[20:42] <slangasek> I guess it's exponential on the delay
[20:42] <slangasek> so yeah
[20:42] <robru> slangasek: it is exponentiation, the exponent is just hidden because we're working backwards from the age to figure out the exponent.
[20:42] <infinity> 1/2/4/8/16/32/32/32/32/32 was the original strawman, and it was determined that 2 is too close to 1, so indeed, his series works well enough.
[20:42] <infinity> But it's hard to explain how he arrives at it.
[20:43] -queuebot:#ubuntu-release- New binary: ibm-java80 [i386] (xenial-proposed/none) [8.0.4.1-0ubuntu1] (no packageset)
[20:43] -queuebot:#ubuntu-release- New binary: ibm-java80 [amd64] (xenial-proposed/none) [8.0.4.1-0ubuntu1] (no packageset)
[20:44] <robru> it becomes clearer if you consider the deltas instead of the absolute number of days. it goes: mail after 1 day, after 2 days, after 4 days, after 8 days, etc. so you get mail on day 1, day 3 (1+2), day 7 (3+4), etc
[20:44] <infinity> Indeed.
[20:44] <infinity> My brain just got there too.
[20:44] <infinity> So, yeah.  I'd be happy just with a comment explaining what it's meant to do.
[20:45] <infinity> The +0.5 is a clever way of getting 1 out of 0, but rather non-obvious, for instance.
[20:45] <infinity> (Well, of getting 1 out of 1 divided by 2, but yeah)
[20:47] <slangasek> so what happens if we miss sending emails for a day?
[20:47] <slangasek> say, because a package hit the age on exactly the right day that a freeze block was in place
[20:47] <robru> slangasek: then what happens is the next time britney does run, it sees it's cache file, says "oh yeah, the last mail I sent is well before the defined cutoff" and then it sends a mail
[20:47] <robru> slangasek: well freeze blocks don't get mailed.
[20:48] <slangasek> robru: and then how long does it wait until the next mail is sent?
[20:48] <slangasek> because now instead of sending at age=3, you've sent at age=4
[20:48] <slangasek> and so if we save that to the cache, the next mail goes out on day 9 instead of on day 7
[20:48] <slangasek> doesn't it?
[20:49] <infinity> slangasek: It should send immediately when it's valid to send again.
[20:49] <robru> slangasek: it follows the formula. refer to the test, the second test case that tests what happens when is_valid is True, it sends the first mail on day 5. This causes the frequency to change, but it still follows the same exponential decrease in frequency.
[20:50] <robru> infinity: yes, it will send immediately as soon as it considers it valid, but delaying one mail delays all future mails too, because it goes by "how long ago the last one was sent" and not just based on the direct age of the package
[20:50] <infinity> Yes, that's sane.
[20:50] <infinity> Otherwise a 3 day freeze would result in you getting back-to-back mails.
[20:50] <infinity> Which would be unhelpful.
[20:50] <slangasek> infinity: except that it also changes the backoff rate
[20:51] <infinity> slangasek: It doesn't change the rate, it just slides the dates?
[20:51] <robru> slangasek: well, it's still exponential, it just has a larger coefficient in that case
[20:51] <slangasek> because the backoff is being derived from age-last_sent_age
[20:51] <robru> infinity: 5.0, 11.0, 23.0, 47.0, 77.0, 107.0, 137.0, 167.0, 197.0
[20:51] <infinity> Oh, indeed.
[20:52] <infinity> I see what you mean.
[20:52] <infinity> So instead of 1<long freeze>2 4 8, you get 1<long freeze>4 8 16
[20:52] <slangasek> right
[20:53] <slangasek> which I don't think is what's wanted
[20:53] <robru> slangasek: I don't think it matters? The point is that it's infrequent and decreasing in frequency?
[20:54] <robru> slangasek: like I don't believe anybody ever said "it MUST email on day 1, 2, 4, 8, 16!". it's just "hey please not every day", so this isn't mailing every day.
[20:55] <slangasek> I was never in favor of exponential backoff but I was ok with that as a compromise.  Now we have an exponential backoff that isn't even applied consistently.
[20:56] <robru> slangasek: how about I just make it every 3 days, starting on day 1?
[20:56] <infinity> No.
[20:56] <infinity> Also, no.
[20:57] <infinity> Literally everyone who knows how a mail filter works will ignore those in the first month.
[20:57] <infinity> And those who don't will filter them by hand.
[20:57] <infinity> But pretend they read them.
[20:58] <infinity> The gap in the exponential backoff isn't ideal, but it's better than a consistent repetition.
[20:58] <robru> infinity: I'm pretty sure everybody in the set of "ubuntu uploaders" can work out a mail filter, and will use a mail filter regardless of whether the emails are daily, weekly, or exponential-backoffly.
[20:58] <infinity> robru: Then why have the feature? :P
[20:58] <robru> infinity: literally because steve asked for it. I don't even care about this at all
[20:59] <infinity> But no, I disagree with that assertion, at least as it applies to me.  With the backoff, I won't be inclined to filter the world, and if I forget about something for two weeks, boom, pie in the face.
[20:59] <infinity> But being told every 3 days is just another thing I'll reflexively delete based on scanning the first few character of the subject line.
[21:00] <infinity> proposed-migration would be the new Viagra.
[21:01] <tsimonq2> infinity: For the past month I had no spam filter so I really relate to that. :P
[21:02] <robru> infinity: slangasek: ok so I literally do not care what gets decided, but I need you two to come to an agreement so I can get this merged
[21:02] <infinity> It doesn't need to be literally exponential or involve fancy math, given the number of integers we're talking here before the monthish cap, you could just hardcode "first mail at 1, second mail at 3, third mail at 7..."
[21:03] <infinity> And to make Steve happy, if one or more of those is missed, you send one, and record all the missed ones as sent.
[21:03] -queuebot:#ubuntu-release- New binary: ibm-java80 [s390x] (xenial-proposed/partner) [8.0.4.1-0ubuntu1] (no packageset)
[21:03] <slangasek> right
[21:04] <infinity> 1, 3, 7, 15, 31, it's 5 integers.
[21:04] <robru> infinity: that's exactly the thing, though, is that you precisely cannot do that. britney isn't a long running process that can just have a list of integers to pop from when it needs. it's a script called periodically by cron and all I know is how long the package has been sitting in proposed, and i have to somehow workout backwards from that whether or not
[21:04] <robru> it's been an appropriate length of time or not. you have to track when the last email was sent and then you have to subtract how long ago that was, and then math it up to create the pattern you want.
[21:05] <infinity> Last mail was sent at three days, we're now at 8 days, you send a mail and claim you sent it at 7.  Last mail was sent at 3, it's now 18, you send a mail and claim it sent at 15.
[21:06] <robru> what?
[21:06] <slangasek> slightly different than what I had in mind, but yes
[21:06] <infinity> There's no rule that the timestamps in your cache have to actually reflect reality.
[21:06] <slangasek> knowing when the last mail was sent is enough to know what the interval should be until the next mail
[21:07] <slangasek> but the interval should be 2^n instead of being based on the date the last mail was sent
[21:07] <robru> slangasek: 1, 3, 7 IS 2^n
[21:08] <robru> 2^n days in between mails
[21:08] <robru> not "every 2^n day"
[21:09] <slangasek> until the first time you miss a mail because of a block hint or an infrastructure outage
[21:09] <slangasek> and then you're 1, 4, 9 or such
[21:09] <robru> slangasek: ok, so if I change this to just have a fixed list of integer days, what's going to happen then is that if there's a delay sending one mail, it won't also delay all future mails, resulting in cases where mails can get "bunched up". the nice thing about the current implementation is that if there's a delay for any reason, future mails are also
[21:09] <robru> delayed.
[21:10] <infinity> Future mails being delayed is fine if you don't miss a step in the sequence.
[21:10] <infinity> So you could record date sent and sequence number.
[21:10] <robru> infinity: you can't "miss a step" in this sequence because there isn't a defined sequence. it just measures the age and increases the delay based on the age.
[21:11] <infinity> Steve's concern is that if you miss the +4, then your next is +8 instead of +4
[21:11] <robru> well that's not what happens.
[21:12] <robru> there is no "you miss +4 so it goes to +8". what happens is, the formula works out what the appropriate delay should be, as a continuous function, for all possible values of daysold. so if the 4th mail is delayed by a couple hours, the fifth mail is also delayed by slightly more hours.
[21:12] <slangasek> we are not in agreement that the delay it's calculating is appropriate.
[21:13] <robru> there is no "oops +4 got lost so the next one isn't until +8". it just sends it when the function tips over the threshhold, which will be "the first possible run after whatever blocks are lifted"
[21:13] <robru> slangasek: I really don't see why it matters whether a mail is sent on the 3rd day or the 4th day. I nominate this conversation for bikeshed of the year.
[21:16] -queuebot:#ubuntu-release- Unapproved: shim (yakkety-proposed/main) [0.9+1465500757.14a5905.is.0.8-0ubuntu3 => 0.9+1474479173.6c180c6-1ubuntu1] (core) (sync)
[21:16] <infinity> I logged into snakefruit, and I've completely forgotten why.
[21:17] -queuebot:#ubuntu-release- Unapproved: shim (xenial-proposed/main) [0.8-0ubuntu2 => 0.9+1474479173.6c180c6-1ubuntu1] (core) (sync)
[21:17] -queuebot:#ubuntu-release- Unapproved: rejected docker-compose [source] (yakkety-proposed) [1.8.0-2~16.10.1]
[21:18] -queuebot:#ubuntu-release- Unapproved: rejected docker-compose [source] (xenial-proposed) [1.8.0-2~16.04.1]
[21:18] -queuebot:#ubuntu-release- Unapproved: ubuntu-mate-artwork (zesty-proposed/universe) [17.04.7 => 17.04.8] (ubuntu-mate)
[21:19] -queuebot:#ubuntu-release- Unapproved: shim-signed (yakkety-proposed/main) [1.21.3 => 1.27~16.10.1] (core)
[21:22] -queuebot:#ubuntu-release- Unapproved: docker-compose (yakkety-proposed/universe) [1.5.2-1 => 1.8.0-2~16.10.1] (no packageset)
[21:25] -queuebot:#ubuntu-release- Unapproved: grub2-signed (yakkety-proposed/main) [1.74 => 1.74.2] (core)
[21:25] -queuebot:#ubuntu-release- Unapproved: grub2 (yakkety-proposed/main) [2.02~beta2-36ubuntu11 => 2.02~beta2-36ubuntu11.2] (core)
[21:26]  * tsimonq2 smiles and patiently waits for Final Beta email
[21:26] <cyphermox> ^ slangasek: yakkety shim update: grub2{-signed} is versioned this way because there was a .1 already before.
[21:26] <slangasek> cyphermox: sure
[21:27] -queuebot:#ubuntu-release- Unapproved: docker-compose (xenial-proposed/universe) [1.5.2-1 => 1.8.0-2~16.04.1] (no packageset)
[21:27] <cyphermox> (in other words, everything is there for the yakkety shim update, and about to upload xenial's now)
[21:29] <flexiondotorg> Apparently - http://www.omgubuntu.co.uk/2017/03/download-ubuntu-17-04-beta-2-release
[21:30] <tsimonq2> flexiondotorg: They always jump the gun...
[21:30] <tsimonq2> flexiondotorg: Always.
[21:30] -queuebot:#ubuntu-release- Unapproved: grub2-signed (xenial-proposed/main) [1.66.8 => 1.66.9] (core)
[21:30] -queuebot:#ubuntu-release- Unapproved: shim-signed (xenial-proposed/main) [1.19~16.04.1 => 1.27~16.04.1] (core)
[21:30] -queuebot:#ubuntu-release- Unapproved: grub2 (xenial-proposed/main) [2.02~beta2-36ubuntu3.8 => 2.02~beta2-36ubuntu3.9] (core)
[21:34] <flexiondotorg> tsimonq2 I know.
[21:58] -queuebot:#ubuntu-release- Unapproved: accepted docker-compose [source] (yakkety-proposed) [1.8.0-2~16.10.1]
[22:01] <infinity> flexiondotorg: Meh, close enough.
[22:03] -queuebot:#ubuntu-release- Unapproved: gobject-introspection (zesty-proposed/main) [1.51.5-1ubuntu1 => 1.52.0-0ubuntu1] (ubuntu-desktop)
[22:14] -queuebot:#ubuntu-release- Unapproved: activity-log-manager (zesty-proposed/main) [0.9.7-0ubuntu24 => 0.9.7-0ubuntu25] (ubuntu-desktop)
[22:26] -queuebot:#ubuntu-release- Unapproved: activity-log-manager (xenial-proposed/main) [0.9.7-0ubuntu23 => 0.9.7-0ubuntu23.1~xenial] (ubuntu-desktop)
[22:26] -queuebot:#ubuntu-release- Unapproved: activity-log-manager (yakkety-proposed/main) [0.9.7-0ubuntu23 => 0.9.7-0ubuntu23.1~yakkety] (ubuntu-desktop)
[22:31] -queuebot:#ubuntu-release- Unapproved: activity-log-manager (trusty-proposed/main) [0.9.7-0ubuntu14.1 => 0.9.7-0ubuntu14.2] (ubuntu-desktop)
[22:31] -queuebot:#ubuntu-release- Unapproved: gnome-photos (zesty-proposed/universe) [3.23.91-0ubuntu1 => 3.24.0-0ubuntu1] (desktop-extra, ubuntugnome)
[22:42] -queuebot:#ubuntu-release- Unapproved: accepted keepalived [sync] (xenial-proposed) [1:1.2.19-1ubuntu0.2]
[22:43] <robert_ancell> Can someone help get activity-log-manager 0.9.7-0ubuntu24  out of proposed? It's depwaiting on a s390x build but if you follow the dependency chain that stops at upstart which doesn't do s390x
[22:43] -queuebot:#ubuntu-release- Unapproved: skalibs (zesty-proposed/universe) [0.47-1.1 => 0.47-1.1] (no packageset) (sync)
[22:44] -queuebot:#ubuntu-release- Unapproved: accepted skalibs [sync] (zesty-proposed) [0.47-1.1]
[22:44] -queuebot:#ubuntu-release- Unapproved: accepted metacity [source] (xenial-proposed) [1:3.18.7-0ubuntu0.3]
[22:47] <nacc> robert_ancell: did the dependency chain change somehow? ubuntu23 built on s390x?
[22:48] -queuebot:#ubuntu-release- Unapproved: debian-installer (zesty-proposed/main) [20101020ubuntu499 => 20101020ubuntu500] (core)
[22:48] <robert_ancell> nacc, I don't think anything changed from the a-l-m end
[22:50] <robert_ancell> nacc, the previous version of a-l-m was compiled in Xenial, and upstart did have a s390x build then
[22:50] <nacc> robert_ancell: oh i'm seeing that now
[22:50] <nacc> robert_ancell: it would seem that activity-log-manager needs to not depend on that package on s390x then?
[22:51] <infinity> robru: Didn't a ton of stuff just hit the queue to remove upstart deps from the desktop/touch chains?
[22:51] <infinity> Err.
[22:51] <infinity> robert_ancell: ^^
[22:52] <robert_ancell> nacc, I wasn't sure if that information should be in the a-l-m package. It doesn't care itself about the architecture and none of the intermediate dependencies seem to have rules like that
[22:52] <robert_ancell> infinity, yeah, I'd hope the a-l-m dependencies get fixed and then this problem wouldn't hit a-l-m itself
[22:52] <infinity> robert_ancell: That would be my take.  This might shake itself out shortly.
[22:53] <nacc> robert_ancell: right, it does seem like it's just a side-effect of other stuff going on right now
[22:53] <robert_ancell> ok
[22:53] <infinity> Removing upstart entirely was a goal for zesty.  We may or may not meet it, but we're definitely still trying.
[22:53] <nacc> infinity: that's what i thought i read earlier too -- but not sure
[22:53] <nacc> infinity: as to stuff just landing that chagned this
[22:53]  * infinity nods.
[22:53] <infinity> Well, "landing".  It may all need review.
[22:54] <nacc> heh, but one of them is your upload infinity: https://launchpad.net/ubuntu/+source/unity-control-center/15.04.0+17.04.20170314-0ubuntu2
[22:54] <nacc> do you get notifications when something is stuck in dep-wait too? or is that just a one-time thing?
[22:54] <infinity> Well, you get notifications from britney of the failure to promote.
[22:54] <infinity> Which you can track back to "oh, cause it never built".
[22:55] <nacc> infinity: ah but in this case, it did get promoted to release
[22:55] <nacc> infinity: i'm not sure why/how?
[22:55] <nacc> i guess s390x doesn't really matter for desktop, maybe something knows that
[22:56] <robert_ancell> I'm pretty sure it doesn't matter on desktop
[22:56] <robert_ancell> Given unity-control-center doesn't have a package currently
[22:57] <infinity> nacc: The binary wasn't there before, thus it was okay.
[22:57] <nacc> infinity: oh i see
[22:57] <infinity> We don't care if binaries build everywhere, we care if something *regresses*.
[22:57] <nacc> infinity: right that makes sense
[22:57] <nacc> infinity: sorry, i often forget that nuance :)
[22:57] <infinity> That said, a ton of desktop stuff will magically build on s390x when the upstart removal is complete.
[22:57] <nacc> right
[23:00] <robert_ancell> On the flip side - we are holding back fixes from users on architectures that actually run desktops...
[23:00] <robert_ancell> Note that a-l-m is usually only accessed through u-c-c
[23:01] -queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (zesty-proposed) [20101020ubuntu500]
[23:01] -queuebot:#ubuntu-release- Unapproved: gnome-themes-standard (zesty-proposed/main) [3.22.2-1ubuntu1 => 3.22.3-1ubuntu1] (ubuntu-desktop)
[23:02] <infinity> robert_ancell: I won't "hold it back" long.  Just going to see how this upstart stuff shakes out, and either your update will Just Work, or I'll give it a nudge.
[23:02] <robert_ancell> infinity, ok, thanks
[23:03] -queuebot:#ubuntu-release- Unapproved: accepted kmenuedit [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:03] -queuebot:#ubuntu-release- Unapproved: accepted kscreenlocker [source] (zesty-proposed) [5.9.4-0ubuntu1]
[23:03] -queuebot:#ubuntu-release- Unapproved: accepted ksysguard [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:03] -queuebot:#ubuntu-release- Unapproved: gnome-documents (zesty-proposed/universe) [3.23.91-0ubuntu1 => 3.24.0-0ubuntu1] (desktop-extra, ubuntugnome)
[23:03] -queuebot:#ubuntu-release- Unapproved: landscape-client (zesty-proposed/main) [16.03-0ubuntu2 => 16.03-0ubuntu3] (ubuntu-server)
[23:03] -queuebot:#ubuntu-release- Unapproved: unity-settings-daemon (zesty-proposed/main) [15.04.1+16.10.20161003-0ubuntu1 => 15.04.1+17.04.20170322-0ubuntu1] (ubuntu-desktop) (sync)
[23:03] -queuebot:#ubuntu-release- Unapproved: accepted kscreen [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:03] -queuebot:#ubuntu-release- Unapproved: accepted oxygen [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:03] -queuebot:#ubuntu-release- Unapproved: makedev (zesty-proposed/universe) [2.3.1-93ubuntu1 => 2.3.1-93ubuntu2] (lubuntu)
[23:03] -queuebot:#ubuntu-release- Unapproved: accepted ksshaskpass [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:03] -queuebot:#ubuntu-release- Unapproved: nova (zesty-proposed/main) [2:15.0.1-0ubuntu1 => 2:15.0.2-0ubuntu1] (openstack, ubuntu-server)
[23:03] -queuebot:#ubuntu-release- Unapproved: gnome-software (zesty-proposed/main) [3.22.7-0ubuntu1 => 3.22.7-0ubuntu2] (ubuntu-desktop)
[23:07] -queuebot:#ubuntu-release- Unapproved: accepted content-hub [sync] (zesty-proposed) [0.3+17.04.20170317.1-0ubuntu1]
[23:07] -queuebot:#ubuntu-release- Unapproved: accepted indicator-datetime [sync] (zesty-proposed) [15.10+17.04.20170322-0ubuntu1]
[23:07] -queuebot:#ubuntu-release- Unapproved: accepted indicator-power [sync] (zesty-proposed) [12.10.6+17.04.20170322-0ubuntu1]
[23:07] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-app-launch [sync] (zesty-proposed) [0.11+17.04.20170321-0ubuntu1]
[23:07] -queuebot:#ubuntu-release- Unapproved: accepted url-dispatcher [sync] (zesty-proposed) [0.1+17.04.20170318-0ubuntu1]
[23:07] -queuebot:#ubuntu-release- Unapproved: accepted indicator-bluetooth [sync] (zesty-proposed) [0.0.6+17.04.20170322-0ubuntu1]
[23:07] -queuebot:#ubuntu-release- Unapproved: accepted libertine [sync] (zesty-proposed) [1.7+17.04.20170320.1-0ubuntu1]
[23:07] -queuebot:#ubuntu-release- Unapproved: accepted indicator-network [sync] (zesty-proposed) [0.9.0+17.04.20170322-0ubuntu1]
[23:07] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-system-settings [sync] (zesty-proposed) [0.4+17.04.20170317.2-0ubuntu1]
[23:07] <infinity> robert_ancell: ^-- Indeed, this above might unstick it.  You're depwait on unity-control-center, and u-c-c is depwait on indicator-datetime, which has an s390x build above.
[23:07] <robert_ancell> \o/
[23:12] -queuebot:#ubuntu-release- Unapproved: accepted qmenumodel [sync] (zesty-proposed) [0.2.12+17.04.20170316.1-0ubuntu1]
[23:12] -queuebot:#ubuntu-release- Unapproved: accepted qtmir [sync] (zesty-proposed) [0.5.1+17.04.20170320.1-0ubuntu1]
[23:12] -queuebot:#ubuntu-release- Unapproved: accepted qtubuntu [sync] (zesty-proposed) [0.64+17.04.20170320-0ubuntu1]
[23:12] -queuebot:#ubuntu-release- Unapproved: accepted unity8 [sync] (zesty-proposed) [8.15+17.04.20170321-0ubuntu1]
[23:12] -queuebot:#ubuntu-release- Unapproved: accepted qtmir-gles [sync] (zesty-proposed) [0.5.1+17.04.20170320.1-0ubuntu1]
[23:12] -queuebot:#ubuntu-release- Unapproved: accepted unity-api [sync] (zesty-proposed) [8.6+17.04.20170317-0ubuntu1]
[23:13] -queuebot:#ubuntu-release- Unapproved: accepted qtubuntu-gles [sync] (zesty-proposed) [0.64+17.04.20170320-0ubuntu1]
[23:15] -queuebot:#ubuntu-release- Unapproved: accepted clutter-gtk [sync] (zesty-proposed) [1.8.2-2]
[23:15] -queuebot:#ubuntu-release- Unapproved: accepted libdrm [sync] (zesty-proposed) [2.4.75-2]
[23:15] -queuebot:#ubuntu-release- Unapproved: accepted ladish [sync] (zesty-proposed) [1+dfsg0-5.1]
[23:15] -queuebot:#ubuntu-release- Unapproved: accepted python-keyring [sync] (zesty-proposed) [10.3.1-1]
[23:16] -queuebot:#ubuntu-release- Unapproved: rejected ladish [sync] (zesty-proposed) [1+dfsg0-5.1]
[23:16] -queuebot:#ubuntu-release- Unapproved: accepted pencil2d [sync] (zesty-proposed) [0.5.4+git20170323.ec4712d+dfsg-1]
[23:19] -queuebot:#ubuntu-release- Unapproved: accepted gnome-photos [source] (zesty-proposed) [3.24.0-0ubuntu1]
[23:19] -queuebot:#ubuntu-release- Unapproved: accepted systemsettings [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:19] -queuebot:#ubuntu-release- Unapproved: accepted user-manager [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:19] -queuebot:#ubuntu-release- Unapproved: accepted gobject-introspection [source] (zesty-proposed) [1.52.0-0ubuntu1]
[23:19] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-mate-artwork [source] (zesty-proposed) [17.04.8]
[23:22] -queuebot:#ubuntu-release- Unapproved: accepted gnome-chess [source] (zesty-proposed) [1:3.24.0-0ubuntu1]
[23:22] -queuebot:#ubuntu-release- Unapproved: accepted lightdm [source] (zesty-proposed) [1.22.0-0ubuntu1]
[23:22] -queuebot:#ubuntu-release- Unapproved: accepted libsecret [source] (zesty-proposed) [0.18.5-3.1ubuntu1]
[23:25] -queuebot:#ubuntu-release- Unapproved: accepted gnome-documents [source] (zesty-proposed) [3.24.0-0ubuntu1]
[23:25] -queuebot:#ubuntu-release- Unapproved: accepted gnome-themes-standard [source] (zesty-proposed) [3.22.3-1ubuntu1]
[23:25] -queuebot:#ubuntu-release- Unapproved: accepted makedev [source] (zesty-proposed) [2.3.1-93ubuntu2]
[23:25] -queuebot:#ubuntu-release- Unapproved: accepted gnome-software [source] (zesty-proposed) [3.22.7-0ubuntu2]
[23:25] -queuebot:#ubuntu-release- Unapproved: accepted nova [source] (zesty-proposed) [2:15.0.2-0ubuntu1]
[23:25] -queuebot:#ubuntu-release- Unapproved: accepted landscape-client [source] (zesty-proposed) [16.03-0ubuntu3]
[23:26] -queuebot:#ubuntu-release- Unapproved: libgweather (zesty-proposed/main) [3.24.0-0ubuntu1 => 3.24.0-0ubuntu2] (kubuntu, ubuntu-desktop)
[23:31] -queuebot:#ubuntu-release- Unapproved: accepted at-spi2-core [source] (zesty-proposed) [2.22.0-5ubuntu4]
[23:31] -queuebot:#ubuntu-release- Unapproved: accepted network-manager [source] (zesty-proposed) [1.4.4-1ubuntu3]
[23:31] -queuebot:#ubuntu-release- Unapproved: accepted ubuntukylin-default-settings [source] (zesty-proposed) [1.3.18]
[23:31] -queuebot:#ubuntu-release- Unapproved: accepted maliit-framework [sync] (zesty-proposed) [0.99.1+git20151118+62bd54b-0ubuntu14]
[23:31] -queuebot:#ubuntu-release- Unapproved: accepted xfce4-notifyd [source] (zesty-proposed) [0.3.6-0ubuntu1]
[23:31] -queuebot:#ubuntu-release- Unapproved: accepted systemd [source] (zesty-proposed) [232-21ubuntu1]
[23:33] -queuebot:#ubuntu-release- Unapproved: accepted kwayland-integration [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:33] -queuebot:#ubuntu-release- Unapproved: accepted kwrited [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:33] -queuebot:#ubuntu-release- Unapproved: accepted libksysguard [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:33] -queuebot:#ubuntu-release- Unapproved: accepted plasma-desktop [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:33] -queuebot:#ubuntu-release- Unapproved: accepted plasma-integration [source] (zesty-proposed) [5.9.4-0ubuntu1]
[23:34] -queuebot:#ubuntu-release- Unapproved: accepted plasma-pa [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:34] -queuebot:#ubuntu-release- Unapproved: accepted kwin [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:34] -queuebot:#ubuntu-release- Unapproved: accepted milou [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:34] -queuebot:#ubuntu-release- Unapproved: accepted plasma-nm [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:34] -queuebot:#ubuntu-release- Unapproved: accepted libkscreen [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:34] -queuebot:#ubuntu-release- Unapproved: accepted plasma-discover [source] (zesty-proposed) [5.9.4-0ubuntu1]
[23:36] -queuebot:#ubuntu-release- Unapproved: accepted bluedevil [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:36] -queuebot:#ubuntu-release- Unapproved: accepted breeze-gtk [source] (zesty-proposed) [5.9.4-0ubuntu1]
[23:36] -queuebot:#ubuntu-release- Unapproved: accepted breeze [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:36] -queuebot:#ubuntu-release- Unapproved: accepted kde-cli-tools [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:36] -queuebot:#ubuntu-release- Unapproved: accepted breeze-grub [source] (zesty-proposed) [5.9.4-0ubuntu1]
[23:36] -queuebot:#ubuntu-release- Unapproved: accepted kactivitymanagerd [source] (zesty-proposed) [5.9.4-0ubuntu1]
[23:36] -queuebot:#ubuntu-release- Unapproved: accepted breeze-plymouth [source] (zesty-proposed) [5.9.4-0ubuntu1]
[23:36] -queuebot:#ubuntu-release- Unapproved: accepted kdecoration [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:37] -queuebot:#ubuntu-release- Unapproved: accepted kde-gtk-config [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:37] -queuebot:#ubuntu-release- Unapproved: accepted kgamma5 [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:37] -queuebot:#ubuntu-release- Unapproved: accepted kinfocenter [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:37] -queuebot:#ubuntu-release- Unapproved: accepted plasma-sdk [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:37] -queuebot:#ubuntu-release- Unapproved: accepted kdeplasma-addons [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:37] -queuebot:#ubuntu-release- Unapproved: accepted kwallet-pam [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:37] -queuebot:#ubuntu-release- Unapproved: accepted khotkeys [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:39] -queuebot:#ubuntu-release- Unapproved: accepted plasma-workspace-wallpapers [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:39] -queuebot:#ubuntu-release- Unapproved: accepted polkit-kde-agent-1 [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:39] -queuebot:#ubuntu-release- Unapproved: accepted sddm-kcm [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:39] -queuebot:#ubuntu-release- Unapproved: accepted plasma-workspace [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:39] -queuebot:#ubuntu-release- Unapproved: accepted powerdevil [source] (zesty-proposed) [4:5.9.4-0ubuntu1]
[23:40] -queuebot:#ubuntu-release- Unapproved: accepted libgweather [source] (zesty-proposed) [3.24.0-0ubuntu2]
[23:42] -queuebot:#ubuntu-release- Unapproved: accepted mediascanner2 [sync] (zesty-proposed) [0.112+17.04.20170322-0ubuntu1]
[23:42] -queuebot:#ubuntu-release- Unapproved: accepted unity-settings-daemon [sync] (zesty-proposed) [15.04.1+17.04.20170322-0ubuntu1]