[00:29] <RAOF> jamiebennett: I'm an SRU team member; if you coordinate with mwhudson about an SRU bug & upload, I'm happy to review.
[05:09] <tjaalton> infinity: I hadn't noticed you acked the lts drivers already, so I've no uploaded the last missing bit, xorg-lts-xenial..
[07:49] <infinity> tjaalton: Danke.
[07:49] <infinity> tjaalton: Is that the list bit?
[07:49] <tjaalton> last, yes
[07:51] <infinity> Err, yes.  last. :P
[07:51] <infinity> I'll review it this morning, flip the dailies over, and people can get to testing, hopefully.
[07:53] <tjaalton> there's an image building for an oem team right now, with this from the ppa
[08:04] <Laney> Ttrying nto load that site
[08:06] <Laney> argh
[08:11] <doko> python-cryptography (1.3.1-2 to 1.4-1)
[08:11] <doko> Maintainer: Tristan Seligmann
[08:11] <doko> 13 days old
[08:11] <doko> python-cryptography/amd64 unsatisfiable Depends: python-cffi-backend-api-min (<= 9729)
[08:11] <doko> python-cryptography/amd64 unsatisfiable Depends: python-cffi-backend-api-max (>= 9729)
[08:11] <doko> are we not able to handle versioned provides?
[08:14] <infinity> Possibly not.
[08:15] <doko> which package to file an issue?
[08:15] <infinity> Not sure if we have a project to track britney issues.
[08:15] <infinity> Odd are we just need to merge with Debian, unless this package is stuck there too.
[08:18] <doko> yes, migrated
[09:35] <cjwatson> infinity: should be a merge, yes
[09:35] <cjwatson> possibly a complicated one
[09:35] <cjwatson> that support was added in Debian relatively recently
[10:42] <infinity> pitti: Could you look into merging britney from Debian, so we can haz versioned provides support?
[10:42] <pitti> infinity: yeah, that's been on my list for a while; they dropped the RDEPENDS list though, I need to see whether there's a replacement (I think there is)
[10:43] <pitti> infinity: that's because of http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#python-cryptography ?
[10:44] <infinity> pitti: Yeah.
[10:44] <pitti> we have such an enormous delta, that's going to take some effort
[10:45] <pitti> maybe I should convert our bzr branch to git first, so that I can do some sensible rebasing; would you mind moving to git?
[10:45] <infinity> pitti: All for it.
[10:59] <infinity> tjaalton:
[10:59] <infinity> -Package: xserver-xorg-video-all
[10:59] <infinity> +Package: xserver-xorg-video-all-lts-xenial
[10:59] <infinity>  Architecture: any
[10:59] <infinity>  Depends:
[10:59] <infinity>   xserver-xorg-video-amdgpu [!hurd-any !kfreebsd-any !s390x],
[10:59] <infinity> - xserver-xorg-video-ati [!hurd-any !s390x],
[10:59] <infinity> - xserver-xorg-video-fbdev [!s390x],
[10:59] <infinity> + xserver-xorg-video-ati-lts-xenial [!hurd-any !s390x],
[10:59] <infinity> + xserver-xorg-video-fbdev-lts-xenial [!s390x],
[10:59] <infinity> tjaalton: What's wrong with that first depends line?
[11:00] <tjaalton> ha
[11:00] <infinity> tjaalton: input has similar issues.
[11:00] <infinity> tjaalton: For synaptics.
[11:02] <tjaalton> and can drop kbd/mouse
[11:03] <infinity> tjaalton: Drop or not, doesn't matter, since it's arch-qualified to oblivion.
[11:03] <infinity> tjaalton: Rejected for the other two issues, though.
[11:03] <tjaalton> true
[11:04] <pitti> infinity: awesome, bzr fast-export crashes on a UnicodeDecodeError *sigh*
[11:05] <infinity> pitti: Watch me be shocked.
[11:07] <tjaalton> infinity: uploaded a new one
[11:07] <infinity> tjaalton: Ta.
[11:08] <infinity> pitti: I hope your infra is happy today, I'm going to copy over a glibc to -proposed in a few minutes.
[11:08] <pitti> infinity: yes, it is
[11:08] <pitti> infinity: not for long :)
[11:08] <infinity> Heh.
[11:08] <infinity> I can upload perl and kdelibs too, if that will help?
[11:09] <pitti> infinity: please, and new pythons
[11:09]  * pitti goes to clean up the armhf runners then
[11:10] <pitti> infinity: one s390x machine is AWOL again (10.100.0.12), it would help if you could resussitate that?
[11:10] <infinity> cpaelzer: ^
[11:11] <infinity> pitti: I keep forgetting how.  I'm a bad mainframe user.
[11:11] <cpaelzer> infinity: ? ... reading
[11:12] <cpaelzer> infinity: I won't have the logins needed but you surely have - let me try to help sorting out what needs to be done :-)
[11:13] <cpaelzer> infinity: I guess you want to log into the z/VM host and "restart" it, that means knowing the disk it is bootet from and ipling from it - is that what you want to do?
[11:13] <infinity> cpaelzer: Probably? :P
[11:13] <cpaelzer> infinity: ok, let me try how far I get without asking you for passwords to foundation/LP machines
[11:13] <infinity> I thought you bounced it for pitti last time.  Maybe it was xnox.
[11:13] <pitti> yes, usually xnos, and sometimes tinoco
[11:14] <cpaelzer> they both have the logins needed for your z/VM host
[11:15] <infinity> I might.  But not sure.
[11:15] <infinity> I have a logon here for something. ;)
[11:15] <infinity> Not the right something.
[11:17] <cpaelzer> steps that have to be taken: 1. find which guest that IP belongs to - it was (?intentionally?) not added to the systemz HW doc
[11:17] <infinity> So maybe we want an xnox or tinoco.
[11:17] <cpaelzer> I guess it is LM120C (C=12)
[11:17] <cpaelzer> then log into the z/VM Host and IPL it from there - yes you want one of the two
[11:17] <cpaelzer> and you can ask them that they share the logins with me so I can help another day if you have trouble early in the day
[11:18] <cpaelzer> infinity: well if you sign it off I can ask them, but I'd need some sort of authorized ack for that request
[11:18] <cpaelzer> not to say I could shred all your disks, but at least I couldn't read them - so it's safe
[11:19] <infinity> cpaelzer: If all you ever do is handle reboot requests, I'm sure I can trust you to do that. :P
[11:19] <cpaelzer> lol
[11:21] <infinity> tjaalton: That looks more plausibly correct.
[11:23] <tjaalton> infinity: great, thx
[11:23] <infinity> pitti: I'm curious how you're killing yours.  Other than the posixtestsuite vs. kernel thing, I've not been able to kill my z/VM buildds.
[11:23] <infinity> pitti: And I sure try.
[11:24] <pitti> heh, I wish I'd know
[11:24] <pitti> as soon as it dies, I have no access to it whatsoever
[11:24] <pitti> but we did install kerneloops back then
[11:24] <infinity> And no reasonable logging to see what it was doing right before death?
[11:24] <pitti> maybe it left a pile of poo somewhere
[11:24] <pitti> well, we do have the worker logs, so we know which test ran
[11:25] <pitti> but that's not very insightful, as it happens with several different ones which also run fine at other times
[11:25] <infinity> Irksome.
[11:50] <pitti> infinity: https://git.launchpad.net/~ubuntu-release/+git/britney2-ubuntu \o/
[11:51] <pitti> (just a straight import, no rebase/merge yet -- I'll start that after lunch)
[12:04] <infinity> [ubuntu/yakkety-proposed] glibc 2.23-1ubuntu1 (Accepted)
[12:05] <infinity> pitti: ^-- Enjoy.
[12:06] <teward> would it be far-fetched to presume July 22nd is the EOL date for 15.10?
[12:07] <teward> going by 9 months' time, and the date of its initial release
[12:07] <infinity> teward: Might be a bit later than that, but ish.
[12:08] <teward> infinity: just trying to ballpark it - over on Ask Ubuntu I have a habit of trying to give 1 months notice about the EOL date :p
[12:08] <infinity> teward: I give 3 weeks.
[12:08] <infinity> For non-LTS.
[12:08] <teward> ack
[12:09] <infinity> Usually.
[12:09] <infinity> I suppose I could cut this one down a bit.
[12:09] <infinity> But I think I'll EOL on the 28th.
[12:09] <infinity> Which means an announce todayish.
[12:11]  * infinity goes copy-and-pasting.
[12:12] <teward> heh