[00:57] <cyphermox> imho, it's pretty late for rebuilding main packages just for PIE, perhaps if there are other bugfixes alongside..
[01:26] <Ukikie> It depends on if its pumpkin pie....
[01:35] <mwhudson> any release team people about?
[02:11] -queuebot:#ubuntu-release- Unapproved: golang-1.6 (xenial-proposed/main) [1.6.2-0ubuntu5~16.04 => 1.6.2-0ubuntu5~16.04.1] (kubuntu, ubuntu-desktop)
[02:32] <cyphermox> mwhudson: it's either too late or too early I think; otherwise too weekend? ;D
[02:39] -queuebot:#ubuntu-release- Unapproved: ubiquity (zesty-proposed/main) [17.04.8 => 17.04.9] (core)
[02:40] -queuebot:#ubuntu-release- Unapproved: ubiquity-slideshow-ubuntu (zesty-proposed/main) [123 => 124] (kubuntu, ubuntu-desktop)
[02:51] -queuebot:#ubuntu-release- Unapproved: golang-1.6 (yakkety-proposed/main) [1.6.3-1ubuntu1 => 1.6.3-1ubuntu1.1] (kubuntu, ubuntu-desktop)
[02:52] <mwhudson> cyphermox: yeah too weekend
[05:49] <estan> good morning folks. any release team member who could kindly have a look at qtbase-opensource-src 5.5.1+dfsg-16ubuntu7.4 in the xenial upload queue? it fixes a quite annoying bug i reported, so i'm eager to have it tested in proposed (https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1598173).
[05:49] <ubot5> Ubuntu bug 1598173 in qtbase-opensource-src (Ubuntu Xenial) "Please consider SRU of "xcb: Compress mouse motion and touch update events"" [Undecided,New]
[05:50] -queuebot:#ubuntu-release- Unapproved: rejected ubiquity-slideshow-ubuntu [source] (zesty-proposed) [124]
[05:51] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (zesty-proposed) [2:10.0.0-0ubuntu5]
[05:51] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (zesty-proposed) [17.04.9]
[06:24] -queuebot:#ubuntu-release- Unapproved: gnss-sdr (zesty-proposed/universe) [0.0.9-1 => 0.0.9-2] (no packageset) (sync)
[06:24] -queuebot:#ubuntu-release- Unapproved: accepted gnss-sdr [sync] (zesty-proposed) [0.0.9-2]
[06:27] -queuebot:#ubuntu-release- Unapproved: r-bioc-genomeinfodb (zesty-proposed/universe) [1.10.2-1 => 1.10.3-1] (no packageset) (sync)
[06:27] -queuebot:#ubuntu-release- Unapproved: accepted r-bioc-genomeinfodb [sync] (zesty-proposed) [1.10.3-1]
[06:31] <infinity> rbalint: I suspect your science is a bit off if glibc is in that list, given that dpkg and gcc didn't change since the last glibc upload.  But also, waaaay too late to be asking to rebuild a bunch of stuff in main.  It can wait for Anonymous Antelope.
=== michi_ is now known as Guest48864
[06:51] <ginggs> rbalint: yw, and thanks for the upload.  i've sync'd r-bioc-genomeinfodb and will trigger the necessary tests
[06:53] <infinity> ginggs: Still hoping to get that whole R mess migrated under the wire?
[07:22] -queuebot:#ubuntu-release- Unapproved: gnome-shell-extension-weather (zesty-proposed/universe) [0~20160325.gitb5415ec-2ubuntu2 => 0~20170402.git34506a6-1] (no packageset) (sync)
[07:22] -queuebot:#ubuntu-release- Unapproved: accepted gnome-shell-extension-weather [sync] (zesty-proposed) [0~20170402.git34506a6-1]
[07:39] <ginggs> infinity: i think a big chunk of them will migrate now - but there are still a couple with bad tests
[07:40]  * apw yawns at the world
[07:40] <infinity> ginggs: Yeah, I briefly looked at the mess when I was on the warpath to make glibc's rdeps all green.  I got everything EXCEPT for r-* because I had better things to do.
[07:42] <infinity> apw: Did the world yawn back?
[07:42] <apw> seems not, seems i am not very interesting
[08:18] <jbicha> hi, what should we do to fix chrome-gnome-shell 8-2ubuntu4~ubuntu16.10.1 not actually being published for 16.10?
[08:18] <jbicha> http://archive.ubuntu.com/ubuntu/pool/universe/c/chrome-gnome-shell/
[08:18] <jbicha> https://github.com/nE0sIghT/chrome-gnome-shell-mirror/issues/44
[08:30] <LocutusOfBorg> hello infinity thanks for curl hint
[08:55] -queuebot:#ubuntu-release- Unapproved: system-config-printer (zesty-proposed/main) [1.5.7+20160812-0ubuntu8 => 1.5.7+20160812-0ubuntu9] (kubuntu, ubuntu-desktop)
[08:55] -queuebot:#ubuntu-release- Unapproved: dnscrypt-proxy (zesty-proposed/universe) [1.9.4-1 => 1.9.4-1build1] (no packageset)
[08:56] -queuebot:#ubuntu-release- Unapproved: ubuntu-gnome-meta (zesty-proposed/universe) [0.77 => 0.78] (ubuntugnome)
[08:56] -queuebot:#ubuntu-release- Unapproved: accepted dnscrypt-proxy [source] (zesty-proposed) [1.9.4-1build1]
[08:56] -queuebot:#ubuntu-release- Unapproved: dnstap-ldns (zesty-proposed/universe) [0.2.0-2 => 0.2.0-2build1] (no packageset)
[08:57] -queuebot:#ubuntu-release- Unapproved: freeipa (zesty-proposed/universe) [4.4.3-3ubuntu1 => 4.4.3-3ubuntu2] (no packageset)
[08:57] -queuebot:#ubuntu-release- Unapproved: accepted freeipa [source] (zesty-proposed) [4.4.3-3ubuntu2]
[08:57] -queuebot:#ubuntu-release- Unapproved: opendnssec (zesty-proposed/universe) [1:2.0.3+-1ubuntu1 => 1:2.0.3+-1ubuntu2] (no packageset)
[08:58] -queuebot:#ubuntu-release- Unapproved: accepted dnstap-ldns [source] (zesty-proposed) [0.2.0-2build1]
[08:58] -queuebot:#ubuntu-release- Unapproved: libzonemaster-perl (zesty-proposed/universe) [1.0.16-1 => 1.0.16-1build1] (no packageset)
[08:58] -queuebot:#ubuntu-release- Unapproved: strongswan (zesty-proposed/main) [5.5.1-1ubuntu2 => 5.5.1-1ubuntu3] (ubuntu-server)
[08:58] -queuebot:#ubuntu-release- Unapproved: libnet-ldns-perl (zesty-proposed/universe) [0.75-1 => 0.75-1build1] (no packageset)
[08:58] -queuebot:#ubuntu-release- Unapproved: pathspider (zesty-proposed/universe) [1.0.1-1 => 1.0.1-1build1] (no packageset)
[08:58] -queuebot:#ubuntu-release- Unapproved: accepted libzonemaster-perl [source] (zesty-proposed) [1.0.16-1build1]
[08:58] -queuebot:#ubuntu-release- Unapproved: python-libtrace (zesty-proposed/universe) [1.6+git20161027-1 => 1.6+git20161027-1build1] (no packageset)
[08:58] -queuebot:#ubuntu-release- Unapproved: accepted pathspider [source] (zesty-proposed) [1.0.1-1build1]
[08:59] -queuebot:#ubuntu-release- Unapproved: accepted libnet-ldns-perl [source] (zesty-proposed) [0.75-1build1]
[08:59] -queuebot:#ubuntu-release- Unapproved: accepted opendnssec [source] (zesty-proposed) [1:2.0.3+-1ubuntu2]
[08:59] -queuebot:#ubuntu-release- Unapproved: accepted python-libtrace [source] (zesty-proposed) [1.6+git20161027-1build1]
[09:01] <infinity> LocutusOfBorg: Dude.  A library transition three days before release? :(
[09:01] <infinity> LocutusOfBorg: One that involves seeded packages, no less?
[09:01] -queuebot:#ubuntu-release- Unapproved: cluster-glue (zesty-proposed/main) [1.0.12-5ubuntu1 => 1.0.12-5ubuntu2] (ubuntu-desktop, ubuntu-server)
[09:02] <LocutusOfBorg> infinity, erm... not my fault, trying to fix other people mistakes
[09:02] <LocutusOfBorg> trying to fix the mess :/
[09:02] <mapreri> only strongswan is seeded, right?
[09:03] <infinity> LocutusOfBorg: It wasn't a mess until you just now uploaded.
[09:03] <infinity> LocutusOfBorg: One library stuck in proposed is not a "mess".
[09:04] <infinity> LocutusOfBorg: Now it's one library and a bunch of stuff that depends on it.
[09:05] -queuebot:#ubuntu-release- Unapproved: tigervnc (zesty-proposed/universe) [1.7.0+dfsg-6ubuntu1 => 1.7.0+dfsg-7ubuntu1] (edubuntu)
[09:09] -queuebot:#ubuntu-release- Unapproved: accepted system-config-printer [source] (zesty-proposed) [1.5.7+20160812-0ubuntu9]
[09:10] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-gnome-meta [source] (zesty-proposed) [0.78]
[09:13] -queuebot:#ubuntu-release- Unapproved: accepted tigervnc [source] (zesty-proposed) [1.7.0+dfsg-7ubuntu1]
[09:14] -queuebot:#ubuntu-release- Unapproved: accepted strongswan [source] (zesty-proposed) [5.5.1-1ubuntu3]
[09:22] <infinity> ginggs: Did you need to do something with gearhead for that last minute fpc upload of yours?
[09:22] <LocutusOfBorg> ta for tigervnc strongswan
[09:26] <LocutusOfBorg> will make it smooth
[09:48] <ginggs> infinity: i don't think we need any rebuild for fpc, everything is statically linked. did you pick up a problem?
[09:50] <infinity> ginggs: NBS picked up a problem.  gearhead build-deps on an fpc-source version you're about to remove.
[09:50] <ginggs> infinity: thanks, i'll look into that
[09:53] <mapreri> infinity: fyi, the top of britney has a "Trying easy from adconrad.... Version mismatch ... Not using hint"
[09:53] -queuebot:#ubuntu-release- Unapproved: ubuntu-gnome-default-settings (zesty-proposed/universe) [17.04.2 => 17.04.3] (ubuntugnome)
[09:54] <infinity> mapreri: Yeah, that's harmless.  It's an old hint I haven't deleted.
=== infinity1 is now known as infinity
[10:38] -queuebot:#ubuntu-release- Unapproved: gearhead (zesty-proposed/universe) [1.302-3 => 1.302-3ubuntu1] (no packageset)
[10:39] -queuebot:#ubuntu-release- Unapproved: accepted gearhead [source] (zesty-proposed) [1.302-3ubuntu1]
[10:41] -queuebot:#ubuntu-release- Unapproved: dpkg (xenial-proposed/main) [1.18.4ubuntu1.1 => 1.18.4ubuntu1.2] (core)
[10:41] -queuebot:#ubuntu-release- Unapproved: dpkg (zesty-proposed/main) [1.18.10ubuntu1 => 1.18.10ubuntu2] (core)
[10:41] -queuebot:#ubuntu-release- Unapproved: dpkg (yakkety-proposed/main) [1.18.10ubuntu1 => 1.18.10ubuntu1.1] (core)
[10:46] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe-edge [amd64] (xenial-proposed) [4.10.0-19.21~16.04.1]
[10:48] -queuebot:#ubuntu-release- Unapproved: accepted dpkg [source] (zesty-proposed) [1.18.10ubuntu2]
[10:48] -queuebot:#ubuntu-release- Unapproved: accepted cluster-glue [source] (zesty-proposed) [1.0.12-5ubuntu2]
[10:49] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-gnome-default-settings [source] (zesty-proposed) [17.04.3]
[10:56] -queuebot:#ubuntu-release- Unapproved: accepted dpkg [source] (xenial-proposed) [1.18.4ubuntu1.2]
[10:56] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (trusty-proposed) [3.13.0-117.164]
[10:58] -queuebot:#ubuntu-release- Unapproved: accepted dpkg [source] (yakkety-proposed) [1.18.10ubuntu1.1]
[11:25] -queuebot:#ubuntu-release- Unapproved: ubuntu-mate-settings (zesty-proposed/universe) [17.04.6 => 17.04.7] (ubuntu-mate)
[11:31] <ginggs> infinity: is forcing bad-test an option for r-bioc-annotationhub/2.6.4-1 ?  this is holding up many of the R packages.  i believe the current failure is also due to NCBI's FTP site reorganization, we already fixed debian bug #859864, but this looks like another.  i'm pretty sure  r-bioc-annotationhub/2.4.2-2 in zesty is affected too, so it's not a regression
[11:31] <ubot5> Debian bug 859864 in src:r-bioc-genomeinfodb "r-bioc-genomeinfodb: Reorganization of ftp://ftp.ncbi.nlm.nih.gov/genomes/all" [Grave,Open] http://bugs.debian.org/859864
[11:31] <ginggs> rbalint ^
[11:31] -queuebot:#ubuntu-release- Unapproved: base-files (zesty-proposed/main) [9.6ubuntu12 => 9.6ubuntu13] (core)
[11:33] <infinity> ginggs: Can the test not be fixed?
[11:33] <infinity> (Or the code the test is calling)
[11:33] <ginggs> infinity: i'll keep looking, but I don't know R from P or Q
[11:34] <jbicha> please unblock ubuntu-gnome-meta, thanks
[11:34] <infinity> ginggs: Well, the bug you referenced is fixed in a new upload...
[11:34] -queuebot:#ubuntu-release- Unapproved: accepted cinder [source] (xenial-proposed) [2:8.1.1-0ubuntu3]
[11:34] <infinity> jbicha: Will unblock when I redo all the metas after lunch.
[11:35] <ginggs> infinity: yup, and i've sync'd that and re-run the tests, but there is still a failure (that appeared on the same date)
[11:35] <infinity> Fun.
[11:39] <infinity> ginggs: If you're positive it's not a regression from 2.4.2-2, yeah, we can badtest it for now.
[11:40] <ginggs> infinity: how can i make 100% sure?
[11:40] <infinity> Run the same tests with the same triggers, except for the r-bioc-annotationhub versions, and compare?
[11:42] <ginggs> do you mean on the ubuntu autopkgtest infra, or locally?
[11:44] <ginggs> infinity: i think http://autopkgtest.ubuntu.com/packages/r/r-bioc-annotationhub/zesty/amd64 confirms it - autopkgtests haven't passed since 2017-01-16
[11:45] <infinity> ginggs: Except while I see 404s in the old tests, I see something very different in new tests?
[11:47] <infinity> ginggs: And, indeed, the new failure seems specific to the migration being attempted.
[11:47] <ginggs> infinity: yes, the 404 is gone, but it is the same test that still fails - FAILURE in test_tidyGRanges: Error in checkIdentical(setNames(rep(c(FALSE, TRUE), c(4, 1)), chr), GenomeInfoDb::isCircular(gr1)) :
[11:48] <infinity> Or maybe the underlying library just doesn't bubble up the 404s anymore.
[11:48] <infinity> Which would be annoying.
[11:48] <infinity> Meh.  I'm going to run 2.4.2-2 with a self-trigger to be sure.
[11:48] <ginggs> infinity: ok, thanks
[12:05] <xnox> infinity, https://code.launchpad.net/~xnox/unity/no-more-upstart-dep/+merge/322283
=== marcusto_ is now known as marcustomlinson
[12:30] -queuebot:#ubuntu-release- Unapproved: apport (zesty-proposed/main) [2.20.4-0ubuntu3 => 2.20.4-0ubuntu4] (core)
[12:31] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-mate-settings [source] (zesty-proposed) [17.04.7]
[12:32] -queuebot:#ubuntu-release- Unapproved: accepted apport [source] (zesty-proposed) [2.20.4-0ubuntu4]
[12:36] -queuebot:#ubuntu-release- Unapproved: accepted base-files [source] (zesty-proposed) [9.6ubuntu13]
[12:39] <jbicha> I'm rebuilding the GNOME iso's to verify the ubiquity theme fix
[13:06] -queuebot:#ubuntu-release- Unapproved: libphysfs (zesty-proposed/universe) [2.0.3-4 => 2.0.3-5] (no packageset) (sync)
[13:07] -queuebot:#ubuntu-release- Unapproved: accepted libphysfs [sync] (zesty-proposed) [2.0.3-5]
[13:11] <infinity> jbicha: Kay.  There will be a mass rebuild later today, but that's fine.
[13:14] <jbicha> right, I just wanted to make sure that if there was a problem, I didn't wait until the last moment!
[13:15] -queuebot:#ubuntu-release- Builds: Ubuntu GNOME Desktop amd64 [Zesty Final] has been updated (20170410)
[13:15] -queuebot:#ubuntu-release- Builds: Ubuntu GNOME Desktop i386 [Zesty Final] has been updated (20170410)
[13:15] <infinity> jbicha: A noble goal.
[13:16] -queuebot:#ubuntu-release- Unapproved: command-not-found (zesty-proposed/main) [0.3ubuntu17.04.1 => 0.3ubuntu17.04.2] (core)
[13:18] -queuebot:#ubuntu-release- Unapproved: mate-panel (zesty-proposed/universe) [1.18.1-0ubuntu1 => 1.18.1-0ubuntu2] (ubuntu-mate, ubuntukylin)
[13:19] -queuebot:#ubuntu-release- Unapproved: labplot (zesty-proposed/universe) [2.3.0-2ubuntu1 => 2.3.0-2ubuntu2] (kubuntu)
=== jgrimm-away is now known as jgrimm
[13:20] -queuebot:#ubuntu-release- Unapproved: twisted (zesty-proposed/main) [16.6.0-2 => 16.6.0-2ubuntu1] (kubuntu, ubuntu-desktop, ubuntu-server) (sync)
[13:21] -queuebot:#ubuntu-release- Unapproved: txzmq (zesty-proposed/universe) [0.7.4-1 => 0.7.4-1ubuntu1] (no packageset) (sync)
[13:21] -queuebot:#ubuntu-release- Unapproved: accepted txzmq [sync] (zesty-proposed) [0.7.4-1ubuntu1]
[13:24] <infinity> jbicha: FYI, that chrome-gnome-shell oops looks fixed now.
[13:29] -queuebot:#ubuntu-release- Unapproved: libmatekbd (zesty-proposed/universe) [1.18.1-0ubuntu1 => 1.18.2-0ubuntu1] (ubuntu-mate, ubuntukylin)
[13:33] <infinity> rbasak: Does anyone care that the ppc64el server ISO is 5MB over CD size?
[13:34] <rbasak> powersj: ^
[13:35] <infinity> rbasak: He usually submits MPs to change the limit, I was asking if you wanted to change seeds to trim the size. :P
[13:36] <rbasak> I don't know. powersj may know better if we care :)
[13:36] <infinity> Fair enough.
[13:37] <rbasak> Or jgrimm may also know if we care ^
[13:37] -queuebot:#ubuntu-release- Unapproved: gnome-logs (zesty-proposed/universe) [3.24.0-0ubuntu1 => 3.24.1-0ubuntu1] (ubuntugnome)
[13:37]  * rbasak knows little about the ppc64el install process
[13:37] <jgrimm> infinity, rbasak yeah i was just starting to type
[13:37] <jgrimm> TL;DR we don't care
[13:38] <infinity> rbasak: Well, the "process" is the same as most places.  In that real sysadmins use netboot of some sort, but they *can* boot optical media too.
[13:38] <infinity> We could fix this if IBM fixed their machines to love compressed kernels.
[13:38] <infinity> (The giant kernels are why it's always larger than x86)
[13:39] <infinity> jgrimm: Not caring works for me.
[13:40] <jgrimm> we'll still 'monitor' for crazy growth that indicates something wildly has gone wrong, but no longer the specific size tied to CD media
[13:42] <infinity> jgrimm: Mmkay.
[14:04] -queuebot:#ubuntu-release- Unapproved: ubuntu-mate-meta (zesty-proposed/universe) [1.189 => 1.190] (ubuntu-mate)
[14:05] -queuebot:#ubuntu-release- Unapproved: ubuntu-meta (zesty-proposed/main) [1.378 => 1.379] (core)
[14:05] -queuebot:#ubuntu-release- Unapproved: xubuntu-meta (zesty-proposed/universe) [2.212 => 2.213] (xubuntu)
[14:05] -queuebot:#ubuntu-release- Unapproved: ubuntustudio-meta (zesty-proposed/universe) [0.167 => 0.168] (ubuntustudio)
[14:07] <infinity> seb128: Langpacks?
[14:13] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-mate-meta [source] (zesty-proposed) [1.190]
[14:13] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-meta [source] (zesty-proposed) [1.379]
[14:14] -queuebot:#ubuntu-release- Unapproved: accepted ubuntustudio-meta [source] (zesty-proposed) [0.168]
[14:15] -queuebot:#ubuntu-release- Unapproved: rejected twisted [sync] (zesty-proposed) [16.6.0-2ubuntu1]
[14:15] -queuebot:#ubuntu-release- Unapproved: accepted xubuntu-meta [source] (zesty-proposed) [2.213]
[14:18] <apw> infinity, you want that command-not-found "reviewed" ?
[14:18] <infinity> apw: Please.
[14:18] -queuebot:#ubuntu-release- Unapproved: accepted mate-panel [source] (zesty-proposed) [1.18.1-0ubuntu2]
[14:19] -queuebot:#ubuntu-release- Unapproved: twisted (zesty-proposed/main) [16.6.0-2 => 16.6.0-2ubuntu1] (kubuntu, ubuntu-desktop, ubuntu-server)
[14:19] <Laney> Review each line explicitly please
[14:20] -queuebot:#ubuntu-release- Unapproved: accepted gnome-logs [source] (zesty-proposed) [3.24.1-0ubuntu1]
[14:20] -queuebot:#ubuntu-release- Unapproved: accepted libmatekbd [source] (zesty-proposed) [1.18.2-0ubuntu1]
[14:20] -queuebot:#ubuntu-release- Unapproved: accepted labplot [source] (zesty-proposed) [2.3.0-2ubuntu2]
[14:22] -queuebot:#ubuntu-release- Unapproved: accepted twisted [source] (zesty-proposed) [16.6.0-2ubuntu1]
[14:26] -queuebot:#ubuntu-release- Unapproved: accepted command-not-found [source] (zesty-proposed) [0.3ubuntu17.04.2]
[14:27] <infinity> apw: Did you read every line of that diff?
[14:27] <infinity> apw: I have my doubts.
[14:28] <apw> infinity, i grepped out the -powerpc, the ripped the 'same lines' diff from movement, and eyeballed the rest
[14:28] <apw> it seemed sane
[14:29] <apw> some movement to univere, some commands dropped and some added in line with waht i expected
[14:30] <apw> (plus i started before i offered :))
[14:30] <apw> but, i may have not read every line as well as Laney would have
[14:31] <infinity> apw: We're just messing with you. :P
[14:32] <apw> infinity, :)
[14:32] <apw> infinity,
[14:40] -queuebot:#ubuntu-release- Builds: Netboot amd64 [Zesty Final] (20101020ubuntu504) has been added
[14:40] -queuebot:#ubuntu-release- Builds: Netboot arm64 [Zesty Final] (20101020ubuntu504) has been added
[14:40] -queuebot:#ubuntu-release- Builds: Netboot armhf [Zesty Final] (20101020ubuntu504) has been added
[14:40] -queuebot:#ubuntu-release- Builds: Netboot i386 [Zesty Final] (20101020ubuntu504) has been added
[14:41] -queuebot:#ubuntu-release- Builds: Netboot ppc64el [Zesty Final] (20101020ubuntu504) has been added
[14:41] -queuebot:#ubuntu-release- Builds: Netboot s390x [Zesty Final] (20101020ubuntu504) has been added
[14:59] -queuebot:#ubuntu-release- Unapproved: ubiquity-slideshow-ubuntu (zesty-proposed/main) [123 => 124] (kubuntu, ubuntu-desktop)
[15:07] <infinity> cyphermox: Did the s/Muon Discover/Discover/ change not suffer the same msgid invalidation problem?
[15:07] <cyphermox> am I not Derpy McDerpface?
[15:08] <infinity> You might be.  Are you?
[15:08] <cyphermox> looks that way
[15:08] <cyphermox> derpty derp .
[15:08] <infinity> Shall I reject?
[15:08] <cyphermox> yeah, I'll go touch it again
[15:08] <cyphermox> right after the DMB meeting
[15:09] -queuebot:#ubuntu-release- Unapproved: rejected ubiquity-slideshow-ubuntu [source] (zesty-proposed) [124]
[16:25] -queuebot:#ubuntu-release- Unapproved: ubiquity-slideshow-ubuntu (zesty-proposed/main) [123 => 124] (kubuntu, ubuntu-desktop)
[16:39] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity-slideshow-ubuntu [source] (zesty-proposed) [124]
[16:40] -queuebot:#ubuntu-release- Unapproved: wxpython3.0 (zesty-proposed/universe) [3.0.2.0+dfsg-3 => 3.0.2.0+dfsg-3ubuntu1] (edubuntu)
[16:50] <apw> ^ that really ought to have a bug# so it can be an SRU
[16:58] -queuebot:#ubuntu-release- Unapproved: accepted wxpython3.0 [source] (zesty-proposed) [3.0.2.0+dfsg-3ubuntu1]
[17:21] -queuebot:#ubuntu-release- Unapproved: poedit (zesty-proposed/universe) [2.0-1~exp1 => 2.0.1-1~exp1~build1] (no packageset)
[17:22] -queuebot:#ubuntu-release- Unapproved: accepted poedit [source] (zesty-proposed) [2.0.1-1~exp1~build1]
[17:23] -queuebot:#ubuntu-release- Unapproved: gui-ufw (zesty-proposed/universe) [17.04.1-1 => 17.04.1-1ubuntu1] (ubuntu-mate)
[17:36] <LocutusOfBorg> apw, you right :) unfortunately this has been an omygodkitten issue, so I did it quick
[17:36] <LocutusOfBorg> anyhow, a bug report is on Debian BTS now https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860043
[17:36] <ubot5> Debian bug 860043 in src:wxpython3.0 "" [Important,Open]
[17:37] <LocutusOfBorg> (I read irclogs when possible, don't rely on it :) )
[17:38]  * LocutusOfBorg leaves, he is on train
=== bregma__ is now known as bregma
=== timp is now known as t1mp
[18:20] -queuebot:#ubuntu-release- Unapproved: content-hub (zesty-proposed/main) [0.3+17.04.20170317.1-0ubuntu1 => 0.3+17.04.20170403-0ubuntu1] (kubuntu, ubuntu-desktop) (sync)
[19:01] -queuebot:#ubuntu-release- Unapproved: tomcat8 (xenial-proposed/main) [8.0.32-1ubuntu1.3 => 8.0.32-1ubuntu1.4] (kubuntu, ubuntu-desktop, ubuntu-server)
[19:01] -queuebot:#ubuntu-release- Unapproved: tomcat8 (zesty-proposed/main) [8.0.38-2ubuntu1 => 8.0.38-2ubuntu2] (kubuntu, ubuntu-desktop, ubuntu-server)
[19:09] -queuebot:#ubuntu-release- Unapproved: epiphany-browser (zesty-proposed/universe) [3.24.0-0ubuntu2 => 3.24.1-0ubuntu1] (desktop-extra)
[19:14] -queuebot:#ubuntu-release- Unapproved: tomcat8 (yakkety-proposed/main) [8.0.37-1ubuntu0.1 => 8.0.37-1ubuntu0.2] (kubuntu, ubuntu-desktop, ubuntu-server)
[19:17] -queuebot:#ubuntu-release- Unapproved: cockpit (zesty-proposed/universe) [137-3 => 138-1] (no packageset) (sync)
[19:17] -queuebot:#ubuntu-release- Unapproved: accepted cockpit [sync] (zesty-proposed) [138-1]
[19:37] <xnox> my laptop did something really weird
[19:37] <xnox> ext4 started to detect journal errors and filesystem got remounted readonly
[19:37] <xnox> and from that point onwards I am enable to run df or gain root via sudo
[19:37] <xnox> all results in input/output errors
[19:37] <xnox> rebooting now.....
[19:38] <xnox> however, this is quite old kernel, not 4.10 =/
[19:43] <Bashing-om> xnox: Off topic for this channel . Suggest ya seek support in your OS channel .
[19:47]  * ogra_ lols
[19:51] -queuebot:#ubuntu-release- New sync: ms-gsl (zesty-proposed/primary) [0~git20170403.ebab8ca-1]
[20:11] -queuebot:#ubuntu-release- Unapproved: gnome-shell-extension-dashtodock (zesty-proposed/universe) [57-1 => 57-1ubuntu1] (no packageset)
[20:12] -queuebot:#ubuntu-release- Unapproved: accepted gnome-shell-extension-dashtodock [source] (zesty-proposed) [57-1ubuntu1]
[20:15] <slangasek> infinity, seb128: based on conversation with cyphermox, I understand that at least part of why we get so many bug reports on shim-signed related to debconf prompts not happening is that the gnome frontend is still broken by default due to missing libgtk2-perl.  This is not an opportune time to discover this vs. release, but the problem affects older releases also and will need SRUed. opinions on
[20:15] <slangasek> seeding libgtk2-perl onto ubuntu-desktop for 17.04?
[20:15] <slangasek> infinity, seb128: this makes a difference in the UX of installing dkms packages (nvidia) from the liveCD, so seems worth pushing in
[20:16] <cyphermox> assuming we get another respin, seems like a relatively easy and safe fix?
[20:18] <slangasek> I'm not asking about including it opportunistically, I'm asking about committing to a respin for this issue
[20:18] <seb128> slangasek, no objection in principle from me, did anyone check if that would pull in other things as well? (we still have gtk2 on the iso so that's ok)
[20:18] <slangasek> Depends: libatk1.0-0 (>= 1.12.4), libc6 (>= 2.14), libcairo2 (>= 1.2.4), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.24.0), libgtk2.0-0 (>= 2.24.0), libpango-1.0-0 (>= 1.18.0), libpangocairo-1.0-0 (>= 1.14.0), perl (>= 5.22.2-1), perlapi-5.22.2, libcairo-perl, libglib-perl (>= 3:1.280), libpango-perl, shared-mime-info
[20:19] <cyphermox> slangasek: I understand that, what I'm saying is it's a moot point if we already are going to respin. my opinion in this case isn't gospel, but I'd respin
[20:19] <seb128> so basically that gtk-perl bindings stack, which is probably small enough
[20:20] <seb128> I don't have data to know if that's worth a respin though, so letting that decision to others
[20:21] <seb128> installing nvidia drivers in a live session doesn't seem an important usecase to me at least
[20:21] <slangasek> isn't the common case that if you're going to install nvidia drivers, you do it during the install?
[20:24] <slangasek> thinking further, maybe this should be a dep of ubuntu-software instead of directly seeded
[20:25] <dmj_s76> When upgrading from 16.10 to 17.04 the nvidia dkms modules don't get rebuilt.
[20:25] <slangasek> that impacts ubuntukylin (and would impact edubuntu)
[20:26] <slangasek> dmj_s76: have you filed a bug report with upgrade logs?
[20:27] <dmj_s76> slangasek: Not yet, we just identified this now.
[20:27] <slangasek> ok
[20:27] <seb128> I don't have nvidia hardware so I don't know how the installer is dealing with those, I know you can enable them from software-properties on an installed system though
[20:27] <dmj_s76> The end result is that there are dkms modules for 4.8 but not 4.10 installed.
[20:27] <seb128> cyphermox, ^ do you know what the installer is doing?
[20:29] <cyphermox> seb128: afaik it's running ubuntu-drivers uninteractively, to get the list of packages to install towards the end of the install process
[20:29] <cyphermox> (when you click "Install third-party drivers"
[20:29] <seb128> so what wouldn't work without libgtk2-perl?
[20:29] <slangasek> seb128: installing nvidia drivers through the gui on a machine that has SecureBoot enabled will blow up
[20:30] <cyphermox> but the installer is "special" in that if you can fallback to Dialog if necessary (given that you have a shell window under the slideshow) and possibly a bit more is done to go uninteractively.
[20:30] <slangasek> falling back to Dialog is horrendous
[20:30] <seb128> slangasek, k, that seems worth a respin indeed
[20:30] <cyphermox> (and furthermore, the default if secure boot is detected is to try to convince the user to set a password for mokutil)
[20:30] <slangasek> if it falls back to dialog, it won't crash on install
[20:31] <cyphermox> slangasek: I have never seen an install fallback to anything
[20:31] <seb128> so that issue is in the LTS and nobody investigated until now?
[20:31] <cyphermox> I think in that case it runs uninteractive
[20:31] <jackpot51> cyphermox: We are talking about `update-manager`, not the installer
[20:31] <dmj_s76> slangasek: Are you guys talking about a separate nvidia issue here?
[20:31] <slangasek> seb128: it's a new consequence of the changes to enforce kernel module signing in the secureboot policy
[20:31] -queuebot:#ubuntu-release- Unapproved: gnome-software (zesty-proposed/main) [3.22.7-0ubuntu2 => 3.22.7-0ubuntu3] (ubuntu-desktop)
[20:32] <jackpot51> cyphermox: `nvidia-375` is installed, then `update-manager -d`, then after reboot the nvidia driver does not load
[20:32] <seb128> slangasek, ok, thanks for the details, so yeah +1 from me to respin with libgtk2-perl
[20:32] <slangasek> cyphermox, seb128: ok, I forgot that this is integrated in ubiquity itself, which means the installer doesn't depend on the debconf gnome frontend for prompting... so now it seems to me maybe we /don't/ need it in 17.04 images
[20:32] <cyphermox> jackpot51: seb128 asked with the words "installer"
[20:33] <slangasek> jackpot51, dmj_s76: you've joined a conversation already in progress that has nothing to do with the upgrade bug you're talking about
[20:33] <jackpot51> ok
[20:33] <dmj_s76> ah, okay...now that makes sense
[20:34] <cyphermox> slangasek: why? isn't it still needed that drivers recommends libgtk2-perl or something?
[20:36] <slangasek> cyphermox: why is that not SRUable?
[20:36] <Bashing-om> seb128: Ya need a ginny pig ? I do have a 17.04 install on a nVidia GT710 card running the nouveau driver . I could reboot and see what results in installing the proprietary driver .
[20:36] <cyphermox> slangasek: oh, it most definitely is; it's just going to be ugly for the installs without network that can't get updates
[20:36] <slangasek> cyphermox: if that debconf prompt is not used in the installer path, even for 'install third-party drivers', it seems a post-release update is fine
[20:37] <cyphermox> I don't think there are very many network drivers depending on dkms
[20:37] <seb128> Bashing-om, thanks, unsure if that's needed, seems people have a good understanding of the problem and when it's an issue
[20:37] <slangasek> cyphermox: right, I think the practical impact of that is nil
[20:38] <cyphermox> slangasek: I think we'll get in a state where the system is installable for most cases; but maybe not all that usable
[20:38] <cyphermox> yes, it's a very small portion of users
[20:38] <cyphermox> only r8168-dkms comes to mind, assuming that's still relevant.
[20:38] <Bashing-om> seb128: K; I do little enough to help .. So I help where I can :)
[20:39] <cyphermox> slangasek: that *might* impact willcooke, if I remember well; could be worth asking him how he does his installs.
[20:39] <cyphermox> (so we know if we're completely forgetting something important)
[20:43] <slangasek> cyphermox: ah - I assumed the set of dkms network drivers in the archive was zero.  If it's not, I think that's sufficient justification for a respin
[20:44] <cyphermox> it's definitely non-zero
[20:44] <cyphermox> I see rtl8812au-dkms too which I don't particularly care about, but I have hardware that requires it
[20:44] <cyphermox> it's some wireless dongle
[20:45] <cyphermox> oh, and broadcom-sta-dkms
[20:46] <cyphermox> I think it will need to be there; STA used to be required for quite a bunch of people.
[20:50] <slangasek> so, if I fix this properly, it's a new Recommends: on gnome-software; that impacts lubuntu, ubuntustudio, ubuntukylin, ubuntu-budgie, xubuntu in addition to ubuntu
[20:51] <cyphermox> on gnome-software?
[20:51] <slangasek> yes
[20:51] <cyphermox> seems odd; but ok
[20:51] <slangasek> ubuntu-software is just a thin layer around gnome-software, it's gnome-software that has the dep on aptdaemon
[20:52] <jbicha> slangasek: gnome-software isn't the right place, maybe software-properties-common?
[20:52] <cyphermox> I don't think we're talking about the same thing
[20:52] <jbicha> I don't believe gnome-software supports debconf
[20:53] <slangasek> jbicha: gnome-software depends on aptdaemon without providing it a frontend
[20:53] <cyphermox> it shouldn't have to
[20:53] <slangasek> jbicha: this isn't an aptdaemon bug, because aptdaemon doesn't know /which/ gui toolkit frontend you want; that's a property of whatever depends on aptdaemon
[20:53] <jbicha> software-properties-gtk also depends on aptdaemon
[20:54] <slangasek> yes, and that package should *also* Recommends: libgtk2-perl
[20:54] <cyphermox> jbicha: gnome-software still probably ought to pull the package in, because you *might* install some dkms package from there.
[20:55] <jbicha> because I'm pretty sure that you can't install NVIDIA drivers using gnome-software/zesty but you can with software-properties-gtk
[20:55] <slangasek> this problem is not limited to software-properties-gtk
[20:55] <slangasek> jbicha: LP: #1679435
[20:55] <ubot5> Launchpad bug 1679435 in gnome-software (Ubuntu) "installing dkms package from software-center, no debconf frontend: package shim-signed 1.27~16.10.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1" [Critical,Triaged] https://launchpad.net/bugs/1679435
[20:55] <slangasek> should fix the title though, since it's not actually "software center" being used :P
[20:56] <cyphermox> slangasek: what of things that use packagekit instead? do we care?
[20:56] <cyphermox> uh-oh, frozen
[20:56] <slangasek> cyphermox: which are those?
[20:56] <jbicha> I think we're miscommunicating there; I don't think anything available in gnome-software uses dkms and I don't believe gnome-software supports debconf at all
[20:56] <cyphermox> slangasek: I'm not sure, I thought there was
[20:58] -queuebot:#ubuntu-release- Unapproved: rejected gnome-software [source] (zesty-proposed) [3.22.7-0ubuntu3]
[20:58] -queuebot:#ubuntu-release- Unapproved: gnome-software (zesty-proposed/main) [3.22.7-0ubuntu2 => 3.22.7-0ubuntu3] (ubuntu-desktop)
[21:01] <cyphermox> slangasek: jbicha seems to have a point; it doesn't look like you can pick a dkms package to install via Software.
=== acheronuk is now known as acheronUK
[21:02] <cyphermox> maybe I'm doing this wrong though; but quick searches when it does work don't turn up anything useful; I tried "dkms", "broadcom", "driver"...
[21:02] <slangasek> cyphermox, jbicha: virtualbox. QED
[21:02] <slangasek> as detailed in the bug I linked
[21:02] <cyphermox> oh, of course.
[21:03] <jbicha> ok, but my second concern is whether gnome-software supports debconf
[21:03] <cyphermox> jbicha: it doesn't have to
[21:03] <slangasek> I don't know what you think that means
[21:03] <slangasek> it is inexcusable for a frontend for installing Debian packages to NOT support debconf
[21:04] <jbicha> please file a bug then
[21:04] <infinity> "suporting debconf" is probably just a question of having libgtk-perl installed.
[21:04] <slangasek> to be clear, you're right that gnome-software doesn't install drivers and therefore it's not release-critical to fix gnome-software for 17.04.  But if we're respinning anyway we could as well fix both
[21:04] <infinity> Maybe.
[21:04] <jbicha> I had this problem when working on the steam/zesty package where I had to drop the mandatory debconf question
[21:04] <slangasek> jbicha: like the one I linked to above already?
[21:05] <slangasek> infinity: yes, that's basically how I'm solving it (one package in queue, another in progress now)
[21:06] <infinity> slangasek: Mmkay.
[21:07] <slangasek> infinity: so you had respins planned anyway? cool
[21:07] <infinity> slangasek: Yeah.  Was waiting for all the unblocks in the stack to wind through, final langpacks seb gave us earlier today, etc.
[21:10] -queuebot:#ubuntu-release- Unapproved: accepted gnome-software [source] (zesty-proposed) [3.22.7-0ubuntu3]
[21:10] -queuebot:#ubuntu-release- Unapproved: accepted gui-ufw [source] (zesty-proposed) [17.04.1-1ubuntu1]
[21:13] <slangasek> infinity: software-properties also uploaded
[21:13] -queuebot:#ubuntu-release- Unapproved: software-properties (zesty-proposed/main) [0.96.24.11 => 0.96.24.12] (desktop-core, ubuntu-server)
[21:14] -queuebot:#ubuntu-release- Unapproved: accepted content-hub [sync] (zesty-proposed) [0.3+17.04.20170403-0ubuntu1]
[21:15] -queuebot:#ubuntu-release- Unapproved: accepted epiphany-browser [source] (zesty-proposed) [3.24.1-0ubuntu1]
[21:15] -queuebot:#ubuntu-release- Unapproved: accepted software-properties [source] (zesty-proposed) [0.96.24.12]
[21:15] <cyphermox> slangasek: the gnome-software change makes sense, but did it work for you?
[21:15] <cyphermox> because http://imgur.com/a/6qqkP
[21:16] <cyphermox> disregard the "Secure Boot not enabled" message, I hacked the script to run anyway -- this is because my desktop does EFI but not Secure Boot.
[21:16] <jbicha> yes, that's similar to what I saw with steam
[21:16] <slangasek> well
[21:17] <slangasek> yeah, perhaps there are other problems here
[21:17] <cyphermox> (but that's a bug in gnome-software anyway)
[21:17] <slangasek> and no, I didn't actually test it
[21:17] <slangasek> how is it a bug in gnome-software?
[21:17] <cyphermox> not properly setting a frontend?
[21:18] <cyphermox> (or running non-interactively here)
[21:18] <jbicha> to me, it's unclear whether gnome-software not supporting debconf is a design decision or a bug
[21:18] <infinity> Design decisions can also be bugs.
[21:19] <infinity> Anyhow, I'm going to let you guys sort this out for a bit, I'll be back in 1.5 hours or so to see the state of proposed and start respins once I massage it to how I like before bed.
[21:19] <cyphermox> probably more an oversight, because most developers working on Software are probably more used to RPM distros, I suppose.
[21:19] <infinity> slangasek: Feel free to self-accept followups, so long as you get a positive review from someone sane.
[21:19] <cyphermox> but I'm just guessing, I have no idea
[21:20] <Laney> I think you can call setDebconfFrontend or something on aptdaemon transactions
[21:20] <jbicha> is it mandatory to show debconf prompts? or is the bug in the package that won't install completely without answering a debconf question?
[21:20] <Laney> FYI
[21:20] <slangasek> infinity: check.  if we miss the 1.5 window, feel free to throw the respin list to me
[21:20] <slangasek> Laney: any chance you can point me to an example?
[21:21] <cyphermox> jbicha: any software may ask debconf questions; for things it needs to know to properly install -- for instance MAAS will ask you for some details about your setup
[21:21] <slangasek> Laney: n/m, I should obviously be looking at update-manager
[21:21] <slangasek> Laney: thanks
[21:21] <slangasek>         yield trans.set_debconf_frontend("gnome")
[21:24] <jbicha> cyphermox: right, but does it cause problems if it doesn't get an answer?
[21:24] <Laney> NFI if that makes aptdaemon magically work or not though
[21:25] <jbicha> I tried looking through Debian Policy earlier about this issue, but I couldn't find a clear guideline
[21:26] <slangasek> cyphermox, Laney: software-properties reuploaded, setting the debconf frontend; anyone have a good way to test this?
[21:26] -queuebot:#ubuntu-release- Unapproved: software-properties (zesty-proposed/main) [0.96.24.12 => 0.96.24.13] (desktop-core, ubuntu-server)
[21:27] <cyphermox> jbicha: you might get exactly what you saw before with update-secureboot-policy, crash or other kind of failure because it's non-interactive, or it might work because of sensible defaults, priority, etc.
[21:27] <cyphermox> slangasek: nvidia?
[21:27] <cyphermox> I'm not sure I still have hardware to test that
[21:29] <slangasek> cyphermox: yes, I don't either; only nvidia box here is non-UEFI, that's why I was talking earlier about putting together a test case
[21:30] <jbicha> slangasek: isn't installing VBox the test case on a clean UEFI install?
[21:30] <cyphermox> yeah, I figured
[21:30] <cyphermox> jbicha: that won't allow you to test software-properties, it only knows about modaliases
[21:30] <slangasek> jbicha: for gnome-software, but not for software-properties - check
[21:30] <jbicha> ok
[21:30] <slangasek> so I'm going to work up a test ppa for all of this
[21:31] <cyphermox> slangasek: short of uploading a fake driver that does dkms, that could be recognized by software-properties, I can't think of a way
[21:31] <slangasek> in the meantime, if someone could test that software-properties still DTRT on a *non* UEFI box, that would be good
[21:31] <cyphermox> fortunately, that fake driver part is not too hard
[21:31] <slangasek> because I made that code change totally blind
[21:31] <cyphermox> yeah
[21:31] <slangasek> cyphermox: do you have anything you can test on for the non-SB case?
[21:32] <cyphermox> maybe, need to go upstairs look at my wife's machine
[21:35] <tsimonq2> infinity: When we have the new codename, I call dibs on creating all the new wiki pages (like I've done for the past 3 or 4 releases :P).
[21:36] <slangasek> dmj_s76, jackpot51: is there a bug w/ logs yet for the nvidia dkms upgrade issue?
[21:36] <jackpot51> Yep, come to #ubuntu-devel to see
[21:36] <slangasek> ok; if another dev is working it now, I don't need to get in the middle :)
[21:36] <jackpot51> https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1681566
[21:36] <ubot5> Ubuntu bug 1681566 in ubuntu-release-upgrader (Ubuntu) "nvidia-375 DKMS module not recompiled on upgrade to 17.04" [Undecided,Confirmed]
[21:37] <jackpot51> Still, we could use more help
[21:37] <jackpot51> bdmurray is helping out
[21:38] <bdmurray> yeah, cause I'm not to sure what is up
[21:38] <bdmurray> slangasek: or because I'm reviewing cloud-init. ;-)
[21:39] <slangasek> yeah, but I'm head-down on a bugfix we're trying to land in the 17.04 image, which takes precedence over an upgrade issue
[21:39] <bdmurray> okay
[21:42] <dmj_s76> infinity: any ideas?
[21:45] <tsimonq2> Release team: any chance the Lubuntu team could get some help with bug 1681178? Is it just adding something to the seed, or is it more complex?
[21:46] <ubot5> bug 1681178 in lubuntu-meta (Ubuntu) "The alternate installer does not install man" [Undecided,New] https://launchpad.net/bugs/1681178
[21:46] <rbalint>  ginggs: i wrote a simple python script for generating autopkgtest rerun links: http://pastebin.ubuntu.com/24356986/
[21:47] <rbalint> ginggs: this is current output: http://pastebin.ubuntu.com/24357014/
[21:47] <rbalint> ginggs: could you please trigger those?
[21:48] <cyphermox> slangasek: yeah, I have a system that can probably test this
[21:53] <tsimonq2> cyphermox: Do you think we should be concerned about this? https://pad.lv/1667453
[21:53] <ubot5> Launchpad bug 1667453 in ubiquity (Ubuntu) "Lubuntu Zesty ubiquity welcome dialog not shown" [Undecided,New]
[21:56] -queuebot:#ubuntu-release- Unapproved: gnome-terminal (zesty-proposed/main) [3.20.2-1ubuntu7 => 3.20.2-1ubuntu8] (ubuntu-desktop)
[21:56] <cyphermox> tsimonq2: I don't know from that bug
[21:56] <cyphermox> I'll sync the world to my system and test this after dinner
[21:57] <bdmurray> cyphermox: which "this"?
[21:57] <cyphermox> bdmurray: tsimonq2's
[22:03] <tsimonq2> cyphermox: Thank you. :)
[22:08] <bdmurray> smoser: Is the change in bug 1665773 necessary if bug 1665694 is fixed?
[22:08] <ubot5> bug 1665773 in cloud-init (Ubuntu Xenial) "wrong configuration example for cc_set_passwords module" [Medium,Confirmed] https://launchpad.net/bugs/1665773
[22:08] <ubot5> bug 1665694 in cloud-init (Ubuntu Yakkety) "cc_set_passwords fails to change passwords specified as chpasswd['list'] in cloud-config" [Medium,Confirmed] https://launchpad.net/bugs/1665694
[22:15] <bdmurray> As I understand it either a list (the way it was supposed to be) or a string will work now and the docs are switching from string to list, while list was the original intent. So it seems strange to me to "fix" the docs.
[22:21] <bdmurray> Given that the documentation isn't wrong I'll let it in.
[22:22] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (yakkety-proposed) [0.7.9-90-g61eb03fe-0ubuntu1~16.10.1]
[22:25] <tsimonq2> bdmurray: Re: bug 1674796, what do you think the fix might be?
[22:25] <ubot5> bug 1674796 in lubuntu-default-settings (Ubuntu) "After alternate install two network applets show up" [Undecided,Confirmed] https://launchpad.net/bugs/1674796
[22:25] <tsimonq2> bdmurray: Any clue what the problem is internally?
[22:25] <bdmurray> tsimonq2: I don't know, sorry
[22:26]  * cyphermox -> dinner, bbl
[22:28] <fossfreedom> tsimonq2: in lubuntu do you run both a X11 system tray and an appindicator  in the panel ?
[22:29] <slangasek> ok what am I doing wrong here?
[22:29] <slangasek> db_fget "$question" seen
[22:29] <slangasek> if [ "$RET" = false ]; then
[22:29] <slangasek> [...]
[22:29] <slangasek> because I am certainly seeing the question immediately before this
[22:33] <slangasek> n/m, still not sure why it didn't work but found a workaround
=== coreycb is now known as coreycb_vaca
[22:46] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (xenial-proposed) [0.7.9-90-g61eb03fe-0ubuntu1~16.04.1]
[22:48] <tsimonq2> fossfreedom: I'm not 100% sure...
[22:49] <fossfreedom> tsimonq2: the reason for the question is that on Ubuntu Budgie we saw the same thing - sometime double network icons - the network-manager applet gets confused between appindicators and the system tray and shows two icons
[22:50] <fossfreedom> in the end I just coded around it - hid the network-manager appindicator version in our appindicator applet implementation
[22:51] <fossfreedom> anyway - may not be your issue - but just putting that bit of info out there.
[23:03] <tsimonq2> Ah ok :)
[23:12] -queuebot:#ubuntu-release- Unapproved: dovecot (zesty-proposed/main) [1:2.2.27-2ubuntu1 => 1:2.2.27-2ubuntu2] (ubuntu-server)
[23:21] <slangasek> hmm, well, I have an affirmative test of a debconf prompt through software-properties now (so, accepting); but my negative test passes even when libgtk2-perl is not installed
[23:21] -queuebot:#ubuntu-release- Unapproved: accepted software-properties [source] (zesty-proposed) [0.96.24.13]
[23:22] <slangasek> because debconf says "sure, I'm going to display that question, trust me"
[23:44] <infinity> tsimonq2: That "doesn't install man" bug is because your ISO's preseed doesn't include standard.
[23:45] <infinity> tsimonq2: I can fix that, but you'll also get recommends, which you hate :P
[23:45] <infinity> (Which might be why it wasn't done?)
[23:45] <tsimonq2> infinity: Didn't we talk about this a while back but somebody was supposed to do something? Rings a bell but isn't clear...
[23:45] <infinity> tsimonq2: It's hardly a new bug, though.
[23:46] <tsimonq2> infinity: Why does including the standard task bring in everything?
[23:47] <tsimonq2> infinity: And weren't we supposed to follow up the other week re: opening floodgates by bringing in all recommends?
[23:47] <infinity> tsimonq2: It's doesn't bring in "everything", it brings in all of the standard task.
[23:47] <infinity> tsimonq2: Which, if you look at "ubuntu-standard" is half recommends.
[23:48] <infinity> Oh.
[23:48] <tsimonq2> Oh?
[23:48] <infinity> But your livefses already install the whole task.
[23:48] <infinity> Not the package minus recommends.
[23:48] <infinity> So, meh.
[23:48] <tsimonq2> But we're talking Alternate, here, I think.
[23:48] <infinity> Yes.
[23:49] <infinity> I'm comparing behaviour.
[23:49]  * cyphermox -> back
[23:49] <tsimonq2> cyphermox: \o/
[23:49] <tsimonq2> cyphermox: Welcome back. :)
[23:51] <cyphermox> hey, I'm in a good mood, I have a Mille-feuille to boot :)
[23:51] <tsimonq2> infinity: Like I said, I think we had this discussion at one point and afaicr it led into "let's get alternate out of here" sooo :P
[23:51] <tsimonq2> cyphermox: :D
[23:53] <infinity> tsimonq2: Well, committed a fix anyway.
[23:54] <tsimonq2> infinity: Got a link? "fix" is kinda generic...
[23:54] <tsimonq2> infinity: Also, does this need a respin?
[23:58] <infinity> tsimonq2: The world is respinning shortly anyway.
[23:58] <wxl> oh noes
[23:59] <infinity> tsimonq2: And the link will be in the bug when the branch is mirror to the public copy.
[23:59] <infinity> wxl: "Oh noes"?  It's Monday. :P
[23:59] <tsimonq2> infinity: Oh, more last-minute low-level kernel thingies? :P
[23:59] <infinity> tsimonq2: No.
[23:59] <infinity> slangasek: How did your battle go?
[23:59] <tsimonq2> infinity: I was joking, but ok. :)