[00:01] <slangasek> infinity: so, what's the story with firefox?  currently blocked by autopkgtest failures?
[00:37] <stokachu> slangasek: i was told that the juju agent was failing to connect to mongo
[00:38] <slangasek> stokachu: seems to have resolved itself on a retry?
[00:38] <stokachu> slangasek: yea i kicked it again and mongo played nice
[00:38] <slangasek> ok
[00:38] <stokachu> slangasek: that's all the issues i know of
[00:45] <ahoneybun> heyo anyone know why this package is missing in YY archive? Package libpng12-0 is not installed.
[00:50] <tsimonq2> !info libpng
[00:50] <cyphermox> ahoneybun: it was transitioned to libpng1.6 in xenial, it seems. any package that depends on it needs to be rebuilt
[00:50] <tsimonq2> cyphermox: seems like some Kubuntu packages are affected
[00:51] <tsimonq2> ahoneybun: what is trying to install it?
[00:56] <ahoneybun> virtual box
[00:57] <ahoneybun> tsimonq2: ^
[00:57] <sarnold> this suggests it depends upon libpng16-16 http://packages.ubuntu.com/yakkety/virtualbox
[00:58] <ahoneybun> I'm grabbing it from the virtualbox website
[00:58] <ahoneybun> that's why
[00:58] <ahoneybun> they have not rebuilt it then
[00:58] <slangasek> stokachu: yeah, it's migrating now
[00:59] <ahoneybun> since the archive has 5.1.6 now I'll just grab from there for now
[00:59] <ahoneybun> thanks cyphermox and sarnold
[00:59] <stokachu> slangasek: cool thanks man
[01:00] <slangasek> ok, I've retested y-u-no-validate and confirmed that it's a real regression introduced by the new firefox
[01:00] <slangasek> whatever that does for us
[01:01] <slangasek> I'm going to go ahead and force firefox in, on the grounds that this gives us the option to remove y-u-no-validate (or leave it broken) rather than waiting further
[02:41] -queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (yakkety-proposed) [20101020ubuntu483]
[03:25] <slangasek> infinity: I've triggered a set of rebuilds; I see that d-i hasn't published quite yet so we'll still need to trigger those in a little bit
[03:29] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate amd64 [Yakkety Final] has been updated (20161012)
[03:29] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate i386 [Yakkety Final] has been updated (20161012)
[03:29] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate powerpc [Yakkety Final] has been updated (20161012)
[03:31] -queuebot:#ubuntu-release- Builds: Netboot amd64 [Yakkety Final] has been updated (20101020ubuntu483)
[03:31] -queuebot:#ubuntu-release- Builds: Netboot arm64 [Yakkety Final] has been updated (20101020ubuntu483)
[03:31] -queuebot:#ubuntu-release- Builds: Netboot armhf [Yakkety Final] has been updated (20101020ubuntu483)
[03:31] -queuebot:#ubuntu-release- Builds: Netboot i386 [Yakkety Final] has been updated (20101020ubuntu483)
[03:31] -queuebot:#ubuntu-release- Builds: Netboot powerpc [Yakkety Final] has been updated (20101020ubuntu483)
[03:31] -queuebot:#ubuntu-release- Builds: Netboot ppc64el [Yakkety Final] has been updated (20101020ubuntu483)
[03:31] -queuebot:#ubuntu-release- Builds: Netboot s390x [Yakkety Final] has been updated (20101020ubuntu483)
[03:40] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Yakkety Final] has been updated (20161012)
[03:40] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop i386 [Yakkety Final] has been updated (20161012)
[03:42] <infinity> slangasek: Then why did you do lubuntu alt? :)
[03:48] -queuebot:#ubuntu-release- Builds: Ubuntu Server amd64 [Yakkety Final] has been updated (20161012)
[03:48] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64 [Yakkety Final] has been updated (20161012)
[03:48] -queuebot:#ubuntu-release- Builds: Ubuntu Server i386 [Yakkety Final] has been updated (20161012)
[03:48] -queuebot:#ubuntu-release- Builds: Ubuntu Server powerpc [Yakkety Final] has been updated (20161012)
[03:48] -queuebot:#ubuntu-release- Builds: Ubuntu Server ppc64el [Yakkety Final] has been updated (20161012)
[03:48] -queuebot:#ubuntu-release- Builds: Ubuntu Server s390x [Yakkety Final] has been updated (20161012)
[03:59] -queuebot:#ubuntu-release- Builds: Ubuntu GNOME Desktop amd64 [Yakkety Final] has been updated (20161012)
[04:00] -queuebot:#ubuntu-release- Builds: Ubuntu GNOME Desktop i386 [Yakkety Final] has been updated (20161012)
[04:07] -queuebot:#ubuntu-release- Unapproved: budgie-wallpapers (yakkety-proposed/universe) [16.04.1.1 => 16.10] (no packageset)
[04:07] -queuebot:#ubuntu-release- Unapproved: accepted budgie-wallpapers [source] (yakkety-proposed) [16.10]
[04:13] -queuebot:#ubuntu-release- New binary: budgie-wallpapers [amd64] (yakkety-proposed/universe) [16.10] (no packageset)
[04:13] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Yakkety Final] has been updated (20161012)
[04:20] -queuebot:#ubuntu-release- New source: budgie-desktop-environment (yakkety-proposed/primary) [0.4.17]
[04:20] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Yakkety Final] has been updated (20161012)
[04:21] <slangasek> infinity: because I didn't notice it hadn't published until after I hit the button, so we get to build it again ;)
[04:21] <infinity> Fair enough.
[04:21] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop i386 [Yakkety Final] has been updated (20161012)
[04:22] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Yakkety Final] has been updated (20161012)
[04:22] <slangasek> infinity: so for firefox, the binaries were dropped for powerpc?  Was someone going to take care of making lubuntu desktop installable again?
[04:22] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop i386 [Yakkety Final] has been updated (20161012)
[04:26] <ahoneybun> ohhh the machines are turning!
[04:28] <slangasek> http://i1.kym-cdn.com/photos/images/original/000/242/631/382.gif
[04:32] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Yakkety Final] has been updated (20161012)
[04:33] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD i386 [Yakkety Final] has been updated (20161012)
[04:46] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Yakkety Final] has been updated (20161012)
[04:46] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop i386 [Yakkety Final] has been updated (20161012)
[04:46] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop powerpc [Yakkety Final] has been updated (20161012)
[05:28] -queuebot:#ubuntu-release- Unapproved: proftpd-dfsg (yakkety-proposed/universe) [1.3.5a-1build1 => 1.3.5a-1ubuntu1] (no packageset)
[05:29] -queuebot:#ubuntu-release- Unapproved: accepted proftpd-dfsg [source] (yakkety-proposed) [1.3.5a-1ubuntu1]
[05:40] -queuebot:#ubuntu-release- Unapproved: proftpd-dfsg (yakkety-proposed/universe) [1.3.5a-1ubuntu1 => 1.3.5a-1ubuntu2] (no packageset)
[05:41] -queuebot:#ubuntu-release- Unapproved: accepted proftpd-dfsg [source] (yakkety-proposed) [1.3.5a-1ubuntu2]
[05:53] -queuebot:#ubuntu-release- Unapproved: qliss3d (yakkety-proposed/universe) [1.4-2 => 1.4-2ubuntu1] (no packageset)
[05:55] -queuebot:#ubuntu-release- Unapproved: accepted qliss3d [source] (yakkety-proposed) [1.4-2ubuntu1]
[05:58] -queuebot:#ubuntu-release- Unapproved: kubuntu-meta (yakkety-proposed/universe) [1.343 => 1.344] (kubuntu)
[05:58] -queuebot:#ubuntu-release- Unapproved: ubuntu-mate-meta (yakkety-proposed/universe) [1.177 => 1.178] (ubuntu-mate)
[05:58] -queuebot:#ubuntu-release- Unapproved: ubuntustudio-meta (yakkety-proposed/universe) [0.161 => 0.162] (ubuntustudio)
[05:58] -queuebot:#ubuntu-release- Unapproved: lubuntu-meta (yakkety-proposed/universe) [0.71 => 0.72] (lubuntu)
[05:58] -queuebot:#ubuntu-release- Unapproved: ubuntu-meta (yakkety-proposed/main) [1.372 => 1.373] (core)
[05:58] -queuebot:#ubuntu-release- Unapproved: ubuntu-gnome-meta (yakkety-proposed/universe) [0.70 => 0.71] (ubuntugnome)
[05:58] -queuebot:#ubuntu-release- Unapproved: xubuntu-meta (yakkety-proposed/universe) [2.207 => 2.208] (xubuntu)
[06:08] <flocculant> infinity slangasek - hi - both the xubuntu images built according to ~ubuntu-cdimage/+livefs/ubuntu/yakkety/xubuntu, but the build logs say 32bit failed - and iso tracker agrees and only has 64bit
[06:09] <flocculant> http://people.canonical.com/~ubuntu-archive/cd-build-logs/xubuntu/yakkety/ that log ...
[06:10] <infinity> Seems to have lost its mind slightly.
[06:10] <infinity> flocculant: I'll retry it.
[06:11] <flocculant> infinity: thanks :)
[06:12] <flocculant> infinity: you expecting more rebuilds at all?
[06:12] <flocculant> not including of course any 'arrrrgh we got to rebuid :|'
[06:15] <pitti> meh, http://people.canonical.com/~ubuntu-archive/priority-mismatches.txt *still* hasn't updated since yesterday morning
[06:15]  * pitti hunts for cronjobs to run manually
[06:18] <infinity> pitti: Yeah, I noticed earlier that archive-reports seems to not be reporting.
[06:18] <infinity> And I'm afraid of what they'll say. :P
[06:19] <infinity> flocculant: Probably one last on late wed, I suspect, but please test, test, test,  so we can sort out what we need to fix. :P
[06:19] <flocculant> yea I know the drill - if only I could get more people to join in :(
[06:23] <pitti> infinity: you already have a hunch what's wrong?
[06:23] <infinity> pitti: Well, there's all those metas I uploaded ^^
[06:23] <infinity> pitti: Or if you mean archive-reports, no.  I haven't looked yet.
[06:24] <pitti> infinity: ah ok, that "I'm afraid of what they'll say" seemed to apply to archive-reports; looking now
[06:24] <infinity> pitti: Oh.  I don't know why they're failing to run.  I have a hunch that when they do run, we won't like the ouput (due to the firefox removal)
[06:24] <infinity> But we'll see.
[06:24] <infinity> And I still didn't cleam up all the prio mismatches because no report to tell me the current state of the world.
[06:25] <pitti> so http://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.yakkety/standard is updated anyway -- no perl and launchpadlib any more
[06:46] -queuebot:#ubuntu-release- New: accepted budgie-wallpapers [amd64] (yakkety-proposed) [16.10]
[06:46] -queuebot:#ubuntu-release- New: accepted openfoam [s390x] (yakkety-proposed) [4.0+dfsg1-3]
[06:46] -queuebot:#ubuntu-release- New: accepted openfoam [ppc64el] (yakkety-proposed) [4.0+dfsg1-3]
[06:47] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop i386 [Yakkety Final] has been updated (20161012.1)
[06:54] <flocculant> infinity: thanks :D
[06:57] -queuebot:#ubuntu-release- Unapproved: ubuntukylin-theme (yakkety-proposed/universe) [1.6.1.2 => 1.6.2] (ubuntukylin)
[07:03]  * infinity makes himself hotdogs for breakfast.
[07:04] -queuebot:#ubuntu-release- Unapproved: qliss3d (yakkety-proposed/universe) [1.4-2ubuntu1 => 1.4-2ubuntu2] (no packageset)
[07:06] -queuebot:#ubuntu-release- Unapproved: accepted qliss3d [source] (yakkety-proposed) [1.4-2ubuntu2]
[07:17] <pitti> infinity: breakfast? are you in London?
[07:22] <acheronuk> I think infinity decided to adopt London timezone for release week, hence late night hotdogs=breakfast?
[07:26] <pitti> ah, mirror/ubuntu-germinate is out of date
[07:28] <pitti> ah-haa! http://paste.ubuntu.com/23311716/
[07:29] <pitti> cjwatson: ^ KeyError: 'Built-Using' in germinate
[07:36] <pitti> cjwatson: trying naïve fix: http://paste.ubuntu.com/23311741/
[07:40] <infinity> pitti: It's been vomiting that Built-Using error a lot longer than the reports have been out of date, though.
[07:41] <acheronuk> so... no firefox in latest images is expected?
[07:41] <infinity> acheronuk: In which image(s)?
[07:41] <pitti> infinity: still a bit weird -- http://people.canonical.com/~ubuntu-archive/germinate-output/ubuntu.yakkety/standard is up to date, while snakefruit:mirror/ubuntu-germinate/ is not -- but update-germinate runs *on* snakefruit
[07:42] <pitti> but:
[07:42] <pitti> 1474560 Oct 11 08:48 ubuntu-germinate
[07:42] <pitti> this totally coincides with archive-reports stopping to update
[07:42] <acheronuk> infinity: the ones timestamped for 04:22 today http://cdimage.ubuntu.com/kubuntu/daily-live/20161012/
[07:42] <infinity> acheronuk: On, x86 images?  No, definitely not expected.
[07:42] <infinity> s/On/Oh/
[07:43] <pitti> but indeed, update-germinate does not touch mirror/ubunut-germinate
[07:44] <infinity> mirror is, well, a mirror.
[07:46] <infinity> pitti: ubuntu-germinate is rsynced from pepo.
[07:46]  * infinity checks the state of pepo.
[07:46] <pitti> $ rsync -aq --include germinate.output --exclude _\* --exclude \*.new --include "*_yakkety_*" --exclude \* --delete --delete-excluded ftpmaster.internal::ubuntu-germinate/ "$HOME/mirror/ubuntu-germinate" -vP
[07:47] -queuebot:#ubuntu-release- New sync: dasher (yakkety-proposed/primary) [4.11+git20130508.adc653-3]
[07:47] <LocutusOfBorg> pitti, dasher seems fixed ^^ please let it go back in yakkety
[07:47] <infinity> It's definitely been touched more recently on ftpmaster.
[07:47] <pitti> I'm just running that manually, seems that actually works
[07:47] <infinity> pitti: ...
[07:48] <pitti> mirror/ubuntu-germinate/standard_ubuntu_yakkety_amd64 is now perl-free
[07:48] <pitti> so why the heck doesn't it work from bin/archive-reports
[07:48] <infinity> I dunno.
[07:49] <infinity> And archive-reports will still perhaps fail to run now, since you updated the mirror manually, thus timestamps won't bump. :/
[07:49] <infinity> But I guess we can hack that check out for a quick by-hand run.
[07:49] <pitti> infinity: at it
[07:49] <infinity> pitti: cron it!
[07:49]  * pitti runnig with sh -x again to see what's going on (disabled in crontab)
[07:50] <pitti> heh
[07:53] <pitti> clearly a systemd bug anyway
[07:53] <infinity> How could it not be?
[07:53] <infinity> Well, that's not fair.  It could be a pulseaudio bug.
[07:53] <infinity> Mirrors pulse.
[07:53] <infinity> It adds up.
[07:53]  * pitti misses the days of "ITZ GTK BUG!"
[07:53] <infinity> Iz steel quite ooften gtk boog.
[07:53] <infinity> Though, it's much harder to figure out when to blame GTK these days.
[07:53] <pitti> particulary when most of our bits are Qt now
[07:53] <infinity> I had a GL surface rendering oddity on my laptop and realized I had literally zero idea how to go about debugging if it was kernel, drm, mesa, compiz, unity, gtk, or... something else entirely.
[07:53] <infinity> Because in our brave new world, literally everything on the screen is a textured GL surface pretending to be something else.
[07:53] <infinity> "No, really, I'm a button."
[07:55] <pitti> http://people.canonical.com/~ubuntu-archive/priority-mismatches.txt updated (manual run)
[07:55] <infinity> Ta.
[07:55] <pitti> hm, that's a bit disappointing; I was hoping some of the libs were due to perl and launchpadlib
[07:56] <pitti> http://people.canonical.com/~ubuntu-archive/architecture-mismatches.txt updated, all clear
[07:56] <infinity> Not super concerned about the libs.
[07:56] <acheronuk> infinity: I see no change in kubuntu seeds since beta2 that could boot firefox off the iso
[07:56] <infinity> acheronuk: No, but we've had some fun times with firefox today.  Will investigate.
[07:56] <pitti> infinity: python3-yaml is due to netplan, I think that's correct
[07:57] <infinity> pitti: Does netplan do python things at boot?  Can I hate you for that?
[07:57] <pitti> infinity: argh, no; it's just a tiny C thingy, taking 1 ms or so
[07:57] <infinity> pitti: Oh, phew.
[07:57] <acheronuk> infinity: ok. thank you :)
[07:57] <infinity> pitti: So just some support utility in python?
[07:57] <pitti> infinity: the python thing is the "netplan" binary, for "force-apply my changed config" (but that's run manually)
[07:57]  * infinity nods.
[07:57] <infinity> Less gross.
[07:58] <pitti> infinity: and that's also for migration from ifupdown (not enabled yet), and some heuristics later on -- really don't want to write that in C
[07:58] <infinity> Kay everything in prio-mismatches looks vaguely sane enough.
[07:58] <infinity> Pulling in all the heimdal stuff is a bit unfortunate, but looks like it was in standard anyway.
[07:58] <infinity> So meh.
[07:59] <infinity> pitti: A component-mismatches would be nice too.  That's the one I'm expecting to be ugly.
[07:59] <infinity> (because of firefox)
[07:59] <pitti> infinity: the main thing that stands out is pinentry-ncurses -- I doubt we are actually using/integrating that
[07:59] <infinity> I hope I'm wrong.
[08:00] <infinity> pitti: Hrm?  pinentry-curses is pretty much the only way to talk to gpg2 absent a GUI.
[08:00] <pitti> infinity: does gnupg call that by itself then?
[08:00] <infinity> pitti: So if gnupg2 is now important, so should pinentry-curses be.
[08:00] <infinity> It's meant to DTRT based on your environment, yeah.
[08:01] <infinity> pitti: Anyhow pinentry-curses is tiny, and the only pinentry guaranteed to work.  So, it should be there.
[08:02] <pitti> ack
[08:02] <infinity> pitti: The caveat is that you want pinentry-(fancy-gui-thing) seeded on each desktop.
[08:02] <infinity> Which I think we did a cycle or two ago?
[08:02] <pitti> yes, that exists
[08:02] <pitti> infinity: http://people.canonical.com/~ubuntu-archive/component-mismatches.txt updated; looks okay
[08:03] <infinity> pitti: Phew.
[08:03]  * pitti is getting good at playing cron monkey
[08:03] <pitti> infinity: cleaning up the main->universe stuff
[08:03] <infinity> pitti: I guess the firefox c-m issue was a build-dep, then.  So archive reorg fixed it.
[08:03] <infinity> (Used to be that if firefox didn't exist on all arches, c-m lost its mind trying to pull in other random browsers)
[08:04] <infinity> Oh, wait.
[08:04] <infinity> No.
[08:04] <infinity> I see a lynx on there. :P
[08:04] <infinity> But that's way less dire than what used to happen.
[08:05] <infinity> And if it's only libpango-doc, maybe that should just be fixed.
[08:05] <infinity> Docs depending on a web browser is rather sill.
[08:05] <infinity> y
[08:05] <pitti> golang* sounds a bit suspicious -- as if some package (lxd/juju-core) switched from "archve packages" to "bundled" again
[08:06]  * pitti leaves that for the moment, we can still do demotions tomorrow
[08:07] <infinity> Tempted to drop the www-browser dep from pango-doc.
[08:07] <pitti> infinity: can fix pango if you want, but that would require another respin
[08:07] <infinity> But I guess we can also just ignore c-m's hint to promote lynx and fix it in Y+1
[08:07] <pitti> so that's just on ppc64el now?
[08:07] <infinity> pitti: We'll almost certainly respin anyway, but I don't think rebuilding pango for that is worth it, we can just ignore c-m's hint.
[08:07] <pitti> ok
[08:07] <infinity> s/ppc64el/everywhere without firefox/
[08:09] <infinity> pitti: Actually, on second thought, sure, gimme a fixed pango.  We can shunt it to SRU/ZZ if it doesn't make a respin.
[08:09] <pitti> infinity: let me do it in Debian svn
[08:09] <pitti> (already at it)
[08:09] <infinity> WFM.
[08:09] <infinity> Docs depending on browsers is so 1996.
[08:10] <infinity> (Plus, I assume it ships something other than just HTML, which makes the dep even more bogus)
[08:10] <infinity> But maybe not.
[08:12] <pitti> no, just HTML, but devhelp/chromium etc.
[08:12] <pitti> https://anonscm.debian.org/viewvc/pkg-gnome?view=revision&revision=51383
[08:13] <pitti> backporting that to our pango now
[08:13] <pitti> (and  urgh @ svn)
[08:15] <infinity> pitti: Also not uncommon to install *doc on a web server and share /usr/share/doc
[08:16] <pitti> uploaded; so, ubuntu1 for yakkety, but package will be syncable again in z
[08:16] <infinity> Kay.
[08:16] -queuebot:#ubuntu-release- Unapproved: pango1.0 (yakkety-proposed/main) [1.40.1-1 => 1.40.1-1ubuntu1] (core)
[08:18] <infinity> The fonts-noto/fonts-droid-fallback thing isn't resolved either. :/
[08:19] -queuebot:#ubuntu-release- Unapproved: accepted pango1.0 [source] (yakkety-proposed) [1.40.1-1ubuntu1]
[08:19] <infinity> pitti: Want to "review" all my metas?
[08:19] <pitti> oh, sure
[08:20] -queuebot:#ubuntu-release- Unapproved: accepted ubuntukylin-theme [source] (yakkety-proposed) [1.6.2]
[08:20] <pitti> so with those, we can just as well land pango
[08:20] <infinity> Yeah, likely.
[08:20] -queuebot:#ubuntu-release- Unapproved: accepted kubuntu-meta [source] (yakkety-proposed) [1.344]
[08:21] -queuebot:#ubuntu-release- Unapproved: accepted lubuntu-meta [source] (yakkety-proposed) [0.72]
[08:21] <infinity> The next respin will be The Last(tm), so I want to gather up whatever reporting we can and fix as many bugs as we can in the next ~6h or so.
[08:21] <pitti> all those ubuntu-mate s390x desktop users!
[08:21] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-gnome-meta [source] (yakkety-proposed) [0.71]
[08:21] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-mate-meta [source] (yakkety-proposed) [1.178]
[08:21] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-meta [source] (yakkety-proposed) [1.373]
[08:22] <pitti> wow, this also mopped up some other recent seed changes
[08:22] <infinity> Yup.  Some flavours were slacking on meta updates, looks like.
[08:22] -queuebot:#ubuntu-release- Unapproved: accepted ubuntustudio-meta [source] (yakkety-proposed) [0.162]
[08:22] -queuebot:#ubuntu-release- Unapproved: accepted xubuntu-meta [source] (yakkety-proposed) [2.208]
[08:22] <infinity> I just did a for i in flavour update of the world.
[08:39] <pitti> https://launchpadlibrarian.net/289284437/buildlog_ubuntu-yakkety-ppc64el.pango1.0_1.40.1-1ubuntu1_BUILDING.txt.gz
[08:39] <pitti> WTF
[08:39] <pitti> /usr/include/powerpc64le-linux-gnu/bits/sigthread.h:1:7: error: stray ‘\377’ in program
[08:39] <pitti> pango FTBFS due to new kernel on ppc64el now
[08:40] <pitti> infinity: you were right with 3D textures and kernel being deeply interwoven now :(
[08:41] <apw> pitti, what did we do now ?
[08:42] <pitti> apw: the above pango1.0 failure on ppc64el
[08:42] <pitti> not sure how to work around this in the pango source, it's a recursive include of a kernel header
[08:43] <infinity> That's not just random corruption in the VM?
[08:43]  * infinity retries.
[08:43] <pitti> here's hope
[08:44] <apw> pitti, also that isn't a kernel header
[08:45] <pitti> apw: oh sorry, it's glibc
[08:45] <apw> not that that makes it any different :)
[08:45] <apw> worse if anything
[08:45] <pitti> sounded very kernel-ish
[08:45] <apw> yeah does indeed, i went and looked for it and everything
[08:45] <pitti> well, /me crosses fingers for random solar radiation bug
[08:46] <pitti> infinity: FAOD, did you process http://people.canonical.com/~ubuntu-archive/priority-mismatches.txt already or want me to?
[08:46] <infinity> pitti: No, but also no.
[08:46] <infinity> Getting there.
[08:47] <infinity> And I can't help seeing FAOD and reading FOAD.
[08:47] <infinity> And I wondered how I hurt you. :P
[08:47] <pitti> subtle spelling, big semantic difference, ouch :)
[08:50] <infinity> pitti: And retry was fine.
[08:50] <pitti> *phew*
[08:51] <pitti> apw: sorry for the adrenaline kick
[08:51] <infinity> Try not to think too hard about what this means for the packages in the archive.
[08:51] <infinity> Reproducible builds would be a lovely way to guard against random memory corruption. :/
[08:52] <pitti> I wonder if there ever was a case for a random one-bit change in openssl etc. that opened a security hole
[08:52] <infinity> It's plausible, but rather unlikely.
[08:53] <infinity> Much more common to just result in crashes (for binaries), or random garbled strings.
[08:53] <pitti> sure (that was the "don't think too hard" bit, fail..)
[08:53] <infinity> Heh.
[08:53] <infinity> BUT I SAID DON'T.
[08:59] <cjwatson> pitti: That's fast-path stuff; I think http://paste.ubuntu.com/23311990/ might be slightly better
[09:00] <cjwatson> but not going to look at it more today, I'll just leave that in my tree for when I next have time
[09:00] <pitti> cjwatson: thanks; also, while it's an actual bug it seems that's not what broke the mirroring anyway
[09:18] <jbicha> infinity: did you forget to update the seeds when you pushed the -meta updates?
[09:19] <infinity> jbicha: Eh?  meta updates pull fresh seeds from bzr.
[09:20] <jbicha> I'm confused then, because I'd expect these pages to be updated:
[09:20] <jbicha> https://code.launchpad.net/~lubuntu-dev/ubuntu-seeds
[09:20] <jbicha> https://code.launchpad.net/~ubuntu-gnome-dev/ubuntu-seeds/
[09:20] <infinity> Why?
[09:20] <infinity> meta is a product of seeds, not the other way around.
[09:20] <infinity> I didn't change seeds, I updates metas to match the seeds.
[09:21] <infinity> (or, rather, to match the intersection of seeds and the archive)
[09:21] <jbicha> oh ok
[09:24] -queuebot:#ubuntu-release- Unapproved: linbox (yakkety-proposed/universe) [1.4.2-1~build1 => 1.4.2-1] (no packageset) (sync)
[09:24] -queuebot:#ubuntu-release- Unapproved: accepted linbox [sync] (yakkety-proposed) [1.4.2-1]
[09:33] <infinity> pitti: You know what's missing with a virtual sprint?  No fridge full of free Coke.
[09:33]  * infinity might have to make a run to buy some non-free Coke.
[09:34] <pitti> infinity: and I thought it was the all-day bitching while we are locked in a small room and torture your craptop :)
[09:34] <infinity> pitti: Well, that too.
[09:34] <infinity> pitti: I miss it in general.  Definitely won't make a habit of this format of "sprinting", IMO.
[09:42] -queuebot:#ubuntu-release- New binary: linbox [amd64] (yakkety-proposed/universe) [1.4.2-1] (no packageset)
[09:46] <LocutusOfBorg> yeah it built!
[10:00] <davmor2> infinity, jibel: any idea how much longer for the ubuntu isos to build tracker still says re-building
[10:06] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-367 (yakkety-proposed/restricted) [367.57-0ubuntu1 => 367.57-0ubuntu2] (no packageset)
[10:06] -queuebot:#ubuntu-release- Unapproved: accepted nvidia-graphics-drivers-367 [source] (yakkety-proposed) [367.57-0ubuntu2]
[10:08] <infinity> davmor2: Erm, good question.
[10:09] <infinity> davmor2: They failed mysteriously.  Retrying.
[10:10] <davmor2> infinity: thanks I'll make a start on netboot they take longer anyway
[10:29] <chrisccoulson> bah, I hate thunderbird
[10:32] <davmor2> chrisccoulson: don't hold back dude tell how you really feel ;)
[10:36] <seb128> chrisccoulson, does it still segfault on yakkety?
[10:36] <chrisccoulson> seb128, yeah, it crashes in the build on armhf and arm64 and crashes at runtime on x86
[10:36] <seb128> :-/
[10:36] <chrisccoulson> this sucks
[10:37] <seb128> getting close from release
[10:37] <chrisccoulson> And yakkety has a really ancient version of thunderbird, because previous uploads never got promoted (because they fail on various architectures)
[10:43] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Yakkety Final] has been updated (20161012.1)
[10:43] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop i386 [Yakkety Final] has been updated (20161012.1)
[10:46] <infinity> chrisccoulson: Just build it with gcc-5?
[10:49] <davmor2> infinity, cyphermox, jibel: Hmm amd64 netboot mini.iso I think there might be an issue. In kvm I get a the UEFI Menu on bios hardware I get the bios menu on uefi hardware I get no boot option at all
[10:54] <chrisccoulson> infinity, i'm trying that now. the thunderbird crash appears to be https://bugzilla.mozilla.org/show_bug.cgi?id=1245783
[11:00] <Laney> pitti: you still looking into archive-reports?
[11:01] <pitti> Laney: not right now, but still on my list, yes
[11:01] <Laney> I'm going to poke quickly
[11:03] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Yakkety Final] has been updated (20161012.1)
[11:03] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop i386 [Yakkety Final] has been updated (20161012.1)
[11:03] <Laney> Oh, is it just because the release isn't changing?
[11:04] <pitti> Laney: /tmp/out is sh -x archive-report , in case that's useful
[11:04] <pitti> Laney: no, it's not
[11:04] <Laney> ok
[11:04] <pitti> Laney: mirror/ubuntu-germinate/ was definitively out of date, and a manual rsync updated it; but archive-reports doesn't
[11:08] -queuebot:#ubuntu-release- Unapproved: openfoam (yakkety-proposed/universe) [4.0+dfsg1-3 => 4.0+dfsg1-3ubuntu1] (no packageset)
[11:08] -queuebot:#ubuntu-release- Unapproved: accepted openfoam [source] (yakkety-proposed) [4.0+dfsg1-3ubuntu1]
[11:12] <acheronuk> infinity: are those meta updates going to fix? https://bugs.launchpad.net/bugs/1632616
[11:13] <infinity> acheronuk: Not sure what went wrong there.  I'm about to look into it.
[11:15] <infinity> It could have just been bad timing on STeve's part and he built the image when firefox literally didn't exist in the archive. :P
[11:16] <infinity> We'll get fresh ones out soonish and see what's what.
[11:16] <infinity> acheronuk: Are you still testing otherwise to see if there are any other bugs that can get knocked out?
[11:18] <acheronuk> infinity: I only had time to do that quick test of live session earlier. I will do more extensive testing shortly. in next hr or 2.
[11:19] <infinity> acheronuk: Kay.  I'd prefer to respin once and call it done rather than do a new image for every bugfix, so the more testing, the merrier.
[11:19] <acheronuk> infinity: ack
[11:47] <infinity> pitti: After another publisher run, priority-mismatches might end up empty.
[11:48] <infinity> Unless I can't type.
[11:48] <pitti> yay
[11:48] <infinity> Which is possible.
[11:48] <pitti> Laney, infinity: did you find out what was wrong with the mirroring? or manually ran it again?
[11:48] <infinity> Neither.
[11:48] <infinity> I thought you were abusing it.
[11:48] <Laney> I'm abusing it
[11:50] <Laney> but it just updated from a plain run, so I'm not really much wiser
[11:51] <infinity> I need to carve out time to make all that triggered from ftpmaster and throw away the terrifying timestamp-comparison stuff.
[11:52] <infinity> Next week looks good.
[11:52] <infinity> Before I forget for another six months.
[12:16] <chrisccoulson> infinity, build with gcc-5 seems to be good (it's running here ok, and the armhf build I'm running looks like it will complete successfully)
[12:24] -queuebot:#ubuntu-release- Unapproved: accepted vlan [source] (xenial-proposed) [1.9-3.2ubuntu1.16.04.1]
[12:25] -queuebot:#ubuntu-release- Unapproved: accepted vlan [source] (trusty-proposed) [1.9-3ubuntu10.1]
[12:26] -queuebot:#ubuntu-release- Unapproved: accepted vlan [source] (precise-proposed) [1.9-3ubuntu6.1]
[12:27] -queuebot:#ubuntu-release- Unapproved: accepted ansible [source] (xenial-proposed) [2.0.0.2-2ubuntu1]
[12:54] -queuebot:#ubuntu-release- Unapproved: thunderbird (yakkety-proposed/main) [1:45.3.0+build1-0ubuntu3 => 1:45.3.0+build1-0ubuntu4] (mozilla, ubuntu-desktop)
[13:42] <balloons> Laney, might you be able to look at https://bugs.launchpad.net/trusty-backports/+bug/1632496 sometime this week?
[13:57] <davmor2> infinity, cyphermox: you guys around properly now?
[13:57] <cyphermox> I've been for a while
[13:58] <cyphermox> totally failed at switching to a UK timezone for this week
[14:00] <davmor2> cyphermox: damn you ;) did you get my message earlier about netboot mini.iso
[14:00] <cyphermox> yep, was about to spin it up
[14:02] <davmor2> cyphermox: seems fine on vm with ovmf to do virtual uefi and secureboot, but on hardware from a usb pendrive it isn't showing a boot option
[14:03] -queuebot:#ubuntu-release- Unapproved: nova (yakkety-proposed/main) [2:14.0.0-0ubuntu1 => 2:14.0.1-0ubuntu1] (openstack, ubuntu-server)
[14:03] <Laney> balloons: I'll try, but release & off Friday
[14:04] <balloons> Laney, ack. If you can just put it on the list to have a look at, I'd appreciate it. I know the release is priority this week
[14:04] <Laney> pitti: I currently think archive-reports is because http://people.canonical.com/~ubuntu-archive/proposed-migration/log/xenial/2016-10-12/13:14:08.log
[14:04] <Laney> poking
[14:05] <pitti> Laney: urgh, good catch; I wasn't aware that britney blocked everything else, I thought it was all parallel
[14:06] <pitti> http://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html
[14:06] <Laney> it has some synchronisation points
[14:06] <Laney> archive-reports
[14:06] <pitti> this is one of these rare bin-only packages there (top of the list); I don't even know what they mean
[14:06] <Laney> I don't know what changed
[14:06] <Laney> the build in question happened ages ago
[14:07] <pitti> britney changed yesterday
[14:08] <Laney> you rebased it?
[14:08] <pitti> yes, I did
[14:08] <pitti> I tested it against yakkety, but not xenial
[14:08] <Laney> brave
[14:09] <pitti> looking into what changed there
[14:10] <Laney> sources['testing']['kicad'] == sources['unstable']['kicad']
[14:10] <Laney> it thinks there's an arm64 binary for it in testing
[14:10] <Laney> which is lies
[14:10] <pitti>  kicad        | 4.0.2+dfsg1-4 | xenial/universe          | source, amd64, armhf, i386, powerpc, ppc64el
[14:10] <pitti>  kicad        | 4.0.2+dfsg1-4 | xenial-proposed/universe | arm64
[14:10] <pitti> wow, this looks really curious
[14:10] <Laney> it managed to build after the release
[14:11] <pitti> so that's what these three binary-only things mean on excuses.html
[14:11] <Laney> some aliasing problem in britney I think
[14:11] <pitti> should we just remove these three binaries?
[14:11] <Laney> bet it got added to one of them and then the other by reference
[14:12] <pitti> yes, that rings a bell
[14:12] <pitti> I simplified merge_sources()/merge_binaries() a bit, as it didn't occur to me that this case could even happen
[14:12] <pitti>  prometheus | 0.16.2+ds-1ubuntu1 | xenial-proposed/universe | ppc64el, s390x
[14:12] <pitti>  kicad        | 4.0.2+dfsg1-4 | xenial-proposed/universe | arm64
[14:13] <pitti> so I'd remove these three binaries from xenial-proposed
[14:13] <Laney> leave them for now so we can fix this bug
[14:13] <pitti> what would be the fix? print an error message and ignore the package?
[14:14] <Laney> it definitely shouldn't say that testing contains the binary
[14:14] <Laney> see what happens after fixing that
[14:14] <ogra_> just convert it to snap during import ;)
[14:15] <Laney> we can have this in devel legitimitely, and britney should copy the binary then
[14:15] <pitti> Laney: does it say that? I thought KeyError in binaries_t would exactly say that testing does not have it?
[14:15] <stokachu> when altering ForceObsoletes in the upgrader package; can set <package>:<arch> to specify only that arch be obsolete?
[14:16] <stokachu> pitti: cjwatson ^ do you know?
[14:16] <pitti> stokachu: sorry, no clue
[14:16] <stokachu> sorry thats in ubuntu-release-upgrader
[14:16] <stokachu> pitti: ok np
[14:17] <stokachu> slangasek: do you know if ^ is possible?
[14:17] <Laney> pitti: binaries_t['arm64'][0] doesn't have kicad but sources_t['testing']['kicad'] does have kicad/arm64
[14:17] <Laney> where binaries_t is self.binaries['testing']
[14:17] <pitti> Laney: ack, then I think I know what to fix -- merge_sources() needs to copy the SourcePackage objects, not just ref them
[14:18] <pitti> merge_binaries() didn't (conceptually) change
[14:21] <cyphermox> davmor2: I concur, not booting the USB.
[14:21] <Laney> pitti: that looks plausible
[14:21]  * pitti writes a test case
[14:22] <davmor2> cyphermox: but on vm it does which is weird cause it displays the uefi monochrome menu and not the aubergine bios one
[14:22] <Laney> I'll put archive-reports back on
[14:22] <Laney> update the copy on snakefruit and there should be a run before very long
[14:22] <davmor2> cyphermox: so no idea what is going on with that
[14:22] <cyphermox> well, depends how your VM is setup I suppose
[14:24] <cyphermox> davmor2: in a VM it works fine for me.
[14:24]  * cyphermox writes the same image to another USB
[14:24] <pitti> Laney: reproduced
[14:25] <davmor2> cyphermox: yeah that's what I say it works on vm just not on hardware
[14:27] <davmor2> cyphermox: does it matter where on the disk the uefi partition is? I think iirc on the default image it is the first partition and on the mini.iso it is the second just flashing an image to confirm that though
[14:27]  * Laney accepts thunderbird
[14:28] <Laney> Would be quite nice to have a non ancient one on the images
[14:28] <davmor2> Laney: but why when there is a claws-mail snap ;)
[14:28] <Laney> well, *I'm* fine - mutt has always worked :P
[14:28] -queuebot:#ubuntu-release- Unapproved: accepted thunderbird [source] (yakkety-proposed) [1:45.3.0+build1-0ubuntu4]
[14:29] <davmor2> Laney: hahaha
[14:29] <Laney> actually it made me rewrite part of my configuration a few weeks ago
[14:29]  * Laney fnar
[14:29] <seb128> was there a reason to not accept libreoffice?
[14:29] <ogra_> it is packaged by a grumpy hamburgian ?
[14:30] <Laney> not that I know of now that the block is in place - I'm looking at it atm
[14:30] <seb128> thanks
[14:30] <Laney> eww
[14:30] <seb128> hackish?
[14:30] <Laney> static bool isUbuntuTheme
[14:30] <davmor2> cyphermox: it's a weird one right
[14:30] <seb128> yeah :-/
[14:33] <infinity> davmor2: Is that a regression?  I have several laptops here where booting EFI from USB requires the BIOS to be in a very specific and non-intuitive setup.
[14:33] <infinity> davmor2: Otherwise, I get variations of "boots the MBR instead", "boots nothing at all", or "forces me to select the bootloader manually".
[14:35] <pitti> Laney: fix pushed: https://git.launchpad.net/~ubuntu-release/britney/+git/britney2-ubuntu/commit/?id=eac1bf30a
[14:35] <pitti> Laney: thanks for spotting!
[14:35] <davmor2> infinity: you can't select anything at all there is nothing shown in the settings if you try and add an entry point
[14:35] <pitti> Laney: so we'll wait until http://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html updated, and then remove the renegade binaries
[14:36] <Laney> pitti: nod, thanks for fixing
[14:36] <Laney> I guess there's not much point in those binaries, it's not like they can go to release
[14:37]  * Laney inserts fingers in ears and accepts LO
[14:39] -queuebot:#ubuntu-release- Unapproved: accepted libreoffice [source] (yakkety-proposed) [1:5.2.2-0ubuntu2]
[14:39] <jbicha> are we ok with other yakkety sru uploads or would it be better if I wait until tomorrow?
[14:41] <infinity> jbicha: If it's clearly an SRU with paperwork to match, etc, it's fine to upload it now, but do make sure people know what's up.
[14:41] <infinity> jbicha: OTOH, doesn't hurt to hold off a day or two. :P
[14:42] <cyphermox> infinity: seems like a regression to me, booting to EFI from USB is something I do often on my X230 ;)
[14:42] <stokachu> infinity: are you familiar with a way to make sure a dropped 32bit arch for a package gets removed during a release upgrade?
[14:43] <pitti> Laney: LibO and tbird are SRUs at this point, right?
[14:43] <Laney> pitti: Either way
[14:43] <pitti> Laney: britney finished for xenial; no crash, excuses updated
[14:43] <Laney> If there's a chance, whack them in - otherwise don't
[14:44]  * cyphermox tries the previous d-i
[14:45] <pitti> ... and renegade xenial-proposed binaries zapped
[14:45] <Laney> wee
[14:45] <Laney> what of the nova in the queue?
[14:45] <infinity> cyphermox: Ahh, I missed the bit where you reproduced.
[14:46] <cyphermox> I hadn't used a mini.iso to boot to USB though
[14:46] <cyphermox> it's reproducible with 483 and 482 :/
[14:46] <infinity> 483 and 482 are identical, save an arm64 change, so that makes sense.
[14:46] <Laney> no bug ref, but only seeded in supported
[14:46] <davmor2> cyphermox: so not new but very annoying
[14:46] <Laney> OTOH it could go south in autopkgtest
[14:47] <cyphermox> infinity: the point was to make sure the grub change really didn't have an impact.
[14:47] <infinity> stokachu: Yes, provide an empty package. :P
[14:47] <infinity> stokachu: There's no way to make people remove packages, no.
[14:47] <Laney> Someone else decide. Food time here.
[14:47] <stokachu> infinity: ok works for me
[14:48] <infinity> cyphermox: It was pretty isolated.
[14:48] <infinity> cyphermox: Anyhow, try xenial?
[14:48] <cyphermox> yeah, that's next.
[14:51] <cyphermox> otoh the mini.isos are meant to be *isos* and probably don't carry the extra magic for booting from USB in EFI if they're just plainly dd'ed to a usb key.
[14:51] <cyphermox> xenial not worky.
[14:54] <infinity> Right.  That's what I thought.
[14:54] <infinity> Not a regression.
[14:54] <ginggs> would someone remove starpu-contrib 1.2.0~rc2+dfsg-2 please? it is stuck dep-wait.  I want to upload 1.1.5-0ubuntu7
[14:59] <davmor2> cyphermox, infinity: yay! is it something I should file as a bug so it is fixed in the future?
[14:59] <infinity> ginggs: Where's libcnf-dev meant to come from?
[14:59] <infinity> davmor2: Nah.
[14:59] <infinity> davmor2: We have a handle on what needs doing, it's more about time than bugs.
[14:59] <ginggs> infinity: it is not actually used
[14:59] <davmor2> infinity: no worries
[14:59] <infinity> ginggs: If it's not, then why not just fix 1.2.0 instead of reverting?
[15:00] <cyphermox> infinity: do you still need access to this ppc box?
[15:00] <ginggs> infinity: see http://metadata.ftp-master.debian.org/changelogs/contrib/s/starpu-contrib/unstable_changelog entry for 1.1.4+dfsg-6
[15:01] <infinity> ginggs: For 1.1.4, sure.  If that's also true for 1.2.0, then...?
[15:02] <infinity> ginggs: But I can do the removal instead.  Not picky.  Just curious.
[15:02] <ginggs> infinity: 1.2.0 is still in NEW
[15:03] <ginggs> infinity: i'd be more comfortable with our 1.1.5 at this stage
[15:03] <infinity> ginggs: Fair.  Removing.
[15:03] <ginggs> infinity: thanks!
[15:03] <infinity> ginggs: Done.
[15:07] <infinity> pitti: So, I think we're approaching another "unblock stuff, migrate world, respin world" breakpoint.
[15:07] <infinity> pitti: Except I'm not sure what to do about thunderbird and its long build time.
[15:12] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-367 (yakkety-proposed/restricted) [367.57-0ubuntu2 => 367.57-0ubuntu3] (no packageset)
[15:13] <pitti> http://people.canonical.com/~ubuntu-archive/priority-mismatches.txt
[15:13] <pitti> infinity: ^ looks reasonable?
[15:13] -queuebot:#ubuntu-release- Unapproved: accepted nvidia-graphics-drivers-367 [source] (yakkety-proposed) [367.57-0ubuntu3]
[15:13] <pitti> these all seem ppc64el specific binaries
[15:14] <pitti> "to be"
[15:14] <infinity> Uhh.
[15:14] <infinity> They shouldn't be.
[15:14] <infinity> Did someone much up.
[15:14] <infinity> s/much/muck/
[15:15] <pitti>  servicelog | 1.1.14-1 | yakkety | source, powerpc, ppc64el
[15:15]  * infinity looks.
[15:15] <pitti>  lsvpd | 1.7.7-1ubuntu1 | yakkety | source, powerpc, ppc64el
[15:15] <infinity> I suspect Steve didn't do as I asked and seed them on both arches. :P
[15:15]  * pitti sighs at lynx in http://people.canonical.com/~ubuntu-archive/component-mismatches.txt -- still out of date mirror?
[15:16] <infinity> Oh, or he can't spell. ;)
[15:16] <infinity>  * ppc64-diag [powerc ppc64el]  # LP: #1417608
[15:16] <infinity> Lolz.
[15:16] <pitti> argh, no, http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#pango1.0 -- looking
[15:16] <pitti> infinity: :)
[15:16] <infinity> pitti: Okay, the ppc stuff should be fixed.
[15:16] <infinity> pitti: pango needs to migrate to remove lynx.
[15:17] <pitti> yep, just saw; at it
[15:17] <infinity> Laney: Can you subscribe the desktop team to fonts-android and fonts-noto?
[15:17] <infinity> Laney: Or whoever is the right team, make them do it.
[15:17] <infinity> Laney: Cause I'm promoting them.
[15:17]  * pitti ponders -- wait for LibO test -- force -- wait for LibO test -- force ..
[15:17] <infinity> pitti: Force.
[15:17] <infinity> pitti: The LibO tests are sketchy anyway.  Assuming some other tests look good, you're good.
[15:19]  * pitti tosses britney a note to pretty please let it in
[15:19] <pitti> infinity: are you unblocking *-mate?
[15:20] <infinity> pitti: *meta?
[15:20] <infinity> And yes, I will.
[15:20] <pitti> infinity: yes, in particular mate-meta :)
[15:20]  * pitti clearly needs caffeine, grabbing a mate tea
[15:21] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (xenial-proposed) [1:20161011.1-0ubuntu0.16.04.1]
[15:21] <infinity> pitti: Yeah, I'm about to do a coffee run here too.
[15:21] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (precise-proposed) [1:20161011.1-0ubuntu0.12.04.1]
[15:22] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (trusty-proposed) [1:20161011.1-0ubuntu0.14.04.1]
[15:23] <infinity> pitti: What's the deal with this golang-go stuff that wants to move to main?  It doesn't show up on the svg.  Does that mean it's explicitly seeded?
[15:23] <infinity> Or something...
[15:23] <pitti> infinity: you mean "to universe"
[15:23] <infinity> Hrm.
[15:23] <infinity> pitti: No.
[15:23] <infinity> I mean to main.
[15:23] <pitti> oh, these two -- no idea
[15:23] <infinity> Oh.
[15:23] <pitti> I'm also suspicious about the main → universe stuff -- that smells like something switched back from using shared libs to internal copies
[15:23] <infinity> I bet those are source renames.
[15:24] <infinity> Or maybe not.
[15:24] <pitti> where "something" is most likely amongst {juju,snapd,lxd}
[15:25] <infinity> Yeah.  Complete loss as to where golang-go* in u->m is coming from.
[15:25] <infinity> I guess I need to grep the germinate output and make my eyes bleed.
[15:26] <infinity> Could be a built-using thing, and the svg version doesn't know how to show those?
[15:26] <slangasek> pitti: the package that switched from archive packages to bundled was snapd; we're going to need to do this anyway for trusty so it doesn't significantly impact the security support story, those can probably just be demoted now
[15:26] <infinity> slangasek: Any idea about the golang* stuff moving the other direction?
[15:26] <pitti> hm, so why are we doing that shared lib thing then?
[15:27] <tsimonq2> Attention release team: https://lists.ubuntu.com/archives/lubuntu-devel/2016-October/000867.html
[15:27] <slangasek> infinity: no, I haven't traced it yet.  maybe xnox can patch things for us to give us a better explanation than 'rescued from'
[15:27] <infinity> tsimonq2: That's because slangasek jumped the gun on building your alternate, I suspect.  A rebuild will fix it.
[15:28] <jdstrand> pitti: chrisccoulson mentioned a procedural question regarding flash updates yesterday. for the future, these are simple security updates that he owns and the only reason an archive admin is involved is because of a limitation in LP where he needs us
[15:28] <infinity> slangasek: A little grep-dctrl or grepping of germinate-output will probably make it obvious.  I'll look after I get back from buying a giant coffee and a slightly less giant doughnut.
[15:29] <jdstrand> pitti: as such, all I do is make sure he uploaded to the right release when accepting from unapproved, then I follow:
[15:29] <jdstrand> https://wiki.ubuntu.com/ArchiveAdministration#Handling_updates_to_partner
[15:29] <tsimonq2> thank you infinity
[15:29] <jdstrand> pitti: and hello btw :)
[15:29] <pitti> hey jdstrand!
[15:30] <jdstrand> I'm happy to continue to be the go to person for those (I just happened to be off yesterday)
[15:33] <slangasek> infinity: amusingly, golang-gocheck is brought in by ubuntu-push, which was also what was pulling in the *previous* batch that we asked them to drop instead of MIRing
[15:34] <xnox> slangasek, golang-ubuntu-push-dev wants golang-go-xdg, but you found it too already. I'm slow =)
[15:35] <slangasek> xnox: yes; I don't want you to look at Packages files for me, I want you to fix it so c-m reports it for me and I don't have to look elsewhere ;)
[15:35]  * xnox ponders how to find all of that in the archive report.
[15:35]  * xnox ponders to write dctrl-grep query for those, nothing better like multi-pass post processing =)
[15:39] -queuebot:#ubuntu-release- Unapproved: xfsprogs (yakkety-proposed/main) [4.3.0+nmu1ubuntu3 => 4.3.0+nmu1ubuntu4] (core)
[15:39] <apw> ^ infinity that is the xfsprogs upload i mentioned, this should unblock the rdeps
[15:40] -queuebot:#ubuntu-release- New binary: openfoam [amd64] (yakkety-proposed/universe) [4.0+dfsg1-3ubuntu1] (no packageset)
[15:42] <bregma> hey archive admins, would it be possible to have Mir-0.24.1 copied from yakkety overlay PPA to the Ubuntu archives? evidently it missed landing in the yakkety archives proper because of the ongoing QA backlog, but it has some bugfixes for the Unity 8 desktop session
[15:43] <infinity> bregma: Nope.
[15:43] <slangasek> stokachu: I think none of us have looked at the ubuntu-release-upgrader code in years; sorry, I knew to point you in that direction because we used to use it a lot, but we haven't in a while and you'll have to look at the code and see what works or not
[15:44] <infinity> bregma: (a) copying from an overlay to the archive is almost certainly wrong, (b) if it doesn't affect the images and live session, it can be an SRU.
[15:44] <stokachu> slangasek: np, we determined that you can't just set juju:i386 in ForcedObsolete
[15:44] <slangasek> ok
[15:44] <stokachu> slangasek: so we'd still require a dummy package
[15:44] <infinity> stokachu: You can obsolete in release-upgrader, but that does nothing for people upgrading without it.
[15:45] <infinity> Upgrade quirks should be a last resort, not an excuse for not fixing the packages to upgrade properly, IMO.
[15:45] <slangasek> well, we need a dummy package in xenial because it's obsoleted in that release and ubuntu-release-upgrader code only triggers on upgrades between releases
[15:46] <stokachu> so we could ForcedObsolete=juju-32bit-package and that would take care of that scenario?
[15:46] <stokachu> think they called the dummy package juju-32bit-unsupported
[15:47] <slangasek> davmor2: why are you testing the mini.iso?  We don't even have test cases for that on the iso tracker
[15:47] <cyphermox> well that's why I suggested putting the debconf prompt in juju, and let it Conflict: juju-2.0 [armhf i386 powerpc] ?
[15:47] <cyphermox> stokachu: ^
[15:47] <davmor2> slangasek: netboot install uses mini.iso
[15:47] <stokachu> cyphermox: i never saw that
[15:47] <cyphermox> that way you prompt, and don't need the transitional package
[15:47] <cyphermox> that may not work though
[15:48] <stokachu> cyphermox: that also doesn't solve the issue between release upgrades
[15:48] <cyphermox> well, it means you won't have juju-2.0.
[15:48] <infinity> stokachu: I'm confused about why this is a difficult problem to solve...
[15:49] <jderose> pitti: if systemd "fails to deactivate swap" when trying to reboot after installing from the yakkety desktop ISO, could that make the reboot hang? https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1632767
[15:49] <cyphermox> what problem are you referring to then?
[15:49] <infinity> stokachu: You switched juju from arch:all to arch:(list).  juju should continue to exist on all arches, but be empty on some.
[15:50] <stokachu> what happens during a release upgrade from juju arch:all to arch:(list)?
[15:50] <stokachu> does that matter?
[15:50] <slangasek> stokachu: nack on adding extra dummy packages just to be able to use ForcedObsolete.  The dummy package should be juju-2.0, which on upgrade should tell the user it's been neutered.
[15:50] <slangasek> davmor2: no, netboot uses *netboot*
[15:51] <infinity> stokachu: The archiness of the package matters not on upgrade.
[15:51] <slangasek> davmor2: if you're testing the netboot test cases with the mini.iso, that's completely beside the point
[15:51] <stokachu> slangasek: so im trying to understand what you meant when you said add juju to the obsoletes list?
[15:51] <slangasek> and if the iso tracker test cases don't make this clear, we need to fix this
[15:51] <xnox> a way to test netboot is with libvirt tftp provider and the netboot files.
[15:51] <slangasek> stokachu: I meant for you to do what you tried to do and found it didn't work because arch-specific
[15:51] <stokachu> slangasek: ah
[15:52] <stokachu> so for xenial then we just change the arch and put a debconf template on juju-2.0?
[15:52] <cyphermox> yes
[15:52] <davmor2> slangasek: http://iso.qa.ubuntu.com/qatracker/milestones/368/builds/133152/downloads check the iso to download this has been the way netboot has been tested for as long as I can remember
[15:52] <cyphermox> stokachu: debconf should only prompt for 32-bit arches though
[15:53] <stokachu> cyphermox: ah, .. so how do you do that? :)
[15:53] <slangasek> davmor2: wow, ok.  that's completely wrong then and we should really stop having you waste your time doing that, because it does not actually test the netboot image
[15:53] <davmor2> slangasek: that or rename it
[15:55] <slangasek> davmor2: I suspect the problem here is that none of us who were actually testing these things before were looking at the download link :/
[15:55] <cyphermox> stokachu: test for the architecture in debian/config; where you do the db_input.
[15:55] <davmor2> slangasek: I was testing it in 6.10 that way
[15:55] <slangasek> heh
[15:56] <davmor2> slangasek: that what I say as long as I can remember it has been using mini.iso
[15:56] <slangasek> davmor2: then I guess we've never tested the netboot images, and no one noticed any problems, so we can just stop testing them ;P
[15:57] <davmor2> slangasek: it was my understanding that it used the same tools just pointing that the main archive for packages rather than a local network but I could be completely wrong
[15:57] <cyphermox> stokachu: e.g. using dpkg --print-architecture; such as it's done by cups.config (check your /var/lib/dpkg/info/cups.config)
[15:58] <stokachu> cyphermox: thanks relaying that now
[15:58] <slangasek> davmor2: the whole point of a netboot test case should be to test that you can actually netboot
[15:59] -queuebot:#ubuntu-release- Unapproved: mate-optimus (yakkety-proposed/universe) [16.10.0-1 => 16.10.1-0ubuntu1] (ubuntu-mate)
[16:00] <stokachu> cyphermox: slangasek thanks
[16:00] <stokachu> infinity: you to fine sir
[16:01] <philroche> infinity, cpc question: Are you expecting any further changes to the packages we care about or are we in a position to build a release candidate for cloud images?
[16:02] <davmor2> slangasek: let me have a play and see what I can cook up the fact that mini.iso is in the netboot infrastructure kinda make its seem like it is the thing that should be tested on the iso tracker :)
[16:02] <infinity> philroche: Depends on which packages you care about.
[16:04] <slangasek> davmor2: the mini.iso is entirely a byproduct of the netboot image build, both come out of the debian-installer package and we've left mini.iso around because it can be useful in some cases
[16:04] <tsimonq2> So now hardinfo is no longer FTBFS but doesn't work.
[16:05] <tsimonq2> (reportedly)
[16:05] <davmor2> slangasek: right okay
[16:05] <cyphermox> tsimonq2: yep.
[16:05] <philroche> infinity, server seed essentially. I only see firefox and libreoffice being respun. anything else?
[16:05] <tsimonq2> Fun...
[16:05] <slangasek> philroche: infinity and I were just talking about the xfsprogs upload
[16:05] <slangasek> which I'm not sure fixes anything we should hold up images for, vs. redirecting this to SRU
[16:05] <tsimonq2> cyphermox: Can you please give me a hand? I'm at school...
[16:06] -queuebot:#ubuntu-release- Unapproved: accepted xfsprogs [source] (yakkety-proposed) [4.3.0+nmu1ubuntu4]
[16:06] -queuebot:#ubuntu-release- Unapproved: accepted nova [source] (yakkety-proposed) [2:14.0.1-0ubuntu1]
[16:06] <philroche> slangasek, Thank you.
[16:07] <cyphermox> tsimonq2: I will drive-by fix it later after I have a successful powerpc install here.
[16:08] <tsimonq2> Thank you cyphermox
[16:09] <tsimonq2> cyphermox: Please keep wxl in the loop as well.
[16:10] <tsimonq2> He's in a morning meeting for another hour but he's technically the release manager. :P
[16:12] <sewaddle> slangasek: and infinity - how are things looking for timings tomorrow.... still UK afternoon?
[16:13] <infinity> sewaddle: That's my plan.
[16:14] <Laney> infinity: MaaaaaaaaaaaaaAAAaaaaaaaaaaaaaAAAaaaaAAaaaaaaaaaaaybe; what pulls them in?
[16:15] <infinity> Laney: ghostscript
[16:15] <sewaddle> infinity: any more detail than that? time-wise?
[16:15] <infinity> sewaddle: Not a precise time, no.
[16:15] <infinity> sewaddle: I barely manage that when we're in the same room an hour before release. :P
[16:15] <sewaddle> infinity: fair enough
[16:21] <pitti> jderose: hm, I did three OVMF.fd (i. e. EFI bios) installs today, reboot worked; I'll have a closer look tomorrow
[16:22] <jderose> pitti: i'll look more too. the only other "weird" thing i did was an oem install (under qemu, not on hardware)... so maybe it's something with the oem paths
[16:23] <pitti> jderose: oh -- I think I actually tested manual partitioning without swap; will re-try with swap them
[16:23] <pitti> then
[16:23] <pitti> but, dinner/basketball/sleep time, so good night everyone!
[16:24] <pitti> infinity: nice job on http://people.canonical.com/~ubuntu-archive/priority-mismatches.txt
[16:26] <jderose> infinity: so do you expect 20161012.1 to be the final ISO?
[16:26] <jderose> pitti: actually, it just worked for me under QEMU in BIOS mode... so doesn't seem to fail every time, just some times
[16:28] <infinity> jderose: Is that the one that doesn't exist yet?  If so, yeah.  All signs point to "it better be, or else".
[16:28] <wxl> got out of the meeting early. are respins in process or what's the plan?
[16:28] <jderose> infinity: er, 20161012.1/  doesn't exist yet?
[16:28] <infinity> jderose: If it exists, then no.  The next one. :P
[16:29]  * infinity isn't paying attention to serials.
[16:29] <jderose> infinity: okay, gotcha :)
[16:34] -queuebot:#ubuntu-release- Unapproved: ubuntukylin-meta (yakkety-proposed/universe) [0.16 => 0.17] (ubuntukylin)
[16:34] <infinity> slangasek: ^-- Missed a meta in my napalm run.
[16:34] <slangasek> infinity: are you asking for review or are you self-accepting?
[16:34] <infinity> slangasek: The former, though I could do the latter.
[16:35] <slangasek> infinity: ok, looking
[16:39] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Yakkety Final] has been updated (20161012.2)
[16:39] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop i386 [Yakkety Final] has been updated (20161012.2)
[16:39] <infinity> flexiondotorg: That mate-optimus, SRU or meant for your final image?
[16:49] <flexiondotorg> SRU is fine.
[16:49] -queuebot:#ubuntu-release- Unapproved: webkit2gtk (yakkety-proposed/main) [2.14.0-1 => 2.14.1-0ubuntu1] (kubuntu, ubuntu-desktop)
[16:49] <infinity> flexiondotorg: Kay.  You're getting new images shortly, whether you want 'em or not, but that upload would delay you by another hour or so, hence the question.
[16:49] -queuebot:#ubuntu-release- Unapproved: initramfs-tools (yakkety-proposed/main) [0.125ubuntu5 => 0.125ubuntu6] (core)
[16:49] <jbicha> webkit ^ is obviously just for sru, thanks
[16:50] <flexiondotorg> infinity, Thanks for the consideration :-)
[16:50] <flexiondotorg> But the crash only presents once nvidia proprietary drivers are install on hybrid graphics systems.
[16:50] <flexiondotorg> So not being in the iso is fine.
[16:51] -queuebot:#ubuntu-release- Unapproved: initramfs-tools (xenial-proposed/main) [0.122ubuntu8.3 => 0.122ubuntu8.4] (core)
[16:52] <jbicha> infinity: whats't the respin for?
[16:53] <infinity> jbicha: Cleaning up metas, fixing broken images in some cases where the mirror was out of sync, etc.  Mostly minor things (well, major in the case of flavors that didn't have a web browser...)
[16:53] <infinity> Evidently, people like web browsers.
[16:53] <jbicha> because Ubuntu GNOME's isos were fine and we only ship i386 and amd64
[16:54] <jderose> infinity: nah, the web is a fad, no need for a browser :p
[16:55] <slangasek> infinity: ubuntukylin-meta accepted - sorry for the delay
[16:55] <infinity> jbicha: The meta still needed updating for archive consistency reasons.  Also, pango got an update, which affects every desktop image.
[16:55] <infinity> jbicha: But if you're happy with the current images, zsyncing the new ones and applying light spot-checking is more than enough.
[16:55] <jbicha> ok
[16:55] -queuebot:#ubuntu-release- Unapproved: accepted ubuntukylin-meta [source] (yakkety-proposed) [0.17]
[16:56] <infinity> jbicha: ie, boot, install, reboot, was anything pink that shouldn't be, was everything pink that should be, yay.
[16:56] <slangasek> infinity: archive consistency> is that just consistency between the seed and the metapackage?  Or is it because the metapackage is built on all archs?
[16:56] <infinity> (pick a random colour, I always seem to use "pink" because I dislike it)
[16:56] <infinity> slangasek: The latter.
[16:56] <slangasek> right
[16:57]  * Laney orders thunderbird to hurry up :P
[16:57] <slangasek> jbicha: so if you don't /support/ ubuntu-gnome on !x86, you can declare that in your metapackage source
[16:57] <slangasek> otherwise, the packages need to be consistent
[16:57] <infinity> (I'd not recommend doing that today :P)
[16:57] <slangasek> indeed
[16:58] <infinity> Laney: I'm not liking its odds.
[16:58] <jbicha> well we did remove s390x because that architecture didn't seem worth it for gnome
[16:58] <Laney> It's dpkg-debbing
[16:58] <infinity> Oh, so it is.
[16:58] <infinity> Does it have any tests to speak of, or will it sail right in?
[16:59] <infinity> (Neither of those is a good answer right now, sadly)
[16:59] <infinity> One means it'll take too long, the other means it won't be tested. :P
[16:59] <infinity> But "it doesn't work at all right now" is a situation that can only improve, right?
[16:59] <slangasek> jbicha: so by removing that architecture and not the others, you get to own the cost of inconsistencies on the other architectures requiring reuploads, even if you don't build images for those archs
[16:59] <Laney> Looks like it triggers atk1.0
[16:59] <Laney> No
[17:00] <Laney> Other way around
[17:00]  * Laney read gud
[17:00] <infinity> Yeah, that way around makes more sense. :P
[17:00] <Laney> Only takes a few minutes
[17:06] <apw> infinity, did you take publishing manual or is there just a whole heap of stuff migrating ?
[17:06] <infinity> apw: thunderbird's busy thudering.
[17:06] <infinity> thundering, too.
[17:07] <infinity> apw: Another one of those packages that highlights the publisher's O(lol) scaling with number of binaries.
[17:09] <apw> infinity, O(lol) that should be a thing
[17:12] <jderose> infinity: apw: bwahahaha, yes, O(lol) should definitely be a thing :D
[17:15] <infinity> apw: It is a thing!
[17:15] <infinity> apw: O(lol) is when solve difficulty appears (due to impatience) to be greater than linear.
[17:16] <infinity> apw: O(whee) is when it seems to get faster with more inputs.
[17:16] <apw> :)
[17:16] <infinity> apw: And O(wat) is when solve time seems to be a sine wave.
[17:18] <jderose> you're killing me, infinity, you're killing me :)
[17:19]  * apw files a bug on launchpad "Publisher runs should be O(whee)"
[17:20] <cyphermox> infinity: you're forgetting O(mg) for all those cases where you just can't do anything else but ^C.
[17:30] <jderose> infinity: do you have new ISOs spinning now, or are you waiting for bits still?
[17:34] <infinity> jderose: The latter, but getting there.
[17:35] <jderose> infinity: cool, sorry to pester :)
[17:35] <wxl> infinity: cypermox was talking about making some fixes to lubuntu's alternate installer. i assume that's one of the things you're waiting on?
[17:36] <infinity> cyphermox: ^?
[17:36] <cyphermox> infinity: yaboot.
[17:36] <infinity> cyphermox: Oh, he didn't specify powerpc. :P
[17:36] <wxl> cyphermox: oh so this only affects ppc? tsimonq2 seemed to suggest it was more general
[17:37] <tsimonq2> sorry wxl
[17:37] <cyphermox> hardinfo is more general, but I didn't get to that
[17:37] <tsimonq2> that's correct
[17:37] <infinity> wxl: I'll be looking at PPC later, but if it doesn't get fixed, it doesn't get fixed.  Best effort, etc.
[17:37] <wxl> cyphermox: the problems i have seen certainly aren't architecture specific
[17:37] <wxl> infinity: i could give a hoot about ppc
[17:37] <infinity> wxl: Which problem(s) are you seeing?
[17:37] <tsimonq2> wxl: O__o what problems?
[17:38] <wxl> bug 1632675
[17:38] <infinity> wxl: Ahh, that should just be a rebuild away.
[17:38] <infinity> wxl: Which is happening Very Soon.
[17:38] <wxl> okie dokie
[17:38] <wxl> carry on y'all :)
[17:39] <infinity> And thunderbird built on all arches.  It's a Christmas miracle.
[17:40] <Laney> Might even work if we're lucky
[17:40] <Laney> Bet the arm64 upload fails
[17:40] <infinity> Laney: Can you test whatever arch chrisccoulson was saying didn't work at all?  amd64?
[17:40] <infinity> Laney: While I'm waiting on the sausage factory to squeeze things out.
[17:40] <Laney> Am doing
[17:41] <chrisccoulson> I did test amd64 earlier from a local build before I uploaded
[17:41]  * Laney hopes that wget doesn't download these debug packages
[17:42]  * tsimonq2 gives the release team another round of coffee and/or Red Bull
[17:44]  * Laney wins at wget
[17:44]  * acheronuk provides donuts
[17:48] <Laney> infinity: This build is totes amazeballs
[17:48]  * Laney unblocks
[17:49] <davmor2> slangasek: so booting via netboot it is identical to mini.iso so I'll complete this and carry on
[17:50] <slangasek> davmor2: when you say it is identical, you mean you get identical results?
[17:51] <davmor2> slangasek: the initrd.gz seems to contain the same initial setup as the cdrom and it looks like the setup so far has been identical etc I'll complete it and confirm though
[17:52] <slangasek> davmor2: ok.  yes, once you've managed to boot it everything *should* be identical from there on out
[17:53] <slangasek> infinity: looks like *-meta have propagated, but xfsprogs did not because its binaries had not published before the britney run.  Should we divert that to SRU now?
[17:54] <slangasek> and, it seems libwpd-doc now wants to bring another web browser into main (dillo)
[17:54] <davmor2> slangasek: so these are the steps I followed https://help.ubuntu.com/community/Installation/NetbootInstallFromInternet so I did a base install so I had the boot stuff on the hdd and then wget'd the 2 files and then manually modded grub are those the steps you would be happier with?
[17:54] <slangasek> that seems like something that can be fixed on the seed side
[17:55] <slangasek> davmor2: ummmm "I wrote these files onto the hard drive" - also not testing *net*boot
[17:56] <slangasek> davmor2: look, clearly this has never been tested right; we should fix that in the future so that we have meaningful netboot tests, but I don't think we're going to fix the test cases between now and 16.10 release
[17:58] <slangasek> davmor2: and if you aren't actually familiar with how to netboot, I don't think it's worth you spending your time right now trying different tests that aren't actually netbooting
[17:58] <davmor2> slangasek: then how should this be run as far as I can tell these are the only instructions for a pc to netboot from the archive, if this is meant to be a pxe boot from the bios then that would be another set of tests all together
[17:58] <slangasek> davmor2: yes, it's precisely supposed to be a pxe boot from the firmware
[18:01] <slangasek> davmor2: and I apologize that we never had eyes on these test cases to make sure they were sane
[18:02] <davmor2> slangasek: no worries https://wiki.ubuntu.com/UEFI/PXE-netboot-install these are the right steps here then right?
[18:03] <slangasek> davmor2: for UEFI, those should be reasonably correct yes
[18:04] <slangasek> infinity: so I'm re-blocking xfsprogs, because it's now waiting on ceph autopkgtest results.  You know my position on whether xfsprogs is worth waiting for :)  If you disagree, you can always unblock it again
[18:05] <slangasek> infinity: but I don't want it to slip into the release pocket right at the point where we're otherwise ready to pull the trigger on image builds
[18:17] <flexiondotorg> slangasek, What is the implication of not having update xfsprogs on the iso?
[18:17] <flexiondotorg> Just curious, it is the alternate file system I test with.
[18:21] <slangasek> flexiondotorg: as far as I'm aware this package has no direct runtime impact, it's an upload to fix build failures
[18:23] <Laney> slangasek: Looks like you missed the boat and it went in anyway
[18:23] <slangasek> Laney: lulz ok
[18:24] <slangasek> so, a half hour wait or so before we trigger anything
[18:25] <slangasek> Laney: and what do we know now about thunderbird?  it's still unblocked, and has finished building but not publishing, so we're roughly an hour out?
[18:25] <slangasek> I would suggest forcing it in now and letting the armhf + arm64 builds catch up in the next cycle, so we can start building images a half hour sooner
[18:26] <slangasek> OTOH I guess you have autopkgtest results you want first
[18:26] <slangasek> (maybe?  not sure where we landed on that discussion above)
[18:26] <Laney> They look published to me now, so we should get adt triggered RSN
[18:28] <slangasek> confirmed, published so the next p-m run will not block on out-of-date binaries anyway
[18:29] <slangasek> by my reckoning, the following images are ready to respin as soon as xfsprogs publishes: kubuntu lubuntu ubuntu-gnome ubuntu-server
[18:29] <slangasek> and also cloud images, gaughen rcj ^^
[18:29] <slangasek> then the following need to wait for thunderbird (if we're waiting for thunderbird): ubuntu (desktop) ubuntukylin ubuntu-mate ubuntustudio xubuntu
[18:30] <wxl> thank god we don't have thunderbird in lubuntu :)
[18:31] <jderose> jbicha: hehe, thanks for fixing my bug description :D
[18:31] <Odd_Bloke> philroche: See Steve's comment above. :)
[18:32] <Laney> huh, no tests got triggered after all
[18:32] -queuebot:#ubuntu-release- New source: python-mock-services (xenial-proposed/primary) [0.2-0ubuntu0.16.04.1]
[18:32] <acheronuk> hopefully kubuntu will get firefox on this spin
[18:36]  * acheronuk crosses everything possible that can be crossed
[18:43] <Laney> I guess that debian/tests/control.in doesn't make Testsuite: autopkgtest get generated in the .dsc file, so they aren't run
[18:47] <slangasek> heh
[18:48] <slangasek> indeed
[18:57] -queuebot:#ubuntu-release- Unapproved: evolution (yakkety-proposed/universe) [3.22.0-2ubuntu1 => 3.22.1-0ubuntu1] (ubuntugnome, ubuntukylin)
[19:01] <jbicha> I'm fine with evolution being an sru
[19:02] <jbicha> the email signature fix is nice though (and Kylin doesn't actually ship Evolution)
[19:17] <slangasek> xfsprogs is published; requesting rebuilds for the first set identified above
[19:17] <slangasek> rcj, Odd_Bloke, philroche, gaughen: ^^ I believe that means everything's settled for cloud image builds
[19:23] <infinity> slangasek: Did you manually make sure the mirror was sane first?
[19:23] <slangasek> infinity: yes
[19:23] <infinity> Ta,
[19:24] <philroche> slangasek, Thank you
[19:26] <slangasek> infinity, Laney: I'm going afk in about 15 minutes and will be out for about 1.5h.  Is one of you in a position to trigger the remaining images once thunderbird publishes?  The list again AIUI is ubuntu ubuntukylin ubuntu-mate ubuntustudio xubuntu
[19:26] <infinity> slangasek: Yup.
[19:26] <slangasek> ok
[19:28] <clivejo> how can I force sftp on dput ubuntu?
[19:29] <xnox> slangasek, if i expand pkg->Built-Using->source->binaries and add those binaries as if they are reverse-depends on the binaries, things should just work no?
[19:30] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate amd64 [Yakkety Final] has been updated (20161012.1)
[19:30] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate powerpc [Yakkety Final] has been updated (20161012.1)
[19:30] -queuebot:#ubuntu-release- Builds: Lubuntu Alternate i386 [Yakkety Final] has been updated (20161012.1)
[19:30]  * xnox is trying to pretend that Built-Using->source->binaries are a yet another "reverse-depends" type (Among with Pre-Depends, Depends, Recommends(sometimes))
[19:30] <slangasek> xnox: yes, conceptually
[19:31]  * xnox ponders if i need to add them as Depends for real.
[19:31] <slangasek> xnox: oh, this is that horrible thing where Built-Using references source packages instead of binaries, isn't it
[19:31] <slangasek> hnngh
[19:32] <slangasek> which winds up being bad because we don't want to pull *all* the binaries from a given source into main
[19:32] <slangasek> xnox: so you kinda sorta want the intersection of Built-Using->binaries and Build-Depends
[19:32] <infinity> Or just the source.
[19:32] <slangasek> heh, or that
[19:32] <infinity> You can have the source in main and all the binaries in universe. :P
[19:33] <slangasek> infinity: however, the -dev packages would then all get "rescued", so that's still c-m being uselessly incomplete at attribution
[19:33] <xnox> infinity, that's what i currently have kind of. I force src in, and by that extension it pulls in all the rest of binaries rescued.
[19:34] <xnox> slangasek, not that simple as intersection of binaries & Build-Depends, because it could be Built-Using->binaries & Build-Depends->pkg->depends
[19:34] <xnox> and so on
[19:34] <slangasek> xnox: I'm going to go hide in a corner now
[19:34] <sudodus> I'll grab and test the Lubuntu Alternate asap :-)
[19:34] <xnox> maybe all of Built-Using->binaries should be forced in as Build-Depends (old-style?)
[19:35] <xnox> infinity, slangasek - in practice at the moment, it's only go, so all binaries go in.....
[19:36] <slangasek> xnox: well, so, as an approximation I would prefer that to what we have now
[19:36] <slangasek> but when it leads to c-m telling us to promote things that otherwise shouldn't need promoted, that'll be bad
[19:37] <slangasek> xnox: oh, here you go.  Only do the Built-Using revdeps thing for binaries that are being rescued
[19:37] <infinity> What it's telling us to pomote now seems correct enough, it's the missing reason that's the annoying bit.
[19:38] <xnox> slangasek, i have a fix just for reason to change from: Rescued from src => Rescued from $binaries_that_list_built_using (Built-Using)
[19:38] <xnox> in practice i simply do not have enough information. I only have source package.
[19:38] <xnox> Maybe we should actually only be promoting source package for these?
[19:39] <infinity> I think it's fair to say that if we're supporting the source due to built-using, the passive rescue of the source's -dev is probably what we want.
[19:39] <infinity> But I could also be down with just promoting the source itself.
[19:39] <slangasek> infinity: the behavior today of what gets rescued is fine, the lack of visible attribution is less fine
[19:39] <infinity> But that means neutering germinate to not rescue binaries from packages that are promoted due to built-using.
[19:40] <xnox> depends how we interpret the archive-reorg "you can always build with build-deps from universe" because we support "ubuntu-push" we do not support golang-foo-bar-baz for everything.
[19:40] <infinity> slangasek: Right, I thikn I said exactly that. :P
[19:40] <xnox> slangasek, but i thought your complaint was also that it is post-factum.
[19:40] <xnox> before something promoted you get a bunch of messages about depends
[19:40] <xnox> those are sorted
[19:40] <xnox> promote, boom magical rescue stuff appears.
[19:40] <slangasek> xnox: you can build with build-deps from universe, but if that build dep results in code being pulled into main (as a dep or as static linking), it has to go through MIR
[19:41] <slangasek> xnox: the post-factum aspect is also annoying, yes
[19:41]  * xnox changing rescue text/messaging will not help with promotion discovery (for components-missmatches)
[19:41] <xnox> i think showing things earlier is better.
[19:42] <slangasek> I agree
[19:42] <infinity> xnox: britney refusing to act with "foo is built-using bar, which is not in the same component" would be nice, yes.
[19:43] <xnox> britney currently refuses to act
[19:43] <infinity> (It would also be nice if the message for "which is not installable" was less opaque to lay people :P)
[19:43] <xnox> but pretends that "dependency is not satisfiable"
[19:43] <infinity> Okay.
[19:43] <xnox> right, that.
[19:43] <infinity> So, again, just an incorrect string.
[19:44] <infinity> But if britney refuses to act, how did we end up here?  britney trading bugs again, or did someone force this stuff in?
[19:44] <xnox> britney prevents migration only
[19:44] <infinity> Yes...
[19:44] <jbicha> clivejo: have a ~/.dput.cf with something like https://paste.ubuntu.com/23314473/ but use your LP username
[19:44] <infinity> xnox: I know what britney does.  But this mismatch is in the release pocket, not proposed.
[19:45] <infinity> xnox: Hence, either you're wrong about britney preventing migration in this case, or someone forced it.
[19:45] <xnox> so c-m shows missing deps; they are fixed; everything looks good; archive admin promotoes; _now_ c-m notices rescue & britney notices uninstalability
[19:45] <infinity> Oh.
[19:45] <infinity> Right, was in the release pocket in universe before someone made matters worse.
[19:45] <xnox> it's probably package has migrated to release, and people are working on a MIR in the release pocket.
[19:45] <infinity> Duh.
[19:46] <infinity> Right, in that case, all we have is c-m to protect us.
[19:46] <infinity> And it's post-facto.
[19:46] <xnox> britney gap-stop was to pacify doko's claim that if we enable universe, things will rapidly pickup transitive built-using deps.
[19:46] <infinity> And there's not much we can do about that.
[19:47] <xnox> so, imho Adding expansion of Built-Using->binaries to be treated as yet another dependency tree is sane
[19:47] <xnox> e.g. along with Pre-Depends, Depends, Recommends(sometimes)
[19:47] <infinity> xnox: I think what happens now is fine, it just needs the reason.
[19:48] <infinity> xnox: As in, it should be attempting to promote the source, and then let germinate rescue what it wants to.
[19:48] <xnox> infinity, what happens now is frustration.
[19:48] <xnox> because everybody (including AA) things everything is done, promote things, and shit happens.
[19:48] <infinity> xnox: The frustration is because the report literally tells me nothing about why those things are promoting.
[19:48] <xnox> ok.
[19:49] <infinity> xnox: I'm not sure how you propose to fix the OTHER frustration, but that's just how MIRs in the release pocket go.
[19:49] <infinity> And built-using is not special there.
[19:49] <slangasek> infinity: there is also the case that, if it's behind a Built-Using, it does not show up on c-m until *after* the thing that's built using it has been promoted
[19:49] <infinity> People promote or seed before deps are done and life sucks.
[19:49] <slangasek> which does mean you get to what you think is the end of the MIR, then new stuff pops up
[19:49] <slangasek> this is not a problem of the MIRs as a whole, and is specific to Built-Using
[19:49] <infinity> slangasek: Sure, that means the MIR process needs to take built-using into account, just like any other dep.
[19:50]  * xnox codes "Built-Using-Binaries" into the germinate world
[19:50] <infinity> slangasek: It's not specific to built-using at all, it's just another dep.
[19:50] <xnox> but first tea and biscuits
[19:50] <flocculant> xnox: excellent call
[19:50] <slangasek> infinity: mortals who try to traverse these deps manually for their MIRs get them wrong
[19:50] <infinity> "Oh, I did an MIR for all my binary deps, but missed my built-using" is a failure of the process documentation today, the bug reporter after we fix the docs. :P
[19:50] <slangasek> c-m should report it, while the MIR is in progress
[19:51] <infinity> slangasek: c-m does report it, minus the useful attribution.  I feel we're talking in circles now.
[19:51] <sudodus> Bug #1632675 'Lubuntu's alternate installer: no kernel modules were found' is squashed - the debian installer is running now :-)
[19:52] <infinity> sudodus: Good.  Please close it.
[19:53] <slangasek> infinity: no, it *doesn't report it* until the reverse-built-using has been promoted
[19:53] <infinity> slangasek: Eh.  That's true for all the deps too.
[19:53] <infinity> Well, promoted or seeded.
[19:53] <xnox> infinity, well, so when ubuntu-desktop gains dependency on "foo" the c-m lists a bunch of new things that need MIR. the whole chain of all deps, but none of the built-using.
[19:53] <infinity> germinate has to want it to be in main before it'll decide what else should go with it.
[19:54] <infinity> Oh.  Then that's just a bug.
[19:54] <xnox> infinity, eventually once the last dep is promoted, magically the built-using of that last intermediate dep ends up in c-m.
[19:54] <infinity> And one I don't understand why it exists.
[19:54] <xnox> yes.
[19:54] <infinity> Why does that bug exist? :P
[19:54] <xnox> because my implementation of built-using is fake =)
[19:54] <infinity> (Sorry, I didn't realize this bug was a thing, since we were talking about the attribution issue before)
[19:55] <xnox> out of the blue, I add it to the set of packages to promote, with no links to seeds =)
[19:55] <xnox> (in germinate brain, it's just there)
[19:55] <infinity> Fun.
[19:55] <xnox> which i'm now trying to fix =)
[19:55] <xnox> properly, hopefully.
[19:56] <infinity> So, I think how that should work is that when you see a built-using, the source package should be added to the same seed as the thing that triggered that.
[19:56] <infinity> And then the rest should fall out correctly.  Rescues, etc.
[19:56] <xnox> infinity, the biggest surprise would be: ubuntu-desktop add foo, all deps satisfied, please promoted, and then c-m explodes into gallizion of rescued golang-*-dev packages =)
[19:56] <infinity> xnox: Right, okay, I agree that's awful, I didn't realize it was implemented in a way that caused that.
[19:57] <infinity> Hence the confusion and talking past each other.
[19:57] <xnox> infinity, i may all have landed on slangasek's plate alone... =)
[19:57] -queuebot:#ubuntu-release- Builds: Ubuntu Server amd64 [Yakkety Final] has been updated (20161012.1)
[19:57] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64 [Yakkety Final] has been updated (20161012.1)
[19:57] -queuebot:#ubuntu-release- Builds: Ubuntu Server i386 [Yakkety Final] has been updated (20161012.1)
[19:57] -queuebot:#ubuntu-release- Builds: Ubuntu Server powerpc [Yakkety Final] has been updated (20161012.1)
[19:57] -queuebot:#ubuntu-release- Builds: Ubuntu Server ppc64el [Yakkety Final] has been updated (20161012.1)
[19:57] -queuebot:#ubuntu-release- Builds: Ubuntu Server s390x [Yakkety Final] has been updated (20161012.1)
[19:59]  * xnox kicks off autotest of s390x
[20:00] <infinity> xnox: With a punch card printer and a little robot to feed them into the slot?
[20:00] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Yakkety Final] has been updated (20161012.1)
[20:00] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop i386 [Yakkety Final] has been updated (20161012.1)
[20:01] <Laney> PUBLISH, YOU
[20:02] <infinity> Laney: It's working on it.
[20:02] <Laney> MORE
[20:02] <infinity> Writing out s390x indices now.
[20:02] <infinity> source next, then some signing, then some dude named Bob joins your family out of the blue, and somehow instead of being creepy, it's a sign of success.
[20:10] <xnox> infinity, honestly, my hackish scripts do involve using script, waiting for "screen to be ready for input", arbitrary sleeps and the like.
[20:10] <xnox> i also want selenium web-browser automation to drive the missing pieces of the LPAR.
[20:12] <infinity> xnox: Not impressed unless you involve a Roomba somehow.
[20:12] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Yakkety Final] has been updated (20161012)
[20:12] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Yakkety Final] has been updated (20161012)
[20:12] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Yakkety Final] has been updated (20161012)
[20:12] -queuebot:#ubuntu-release- Builds: Ubuntu Base i386 [Yakkety Final] has been updated (20161012)
[20:12] -queuebot:#ubuntu-release- Builds: Ubuntu Base powerpc [Yakkety Final] has been updated (20161012)
[20:12] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Yakkety Final] has been updated (20161012)
[20:12] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Yakkety Final] has been updated (20161012)
[20:13] <xnox> infinity, slangasek - i'm not entirely convinced by the rissotto recipes in hacked/wikileaked clinton emails.
[20:13] <xnox> *risotto
[20:14] -queuebot:#ubuntu-release- Builds: Ubuntu GNOME Desktop amd64 [Yakkety Final] has been updated (20161012.1)
[20:14] -queuebot:#ubuntu-release- Builds: Ubuntu GNOME Desktop i386 [Yakkety Final] has been updated (20161012.1)
[20:20] <infinity> Laney: So, once this kubuntu build finishes, we should be in a position to refresh the mirror and do the rest.
[20:22] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Yakkety Final] has been updated (20161012.1)
[20:22] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop i386 [Yakkety Final] has been updated (20161012.1)
[20:22] <infinity> And there it is.  Forcing a mirror refresh.
[20:27] <acheronuk> and the manifest says we have a browser. thank you :)
[20:28] <infinity> acheronuk: Good, cause if you didn't, I'd have no idea why. :P
[20:28] <Laney> Bonus diddlyonus
[20:29] <infinity> Laney: I think that's just bone-diddly-onus.
[20:29] <Laney> You bone your way and I'll bone mine
[20:29] <infinity> "I'm a murd-durdilly-urdler!"
[20:30]  * infinity taps his foot at rsync.
[20:32] <xnox> infinity, kick of cdn mirroring too?
[20:32] <infinity> Not yet.
[20:37] <infinity> Laney, slangasek: remaining builds kicked off.
[20:37] <infinity> Taking a bit of a coffee break, will check progress in a bit.
[20:38] <Laney> Nice one
[20:56] <clivejo> jbicha: when I use sftp Im getting Unable to connect to SSH host upload.ubuntu.com; EOF during negotiation
[20:56] <clivejo> I can sftp to my ppa's
[20:59] -queuebot:#ubuntu-release- Unapproved: hardinfo (yakkety-proposed/universe) [0.5.1-1.4ubuntu2 => 0.5.1-1.4ubuntu3] (lubuntu)
[21:02] <jderose> infinity: so is there another Ubuntu desktop ISO coming still?
[21:03] <wxl> jderose: waiting for thunderbird still i believe
[21:03] <jderose> wxl: gotcha, thanks!
[21:03] <wxl> np :)
[21:06] <Laney> It's building now
[21:06] <wxl> Laney: it meaning thunderbird, right? not the images themselves?
[21:06] <Laney> No, the images
[21:06] <Laney> https://launchpad.net/builders
[21:06] <wxl> ooh yay
[21:07] <wxl> Laney: thx for that link btw. didn't even know about that
[21:12] <Laney> wxl: There's also https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/yakkety/ubuntu / https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/yakkety/lubuntu etc
[21:12] <wxl> Laney: those i know about
[21:12] <Laney> ok, well they show the same builds
[21:16] <slangasek> xnox: risotto?  that's made with rice, that proves it's the Chinese not the Russians who are behind this
[21:20] -queuebot:#ubuntu-release- Unapproved: zabbix (xenial-proposed/universe) [1:2.4.7+dfsg-2ubuntu2 => 1:2.4.7+dfsg-2ubuntu2.1] (no packageset)
[21:35] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Yakkety Final] has been updated (20161012.2)
[21:35] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop i386 [Yakkety Final] has been updated (20161012.2)
[21:35] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Yakkety Final] has been updated (20161012.2)
[21:35] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop i386 [Yakkety Final] has been updated (20161012.2)
[21:37] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Yakkety Final] has been updated (20161012.3)
[21:37] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop i386 [Yakkety Final] has been updated (20161012.3)
[21:41] -queuebot:#ubuntu-release- Unapproved: calligra (yakkety-proposed/universe) [1:2.9.7-0ubuntu18 => 1:2.9.11-0ubuntu1] (kubuntu)
[21:43] <clivejo> ^^^ santa_
[21:43] <infinity> jderose: ^
[21:43] -queuebot:#ubuntu-release- Unapproved: juju-core (xenial-proposed/main) [2.0~beta15-0ubuntu2.16.04.1 => 2.0~rc3-0ubuntu1.16.04.1] (ubuntu-server)
[21:44] <jderose> infinity: that's what i'm talkin' about, daddy needs a new ISO. thanks!
[21:44] <infinity> Heh
[21:44]  * infinity decides to take a nap.
[21:45] <santa_> pitti: ↑ there you got it, our fixed calligra. I'm glad we demoted it temporarily to -proposed; it took some time to fix it
[21:46] <santa_> clivejo: thank you very much for the upload
[21:46] <clivejo> sorry it took so long, had issues with sftp!
[21:47] <santa_> np
[21:48] <clivejo> santa_: is there any way to get that patch for search in?
[21:48] <clivejo> LP 1632848
[21:50] <santa_> clivejo: I have uploaded a fixed version to our ppa, I will test it tomorrow and give you a ping to upload it
[21:50] <santa_> I hope it fits for -updates
[21:53] <ginggs_> would someone accept the openfoam-examples package from NEW please? It didn't build the first time around because of OOM on amd64
[22:09] <philroche> infinity, slangasek, I'm EOD now. As such I'm handing over cpc release lead to rcj
[22:10] <rcj> philroche, thanks.  I'll drive from here.
[22:10] <rcj> slangasek, infinity: we have images pre-publishing and testing
[22:19] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Yakkety Final] has been updated (20161012.1)
[22:19] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD i386 [Yakkety Final] has been updated (20161012.1)
[22:33] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Yakkety Final] has been updated (20161012.1)
[22:33] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop i386 [Yakkety Final] has been updated (20161012.1)
[22:33] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop powerpc [Yakkety Final] has been updated (20161012.1)
[22:59] -queuebot:#ubuntu-release- Unapproved: ubuntu-mate-welcome (yakkety-proposed/universe) [16.10.10 => 16.10.11] (ubuntu-mate)
[23:02] -queuebot:#ubuntu-release- Unapproved: mate-netbook (yakkety-proposed/universe) [1.16.0-1 => 1.16.1-1] (ubuntu-mate) (sync)
[23:03] -queuebot:#ubuntu-release- Unapproved: mate-terminal (yakkety-proposed/universe) [1.16.0-1 => 1.16.1-1] (ubuntu-mate) (sync)
[23:54] <tsimonq2> Thunderbird is unusable after the update for reading emails in another window
[23:54] <tsimonq2> This is what it's stuck at: http://img.ctrlv.in/img/16/10/13/57fecd43b1209.png
[23:55] <slangasek> tsimonq2: AIUI the previous version was also described as "unusable", was that not the case?
[23:55] <tsimonq2> slangasek: it worked fine
[23:55] <tsimonq2> slangasek: regression, is what I'm saying
[23:55] <tsimonq2> I've been using the Thunderbird in the archive for MONTHS now
[23:55] <slangasek> ok
[23:56] <slangasek> tsimonq2: so, there's not really any runway for resolving this before release, unfortunately
[23:56] <slangasek> tsimonq2: add it to release notes?
[23:56] <slangasek> (file a bug, add to release notes)
[23:57] <tsimonq2> slangasek: who ships with Thunderbird as the default?
[23:57] <flexiondotorg> Ubuntu, Ubuntu MATE
[23:57] <flexiondotorg> Xubuntu?
[23:58] <tsimonq2> apt depends says...
[23:58] <tsimonq2>   Recommends: xubuntu-desktop
[23:58] <tsimonq2>   Recommends: ubuntustudio-desktop
[23:58] <tsimonq2>   Recommends: ubuntukylin-desktop
[23:58] <tsimonq2>   Recommends: ubuntu-mate-desktop
[23:58] <tsimonq2>   Recommends: ubuntu-desktop
[23:59] <tsimonq2> and that's it
[23:59] <flexiondotorg> Yep, was just pasting ;-)
[23:59] <tsimonq2> (there's a bunch more stuff, those are just the high-level metapackages
[23:59] <tsimonq2> s/depends/rdepends/