[04:56] <Mirv> thanks Laney & co, good that there is a decision wrt to packagekit
[06:39] <Saviq> trainguards, can someone please retry those builds for us https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-001/+build/10582957 https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-001/+build/10583028 - it's a flaky test it seems
[06:39] <Saviq> now https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-001/+build/10583430 is something completely different - any idea where's libsystem-settings-dev gone ¿? http://pastebin.ubuntu.com/22780559/
[06:41]  * Saviq → -release
[06:41] <Saviq> oh grr, I'm already here...
[06:41] <Saviq> so yeah, @all, any idea what's happened with libsystem-settings-dev in proposed amd64? it's there for i386 http://pastebin.ubuntu.com/22780603/
[06:42] <Saviq> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-073/+build/10540325 says it should be there, so it got lost somewhere ¿?
[06:59] <Mirv> Saviq: :D retrying
[07:03] <Mirv> Saviq: the log says it's not being installed (due to something), not that it wouldn't be there. the problem is that slangasek deleted https://launchpad.net/ubuntu/yakkety/amd64/libsystemsettings-dev but did not delete https://launchpad.net/ubuntu/yakkety/amd64/libsystemsettings1 . theory is he was only supposed to remove s390x of each src:ubuntu-system-settings package, but ended up deleting
[07:03] <Mirv> libsystemsettings-dev on amd64 too
[07:06] <Saviq> Mirv, well, yeah I checked that it's not there... at least apt policy says so, any idea how to fix? do we need to reupload src:ubuntu-system-settings, or will that bring s390x back...
[07:07] <Mirv> Saviq: we'd need ubuntu-system-settings with https://code.launchpad.net/~timo-jyrinki/ubuntu-system-settings/stop_s390x_problems_depend_on_upstart/+merge/302143 added
[07:08] <Saviq> only where... https://requests.ci-train.ubuntu.com/#/tickets?active_only&search=ubuntu-system-settings
[07:09] <Saviq> biab
[07:10] <Mirv> 060 is the priority according to trello logs
[09:14] <tseliot> apw: hey, can you approve nvidia-367 in yakkety NEW, please?
[10:03] <LocutusOfBorg> cjwatson, FYI we should be good until level 10
[10:03]  * LocutusOfBorg haskell side
[10:05] <ogra_> so haskell is actually a game ! i knew it seeing all these masses of uploads every cycle !!
[10:06] <Laney> karma factory
[10:06]  * ogra_ waits to see the haskell-endboos package uploaded
[10:06] <ogra_> *endboss
[10:06] <LocutusOfBorg> lol
[10:07] <LocutusOfBorg> the princess in another castle (citation needed)
[10:07] <LocutusOfBorg> s/in/is in/
[10:08] <ginggs> transition tracker tetris
[10:24] <Mirv> seb128: Laney: so is the ETA for unlocking transition earlier end of this week? I'm pondering whether to explode potential can of GCC6 worms by a qtbase and qtdeclarative updates or whether to do this one transition first. copying those would trigger thousands of autopkgtests again.
[10:24] <Mirv> s/earlier/earliest/
[10:24] <Laney> I would wait if I were you
[10:25] <Mirv> Laney: ok then
[10:25] <Mirv> there's no hurry with those as such
[10:27] <Mirv> there may be a UITK s390x fix now happening, while leaving camitk itksnap jacktrip nifti2dicom nomacs still there (ffmpeg? webp?) plus the lubuntu-qt-desktop/muon/plasma-discover regarding pkg-kit 1.0
[10:32] <Mirv> well the landers will be in a painful situation, but the pain won't stop until the migration is done anyway
[10:33] <Laney> Mirv: If you want to do the packagekit stuff you can, btw
[10:40] <Mirv> I can do monkey work, but otherwise not familiar at all with packagekit
[10:41] <Laney> It is monkey work
[10:43] <Mirv> I see "upload click to drop the packagekit backend binary" bug #1496292 but it was unclear to me reading yesterday's discussion if that should be done or if need to wait for the Unity 8 feature first
[10:45] <Laney> Mirv: The decision was to do it, and have a gap before the new feature is ready
[10:45] <Laney> So drop that, find any reverse dependencies and mutilate those until they give in
[10:47]  * Mirv goes monkeying click, ubuntu-touch seed and unity8-desktop-session
[10:47] <cjwatson> there's an existing MP for the click stuff
[10:47] <cjwatson> please use it rather than monkeying independently
[10:47] <Mirv> ok
[10:47] <Mirv> from February, nice
[10:47] <cjwatson> (I don't like it much, but it's not wrong in itself)
[10:47] <cjwatson> https://code.launchpad.net/~unity-api-team/click/drop_packagekit/+merge/285225
[10:48] <cjwatson> my disapprove vote is "I don't like this direction", not "this patch is wrong"
[10:49]  * cjwatson links the bug
[10:50]  * Mirv did the same
[10:51] <Laney> Thanks, I was just digging that up
[10:52] <Laney> It would have been better to give it the D-Bus interface that mvo worked on. Not sure why that approach wasn't pursued, but I don't propose to re-open that discussion now. :)
[10:53] <cjwatson> That's what I wanted too, but you can see my attempt to argue that in the MP above
[10:54] <cjwatson> And I don't really get to both mostly-abandon the project and control its direction :-)
[10:57] <Mirv> https://code.launchpad.net/~timo-jyrinki/unity8-desktop-session/drop_click_packagekit_plugin/+merge/302389
[10:57] <Mirv> https://code.launchpad.net/~timo-jyrinki/ubuntu-seeds/ubuntu-touch.yakkety_drop_packagekit_plugin_click/+merge/302390
[10:57] <Mirv> the click seems to build alright
[12:44] <Mirv> so the ubuntu-system-settings wrong binaries removal is now starting to hurt, I'm trying to fastlane u-s-s rebuild into archives but without bringing the removed s390x binaries back (ie merge that one MP manually)
[14:13] <happyaron> hi, anyone can look at the SRU queue of xenial for network-manager?
[14:46] <sil2100> Laney: hey! Are you the one working on the libwebp transition? https://people.canonical.com/~ubuntu-archive/transitions/html/auto-libwebp.html
[14:47] <sil2100> Or maybe anyone else is tracking it?
[14:49] <Laney> sil2100: a bit, why?
[15:42] <sil2100> Laney: was just wondering if maybe some help is needed there
[15:43] <Laney> sil2100: There's 2 KDE/Qtish ones that are left, that I didn't touch yet until I've examined update_output.txt a little bit
[17:44] <sergiusens> slangasek hi there, can you let that guy in please? ^
[17:45] <slangasek> Mirv, Saviq: ugh; did ubuntu-system-settings get sorted already?  it is possible to recover the binaries (sorry, I thought I had ^Ced my wrong deletion in time but apparently not), if that would help
[17:45] <slangasek> sergiusens: looking
[17:47] <slangasek> sergiusens: can you confirm (on the bug) whether the packaging QA has already been done, or is yet to be done, per https://wiki.ubuntu.com/SnapcraftUpdates ?
[17:49] <sergiusens> slangasek that usually happens with the binary debs that end up built in -proposed
[17:49] <slangasek> sergiusens: ok
[17:50] <sergiusens> slangasek I ask elopio to clarify that part of the wiki
[17:50] <slangasek> sergiusens: accepted
[17:50] <sergiusens> slangasek thanks
[18:23] <Mirv> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#ubuntu-ui-toolkit would need to be run with --all-proposed to pick up a fixed unity8
[18:24] <Mirv> slangasek: yes that one is fixed
[18:24] <Mirv> same for http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#ubuntu-system-settings
[18:28] <slangasek> Mirv: ubuntu-ui-toolkit shows no blocking test failures
[18:29] <slangasek> for ubuntu-system-settings, I guess it's the unity8 tests that need rerun?
[18:30] <slangasek> (retriggered)
[18:33] <Mirv> slangasek: does not? the same unity8 tests are red for ui-toolkit too. http://people.ubuntu.com/~timo-jyrinki/uitk.png
[18:34] <Mirv> cjwatson: Laney: sil2100: it seems that the click branch https://code.launchpad.net/~unity-api-team/click/drop_packagekit/+merge/285225 was unfortunately not enough for click's own autopkgtests: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#click
[18:34] <slangasek> Mirv: ok, let me hit refresh in my browser and look again ;)
[18:34] <slangasek> Mirv: hey, lookie there. ok.
[18:35] <slangasek> Mirv: retriggered for both
[18:36] <Mirv> slangasek: ok :) thanks, --all-proposed is generally now needed since so much is in proposed. that click issue is one of the remaining blockers, although now landed it fails its own autopkgtests.
[18:46] <bdmurray> slangasek: Could you have a look at my update-manager upload in the trusty SRU queue?
[19:04] <slangasek> bdmurray: looking
[19:05] <slangasek> bdmurray: I don't understand the code change; does 'universal_newlines=True' implicitly trigger decode()?
[19:06] <slangasek> bdmurray: ok, the documentation tells me that "yes"
[19:06] <bdmurray> slangasek: yes
[19:06] <slangasek> accepted
[19:07] <coreycb> bdmurray, hello, when you have a moment can you take a look at releasing python-keystonemiddleware for xenial?  bug 1533724 has been verified.
[19:09] <bdmurray> coreycb: done
[19:09] <coreycb> bdmurray, thanks
[23:58] <mwhudson> can someone delete juju-mongodb2.6 from yakkety-proposed?
[23:58] <mwhudson> the package in release was deleted a couple of days ago
[23:59] <mwhudson> (see https://bugs.launchpad.net/ubuntu/+source/juju-mongodb2.6/+bug/1610778)