[00:03] <jbicha> valorie: can we quote you on that?
[00:08] <wxl> this buds for you, cyphermox https://imgflip.com/i/1xsh02
[00:13] -queuebot:#ubuntu-release- Unapproved: audit (zesty-proposed/main) [1:2.6.6-1ubuntu1 => 1:2.6.6-1ubuntu1.1] (core)
[00:14] -queuebot:#ubuntu-release- Unapproved: audit (xenial-proposed/main) [1:2.4.5-1ubuntu2 => 1:2.4.5-1ubuntu2.1] (core)
[00:46] <cyphermox> wxl: \m/
[01:28] <valorie> lol
[01:28] <valorie> yes, I got both new spins perfectly
[01:46] <cyphermox> valorie: great
[01:47] <valorie> once I finish my backups, I will start testing
[01:47] <cyphermox> I'm off to bed, will do testing in the early morning.
[01:48] <cyphermox> I did find https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1724417 on the way, that broke the install completely (duh)
[01:48] <cyphermox> but it's very much environment-specific it seems. something in having a previous LVM install broke ubiquity there.
[01:49] <cyphermox> if I reinstall again with "erase entire disk", it's good. I'd be very interested to know if someone else finds this
[05:01] <jibel> cyphermox, I saw an instance of this issue reported on LP.
[05:10] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (artful-proposed/main) [2.477 => 2.478] (desktop-core)
[05:17] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (artful-proposed) [2.478]
[05:40] <slangasek> Laney: the above livecd-rootfs fixes a bug specific to the subiquity images, no respins needed for anything else; would you be able to shepherd a respin once it's published to artful?
[05:56] <ouroumov__> tsimonq2, xcalib hasn't been working at all since 16.10, can we remove it from the archive until the maintainer gets it fixed?
[06:06] -queuebot:#ubuntu-release- Unapproved: virtualbox-ext-pack (artful-proposed/multiverse) [5.1.30-2~build1 => 5.1.30-2] (no packageset) (sync)
[06:06] -queuebot:#ubuntu-release- Unapproved: accepted virtualbox-ext-pack [sync] (artful-proposed) [5.1.30-2]
[07:25] <sil2100> jibel: hey, I wonder if LP: #1724417 is something that can potentially happen to others?
[07:26] <jibel> sil2100, it does, I saw another instance of this crash for it is lost in LP now.
[07:26] <jibel> s/for/but/
[07:26] <jibel> er
[07:26] <sil2100> jibel: for artful only, or is it something older?
[07:26] <jibel> sil2100, it was artful IIRC
[07:27] -queuebot:#ubuntu-release- New binary: fast5 [amd64] (artful-proposed/universe) [0.6.3-1] (no packageset)
[07:27] <jibel> i'll try to find it, it was filed against grub2 and marked invalid
[07:27] <jibel> and reported sometime last week
[07:29] <sil2100> A bit worrying
[07:29] <sil2100> I'd prefer not needing to wait for the investigation/fix and to do a full re-spin, we might re-spin the subiquity images though
[07:30] -queuebot:#ubuntu-release- New: accepted fast5 [amd64] (artful-proposed) [0.6.3-1]
[07:31] <jibel> sil2100, bug 1722594
[07:32] <sil2100> jibel: thanks, let's mention it on the other bug
[07:39] <valorie> anyone know if there is a fix in the works for the "clicking doesn't work" in ubiquity? when I filed it tonight LP didn't find the previous bug
[07:41] <valorie> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1724467
[07:41] <valorie> I know it was reported previously because I've looked at it
[07:47] <sil2100> hm, didn't see this bug happening to me
[07:48] <smb> sil2100, it seems to happen to me too. but only if grub install fails. the dialog that comes up has non-working ok or cancel buttons
[07:48] <smb> so one cannot graphically escape
[07:49] <smb> sil2100, for the install fails when lvm is present: I had that with maas but it might be only similar but not the same reasons. curtin erases something then fails to write something to a disk which I don't know would exist.
[07:50] <smb> jibel, ^
[07:50] <sil2100> Ok, so that looks like the bug cyphermox encountered
[07:50] <smb> sil2100, but it would be two completely different environments
[07:58] <jibel> i can reproduce the non-working ok/canel buttons
[07:58] <jibel> for example when you force a non-uefi install on a  uefi system
[08:03] <Laney> righto
[08:03] <Laney> should I action Steve's request?
[08:04] <jibel> slightly different bug than valorie's
[08:04]  * sil2100 hates installer bugs
[08:05] <jibel> that's a way to prevent grub installer from failing later :)
[08:09] <sil2100> Steve's request?
[08:10] <Laney> subiquity respin for livecd-rootfs
[08:11] <sil2100> Laney: yeah, you want to push the button?
[08:11] <Laney> ok
[08:13] <jibel> bug 1724482
[08:18] <sil2100> jibel: thanks for filling it in!
[08:18] <jibel> it's different from valorie's bug
[08:31] -queuebot:#ubuntu-release- Unapproved: ubuntu-mate-welcome (artful-proposed/universe) [17.10.14 => 17.10.15] (ubuntu-mate)
[08:56] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (zesty-proposed) [2.28.5+17.04]
[09:00] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (xenial-proposed) [2.28.5]
[09:06] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Artful Final] has been updated (20171018)
[09:08] -queuebot:#ubuntu-release- Unapproved: gnome-session (artful-proposed/main) [3.26.1-0ubuntu5 => 3.26.1-0ubuntu6] (ubuntu-desktop)
[09:13] -queuebot:#ubuntu-release- Unapproved: gdm3 (artful-proposed/main) [3.26.1-3ubuntu2 => 3.26.1-3ubuntu3] (ubuntu-desktop)
[09:15] -queuebot:#ubuntu-release- New sync: golang-github-opencontainers-selinux (artful-proposed/primary) [1.0.0~rc1+git20170621.5.4a2974b-1]
[09:16] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (trusty-proposed) [2.28.5~14.04]
[09:25] -queuebot:#ubuntu-release- Unapproved: accepted gce-compute-image-packages [source] (zesty-proposed) [20171006+dfsg1-0ubuntu1~17.04.0]
[09:26] -queuebot:#ubuntu-release- Unapproved: accepted gce-compute-image-packages [source] (xenial-proposed) [20171006+dfsg1-0ubuntu1~16.04.0]
[09:26] -queuebot:#ubuntu-release- Unapproved: accepted gce-compute-image-packages [source] (trusty-proposed) [20171006+dfsg1-0ubuntu1~14.04.0]
[09:38] -queuebot:#ubuntu-release- New: accepted golang-github-opencontainers-selinux [sync] (artful-proposed) [1.0.0~rc1+git20170621.5.4a2974b-1]
[09:40] -queuebot:#ubuntu-release- New binary: golang-github-opencontainers-selinux [amd64] (artful-proposed/none) [1.0.0~rc1+git20170621.5.4a2974b-1] (no packageset)
[09:41] -queuebot:#ubuntu-release- New: accepted golang-github-opencontainers-selinux [amd64] (artful-proposed) [1.0.0~rc1+git20170621.5.4a2974b-1]
[09:42] -queuebot:#ubuntu-release- Unapproved: iptstate (xenial-proposed/universe) [2.2.5-1build1 => 2.2.5-1ubuntu0.1] (no packageset)
[09:49] -queuebot:#ubuntu-release- Unapproved: fast5 (artful-proposed/universe) [0.6.3-1 => 0.6.3-1ubuntu1] (no packageset)
[09:50] -queuebot:#ubuntu-release- Unapproved: accepted fast5 [source] (artful-proposed) [0.6.3-1ubuntu1]
[10:25] -queuebot:#ubuntu-release- New binary: linux-signed-hwe-edge [amd64] (xenial-proposed/main) [4.13.0-16.19~16.04.3] (kernel)
[10:29] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-edge [amd64] (xenial-proposed) [4.13.0-16.19~16.04.3]
[10:29] -queuebot:#ubuntu-release- New: accepted ppc64-diag [powerpc] (xenial-proposed) [2.7.4-1~16.04]
[10:29] -queuebot:#ubuntu-release- New: accepted ppc64-diag [ppc64el] (xenial-proposed) [2.7.4-1~16.04]
[10:35] <infinity> flexiondotorg: Tell me about this mate-welcome thing.
[10:44] -queuebot:#ubuntu-release- Unapproved: accepted gdm3 [source] (artful-proposed) [3.26.1-3ubuntu3]
[10:45] -queuebot:#ubuntu-release- Unapproved: accepted gnome-session [source] (artful-proposed) [3.26.1-0ubuntu6]
[12:18] <flexiondotorg> infinity: ubuntu-mate-welcome is just an bug fix update.
[12:18] <flexiondotorg> Post release update. Not needed for the image.
[12:18] <infinity> flexiondotorg: Kay.
[12:19] <flexiondotorg> infinity: Could you sync mate-settings-daemon from Debian unstable please?
[12:19] <flexiondotorg> 1.18.3-1
[12:19] <flexiondotorg> It is a bug fix release.
[12:19] <flexiondotorg> Again, not required for the image. Post release update is fine.
[12:21] <infinity> flexiondotorg: Post-release implies SRU.  I'd rather not have a sync as an SRU.
[12:22] <apw> which implies you need an sru bug with all the trimmings for both of those too
[12:23] <flexiondotorg> So I need to SRU something even though the release is not released yet?
[12:24] <flexiondotorg> These can be staged in updates ready to be installed post iso imnstall?
[12:24] <flexiondotorg> *can't
[12:24] <infinity> flexiondotorg: I mean, you either want it in the release pocket (and on images), or it's an SRU.
[12:24] <infinity> flexiondotorg: And given it's a two point release bump, it probably wouldn't be acceptable to jam in last minute.
[12:24] <flexiondotorg> I would prefer to have them on images and respin and test that SRU both of them.
[12:25] <flexiondotorg> *than SRYU
[12:25] <infinity> So, I don't see how it would be more acceptable post-release without some process behind it.
[12:26] <flexiondotorg> infinity: How can we proceed with landing them in the release pocket and respinning?
[12:26] <infinity> Or maybe you meant 1.18.1-3, not 1.18.3-1
[12:27] <flexiondotorg> Yes, correct. 1.18.1-3 for mate-settings-daemon.
[12:27] <infinity> Your numerical dyslexia made it sound worse. :P
[12:27] <flexiondotorg> :-)
[12:27] <infinity> flexiondotorg: Anyhow, "staging it for right after release" is a 0-day SRU.  It should obviously be tested to fix the bug it claims to fix.
[12:28] <flexiondotorg> It has been tested.
[12:28] <infinity> flexiondotorg: Pushing it to the release pocket today and respinning would, IMO, have exactly the same requirement.  Pushing in last minute fixes implies testing that they're not crap.
[12:28] <infinity> flexiondotorg: Like any other SRU, testing it after it's built, not before.
[12:28] <apw> flexiondotorg, if that ubuntu-mate-welcome is going to be an SRU it doesn't appear to have a bug associaited
[12:29] <flexiondotorg> ubuntu-mate-welcome fixes issues identified from community feedback. No associated LP bugs.
[12:30] <apw> rigth but to SRU it we would have to file a bug to process it against, and normally that is in the changelog
[12:30] <infinity> Anyhow, you also have 0 test results on your current images, so I'm not against pushing this stuff in and respinning.
[12:30] <infinity> That's up to you.
[12:31] <flexiondotorg> We have been testing the isos. But that was lost after the rebuild yesterday. We have bodies ready to test a respin.
[12:32] <flexiondotorg> If you can sync/release those infinity, we can get the tests completed.
[12:32] <flexiondotorg> By this evening.
[12:33] <infinity> Oh.  It's you and kylin.  Hrm.
[12:33] <infinity> Didn't realise they switched to mate this cycle.
[12:33] <jibel> infinity, for info, for the moment we are blocking the release of Ubuntu Desktop on bug 1723577
[12:34] <jibel> infinity, regression in gnome-shell 3.26.1-0ubuntu1
[12:34] <infinity> jibel: Yeah, I'm aware.
[12:34] <jibel> k
[12:34] -queuebot:#ubuntu-release- Unapproved: lshw (trusty-proposed/main) [02.16-2ubuntu1.3 => 02.16-2ubuntu1.4] (core)
[12:34] <flexiondotorg> infinity: Kylin switched to MATE (or their customised version UKUI) in 17.04.
[12:34] <didrocks> we found it's due to GNOME Shell
[12:35] <didrocks> sorry, multi-plexing :p
[12:35] <infinity> flexiondotorg: Yeah, I missed that memo.  Anyhow, my point was that if I accept mate-settings-daemon, it affects them too, not just you.
[12:35] <flexiondotorg> Oh, OK.
[12:36] <infinity> flexiondotorg: You're probably best off just putting SRU paperwork on the bug and doing it as a 0-day.  I'm not sure where the "if I have to do an SRU, I'll die a bit inside" thing comes from, but it's not that bad. :P
[12:37] <flexiondotorg> OK. I'll start the SRU process on Friday. No time prior to that.
[12:37] <flexiondotorg> infinity: What ubuntu-mate-welcome?
[12:37] <flexiondotorg> *what about
[12:38] <infinity> flexiondotorg: What "process"?  I mean, literally, add the SRU template to the bug, and bam, it's an SRU.  I can even accept it today, you can test, and we can release it tomorrow, if your testing appears sane.
[12:38] <flexiondotorg> There is no bug in LP.
[12:38] <infinity> flexiondotorg: mate-welcome is only on your images, so we could respin for that, if you want.  And given when mate-welcome is first seen (y'know, on first boot), that seems appropriate.
[12:39] <flexiondotorg> Yes please.
[12:39] <infinity> flexiondotorg: Oh, for the sync?  Yeah.  There's no bug for that, but unpacking, changing version number to -2ubuntu1 and adding a bug number would be trivial. :P
[12:43] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-mate-welcome [source] (artful-proposed) [17.10.15]
[12:47] <infinity> wxl: Should I be worried that there are no test results posted for lubuntu?
[12:49]  * sil2100 is running i386 ubuntustudio tests
[12:49] <sil2100> But it's slow, since my machine is thrashed with autopkgtest debugging as well
[12:50] <sil2100> (and my laptop is really old and slow)
[12:50] <smb> infinity, apw, not sure this was brought up by others, I struggle with artful desktop install (via live) locking up on boot about the time of switching to gdm (amd cpu + older nvidia gpu)
[12:51] <sil2100> smb: not sure if it's related to the issues the desktop guys are debugging, but did you try downgrading gnome-shell to 3.26.0-1ubuntu2 ?
[12:52] <smb> sil2100, not yet as its hard to do that when you have no place to type
[12:52] <infinity> smb: "struggle", as in it occasionally works, or "struggle", as in you hang out with too many Brits, and you really mean "it's completely broken"?
[12:52] <sil2100> Since from the current debugging and bisecting it seems that later versions of g-s seem to have issues with some cards
[12:53] <smb> infinity, rather the latter. I think I had one half working where gdm came up in low-gfx mode but then shell would not come up (segfaulting)
[12:53] <sil2100> infinity: I think he means it doesn't work, since he said he has no place to type ;p
[12:54] <smb> all my other attempts (about 5) were locking up before
[12:54] <smb> and I am too old to get grub screen up
[12:56]  * smb resorts to tweak stuff from live-image
[12:59] <flexiondotorg> infinity: mate-settings-daemon_1.18.1-2ubuntu1 just uploaded. Here is the SRU bug http://pad.lv/1724569
[12:59] -queuebot:#ubuntu-release- Unapproved: mate-settings-daemon (artful-proposed/universe) [1.18.1-2 => 1.18.1-2ubuntu1] (ubuntu-mate, ubuntukylin)
[13:03] <infinity> flexiondotorg: You built that source on Debian, didn't you?
[13:03] <infinity> flexiondotorg: (The bug closure didn't get parsed in .changes)
[13:04] <andreas> where do I file a bug against the ubuntu server installer? What's the project in lp?
[13:04] <infinity> andreas: Which installer?
[13:04] <andreas> ubuntu-server, I think it's "d-i"?
[13:04] <andreas> the text mode installer, not subiquity
[13:05] <infinity> andreas: subiquity is also text mode.
[13:05] <andreas> ok, but it's not subiquity
[13:05] <infinity> andreas: But if you mean the classic images, then yes, debian-installer
[13:05] <sil2100> Depends what images you used
[13:05] <andreas> http://cdimage.ubuntu.com/ubuntu-server/daily/current/
[13:05] <andreas> server amd64
[13:05] <flexiondotorg> infinity: Reject it. Built with my Debian environment variables set. I'll build again ith DEB_VENDOR=Ubuntuy
[13:06] <infinity> andreas: debian-installer is the installer on those images, yes.
[13:06] -queuebot:#ubuntu-release- Unapproved: rejected mate-settings-daemon [source] (artful-proposed) [1.18.1-2ubuntu1]
[13:07] <andreas> infinity: and our project in lp for it?
[13:07] <infinity> andreas: ...
[13:07] <andreas> https://bugs.launchpad.net/debian-installer is really the debian one, not our fork I presume
[13:07] <infinity> andreas: https://launchpad.net/ubuntu/+source/debian-installer
[13:07] <infinity> andreas: It's a package.
[13:08] <andreas> thanks
[13:10] -queuebot:#ubuntu-release- Unapproved: mate-settings-daemon (artful-proposed/universe) [1.18.1-2 => 1.18.1-2ubuntu1] (ubuntu-mate, ubuntukylin)
[13:16] <cyphermox> sil2100: you said some other bug looked like what I had seen yesterday?
[13:19] <sil2100> cyphermox: yeah, left the link in the comments of your bug, jibel passed that bug to me
[13:24] -queuebot:#ubuntu-release- Unapproved: accepted mate-settings-daemon [source] (artful-proposed) [1.18.1-2ubuntu1]
[14:33] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Artful Final] has been updated (20171018)
[14:33] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop i386 [Artful Final] has been updated (20171018)
[14:34] <didrocks> sil2100: infinity: so, a GNOME Shell near you in few minutes
[14:34] <didrocks> we found the revert needed, it doesn't really impact us (headless mode)
[14:34] <didrocks> the contributor confirmed it works for him
[14:34] <didrocks> seb128 and I did try on a VM, the Shell still starts
[14:34] <didrocks> and willcooke tried suspend/resume
[14:36] <sil2100> \o/
[14:36] <sil2100> This is excellent news
[14:36] <sil2100> Will review it as soon as it appears in the queue
[14:36] <willcooke> thanks didrocks sil2100
[14:41] -queuebot:#ubuntu-release- Unapproved: gnome-shell (artful-proposed/main) [3.26.1-0ubuntu3 => 3.26.1-0ubuntu4] (desktop-extra, mozilla, ubuntu-desktop)
[14:41] <didrocks> sil2100: and here we go ^
[14:41] <sil2100> \o/
[14:41] <sil2100> Taking care of that one
[14:41] <didrocks> I'm letting that in good hands :)
[14:43] <sil2100> didrocks, infinity: ^ accepted
[14:43] <sil2100> Will need to get it through -proposed
[14:43] -queuebot:#ubuntu-release- Unapproved: accepted gnome-shell [source] (artful-proposed) [3.26.1-0ubuntu4]
[14:49] <smb> sil2100, just for info (I see the new version is already coming) downgrading gnome-shell did not help in my case
[14:52] <sil2100> hmmm, so unrelated then
[14:52] <sil2100> smb: could you fill in a bug in this case?
[14:53] <smb> sil2100, yeah, well I fist want to try the ubuntu4 one to be sure, then I file one
[14:55] <chrisccoulson> I've still got flashplugin/partner packages sat in the queue for trusty -> zesty. Can anyone approve them? (Usually it's Jamie but he's not around)
[14:55] <sil2100> chrisccoulson: slangasek, when he's up, should be able to help you
[14:56] <sil2100> hmmm, or maybe I should try checking if I don't have the power to approve those
[14:57]  * sil2100 waits impatiently for the publisher to do its job
[15:01] <sil2100> chrisccoulson: ok, I tried accepting the zesty one, let's see if it worked correctly
[15:01] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (zesty-proposed) [1:20171016.1-0ubuntu0.17.04.1]
[15:02] <sil2100> chrisccoulson: looks like it worked, let me take a look at the others
[15:03] <sil2100> slangasek: hope you don't mind me doing those? I guess I should be good since I'm part of canonical-partner-dev + SRU?
[15:05] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (xenial-proposed) [1:20171016.1-0ubuntu0.16.04.1]
[15:06] <sil2100> chrisccoulson: all looked good, accepted
[15:06] <chrisccoulson> sil2100, thanks
[15:06] -queuebot:#ubuntu-release- Unapproved: accepted adobe-flashplugin [source] (trusty-proposed) [1:20171016.1-0ubuntu0.14.04.1]
[15:06] <chrisccoulson> sil2100, they do need copying from -proposed shortly as well
[15:13] <slangasek> sil2100: ah, I hadn't given thought to the fact that this intersection of permissions gives you queue access; I'm ok with you reviewing the unapproved queue on partner, yes
[15:19] <sil2100> chrisccoulson: this I think I cannot do, only slangasek ;p
[15:20] <sil2100> slangasek: btw. since I never did this before, how do I tag a package to ignore the britney lock during such a freeze?
[15:20] <sil2100> slangasek: I'm asking since we're waiting for the gnome-shell regression to be fixed, the package is in -proposed and once it gets tested we'd like to get it released and images re-built
[15:21] <sil2100> smb: new gnome-shell in artful-proposed! Could you test if it also fixes your case?
[15:21] <sil2100> didrocks, jibel: ^ can you guys also do testing on the -proposed gnome-shell?
[15:21] <smb> sil2100, sure
[15:27] <slangasek> sil2100: 'unblock' hint
[15:28] <smb> sil2100, pass! \o/ we have a gui
[15:33] <smb> now "only" network-manager should answer dns queries on 127.0.1.1 ...
[15:35] <sil2100> smb: wow, nice!
[15:35] <sil2100> slangasek: thanks!
[15:38] <xnox> smb, artful? on artful there should be no 127.0.1.1...
[15:39] <smb> xnox, but that is what I have in /etc/resolv.conf
[15:39] <xnox> smb, is that clean install or upgrade?
[15:39] <smb> xnox, iso testing fresh install
[15:39] <xnox> smb, server or desktop? ifupdown or network-manager? default config?
[15:39] <smb> desktop
[15:39] <xnox> that can't be good
[15:40]  * xnox syncs latest image
[15:41] <smb> xnox, file gnerated by networkmanager (it says)
[15:41] <xnox> smb, yeah, it should not do that....
[15:42] <sil2100> gnome-shell autopkgtests in progress, hope those finish quick
[15:48] <smb> xnox, if that is helping any, this is an installation made from the live image. have not tried direct install yet
[15:49] <xnox> smb, well, i synced artful ubuntu desktop iso, booted into live session, did check that in the life session resolv.conf is a symlink to stub-resolve.conf
[15:49] <xnox> currently launched install ubuntu 17.10 and running that at the moment.
[15:51] <xnox> smb, in-target at the moment still has /target/etc/resolv.conf pointing at the right thing.
[15:52] <xnox> smb, is this VM or laptop? did you have networking during install? wifi or ethernet?
[15:52]  * xnox is in a VM with ethernet auto-dhcp connected
[15:52] <smb> xnox, desktop and had ethernet
[15:52] <xnox> ack
[15:53] <smb> xnox, ugh maybe it was accidentally me
[15:54] <xnox> smb, what's your NetworkManager -printconfig? or some such?
[15:54] <smb> xnox, sorry I think I know what happened and its user fault
[15:55] <xnox> smb, what was it? i'm curious now =)
[15:55] <smb> xnox, I had to manually mount the disk to do a chroot install of sshd (because of the gnome-shell problem)
[15:56] <smb> xnox, so for that to work I added a nameserver manually and then removed resolv.conf assuming it would regenerate itself correctly
[15:56] <xnox> ha
[15:56] <xnox> if there is no resolv.conf yes networkmanager takes over it
[15:56] <xnox> i guess we could make it create the symlink to stub-resolv.conf
[15:57] <xnox> regular install works fine, it seems.
[15:57] <smb> xnox, some automatic habit from before when having a resolv.conf would prevent the right new resolvconf ways of things
[15:59] <xnox> resolvconf is dead
[15:59] <xnox> resolved is the new world order
[16:03] <xnox> smb, however resolvconf on boot would check its stampfiles and would re-generate the symlink. horum.
[16:04] <smb> xnox, so why does resolvd not create the right link when its missing =:P Systemd people are not that shy in other cases
[16:04] <smb> hah beat me to say it
[16:04] <bdmurray> The Release Notes make include a link to "Less Popular Ubuntu Images" is there a better way to describe those?
[16:05] <xnox> smb, hm, i guess i could include a tmpfiles.d snippet to do that.
[16:05] <xnox> l /etc/resolv.conf ../run/systemd/resolve/stub-resolv.conf
[16:05] <xnox> or some such
[16:06] <smb> xnox, yeah, I can confirm that doing that is preventing nm from interfering and the network icon finally is without that question mark...
[16:08] <smb> At least as a positive, once the ISOs are regenerated with the updated gnome-shell I won't get tempted to mess with the installation
[16:33] <sil2100> Ok, autopkgtests for gnome-shell finished successfully - anyone can do a quick dogfood run of it before I hint it in?
[16:40] <wxl> infinity: tsimonq2 is primarily running the show. have you asked him?
[16:40] <tsimonq2> Huh what? :)
[16:42] <smb> sil2100, does me pick it ok, count?
[16:44] <tsimonq2> Oh. infinity, don't be worried :)
[16:55] <sil2100> Ok, let me try hinting it in then!
[16:56] <sil2100> (this will take a minute)
[16:58] <sil2100> gnome-shell unblocked
[16:58] <sil2100> smb, jibel: thanks for the tests! And didrocks thanks for the fixed package ;)
[16:59] <sil2100> infinity: are you ok with me re-building the desktop images with the new gnome-shell?
[16:59] <sil2100> (once it migrates)
[17:06] <didrocks> great!
[17:14] <jibel> sil2100, go ahead, rebuild the desktop images.
[17:14] <jibel> once g-s is puvlished
[17:25] <sil2100> Why is this taking so long...
[17:32]  * sil2100 grows impatient
[17:34] <apw> sil2100, its the publisher, you are watching it ... therefore it is hiding
[17:36] <sil2100> But I see in the britney logs: "Copying: gnome-shell/3.26.1-0ubuntu4" so yay
[17:39] <sil2100> Ok, I guess soon I'll be able to kick the new image
[17:40] <sil2100> We'll probably have to wait for the final publisher tick
[18:07] <sil2100> This publisher is killing me
[18:09] <flocculant> sil2100: found an issue with friendly recovery - a missing file warning, bug 1724643 . Doubt it's a great problem in the scheme of things, just makes friendly-recovery more abitunfriendly-recovery :)
[18:10] <sil2100> flocculant: does it still work then? Or does this warning cause it to exit?
[18:11] <sil2100> I'm fine with it just giving this warning, non-critical, a bit ugly but yeah
[18:11] <flocculant> it works ok - just shows the warning - forgot to put that in bug - will do now
[18:11] <flocculant> yea - was my impression, just thought I would mention it :)
[18:11]  * sil2100 sees the new gnome-shell in the release pocket as per rmadison
[18:12] <flocculant> sil2100: if it had not worked I would have started with - Sorry but :)
[18:25] <sil2100> Ok, I think it's safe enough to kick a rebuild
[18:25] <sil2100> jibel, infinity: ^
[18:26] <sil2100> Rebuild requested
[18:27] <jibel> sil2100, thanks
[18:54] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Artful Final] has been updated (20171018)
[19:06] <sil2100> Rebuild finished o/
[19:06] <sil2100> Let me check the manifest
[19:07] <sil2100> Ok, it has the right gnome-shell so we're good
[19:16]  * sil2100 goes AFK for a bit to do life™
[19:23] -queuebot:#ubuntu-release- Unapproved: python3.7 (artful-proposed/universe) [3.7.0~a1-1 => 3.7.0~a2-1] (no packageset)
[19:23] -queuebot:#ubuntu-release- Unapproved: accepted python3.7 [source] (artful-proposed) [3.7.0~a2-1]
[20:51] -queuebot:#ubuntu-release- Builds: Upgrade Kubuntu amd64 [Artful Final] (20171018) has been added
[20:51] -queuebot:#ubuntu-release- Builds: Upgrade Lubuntu amd64 [Artful Final] (20171018) has been added
[20:51] -queuebot:#ubuntu-release- Builds: Upgrade Ubuntu MATE amd64 [Artful Final] (20171018) has been added
[20:51] -queuebot:#ubuntu-release- Builds: Upgrade Ubuntu MATE i386 [Artful Final] (20171018) has been added
[20:51] -queuebot:#ubuntu-release- Builds: Upgrade Ubuntu Server amd64 [Artful Final] (20171018) has been added
[20:51] -queuebot:#ubuntu-release- Builds: Upgrade Ubuntu Server i386 [Artful Final] (20171018) has been added
[20:51] -queuebot:#ubuntu-release- Builds: Upgrade Lubuntu i386 [Artful Final] (20171018) has been added
[20:51] -queuebot:#ubuntu-release- Builds: Upgrade Ubuntu Studio amd64 [Artful Final] (20171018) has been added
[20:51] -queuebot:#ubuntu-release- Builds: Upgrade Ubuntu Studio i386 [Artful Final] (20171018) has been added
[20:51] -queuebot:#ubuntu-release- Builds: Upgrade Ubuntu amd64 [Artful Final] (20171018) has been added
[20:51] -queuebot:#ubuntu-release- Builds: Upgrade Ubuntu i386 [Artful Final] (20171018) has been added
[20:51] -queuebot:#ubuntu-release- Builds: Upgrade UbuntuKylin amd64 [Artful Final] (20171018) has been added
[20:51] -queuebot:#ubuntu-release- Builds: Upgrade Kubuntu i386 [Artful Final] (20171018) has been added
[20:52] -queuebot:#ubuntu-release- Builds: Upgrade UbuntuKylin i386 [Artful Final] (20171018) has been added
[20:52] -queuebot:#ubuntu-release- Builds: Upgrade Xubuntu amd64 [Artful Final] (20171018) has been added
[20:52] -queuebot:#ubuntu-release- Builds: Upgrade Xubuntu i386 [Artful Final] (20171018) has been added
[22:45] <bdmurray> infinity: so just test whatever catches my fancy?
[22:46] <tsimonq2> Test Lubuntu. <3
[22:48] <infinity> bdmurray: Things without results, ideally.
[22:49] <bdmurray> Okay I forget was there a way for people to communicate what they plan on testing?
[22:49] <bdmurray> Oh, there it is "In Progress"