/srv/irclogs.ubuntu.com/2017/05/05/#ubuntu-release.txt

-queuebot:#ubuntu-release- New binary: gcc-7-cross-ports [i386] (artful-proposed/universe) [0ubuntu3] (no packageset)01:51
=== lynxorian is now known as lyn||ian
=== cpaelzer_ is now known as cpaelzer
slangaseknacc: php7.x-xml should be fixed to not Provide: php-xml, that's what was still holding php7.0 in main06:26
acheronukcontact SRU team in here, or somewhere else?07:21
acheronukanyway... got an email about this on phased updates https://errors.ubuntu.com/?release=Ubuntu%2017.04&package=k3b&period=day&version=17.04.0-0ubuntu107:30
acheronukcan't see anything in the build and changes that would account for any increased crash rate there.07:30
acheronukI suspect is it more a case of, "oooh, and update to something I don't normally use. I'll launch it and have a look". Then managing to trigger a crash I can't replicate, which they may well have got with the previous build had the bothered to do the same with that07:32
acheronukoh, and if I look at a timescale of a week or more on that report page and look at all versions (i.e. from before the start of the update phasing or that version was uploaded), I see more occurrences or exactly the same reports07:50
acheronukso if there is a crash (that I can't track or reproduce) evidence is very strong that it is not the SRU update build itself07:56
apwacheronuk, yes SRU is "here"08:06
acheronukapw: thanks. glad I wasn't talking pointlessly into the void there :)08:07
Laneyboth things could be true :)08:07
apwacheronuk, there also is "a major uptick" but htat is from 1 to 3 reports if i am reading this right08:09
apwacheronuk, and i assuem that is because you had none in 17.04 before it released, and then got some users, who are hitting these rare bugs08:10
apwacheronuk, is it telling you the thing has been stopped ?08:10
acheronukapw: agreed08:11
acheronukor at least that is the way it seems to me08:11
acheronuk2 secs08:11
acheronukapw: email "Further phasing of this update has been stopped until the errors have either been fixed or determined to not be a result of this Stable Release Update."08:11
apwLaney, do you know one determines that ?08:12
apwor indicates one has ....08:13
Laneyummmmmmmmmmmmmmmmm08:15
Laneyon a case by case basis AFAIK08:15
infinityacheronuk: You're reading it wrong.  The double free is definitely new.08:15
infinityA few of these are new.08:15
infinityhttps://errors.ubuntu.com/problem/ccf29ca2fc3a7fd8440f77fb469260998c2725bc is new.08:16
acheronuklink does not work for me ^^^08:17
infinityacheronuk: And I'm not sure how you can confidently say that you see nothing in a 6MB diff to account for that. :P08:17
acheronukinfinity: the double free says 1 occurrence for version 17.04.0-0ubuntu1, but checking over all versions (which must be pre-SRU builds) it is 3 occurrences08:21
acheronukinfinity: and the other error certainly has occurrences prior to the SRU build08:22
infinityI may be having windowing issues indeed.08:23
infinityAnd also just diffed the sources to see it was pretty much all po updates.08:23
infinityWell, and some XML, which could cause random crashes in an XML parser, I suppose, but meh.08:24
acheronukinfinity: not saying I discount these crashes. I will be keeping an eye on bug reports to see if we get anything concrete to work with and that shows the affect users adversly08:24
infinityFWIW, one of these double-frees is "new", in that the identical signature hasn't been seen on a previous version, but this software seems to just randomly vomit double-frees all over the place, in many versions, so I don't think this is so much new as just a slightly different codepath with the same bug. :P08:27
acheronukinfinity: right. this is the 1st time I have really had to use that crash data pages, and can't log in anyway, so may have missed that :/08:28
infinityYeah, I'm not sure who you ask to get access, but you should ask nicely for access for things you can upload.08:28
infinity(It's locked down by default because stack traces of random user cores are potentially very sensitive, so I suspect there's some interview process where you have to promise to be a good person)08:29
acheronukinfinity: agreed. already submitted the canonical for asking for permission to view them on packages in the kubuntu set08:29
infinityAnyhow, I think I'm okay with phasing this back up.08:30
infinityAfter looking at the mess in more detail.08:30
acheronuk*canonical online form I mean08:30
infinityacheronuk: And done.08:31
acheronukinfinity: thank you. :) As said, will keep an eye on bug reports, forum posts etc.08:32
LocutusOfBorginteresting, with windows style line endings the #!/bin/sh is not correctly interpreted08:48
LocutusOfBorgis this a regression? http://autopkgtest.ubuntu.com/packages/v/vtk6/artful/amd6408:49
infinityLocutusOfBorg: /bin/sh^M is very much not a valid interpreter. :P08:50
LocutusOfBorgwell, it is the windows style line ending 0a0d, we might check it and use it anyway?08:50
LocutusOfBorgin the meanwhile I'll ask anton to stop using that stuff, and I uploaded a fixed one08:51
LocutusOfBorgI was just curious08:51
infinityLocutusOfBorg: Or, don't write shell scripts in notepad.08:51
infinityLocutusOfBorg: Pretty sure you won't convince the kernel folks to parse DOS magic.08:52
apwLocutusOfBorg, right that is a windows line ending, linux uses unix line endings08:52
apwwindows is of course wrong :)08:53
infinityCan't fathom how or why that upload changed ALL those line endings.08:53
infinityThe diff is a mess.08:53
LocutusOfBorgI'm not saying windows is right, of course :)08:53
LocutusOfBorginfinity, yes, I don't even find such changes in git08:53
LocutusOfBorgI'm cloning the repo right now08:54
infinityLocutusOfBorg: He somehow did a unix2dos number on pretty much all of debian/patches and debian/tests.08:56
apwderp08:56
LocutusOfBorgjust on the patch headers, of course08:56
LocutusOfBorgthis seems intentional08:56
LocutusOfBorgand intentionally wrong08:56
infinityLocutusOfBorg: Some headers.  A few complete patches.08:57
infinityLocutusOfBorg: It's weird.08:57
LocutusOfBorgI think quilt complains08:57
LocutusOfBorgor maybe they are not applied08:57
LocutusOfBorgnice to see how science team can screw up things08:57
infinityAbsolutely bizarre, at any rate.08:57
LocutusOfBorgApplying patch 10_allpatches.patch08:58
LocutusOfBorg(Stripping trailing CRs from patch; use --binary to disable.)08:58
LocutusOfBorghe did that because the source is probably wrong08:59
-queuebot:#ubuntu-release- New: rejected gcc-7-cross-ports [i386] (artful-proposed) [0ubuntu3]09:10
-queuebot:#ubuntu-release- New: rejected gcc-7-cross-ports [ppc64el] (artful-proposed) [0ubuntu3]09:10
-queuebot:#ubuntu-release- Unapproved: x11proto-core (xenial-proposed/main) [7.0.28-2ubuntu1 => 7.0.31-1~ubuntu16.04.1] (core, xorg)09:13
-queuebot:#ubuntu-release- Unapproved: libdrm (xenial-proposed/main) [2.4.70-1~ubuntu16.04.1 => 2.4.76-1~ubuntu16.04.1] (core, xorg)09:16
-queuebot:#ubuntu-release- Unapproved: libxfont (xenial-proposed/main) [1:1.5.1-1 => 1:2.0.1-3~ubuntu16.04.1] (core, xorg)09:18
-queuebot:#ubuntu-release- New source: libxfont1 (xenial-proposed/primary) [1:1.5.2-4~ubuntu16.04.1]09:18
LocutusOfBorgapw, please accept virtualbox-* in yakkety and zesty unapproved queues? :)09:23
-queuebot:#ubuntu-release- Unapproved: libwacom (xenial-proposed/main) [0.18-1 => 0.22-1~ubuntu16.04.1] (kubuntu, ubuntu-desktop)09:23
-queuebot:#ubuntu-release- New source: llvm-toolchain-4.0 (xenial-proposed/primary) [1:4.0-1ubuntu1~16.04.1]09:25
-queuebot:#ubuntu-release- Unapproved: wayland (xenial-proposed/main) [1.9.0-1 => 1.12.0-1~ubuntu16.04.1] (desktop-core, ubuntu-server, xorg)09:27
apwLocutusOfBorg, the SRU bug you have used for the zesty one is the same as for xenial, can you some how say the version pairs for the other srus which apply09:29
apwLocutusOfBorg, perhaps right at the top "Zesty affects version X and fixed in Y"09:29
tjaaltoninfinity: ^ uploaded the first batch of hwe-16.04 refresh. have a look when you're back from holidays09:36
LocutusOfBorgapw, will do shortly (meeting now)09:42
LocutusOfBorgcan we please know what is the plan with src:location-service and boost-1.61^09:42
apwxnox, ^ ?09:53
sil2100Do we use location-service for anything besides the now-deprecated touch?09:58
-queuebot:#ubuntu-release- Unapproved: accepted virtualbox [source] (zesty-proposed) [5.1.22-dfsg-0ubuntu1.17.04.1]09:59
infinitysil2100: Probably not, but following the rdep trail tears out basically all of touch. :P10:02
infinitysil2100: So, someone should either fix it, unentangle it, or decide WTF to do with the whole stack.10:02
sil2100hah, I guess we might really start considering just thrashing touch altogether10:03
-queuebot:#ubuntu-release- Unapproved: rejected virtualbox-ext-pack [source] (zesty-proposed) [5.1.22-2ubuntu1.17.04.1]10:03
Laneyxn_ox is looking at the removals alreaady10:04
infinityLaney: Unless he's started on a second round, he was originally just looking at a shallow set that directly involved upstart.10:05
LaneySecond round is correct.10:06
infinityOh, shiny.10:06
LocutusOfBorgok I will disentangle location-service by making it build agasint boost-1.6210:06
LocutusOfBorgand then ask removal of boost1.6110:06
infinityWell, I won't lose sleep over it if it all gets torn out.10:06
Laneyhttps://code.launchpad.net/~xnox/ubuntu-seeds/unity8-removals/+merge/32361510:06
-queuebot:#ubuntu-release- Unapproved: rejected virtualbox-guest-additions-iso [source] (zesty-proposed) [5.1.22-1ubuntu1.17.04.1]10:07
LocutusOfBorgreject? :(10:07
apwLocutusOfBorg, version numbers of the support packages are newer than artful10:09
infinityLocutusOfBorg: I suspect the version you were looking for there was 5.1.22-1~17.04.1 (or, if there really are Ubuntu changes and it's not just a straight backport, 5.1.22-1~ubuntu17.04.1)10:11
LocutusOfBorgthe first one is good, reuploading10:12
LocutusOfBorgapw, please accept virtualbox/yakkety and reject the other two :)10:14
infinityLocutusOfBorg: The verb you're looking for is "review", not "accept". ;)10:14
apwinfinity, i've nearly correct that a couple of times too :)10:15
LocutusOfBorgs/accept/review/g :)10:16
LocutusOfBorgI forgot, -i irclogs.ubuntu.com/* :D10:16
-queuebot:#ubuntu-release- Unapproved: rejected virtualbox-ext-pack [source] (yakkety-proposed) [5.1.22-2ubuntu1.16.10.1]10:19
-queuebot:#ubuntu-release- Unapproved: rejected virtualbox-guest-additions-iso [source] (yakkety-proposed) [5.1.22-1ubuntu1.16.10.1]10:19
LocutusOfBorgand reuploaded :)10:19
-queuebot:#ubuntu-release- Unapproved: virtualbox-ext-pack (zesty-proposed/multiverse) [5.1.18-1 => 5.1.22-2~17.04.1] (no packageset)10:20
LocutusOfBorgfortunately the virtualbox-* don't suffer from strange versioning schemes10:20
LocutusOfBorg(they don't suffer anymore)10:20
infinityThey do, however, still suffer from being virtualbox.10:20
-queuebot:#ubuntu-release- Unapproved: virtualbox-ext-pack (yakkety-proposed/universe) [5.1.6-2ubuntu1 => 5.1.22-2~16.10.1] (no packageset)10:21
-queuebot:#ubuntu-release- Unapproved: virtualbox-guest-additions-iso (zesty-proposed/multiverse) [5.1.18-1 => 5.1.22-1~17.04.1] (no packageset)10:21
-queuebot:#ubuntu-release- Unapproved: virtualbox-guest-additions-iso (yakkety-proposed/multiverse) [5.1.6-1 => 5.1.22-1~16.10.1] (no packageset)10:21
ginggswould someone please bump the pysam hint to 'force-badtest python-pysam/0.10.0+ds-2/armhf python-pysam/0.10.0+ds-2/i386'  ?10:21
ginggsand please rm deepnano:armhf from artful-proposed - it built where it is not installable10:22
LocutusOfBorginfinity, I meant, there was a automatically-evaluated version check in ext-pack against the same virtualbox minor release, but I fixed it10:22
infinityLaney: ^-- Can we make britney/autopkgtest/whoever forget those arches had results?  Hinting them forever because they're no longer built isn't super sane.10:22
apwi seem to remeber we have to remove the results in-toto from swift to do that currently (or something)10:23
infinityginggs: Removal done.10:23
ginggsinfinity: thanks10:23
Laneyinfinity: No, but you can use 'all' for the version10:24
infinityLaney: Sure, but then if it *does* build on those arches in the future, we'll continue ignoring it until someone notices.10:24
infinityLaney: Which is why I didn't use /all10:24
LaneyIt's that or go hack swift and delete the results10:24
=== darkxst_ is now known as darkxst
ginggsLaney: would one have to delete all the past results, or just for the current series?10:25
apwi wonder if there is something we can do outside to extract the /all/ hints and verify them10:25
infinitySeems like a bit of a weird bug that we request tests on an arch that has no binaries.10:26
apwi assume it has some via _all10:27
infinityOh, indeed, python-pysam-tests is arch:all.10:27
infinityThough, that's not the bug.10:29
Laneyginggs: You would delete all passed results for the series in question so it's alwaysfailed, and then I think there's a cache in britney to remove too.10:29
infinityI've ignored other stuff that has no arch:all bits.10:29
infinityWe seem to just keep requesting tests on all arches forever.10:29
infinityThough, it also looks like I used foo/all/arch for lots of those, so not sure why python-pysam is special in my mind.10:30
infinityI'll /all it for now.10:30
LaneyWrite a test for it: tests/test_autopkgtest.py10:30
LaneyAssuming this bug exists and therefore it's not tested for10:31
apwinfinity, i think in the short term we should perioducally check the /all/ for good and rip them, i recon we could that prgramtically pretty easy10:31
infinityAnyhow, updated the hint for now.  That's all the energy I have for it at 4:30am.10:32
ginggsinfinity: thanks10:33
LaneyI filed https://bugs.launchpad.net/auto-package-testing/+bug/168851610:37
ubot5`Ubuntu bug 1688516 in Auto Package Testing "No way to mark a test as 'accepted regression'" [Undecided,New]10:37
infinityLaney: That sounds like a reasonable feature.  I'd bikeshed the key as "force-failtest" to match badtest and skiptest, though.10:40
LaneyMakes sense10:41
=== chrisccoulson_ is now known as chrisccoulson
apwinfinity, that was the name i came up with too10:59
infinityapw: Fools seldom differ.11:01
apwso very true, and we are that :)11:01
-queuebot:#ubuntu-release- Unapproved: neutron-lbaas (yakkety-proposed/universe) [2:9.0.0-0ubuntu1 => 2:9.0.0-0ubuntu2] (openstack, ubuntu-server)12:11
ginggslocation-service has migrated, can src:boost1.61 be removed from artful please?12:29
apwwon't that show up automatically on the nbs report if you are right it is no longer needed12:36
apwno i am mixing my metaphors, ignore me12:37
apw(it is not the same source)12:38
infinityginggs: Be a bit more patient for it to stop showing up in reverse-depends.12:38
apwthat12:38
-queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (trusty-proposed) [3.13.0-119.166]12:45
* ginggs waits patiently12:46
-queuebot:#ubuntu-release- Unapproved: rejected cgroup-lite [source] (trusty-backports) [1.11~ubuntu14.04.3]12:55
apw^ duplicate in the queue12:56
-queuebot:#ubuntu-release- Unapproved: accepted virtualbox-ext-pack [source] (zesty-proposed) [5.1.22-2~17.04.1]13:02
-queuebot:#ubuntu-release- Unapproved: accepted virtualbox-guest-additions-iso [source] (zesty-proposed) [5.1.22-1~17.04.1]13:03
-queuebot:#ubuntu-release- Unapproved: chrome-gnome-shell (xenial-proposed/universe) [8-2ubuntu4~ubuntu16.04.1 => 9-0ubuntu1~ubuntu16.04.2] (no packageset)13:11
-queuebot:#ubuntu-release- Unapproved: chrome-gnome-shell (yakkety-proposed/universe) [8-2ubuntu4~ubuntu16.10.1 => 9-0ubuntu1~ubuntu16.10] (no packageset)13:13
-queuebot:#ubuntu-release- Unapproved: chrome-gnome-shell (zesty-proposed/universe) [8.2.1-1ubuntu1 => 9-0ubuntu1~ubuntu17.04] (ubuntugnome)13:13
-queuebot:#ubuntu-release- Unapproved: apt (xenial-proposed/main) [1.2.20 => 1.2.22] (core)13:15
-queuebot:#ubuntu-release- Unapproved: apt (zesty-proposed/main) [1.4 => 1.4.2~17.04.1] (core)13:15
-queuebot:#ubuntu-release- Unapproved: apt (yakkety-proposed/main) [1.3.5 => 1.3.7] (core)13:15
-queuebot:#ubuntu-release- Unapproved: nova (yakkety-proposed/main) [2:14.0.4-0ubuntu1.2 => 2:14.0.5-0ubuntu1] (openstack, ubuntu-server)14:07
-queuebot:#ubuntu-release- Unapproved: google-perftools (yakkety-proposed/main) [2.4-0ubuntu5 => 2.4-0ubuntu5.16.10.1] (ubuntu-server)14:30
LocutusOfBorgsoooo somebody please kick boost1.61 out from Ubuntu? :)14:34
apwLocutusOfBorg, still showing up in reverse-depends14:35
LocutusOfBorgnah14:35
LocutusOfBorglocation-service is fixed and migrated one hour ago14:35
LocutusOfBorg ubuntu-location-service-bin | 3.0.0+16.10.20160912-0ubuntu3 | artful/universe  | amd64, arm64, armhf, i386, ppc64el14:36
apwand it is still showing up in reverse speends14:36
apwpresuambly because it is out of date, and one wants it to be in date14:36
LocutusOfBorga mistake in my upload or I just need to wait?14:36
LocutusOfBorgah ok :(14:37
LocutusOfBorgs/:(/:)14:37
LocutusOfBorg(dear, isn't this a fork bomb?)14:37
apwtill the location poop goes away one cannot tell what all else in there is a lie14:37
LocutusOfBorgseems legit14:37
LocutusOfBorghttp://people.canonical.com/~ubuntu-archive/transitions/html/boost1.62.html14:38
LocutusOfBorgthis page is good now14:38
LocutusOfBorgthis is why I requested it14:38
LocutusOfBorgbut I'll prod again when reverse-depends is happy14:38
apwLocutusOfBorg, right i am sure it is good, but either i have to work it out myself, or i can ignore it for an hour and let reverse-depends sort it out14:39
LocutusOfBorgI prefer the latter14:39
LocutusOfBorg:)14:39
jamespageo/14:54
jamespagethe MIR for vine is blocking quite a large number of packages in artful-proposed related to OpenStack14:54
jamespagevia http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#python-amqp14:54
jamespageif soneone in the MIR team has cycles to review that would be awesome:14:55
jamespagehttp://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#python-amqp14:55
jamespagebug 168809114:55
ubot5`bug 1688091 in vine (Ubuntu) "[MIR] vine" [Undecided,New] https://launchpad.net/bugs/168809114:55
LocutusOfBorginfinity, when you are back from VAC, something for you :) LP: #1669578 your opinion is needed :p14:57
ubot5`Launchpad bug 1669578 in screen (Ubuntu) "Get ttyname() to work properly in containers" [High,Fix committed] https://launchpad.net/bugs/166957814:57
naccslangasek: i think that's intentional, in case someone does remove php-defaults, php7.1-xml, e.g., will still satisfy php-xml depends? I'll ask ondrej though15:08
cyphermoxslangasek: fwiw, I see trusty's shim update is still in the queue for review, not even in proposed.15:30
=== didrocks1 is now known as didrocks
slangaseknacc: it may be intentional but it's still busted (and inconsistent across different modules built from php7.x)15:57
naccslangasek: ack, do you have handy an example of a binpkg that doesn't do that? the few i looked at did it like php7.1-xml15:58
slangaseknacc: uh... ok maybe they all do it but germinate walked a different path in some cases.  I was assuming the bins we did successfully demote didn't have this problem but spot check says they do also15:59
slangaseknacc: anyway, it's super confusing to have a metapackage that depends on a real package that provides the metapackage15:59
slangasekcyphermox: is the shim in trusty queue current wrt the last round of xenial+ changes?15:59
naccslangasek: yeah it's confusing, i agree :)16:00
naccslangasek: i'll work with ondrej on it in debian16:00
-queuebot:#ubuntu-release- Unapproved: accepted kexec-tools [source] (xenial-proposed) [1:2.0.10-1ubuntu2.2]16:01
LocutusOfBorgplease also review vbox* yakkety? I just setup my VM to test16:13
LocutusOfBorgqpga16:13
-queuebot:#ubuntu-release- Unapproved: accepted iproute2 [source] (xenial-proposed) [4.3.0-1ubuntu3.16.04.1]16:22
* apw looks at vbox16:23
-queuebot:#ubuntu-release- Unapproved: accepted iproute2 [source] (yakkety-proposed) [4.3.0-1ubuntu3.16.10.1]16:26
cyphermoxslangasek: as far as I know, only missing your extra apport changes.16:33
slangasekcyphermox: ok16:36
-queuebot:#ubuntu-release- Unapproved: accepted google-perftools [source] (yakkety-proposed) [2.4-0ubuntu5.16.10.1]16:40
-queuebot:#ubuntu-release- Unapproved: accepted google-perftools [source] (xenial-proposed) [2.4-0ubuntu5.16.04.1]16:41
-queuebot:#ubuntu-release- Unapproved: accepted neutron-lbaas [source] (yakkety-proposed) [2:9.0.0-0ubuntu2]16:42
-queuebot:#ubuntu-release- New binary: e-mem [amd64] (artful-proposed/universe) [0.0+20160706-1] (no packageset)17:10
-queuebot:#ubuntu-release- New binary: node-create-hash [amd64] (artful-proposed/universe) [1.1.2+20170429gitd433cd382e6-1] (no packageset)17:11
-queuebot:#ubuntu-release- New binary: node-verror [amd64] (artful-proposed/universe) [1.10.0-1] (no packageset)17:11
-queuebot:#ubuntu-release- New binary: e-mem [i386] (artful-proposed/universe) [0.0+20160706-1] (no packageset)17:13
santa_hi17:23
santa_dear release managers,17:24
santa_may I poke you about the kdepim new reviews?17:24
santa_http://gpul.grupos.udc.es/ka-iron-hand_reports/applications_archive/16.12.3_artful_retry_builds.pdf17:24
santa_↑ it would be nice if we could get this flying spaggheti monster built17:24
santa_if we need to correct something in our packaging, just let us know, so we will correct it17:25
-queuebot:#ubuntu-release- Unapproved: accepted gnome-software [source] (zesty-proposed) [3.22.7-0ubuntu3.17.04.2]17:29
jbicha^ oh, I guess that's going to clobber the other gnome-software/zesty SRU :(17:30
jbichais it too late now to promote the older verified one?17:31
jbichaslangasek: ^17:39
-queuebot:#ubuntu-release- New: accepted e-mem [amd64] (artful-proposed) [0.0+20160706-1]17:45
-queuebot:#ubuntu-release- New: accepted node-create-hash [amd64] (artful-proposed) [1.1.2+20170429gitd433cd382e6-1]17:45
-queuebot:#ubuntu-release- New: accepted e-mem [i386] (artful-proposed) [0.0+20160706-1]17:45
-queuebot:#ubuntu-release- New: accepted node-verror [amd64] (artful-proposed) [1.10.0-1]17:45
xnoxLaney, did you review that removals package list? I will start working on filing removal bugs.17:56
jbichathat's a lot of bugs…18:01
slangasekjbicha: it's technically not too late, but AIUI this is a high-priority regression for the desktop team and so I'm ok with also pushing out both SRUs on Monday-ish18:20
slangasekjbicha: (I don't really want to release an SRU on Friday, so...)18:21
jbichaok, that's fine with me18:22
-queuebot:#ubuntu-release- Unapproved: accepted keystone [source] (xenial-proposed) [2:9.3.0-0ubuntu1]18:33
-queuebot:#ubuntu-release- Unapproved: aodh (yakkety-proposed/main) [3.0.1-0ubuntu0.16.10.1 => 3.0.2-0ubuntu1] (openstack)19:05
-queuebot:#ubuntu-release- Unapproved: ceilometer (yakkety-proposed/main) [1:7.0.2-0ubuntu1 => 1:7.0.3-0ubuntu1] (openstack, ubuntu-server)19:10
-queuebot:#ubuntu-release- Unapproved: cinder (yakkety-proposed/main) [2:9.1.2-0ubuntu2 => 2:9.1.4-0ubuntu1] (openstack, ubuntu-server)19:29
-queuebot:#ubuntu-release- Unapproved: horizon (yakkety-proposed/main) [3:10.0.2-0ubuntu1 => 3:10.0.3-0ubuntu1] (openstack, ubuntu-server)19:37
-queuebot:#ubuntu-release- Unapproved: heat (yakkety-proposed/main) [1:7.0.2-0ubuntu1 => 1:7.0.3-0ubuntu1] (openstack, ubuntu-server)19:49
-queuebot:#ubuntu-release- Unapproved: neutron-fwaas (yakkety-proposed/main) [1:9.0.0-0ubuntu1 => 1:9.0.1-0ubuntu1] (openstack, ubuntu-server)19:50
-queuebot:#ubuntu-release- Unapproved: neutron (yakkety-proposed/main) [2:9.2.0-0ubuntu2 => 2:9.3.1-0ubuntu1] (openstack, ubuntu-server)20:01
-queuebot:#ubuntu-release- Unapproved: neutron-lbaas (yakkety-proposed/universe) [2:9.0.0-0ubuntu2 => 2:9.2.0-0ubuntu1] (openstack, ubuntu-server)20:20
-queuebot:#ubuntu-release- New binary: x265 [s390x] (artful-proposed/universe) [2.4-1] (kubuntu)21:07
-queuebot:#ubuntu-release- New binary: x265 [i386] (artful-proposed/universe) [2.4-1] (kubuntu)21:09
-queuebot:#ubuntu-release- New binary: x265 [arm64] (artful-proposed/universe) [2.4-1] (kubuntu)21:11
-queuebot:#ubuntu-release- New binary: x265 [ppc64el] (artful-proposed/universe) [2.4-1] (kubuntu)21:11
-queuebot:#ubuntu-release- New binary: x265 [armhf] (artful-proposed/universe) [2.4-1] (kubuntu)21:11
-queuebot:#ubuntu-release- New binary: x265 [amd64] (artful-proposed/universe) [2.4-1] (kubuntu)21:12
-queuebot:#ubuntu-release- Unapproved: cloud-initramfs-tools (trusty-proposed/main) [0.25ubuntu1.14.04.1 => 0.25ubuntu1.14.04.2] (ubuntu-server)21:25
-queuebot:#ubuntu-release- Unapproved: cloud-initramfs-tools (xenial-proposed/main) [0.27ubuntu1.3 => 0.27ubuntu1.4] (edubuntu, ubuntu-server)21:27
-queuebot:#ubuntu-release- Unapproved: cloud-initramfs-tools (yakkety-proposed/main) [0.30ubuntu1.1 => 0.30ubuntu1.2] (edubuntu, ubuntu-server)21:28

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!