[05:27] <Logan> queuebot appears to be sleeping
=== nudtrobert1 is now known as nudtrobert
[12:16] <rbasak> bdmurray: please could you accept juju-core 1.22.8-0ubuntu1~14.04.1 into trusty-updates? I have another upload pending but this one is clear so no reason to hold it up for the second SRU I think.
[12:16] <rbasak> bdmurray: the two bugs referred to in the report that aren't green don't actually have bug tasks against Ubuntu so I think they can be ignored.
[12:17] <rbasak> (they don't need bug tasks against Ubuntu and doesn't explicitly need SRU verification because of the MRE)
=== s8321414_ is now known as s8321414
[17:05] <rbasak> bdmurray: please could you accept juju-core 1.22.8-0ubuntu1~14.04.1 into trusty-updates? I have another upload pending but this one is clear so no reason to hold it up for the second SRU I think.
[17:05] <rbasak> bdmurray: the two bugs referred to in the report that aren't green don't actually have bug tasks against Ubuntu so I think they can be ignored.
[17:05] <rbasak> (they don't need bug tasks against Ubuntu and doesn't explicitly need SRU verification because of the MRE)
[17:06] <bdmurray> rbasak: sorry, I saw your ping earlier and I'll get to it shortly
[17:17] <teward> there's no upgrade path for LTS 14.04 -> 15.04 directly is there for those releases?
[17:21] <bdmurray> teward: there is an upgrade path
[17:21] <teward> bdmurray: 14.04 -> 14.10 -> 15.04, or is there a direct upgrade path skipping over the EOL 14.10?
[17:21] <bdmurray> teward: it skips over 14.10
[17:21] <teward> bdmurray: so 14.04 -> 15.04 directly then?
[17:22] <bdmurray> teward: yes, but I think its broken right now - bug 1497688
[17:22] <ubot2> bug 1497688 in lvm2 "dmsetup and libdevmapper1.02.1 fail to install, depend on each other" [High,Confirmed] https://launchpad.net/bugs/1497688
[17:22] <teward> bdmurray: thanks
[17:23] <bdmurray> teward: the skiping is documented in bug 1497024
[17:23] <ubot2> bug 1497024 in update-manager "release upgrades should jump over unsupported releases" [High,Fix released] https://launchpad.net/bugs/1497024
[17:23] <bdmurray> teward: and it only happen if "Prompt=normal" in /etc/update-manager/release-upgrades
[17:28] <rbasak> bdmurray: no problem, thanks.
[17:28] <teward> bdmurray: ack, thanks for the information.  Was trying to confirm that this all was the case :)
[17:30] <teward> bdmurray: is this going to be a consistent thing going forward for all releases which EOL, such that the upgrade paths will 'skip over' EOL releases?
[17:30] <teward> or is this something just for this cycle
[17:30] <teward> this previous cycle and 14.04  *
[17:31] <bdmurray> I think its something we did for Raring or Saucy and something we'll do going forward because it'll help ensure that the LTS to LTS upgrade will work.
[17:33] <wxl> hey folks can anyone tell me what's wrong with our alternate builds? looks to me like the whole thing is riddled with errors http://people.canonical.com/~ubuntu-archive/cd-build-logs/lubuntu/xenial/daily-20151029.log
[17:35] <wxl> GPG error?
[17:36] <wxl> maybe /srv/cdimage.ubuntu.com/scratch/lubuntu/xenial/daily/apt/xenial-amd64/apt/ doesn't exist?
[17:39] <wxl> no testcases for xenial for anyone either http://iso.qa.ubuntu.com/qatracker/milestones/351/builds
[17:40] <cjwatson> wxl: the problem is in fact the unprocessed python3.[45]-related entries on http://people.canonical.com/~ubuntu-archive/priority-mismatches.html
[17:41] <cjwatson> (the log is copious, but searching for "error while building official images" can help)
[17:41] <cjwatson> wxl: processing now
[17:43] <wxl> cjwatson: yeah i guess it makes sense that the error message would come right after the error. and now that i see the error, i can see that the problem is that the image was missing those packages. but the jump to the fact that it's unprocessed entries is not clear. that being said, i'm glad you're here :)
[17:47] <cjwatson> it's not a clear failure mode at all.  debootstrap gets sad when the archive overrides say that stuff is in the base system when they're not available (in context, not available due to not being in the relevant seed output)
[17:47] <cjwatson> anyway reporting it here is the right thing to do.  should be fixed after an archive cycle or two
[17:47] <wxl> k great
[17:47] <wxl> any clues on the lacking testcases then?
[17:48] <cjwatson> no, sorry
[17:48] <wxl> qa is responsible for the repo. maybe they've done messed it up :)
[17:48] <wxl> i'll check with them
[17:48] <wxl> thanks!
[18:56] <cyphermox> wxl: which missing test cases?
[20:06] <wxl> cyphermox: none anymore. qa fixed it.
[20:06] <cyphermox> ok
[20:07] <cyphermox> I still want to do some breaking of the daily builds with new installer shiny (and fix it immediately), if I can get back to this
[20:11] <Logan> stgraber: know why queuebot is missing?
[20:15] <stgraber> not sure, it thinks it's running :)
[20:15] <stgraber> anyway, just kicked it
[22:20] <Ukikie> Logan: You killed Timmy (queuebot) again!