[14:46] <sdeziel> I'd like to know why a certain package (ganeti) was not imported into 17.10 and is thus missing from 18.04.
[14:50] <cjwatson> https://launchpad.net/ubuntu/+source/ganeti   seems to be there
[14:50] <cjwatson> ah, only in -proposed
[14:51] <cjwatson> it had/has (I haven't checked whether it still does) a dependency which was broken (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865399); furthermore, its autopkgtests are broken
[14:52] <cjwatson> http://autopkgtest.ubuntu.com/packages/g/ganeti
[14:55] <sdeziel> thanks cjwatson!
[15:00] <sdeziel> cjwatson: the autopkgtests I checked all be failed because there is not enough RAM available: Not enough memory on node node1 for creating instance instance1: needed 1024 MiB, available 809 MiB
[15:01] <cjwatson> sdeziel: I haven't looked in any more detail, and won't; just telling you what I know
[15:01] <sdeziel> alright, thanks for the pointers
[15:53] <bdmurray> rlink: for what package?
[16:13] <bdmurray> rlink: Ah, I've seen your email to me now. I'll have at your request today.
[18:22] <rlink> bdmurray:  Got it.  Thanks.
[18:24] <rlink> bdmurray:  So, this doesn't look like a regression introduced by my network-manager SRU.  This is a problem in nm-connection-editor (from network-manager-gnome) that has been happening since at least October (I stopped scrolling back after that)
[18:25] <bdmurray> rlink: What was the crash again?
[18:25] <rlink> I'm guessing the error report flagged network-manager because bits of libnm show up in the stack trace?
[18:25] <rlink> https://errors.ubuntu.com/problem/bf601527363a0557bea54d20de626f6a8d74d586
[18:29] <bdmurray> rlink: Did nm-connection-editor move packages?
[18:31] <rlink> bdmurray: Not a clue.  It doesn't come from network-manager.  As far as I can tell, it comes from network-manager-gnome, whose source package is network-manager-applet
[18:32] <rlink> The above is also true at least as far back as 14.04
[18:33] <rlink> bdmurray:  Oh, found a 12.04 box.  Also true as far back as 12.04
[18:33] <bdmurray> rlink: Can you pastebin the email you got? FWIW this isn't blocking phasing anymore.
[18:35] <rlink> bdmurray: I wish I could, but I looked for it yesterday and I seem to have accidentally deleted it.
[18:38] <rlink> bdmurray: I could go pull it from tape, if you need it that badly.
[18:38] <bdmurray> rlink: I have logs from the server I can look at, thanks though.
[18:56] <rlink> bdmurray:  Oh.  The phased-update page for Xenial doesn't list network-manager any more.  It did as of late last week.
[18:58] <rlink> And it looks like it has already reached 100% phasing?
[18:59] <bdmurray> rlink: Yes, that's what I tried to say earlier.
[18:59] <rlink> Yeah, I misunderstood.  I thought you meant the block was gone, but I didn't realize the phaseing had resumed.
[19:00] <rlink> Sorry.  I stopped checking the phased-update page after a week of waiting for my error-tracker-access approval. ;-)
[19:51] <bdmurray> rlink: ah, 1.1.93 (in the release pocket for xenial) did produce the network-manager-gnome package. The error tracker doesn't deal well with packages moving about.
[19:53] <rlink> bdmurray:  Oh!  Okay, that makes sense.  Thank you for the insight!
[19:59] <slangasek> infinity, kees: do we have a TB chair for today's meeting?