[01:04] <flexiondotorg> slangasek: I uploaded mate-desktop yesterday to fix a bug with upgrading.
[01:05] <flexiondotorg> It hasn't migrated out of proposed, I don't see anything in excuses.
[01:05] <flexiondotorg> Lots of user keep bumping into the issue this update fixes.
[01:06] <flexiondotorg> Any idea why it is not migrating from proposed?
[01:06] -queuebot:#ubuntu-release- New: accepted deal.ii [arm64] (bionic-proposed) [8.5.1-1]
[01:06] -queuebot:#ubuntu-release- New: accepted wxpython4.0 [arm64] (bionic-proposed) [4.0.1+dfsg-2]
[01:06] -queuebot:#ubuntu-release- New: accepted wxpython4.0 [i386] (bionic-proposed) [4.0.1+dfsg-2]
[01:06] -queuebot:#ubuntu-release- New: accepted wxpython4.0 [s390x] (bionic-proposed) [4.0.1+dfsg-2]
[01:06] -queuebot:#ubuntu-release- New: accepted wxpython4.0 [amd64] (bionic-proposed) [4.0.1+dfsg-2]
[01:06] -queuebot:#ubuntu-release- New: accepted wxpython4.0 [ppc64el] (bionic-proposed) [4.0.1+dfsg-2]
[01:06] -queuebot:#ubuntu-release- New: accepted wxpython4.0 [armhf] (bionic-proposed) [4.0.1+dfsg-2]
[01:06] -queuebot:#ubuntu-release- New: accepted deal.ii [amd64] (bionic-proposed) [8.5.1-1]
[01:06] -queuebot:#ubuntu-release- New: accepted deal.ii [s390x] (bionic-proposed) [8.5.1-1]
[01:06] -queuebot:#ubuntu-release- New: accepted deal.ii [ppc64el] (bionic-proposed) [8.5.1-1]
[01:07] <tsimonq2> flexiondotorg: The update output says that it makes gir1.2-mate-desktop uninstallable, on at minimum armhf.
[01:07] <slangasek> flexiondotorg: because it's not "correctly" replacing the package, when you are still building it from this same source package
[01:08] <slangasek> flexiondotorg: also, unversioned Breaks+Replaces is almost never correct; it's unversioned Conflicts+Replaces, or versioned Breaks+Replaces; see policy
[03:38] -queuebot:#ubuntu-release- New: accepted kubuntu-wallpapers [source] (bionic-proposed) [18.04.0]
[03:44] -queuebot:#ubuntu-release- New binary: kubuntu-wallpapers [amd64] (bionic-proposed/none) [18.04.0] (no packageset)
[04:09] -queuebot:#ubuntu-release- Unapproved: gnome-software (xenial-proposed/main) [3.20.5-0ubuntu0.16.04.8 => 3.20.5-0ubuntu0.16.04.10] (ubuntu-desktop)
[07:11] -queuebot:#ubuntu-release- Unapproved: ceph (artful-proposed/main) [12.2.2-0ubuntu0.17.10.1 => 12.2.4-0ubuntu0.17.10.1] (kubuntu, ubuntu-desktop, ubuntu-server)
[07:53] <didrocks> sil2100: hey! I know that seb128 opened the FFe, but I think he didn't suscribe the release team. As now, I want to upload the first components, I added more info and suscribe the team on bug #1755456. Do you mind having a look?
[07:55] <sil2100> didrocks: hey! Sure
[07:55] <didrocks> thanks :)
[08:12] <sil2100> didrocks: approved
[08:13] <sil2100> (why soo laaatee?!)
[08:13] <didrocks> sil2100: because the request was after FF already
[08:13] <didrocks> (so not even started developping)
[08:13] <didrocks> thanks!
[08:38] <juliank> I guess I'll fix adequate to not fail autopkgtest
[08:50] <juliank> the fix was trivial: inserting a ? in a regesx
[08:51] <juliank> (ldd removed a comma in its output for undefined symbols, hence I added a ? after the comma in the regex :D)
[10:25] -queuebot:#ubuntu-release- New source: ubuntu-report (bionic-proposed/primary) [1.0.0]
[10:27] -queuebot:#ubuntu-release- New: accepted ubuntu-report [source] (bionic-proposed) [1.0.0]
[10:29] -queuebot:#ubuntu-release- New binary: ubuntu-report [s390x] (bionic-proposed/none) [1.0.0] (no packageset)
[10:30] -queuebot:#ubuntu-release- New binary: ubuntu-report [amd64] (bionic-proposed/none) [1.0.0] (no packageset)
[10:30] -queuebot:#ubuntu-release- New binary: ubuntu-report [ppc64el] (bionic-proposed/none) [1.0.0] (no packageset)
[10:30] -queuebot:#ubuntu-release- New binary: ubuntu-report [i386] (bionic-proposed/none) [1.0.0] (no packageset)
[10:31] -queuebot:#ubuntu-release- New binary: ubuntu-report [arm64] (bionic-proposed/none) [1.0.0] (no packageset)
[10:31] -queuebot:#ubuntu-release- New binary: ubuntu-report [armhf] (bionic-proposed/none) [1.0.0] (no packageset)
[10:37] -queuebot:#ubuntu-release- New: accepted ubuntu-report [amd64] (bionic-proposed) [1.0.0]
[10:37] -queuebot:#ubuntu-release- New: accepted ubuntu-report [armhf] (bionic-proposed) [1.0.0]
[10:37] -queuebot:#ubuntu-release- New: accepted ubuntu-report [ppc64el] (bionic-proposed) [1.0.0]
[10:37] -queuebot:#ubuntu-release- New: accepted ubuntu-report [arm64] (bionic-proposed) [1.0.0]
[10:37] -queuebot:#ubuntu-release- New: accepted ubuntu-report [s390x] (bionic-proposed) [1.0.0]
[10:37] -queuebot:#ubuntu-release- New: accepted ubuntu-report [i386] (bionic-proposed) [1.0.0]
[11:13] <acheronuk> apw or anyone else: could the kubuntu-wallpapers binary be accepted please?
[11:26] <sil2100> acheronuk: let me take a look
[11:27] <sil2100> acheronuk: do you know who reviewed the source?
[11:27] <acheronuk> sil2100: slangasek did AFAIK
[11:28] <sil2100> Ok
[11:28] <sil2100> Looking at it now
[11:30] <sil2100> acheronuk: all good, done
[11:31] -queuebot:#ubuntu-release- New: accepted kubuntu-wallpapers [amd64] (bionic-proposed) [18.04.0]
[11:33] <acheronuk> sil2100: Great. Thank you. BTW, that is likely to be the last new source we need for 18.04, so could Kubuntu perhaps get a packageset update, once my bzr push to our seeds adding that registers?
[11:33] <acheronuk> well, if not last, we can motu others
[11:40] <sil2100> acheronuk: I did one in the morning today
[11:40] <sil2100> Ah
[11:40] <sil2100> Packageset!
[11:40] <sil2100> Sorry, mis-read
[11:40] <sil2100> Yeah
[11:40] <acheronuk> sil2100: yup
[11:41] <acheronuk> if it's convenient. no huge rush
[11:57] -queuebot:#ubuntu-release- Unapproved: accepted plymouth [source] (xenial-proposed) [0.9.2-3ubuntu13.3]
[12:06] -queuebot:#ubuntu-release- Unapproved: accepted xdg-user-dirs [source] (xenial-proposed) [0.15-2ubuntu6.16.04.1]
[13:11] -queuebot:#ubuntu-release- Unapproved: neutron (xenial-proposed/main) [2:8.4.0-0ubuntu7.2 => 2:8.4.0-0ubuntu7.3] (openstack, ubuntu-server)
[13:29] -queuebot:#ubuntu-release- Unapproved: libreoffice (artful-proposed/main) [1:5.4.5-0ubuntu0.17.10.5 => 1:5.4.6-0ubuntu0.17.10.1] (kubuntu, ubuntu-desktop)
[13:31] -queuebot:#ubuntu-release- Unapproved: libreoffice-l10n (artful-proposed/main) [1:5.4.5-0ubuntu0.17.10.1 => 1:5.4.6-0ubuntu0.17.10.1] (ubuntu-desktop)
[13:40] -queuebot:#ubuntu-release- Unapproved: neutron (artful-proposed/main) [2:11.0.3-0ubuntu1.1 => 2:11.0.3-0ubuntu2] (openstack, ubuntu-server)
[13:49] -queuebot:#ubuntu-release- Unapproved: cloud-init (artful-proposed/main) [17.2-35-gf576b2a2-0ubuntu1~17.10.2 => 18.2-0ubuntu1~17.10.1] (edubuntu, ubuntu-cloud, ubuntu-server)
[15:19] <sil2100> acheronuk: actually, since Final Beta is really close, could you regenerate the required bits from https://community.kde.org/Kubuntu/L10n ? If needed, of course
[15:30] <sil2100> acheronuk: also, I started https://help.ubuntu.com/community/BionicUpgrades - could you start preparing the Kubuntu version of the upgrade document?
[15:45] <slangasek> Laney: so I seem to have successfully received a test mail from autopkgtest-web/0
[15:46] <Laney> good
[15:47] -queuebot:#ubuntu-release- Unapproved: zfs-linux (xenial-proposed/main) [0.6.5.6-0ubuntu19 => 0.6.5.6-0ubuntu20] (no packageset)
[15:48] -queuebot:#ubuntu-release- Unapproved: zfs-linux (artful-proposed/main) [0.6.5.11-1ubuntu3.2 => 0.6.5.11-1ubuntu3.3] (core)
[15:49] <Laney> maybe if we just remove ssmtp from autopkgtest-cloud-worker/3 the juju configured postfix will take over and work
[15:50] <Laney> hmm that one doesn't have relayhost
[16:12] <acheronuk> sil2100: our language packs don't need regenerating in that fashion. they are a static tarball release
[16:13] <acheronuk> sil2100: ack on the upgrade wiki
[16:13] <sil2100> acheronuk: so the versions from 17th are all good for final beta?
[16:20] -queuebot:#ubuntu-release- New: accepted linux-gcp [amd64] (bionic-proposed) [4.15.0-1002.2]
[16:21] <acheronuk> sil2100: yes. in fact,most kde now ships translations with each individual source, and those l10n cover the small amount of left over things that haven't changed in a long time
[16:24] <sil2100> Excellent
[16:42] <cjwatson> Redeployed a bug-fixed version of the changes that broke the publisher yesterday, so keeping an eye on it.
[17:16] <doko> with ruby-debugger-ruby-core-source and subversion migrated, I'm removing ruby2.3 \o/
[17:17] <nacc> doko: nice!
[17:17] <slangasek> woohoo
[17:18] <doko> now get that node-js thing migrating ...
[17:20] <cjwatson> Publisher looks fine.
[17:21] <cjwatson> Just as well since I'm off out. :)
[17:23] -queuebot:#ubuntu-release- Unapproved: neutron (xenial-proposed/main) [2:8.4.0-0ubuntu7.2 => 2:8.4.0-0ubuntu7.3] (openstack, ubuntu-server)
[17:27] <doko> slangasek: the recent gcc-7 upload has the backport for the armhf build failure you mentioned last week. sorry, can't remember the package name, but you can revert that -O1 workaround
[17:36] <slangasek> doko: ok, I can't remember the package either ;)  I guess I'll look at -changes later to figure it out, thanks
[17:37] <ginggs> is it possible to remove node-is-glob 4.0.0-1 from proposed?  it seems to break a couple of things
[17:40] <ginggs> and I think node-policyfile/0.0.5-3ubuntu1 can be removed from release, it has no rdeps, and uses deprecated process.EventEmitter
[17:49] <slangasek> ginggs: node-is-glob: why do we consider this a bug in node-is-glob, as opposed to a bug in the things that have not been updated to be compatible with it?
[17:49] <slangasek> if the upstream answer is that the revdeps need to be updated, why not leave node-is-glob in -proposed until they're fixed (possibly next cycle)?
[17:50] <slangasek> (one possible valid answer is that node-is-glob should also then have versioned Breaks against prior versions of its old revdeps)
[17:52] <slangasek> ginggs: node-policyfile> the current autopkgtest failure seems to be more than just a deprecation issue.  is process.EventEmitter obsolete?  has its interface changed?  Should Debian bug #872894 have its severity raised?
[17:53] <ginggs> slangasek: re: node-policyfile first it was a warning, now it is a failure. so yes, I think the severity should be bumped
[17:55] <slangasek> ginggs: if you do so I will use that as the justification for removal from bionic
[17:56] <ginggs> slangasek: ok
[17:58] <ginggs> slangasek: re: is-glob I don't understand why node-glob-base, node-glob-parent and node-parse-glob autopkgtests are now pulling in node-is-glob from -proposed, which then fails
[18:09] <ginggs> slangasek: I bumped the severity of 872894
[18:10] <tsimonq2> doko: What was decided re: src:mercurial?
[18:13] <doko> tsimonq2: no idea, please see http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
[18:18] <tsimonq2> doko: You pinged me yesterday in #ubuntu-devel ...
[18:28] <doko> tsimonq2: no decision, however the autopkg tests still fail
[18:30] <tsimonq2> doko: Please remove it from proposed then.
[18:30] <ginggs> slangasek: node-glob-base, node-glob-parent and node-parse-glob upstreams all have issues open for months, with no progress
[18:33] <tsimonq2> slangasek: peruse> So, how might I do version numbers going forward until it's synced?
[18:39] -queuebot:#ubuntu-release- Unapproved: cloud-init (xenial-proposed/main) [17.2-35-gf576b2a2-0ubuntu1~16.04.2 => 18.2-0ubuntu1~16.04.1] (edubuntu, ubuntu-cloud, ubuntu-server)
[18:50] <slangasek> tsimonq2: sorry, I'm not sure I have context - last we talked about peruse was the private library, what's the versioning question?
[18:53] <tsimonq2> slangasek: Someone accepted it after I screwed up and uploaded a Debian version
[18:53] <tsimonq2> slangasek: Look at the version in Bionic.
[18:56] <slangasek> tsimonq2: ok, so next upload add in ubuntu1 to the versioning
[18:56] <slangasek> it'll still be "wrong" because it should really be 1.2+dfsg-0ubuntu1 instead of 1.2+dfsg-1ubuntu1, but it'll be less wrong
[18:58] <tsimonq2> slangasek: ack, thanks.
[19:28] -queuebot:#ubuntu-release- Unapproved: cloud-init (artful-proposed/main) [17.2-35-gf576b2a2-0ubuntu1~17.10.2 => 18.2-0ubuntu1~17.10.1] (edubuntu, ubuntu-cloud, ubuntu-server)
[19:31] <blackboxsw> arges: or rbasak: if there is time today we have a couple of queued uploads for artful and xenial proposed for cloud-init for a new SRU
[19:31] <blackboxsw> our new SRU bug is https://bugs.launchpad.net/cloud-init/+bug/1759318
[19:32] <blackboxsw> oops paste fail
[19:32] <blackboxsw> our new SRU for cloud-init is https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1759406
[20:32] -queuebot:#ubuntu-release- New sync: iotjs (bionic-proposed/primary) [1.0-1]
[21:17] <LocutusOfBorg> sigh, glib2.0 needs some care, I can't really reproduce locally
[21:17] <LocutusOfBorg> GLib-GIO:ERROR:../../../../../gio/tests/network-monitor.c:171:reach_cb: assertion failed (error == NULL): Host unreachable (g-io-error-quark, 37)
[21:17] <LocutusOfBorg> Bail out! GLib-GIO:ERROR:../../../../../gio/tests/network-monitor.c:171:reach_cb: assertion failed (error == NULL): Host unreachable (g-io-error-quark, 37)
[21:17] <LocutusOfBorg> FAIL: glib/network-monitor.test (Child process killed by signal 6)
[21:17] <LocutusOfBorg> this seems a regression in some infrastructure configuration?
[22:33] -queuebot:#ubuntu-release- New sync: arch-install-scripts (bionic-proposed/primary) [18-1]
[22:34] <xnox> slangasek, ruby2.3 can be removed now \o/ https://bugs.launchpad.net/ubuntu/+source/ruby2.3/+bug/1759707
[22:35] <slangasek> xnox: I think doko already removed it this morning
[22:35] <xnox> ah
[22:35] <xnox> then my local cache proxy charm is behind rsyncing the archive.
[22:35] <xnox> sorry for the noise.
[22:35] <slangasek> :)
[22:35] <tsimonq2> slangasek: This isn't release-critical, but currently the switch to Calamares on Lubuntu Next is blocked by some bad kernel handling. https://bazaar.launchpad.net/%7Ekdeneon/livecd-rootfs-neon/bionic/revision/1363 has the details on what I think should probably be done; I can either write a script for Calamares to do lots of kernel hackery or just special case that change for Lubuntu Next. It'd
[22:36] <tsimonq2> also be good to know if ubiquity is hardcoded anywhere in the tooling so I can special-case Lubuntu Next...
[22:36] <tsimonq2> (because ofc Lubuntu Next isn't getting a release, yet)
[22:37] <tsimonq2> slangasek: Of course this'll eventually become more urgent because Kubuntu's going to make the same move next cycle.
[22:39] <slangasek> tsimonq2: I don't think that should be done at all; I think if you're going to switch installers, you should integrate with the existing interfaces provided by the other components in the distro...
[22:40] <tsimonq2> slangasek: d-i?
[22:40] <slangasek> that's nothing to do with d-i
[22:41] <slangasek> it's casper, and livecd-rootfs
[22:41] <tsimonq2> So, you don't think *what* should be done? :
[22:41] <tsimonq2> *:)
[22:41] <slangasek> tsimonq2: you said it has the details on what you think should probably be done, and it points to a commit that shows setting BINARY_REMOVE_LINUX=false, and I think that's a wrong solution
[22:42] <tsimonq2> slangasek: Ah.
[22:42] <slangasek> because that means you get an extra unused copy of vmlinuz on your image inside the squashfs which duplicates the one used to boot the image
[22:42] <tsimonq2> Makes sense.
[22:43] <tsimonq2> So, I'll see what code Ubiquity has hidden in install.py to do this kernel mangling correctly.