[01:23] -queuebot:#ubuntu-release- Unapproved: ubiquity (bionic-proposed/main) [18.04.6 => 18.04.7] (core) [01:26] -queuebot:#ubuntu-release- Unapproved: cloud-init (bionic-proposed/main) [18.2-9-g49b562c9-0ubuntu1 => 18.2-14-g6d48d265-0ubuntu1] (edubuntu, ubuntu-cloud, ubuntu-server) [02:04] -queuebot:#ubuntu-release- Unapproved: ecj (bionic-proposed/universe) [3.13.2-1 => 3.13.3-1] (kubuntu) (sync) [02:13] can we please force pass xorg-server? I need it to go through so I can make sure we're getting proper permissions from the install media, and we're starting to cut it close [02:14] though, it may be close to migrating by itself, looks like only one test needs to finish [02:32] -queuebot:#ubuntu-release- Unapproved: gnome-initial-setup (bionic-proposed/main) [3.28.0-2ubuntu3 => 3.28.0-2ubuntu6] (ubuntugnome) [02:49] -queuebot:#ubuntu-release- Unapproved: carrotsearch-hppc (bionic-proposed/universe) [0.6.1-4 => 0.6.1-5] (no packageset) (sync) [02:50] -queuebot:#ubuntu-release- Unapproved: accepted carrotsearch-hppc [sync] (bionic-proposed) [0.6.1-5] [02:50] -queuebot:#ubuntu-release- Unapproved: csvjdbc (bionic-proposed/universe) [1.0.34-1 => 1.0.34-2] (no packageset) (sync) [02:51] -queuebot:#ubuntu-release- Unapproved: accepted csvjdbc [sync] (bionic-proposed) [1.0.34-2] [02:51] -queuebot:#ubuntu-release- Unapproved: easymock (bionic-proposed/universe) [3.5.1+ds-1 => 3.6-1] (no packageset) (sync) [02:51] -queuebot:#ubuntu-release- Unapproved: accepted easymock [sync] (bionic-proposed) [3.6-1] [02:54] -queuebot:#ubuntu-release- Unapproved: jboss-modules (bionic-proposed/universe) [1.7.0-1 => 1.8.1-1] (no packageset) (sync) [02:55] -queuebot:#ubuntu-release- Unapproved: accepted jboss-modules [sync] (bionic-proposed) [1.8.1-1] [02:55] -queuebot:#ubuntu-release- Unapproved: jug (bionic-proposed/universe) [2.0.0-2 => 3.1.5-1] (no packageset) (sync) [02:55] -queuebot:#ubuntu-release- Unapproved: accepted jug [sync] (bionic-proposed) [3.1.5-1] [02:57] -queuebot:#ubuntu-release- Unapproved: libcommons-validator-java (bionic-proposed/universe) [1:1.6-1 => 1:1.6-2] (no packageset) (sync) [02:57] -queuebot:#ubuntu-release- Unapproved: accepted libcommons-validator-java [sync] (bionic-proposed) [1:1.6-2] [02:58] -queuebot:#ubuntu-release- Unapproved: libhamcrest-java (bionic-proposed/universe) [1.3-6 => 1.3-7] (no packageset) (sync) [02:58] -queuebot:#ubuntu-release- Unapproved: accepted libhamcrest-java [sync] (bionic-proposed) [1.3-7] [02:59] -queuebot:#ubuntu-release- Unapproved: libhibernate3-java (bionic-proposed/universe) [3.6.10.Final-8 => 3.6.10.Final-9] (no packageset) (sync) [03:00] -queuebot:#ubuntu-release- Unapproved: accepted libhibernate3-java [sync] (bionic-proposed) [3.6.10.Final-9] [03:00] -queuebot:#ubuntu-release- Unapproved: libjgoodies-binding-java (bionic-proposed/universe) [2.13.0-1 => 2.13.0-2] (no packageset) (sync) [03:01] -queuebot:#ubuntu-release- Unapproved: accepted libjgoodies-binding-java [sync] (bionic-proposed) [2.13.0-2] [03:01] -queuebot:#ubuntu-release- Unapproved: libpdfbox2-java (bionic-proposed/universe) [2.0.8-2 => 2.0.9-1] (no packageset) (sync) [03:01] -queuebot:#ubuntu-release- Unapproved: accepted libpdfbox2-java [sync] (bionic-proposed) [2.0.9-1] [03:01] -queuebot:#ubuntu-release- Unapproved: libproxool-java (bionic-proposed/universe) [0.9.1-9 => 0.9.1-10] (no packageset) (sync) [03:02] -queuebot:#ubuntu-release- Unapproved: accepted libproxool-java [sync] (bionic-proposed) [0.9.1-10] [03:02] -queuebot:#ubuntu-release- Unapproved: livetribe-jsr223 (bionic-proposed/universe) [2.0.6-1 => 2.0.6-2] (no packageset) (sync) [03:04] -queuebot:#ubuntu-release- Unapproved: accepted livetribe-jsr223 [sync] (bionic-proposed) [2.0.6-2] [03:04] -queuebot:#ubuntu-release- Unapproved: sqlline (bionic-proposed/universe) [1.0.2-5 => 1.0.2-6] (no packageset) (sync) [03:04] -queuebot:#ubuntu-release- Unapproved: accepted sqlline [sync] (bionic-proposed) [1.0.2-6] [03:04] -queuebot:#ubuntu-release- Unapproved: trove (bionic-proposed/universe) [2.1.0-2 => 2.1.0-3] (openstack) (sync) [03:04] -queuebot:#ubuntu-release- Unapproved: tomcat8 (bionic-proposed/universe) [8.5.29-1 => 8.5.30-1] (kubuntu) (sync) [03:05] -queuebot:#ubuntu-release- Unapproved: accepted ecj [sync] (bionic-proposed) [3.13.3-1] [03:05] -queuebot:#ubuntu-release- Unapproved: accepted tomcat8 [sync] (bionic-proposed) [8.5.30-1] [03:08] -queuebot:#ubuntu-release- Unapproved: accepted trove [sync] (bionic-proposed) [2.1.0-3] [03:44] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (bionic-proposed) [18.04.7] [03:44] -queuebot:#ubuntu-release- Unapproved: gnome-software (bionic-proposed/main) [3.28.1-0ubuntu3 => 3.28.1-0ubuntu4] (ubuntu-desktop) [04:40] slangasek: ffmpeg> Didn't get a chance to look tonight, but I'll do it tomorrow. [06:17] -queuebot:#ubuntu-release- Unapproved: hedgewars (bionic-proposed/universe) [0.9.24-dfsg-2 => 0.9.24.1-dfsg-1] (no packageset) (sync) [06:17] -queuebot:#ubuntu-release- Unapproved: accepted hedgewars [sync] (bionic-proposed) [0.9.24.1-dfsg-1] [06:42] -queuebot:#ubuntu-release- Unapproved: apt (bionic-proposed/main) [1.6~rc1 => 1.6] (core) (sync) [06:42] -queuebot:#ubuntu-release- Unapproved: python-apt (bionic-proposed/main) [1.6.0~rc3 => 1.6.0] (core) (sync) [06:43] sil2100: ^ final release bumps (+ making zstd optional in upstream build scripts for apt) [06:43] um, cannot ftp to upload.ubuntu.com [06:47] -queuebot:#ubuntu-release- Unapproved: networkd-dispatcher (bionic-proposed/main) [1.7-0ubuntu2 => 1.7-0ubuntu3] (no packageset) [06:48] ^ it's working again :) [06:51] wait, I forgot to close the bug report attached to the card. [06:52] juliank: I'll take care of it in a moment, just want to upload something myself [06:53] sil2100: awesome :) [06:53] I wonder if I should re-upload networkd-dispatcher or close the bug manually. Latter seems easier [07:04] There's no requirement for changelogs to devel to track bug numbers - even though it is a good practice [07:05] -queuebot:#ubuntu-release- Unapproved: software-properties (bionic-proposed/main) [0.96.24.32 => 0.96.24.32.1] (desktop-core, ubuntu-server) [07:07] ^ that's an easy one line to add a missing build-depends from the previous upload from yesterday that ftbfses [07:11] Ok, looking at the queue now [07:14] -queuebot:#ubuntu-release- Unapproved: console-setup (bionic-proposed/main) [1.178ubuntu1 => 1.178ubuntu2] (core) [07:16] -queuebot:#ubuntu-release- Unapproved: accepted zfs-linux [source] (bionic-proposed) [0.7.5-1ubuntu15] [07:17] cyphermox, next time there is a console-setup change that create issues for ubiquity and require it to catch up it would be good to track/document that with a milestoned bugs [07:17] it would avoid having to "rediscover" the issue [07:17] -queuebot:#ubuntu-release- Unapproved: accepted indicator-china-weather [source] (bionic-proposed) [2.2.8-0ubuntu1] [07:17] -queuebot:#ubuntu-release- Unapproved: accepted ukui-menus [source] (bionic-proposed) [1.1.3-0ubuntu1] [07:18] -queuebot:#ubuntu-release- Unapproved: accepted software-properties [source] (bionic-proposed) [0.96.24.32.1] [07:19] I tested that locally, but I guess we'll have to keep an eye out if my re-removal of the xkb-keymap bits didn't break something that started depending on it [07:19] But seeing we did not have that before artful and it didn't seem to be followed up, I doubt it [07:21] -queuebot:#ubuntu-release- Unapproved: accepted curtin [source] (bionic-proposed) [18.1-5-g572ae5d6-0ubuntu1] [07:21] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (bionic-proposed) [2:12.0.1-0ubuntu1] [07:21] -queuebot:#ubuntu-release- Unapproved: accepted apt [sync] (bionic-proposed) [1.6] [07:21] -queuebot:#ubuntu-release- Unapproved: accepted python-apt [sync] (bionic-proposed) [1.6.0] [07:22] https://codesearch.debian.net/search?q=keyboard-configuration%2Fxkb-keymap&perpkg=1 gives an idea about where it's used in Debian [07:24] not really likely to create issues, they just seem to be components that try to preseed the value but they do it also for the other keyboard variables [07:26] would be to nice to get the gnome-initial-setup updates accepted as well [07:26] they are basically still doing UI changes etc [07:27] but that feature is late and improvements needed, which we know suck, but it is a requirement that has been imposed on us so not much way around [07:27] the current version in the queue is getting closer from being acceptable for release though [07:27] so it should stop changing UI after that [07:28] Yeah, I'll get to it in a bit [07:30] -queuebot:#ubuntu-release- Unapproved: accepted virtualbox [sync] (bionic-proposed) [5.2.10-dfsg-2] [07:31] thx [07:31] sil2100, how did you test? did you rebuild an iso? [07:32] -queuebot:#ubuntu-release- Unapproved: accepted dpkg [source] (bionic-proposed) [1.19.0.5ubuntu2] [07:32] -queuebot:#ubuntu-release- Unapproved: accepted leptonlib [sync] (bionic-proposed) [1.75.3-3] [07:35] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-mate-guide [source] (bionic-proposed) [18.04.4-0ubuntu1] [07:36] jibel: yes, modified the squashfs and recreated the iso [07:38] okay, i'll try it too [07:38] sil2100: the fastest way I found as well to test a fix [07:40] seb128: re: gnome-initial-setup - the documentation team is aware of the ongoing changes for that one? [07:40] (do we have some UIFe-like thing for it?) [07:41] -queuebot:#ubuntu-release- Unapproved: accepted console-setup [source] (bionic-proposed) [1.178ubuntu2] [07:42] sil2100, yes [07:43] oh my, 3 versions of it, I'll reject the 2 first and pick up the last one [07:43] -queuebot:#ubuntu-release- Unapproved: accepted mugshot [sync] (bionic-proposed) [0.4.0-1] [07:43] sil2100, that was part of the ffe you acked [07:43] thx [07:44] -queuebot:#ubuntu-release- Unapproved: ubuntu-report (bionic-proposed/main) [1.0.9 => 1.0.10] (no packageset) [07:44] ^ a one line change to get autopkgtests passing now that we use vendor deps. Tested locally on my autopkgtest vm [07:44] documentation is not an issue since the feature is not in our desktop guide [07:44] ETOOMANYFFES [07:44] seb128: thanks [07:44] thank you for the reviews! [07:46] -queuebot:#ubuntu-release- Unapproved: rejected gnome-initial-setup [source] (bionic-proposed) [3.28.0-2ubuntu4] [07:46] -queuebot:#ubuntu-release- Unapproved: accepted gnome-initial-setup [source] (bionic-proposed) [3.28.0-2ubuntu6] [07:46] -queuebot:#ubuntu-release- Unapproved: rejected gnome-initial-setup [source] (bionic-proposed) [3.28.0-2ubuntu5] [07:47] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-report [source] (bionic-proposed) [1.0.10] [07:47] thx! [07:48] thanks for accepting leptonlib! please accept tesseract, needed to fix autopkgtests on ocrmypdf [07:48] -queuebot:#ubuntu-release- Unapproved: accepted gnome-software [source] (bionic-proposed) [3.28.1-0ubuntu4] [07:48] -queuebot:#ubuntu-release- Unapproved: accepted networkd-dispatcher [source] (bionic-proposed) [1.7-0ubuntu3] [07:48] -queuebot:#ubuntu-release- Unapproved: accepted cloud-init [source] (bionic-proposed) [18.2-14-g6d48d265-0ubuntu1] [07:48] ginggs: yw! I was looking at that, need to re-check it - since the sync seems to be of a new upstream snapshot, I need to check if there are no FF-breaking changes there [07:58] -queuebot:#ubuntu-release- Unapproved: unattended-upgrades (bionic-proposed/main) [1.0ubuntu2 => 1.1ubuntu1] (desktop-core, ubuntu-server) [08:01] sil2100: ok, thanks - debian's changelog is quite verbose :) [08:53] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-390 (bionic-proposed/restricted) [390.48-0ubuntu2 => 390.48-0ubuntu3] (ubuntu-desktop) [09:09] can an admin reject nvidia-graphics-drivers-390 (390.48-0ubuntu3), please? I would like to add one more fix [09:10] tjaalton: ^ [09:11] tseliot, done [09:11] -queuebot:#ubuntu-release- Unapproved: rejected nvidia-graphics-drivers-390 [source] (bionic-proposed) [390.48-0ubuntu3] [09:11] apw: thanks! [09:27] -queuebot:#ubuntu-release- Unapproved: open-vm-tools (bionic-proposed/main) [2:10.2.0-3ubuntu2 => 2:10.2.0-3ubuntu3] (edubuntu, ubuntu-cloud, ubuntu-server) [10:49] -queuebot:#ubuntu-release- Unapproved: chrony (bionic-proposed/main) [3.2-4ubuntu3 => 3.2-4ubuntu4] (ubuntu-server) [11:36] -queuebot:#ubuntu-release- Unapproved: ubiquity (bionic-proposed/main) [18.04.7 => 18.04.8] (core) [11:40] slangasek,infinity: So, can either of you still reproduce this "Lubuntu ubiquity runs plugininstall.py as non-root" thing? I just spent some time trying to get it to happen with today's image (after applying the fix from 18.04.7 in-place using break=casper-bottom) and can't; plugininstall.py runs as root and it all works fine. But maybe I'm doing something slightly different? [11:55] -queuebot:#ubuntu-release- Unapproved: tomcat8 (bionic-proposed/universe) [8.5.30-1 => 8.5.30-1ubuntu1] (kubuntu) [11:59] apw: it was a false alarm. I have re-uploaded nvidia [11:59] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-390 (bionic-proposed/restricted) [390.48-0ubuntu2 => 390.48-0ubuntu3] (ubuntu-desktop) [12:17] -queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (bionic-proposed) [18.04.8] [12:24] -queuebot:#ubuntu-release- Unapproved: virtualbox-guest-additions-iso (bionic-proposed/multiverse) [5.2.8-2 => 5.2.10-2] (no packageset) (sync) [12:25] -queuebot:#ubuntu-release- Unapproved: accepted virtualbox-guest-additions-iso [sync] (bionic-proposed) [5.2.10-2] [12:32] cjwatson: today's lubuntu iso seems to crash ubuitity-dm if install is selected in the boot menu and go straight to the live session [12:33] acheronuk: see where I wrote "after applying the fix from 18.04.7 in-place" [12:33] that's the fix for that bug [12:34] ah. will have to wait for another iso to test that [12:34] yep, that's why for now I just asked people I was sure were comfortable hacking stuff in-place using break=casper-bottom :) [12:35] fair enough [12:40] (and also who I knew for certain had reproduced this bug in the past) [12:41] is it possible to process hedgewars removal on ppc64el? [12:41] https://bugs.launchpad.net/ubuntu/+source/hedgewars/+bug/1765392 [12:41] Ubuntu bug 1765392 in hedgewars (Ubuntu) "please remove hedgewars on ppc64el" [Undecided,New] [12:58] cjwatson: well I got it when testing for previous milestone. but I'm leaving well alone now [13:00] I believe you, but I don't know whether it's gone away on its own or whether I'm doing something different that doesn't provoke it [13:03] -queuebot:#ubuntu-release- Unapproved: ubuntu-report (bionic-proposed/main) [1.0.10 => 1.0.11] (no packageset) [13:07] * acheronuk shrugs [13:18] why is xorg-server still set to "Not considered"? [13:18] I don't see any failures [13:22] mdeslaur: kdevelop/4:5.2.1-1ubuntu4: amd64: Test in progress, [13:23] passed @ 13:16:54 UTC so should be ok on next run? [13:23] acheronuk: ugh, I'm blind apparently [13:23] acheronuk: thanks :) [13:23] * mdeslaur crosses fingers [13:30] Apparently successful [13:30] final: apt,console-setup,neutron,tomcat8,ubuntu-report,virtualbox,xorg-server [13:30] :) [13:31] \o/ [13:43] the apparmor autopkgtest, afaics, are not passing due to perl deps not migrating (please correct me if I'm wrong). is there an update on perl's migration? [13:43] * mdeslaur hides [13:47] -queuebot:#ubuntu-release- Unapproved: dkms (bionic-proposed/main) [2.3-3ubuntu6 => 2.3-3ubuntu7] (kubuntu, ubuntu-desktop) [13:47] -queuebot:#ubuntu-release- Unapproved: shim-signed (bionic-proposed/main) [1.33.1 => 1.34] (core) [14:08] darkxst: is libzip 1.5 happening? [14:10] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (artful-proposed) [2.32.5+17.10] [14:10] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (xenial-proposed) [2.32.5] [14:11] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (trusty-proposed) [2.32.5~14.04] [14:12] acheronuk: ffe wasn't approved (yet) [14:32] * sil2100 just promoted pv to main [14:44] Ok, spinning new base language-packs [14:44] jdstrand: I think that's an autopkgtest bug :((((((((((((( https://salsa.debian.org/ci-team/autopkgtest/merge_requests/2 [14:44] CI bug (Merge request) 2 in autopkgtest "Remove the right autopkgtest-default-release file" (comments: 0) [Opened] [14:44] -queuebot:#ubuntu-release- Unapproved: xorg (bionic-proposed/main) [1:7.7+19ubuntu6 => 1:7.7+19ubuntu7] (core, xorg) [14:45] Laney: ah. ok. tbh, I couldn't make heads or tails of the log. the failure seemed completely unrelated to my upload (which was only a handul of profile changes) [14:45] you got a dependency on the latest perl [14:45] Laney: thank you for taking a look. what do I need to do to resolve this? [14:45] -queuebot:#ubuntu-release- Unapproved: gnome-session (bionic-proposed/main) [3.28.1-0ubuntu1 => 3.28.1-0ubuntu2] (ubuntu-desktop) [14:46] but that wasn't available when pinning just apparmor [14:46] * jdstrand nods wrt latest perl [14:46] we tried to fall back to using all of proposed [14:46] but that didn't work [14:46] two seconds and you can retry [14:46] Laney: not, I retried amd64 an hour ago or so [14:46] note* [14:46] just for giggles [14:47] well yes, but that was before I fixed it [14:47] try now [14:47] bah, reject that xorg upload [14:47] I'll fix that first [14:47] sure-- I was just saying it may still be running, etc, but I can keep an eye on that [14:47] * jdstrand tries i386 [14:48] it looks like amd64 from an hour ago finished. if i386 passes, I'll do all the others [14:48] Laney: thanks! [14:49] (to be clear, amd64 from an hour ago finished and failed; I'll retry it after i386) [14:52] -queuebot:#ubuntu-release- Unapproved: xorg (bionic-proposed/main) [1:7.7+19ubuntu6 => 1:7.7+19ubuntu7] (core, xorg) [14:57] -queuebot:#ubuntu-release- Unapproved: cloud-utils (artful-proposed/main) [0.30-0ubuntu2 => 0.30-0ubuntu2.1] (edubuntu, ubuntu-server) [14:59] -queuebot:#ubuntu-release- Unapproved: cloud-utils (xenial-proposed/main) [0.27-0ubuntu25 => 0.27-0ubuntu25.1] (edubuntu, ubuntu-server) [15:03] jdstrand: ✓ it worked [15:04] woo! [15:04] Laney: thanks again :) [15:04] np! [15:04] Hello, I was wondering if it would be possible to have ubuntu-report 1.0.11 pushed into the release? The package is currently waiting on unapproved. [15:05] Everything in unapproved will be reviewed [15:06] Laney: Excellent, cheers. [15:06] de nada [15:22] Laney: any idea about the pyfai uninstallability in the autopkg tests? [15:25] doko: no, but see the previous conversation and maybe retry [15:27] I assume that someone's looking at the Perl Regressions in the autopkgtests? [15:47] -queuebot:#ubuntu-release- Unapproved: openjdk-lts (bionic-proposed/main) [10~46-5ubuntu1 => 10.0.1+10-1ubuntu1] (ubuntu-desktop) [15:47] -queuebot:#ubuntu-release- Unapproved: accepted openjdk-lts [source] (bionic-proposed) [10.0.1+10-1ubuntu1] [15:48] -queuebot:#ubuntu-release- Unapproved: accepted tomcat8 [source] (bionic-proposed) [8.5.30-1ubuntu1] [15:48] -queuebot:#ubuntu-release- New: accepted lightdm-settings [source] (bionic-proposed) [1.1.4-0ubuntu1] [15:50] -queuebot:#ubuntu-release- New binary: lightdm-settings [amd64] (bionic-proposed/none) [1.1.4-0ubuntu1] (no packageset) [15:51] -queuebot:#ubuntu-release- Unapproved: orca (bionic-proposed/main) [3.27.91-1ubuntu2 => 3.28.0-3ubuntu1] (ubuntu-desktop) [15:55] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (bionic-proposed/main) [2.522 => 2.523] (desktop-core) [16:03] cjwatson: I hadn't tested with a more recent image, hmm [16:04] I don't see anything that might plausibly have fixed it either, but given that we don't understand the root cause ... === alan_g_ is now known as alan_g|EOD [16:08] -queuebot:#ubuntu-release- New: accepted lightdm-settings [amd64] (bionic-proposed) [1.1.4-0ubuntu1] [16:08] -queuebot:#ubuntu-release- Unapproved: cross-toolchain-base (bionic-proposed/main) [25ubuntu4 => 25ubuntu5] (ubuntu-desktop) [16:09] -queuebot:#ubuntu-release- Unapproved: accepted cross-toolchain-base [source] (bionic-proposed) [25ubuntu5] [16:30] infinity: new base langpacks prepared, uploaded, approved and building [16:30] Hopefully they're good, I only sanity-tested 2 [16:32] the queue has two uploads of 'xorg', drop the older one [16:35] k [16:35] thx [16:36] -queuebot:#ubuntu-release- Unapproved: rejected xorg [source] (bionic-proposed) [1:7.7+19ubuntu7] [16:48] -queuebot:#ubuntu-release- Unapproved: udisks2 (bionic-proposed/main) [2.7.6-2ubuntu6 => 2.7.6-3] (desktop-core, ubuntu-server) (sync) [16:53] bdmurray: hey! I'll be releasing systemd for trusty now (just so you won't waste your time later by accident trying to re-publish it) [16:55] sil2100: okay [16:56] slangasek: could you update your gvfs britney hint? [16:58] -queuebot:#ubuntu-release- Unapproved: accepted xfsprogs [source] (trusty-proposed) [3.1.9ubuntu2.1] [17:01] Ok, /me is done for today [17:01] -queuebot:#ubuntu-release- Unapproved: accepted ifupdown [source] (xenial-proposed) [0.8.10ubuntu1.3] [17:07] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-report [source] (bionic-proposed) [1.0.11] [17:16] jbicha: done [17:21] cjwatson: confirmed, lubuntu install failure unreproducible; job done! [17:23] correct me if i'm wrong but in the autopkgtests update excuses file, "Depends: [packagename] perl (not considered)" means that the Perl autopkgtests need to pass and perl needs to be released from proposed as well, right? (Just trying to chase down something..) [17:24] sigh [17:24] what the hell is wrong with perl deps [17:25] and is anyone working on getting it unblocked? mdeslaur ? [17:25] teward: yes your analysis is correct [17:26] slangasek: sorry, I'm not working on it, no [17:27] mdeslaur: could you? :) it's your package sync [17:27] -queuebot:#ubuntu-release- New sync: cpprest (bionic-proposed/primary) [2.10.2-3] [17:27] and dh_perl's shitty autogenerated deps are blocking other packages [17:28] slangasek, I renamed src:casablanca to src:cpprest to match the binary package [17:28] content is mostly the same, same upstream, I also install now the cmake bindings [17:28] can you please consider processing it? [17:28] (also, decruft or whatever you call src:casablanca :) ) [17:28] I opened the same decruft bug in Debian this morning [17:28] btw I'm partially working wrt perl migration [17:28] slangasek: I'll take a look (remind me never to touch perl again) [17:33] -queuebot:#ubuntu-release- Unapproved: i2p (bionic-proposed/universe) [0.9.33-2 => 0.9.34-1] (no packageset) (sync) [17:33] -queuebot:#ubuntu-release- Unapproved: accepted i2p [sync] (bionic-proposed) [0.9.34-1] [17:56] ocrmypdf is blocked from migrating from -proposed because of a test failure on s390x, but it is not even in -release, so how is this a regression? [17:57] btw, this is fixed by the tesseract sync which is not yet approved [18:10] -queuebot:#ubuntu-release- Unapproved: stunnel4 (bionic-proposed/universe) [3:5.44-1ubuntu2 => 3:5.44-1ubuntu3] (no packageset) [18:10] -queuebot:#ubuntu-release- Unapproved: accepted stunnel4 [source] (bionic-proposed) [3:5.44-1ubuntu3] [18:15] LocutusOfBorg: I took care of stunnel4, is there anything else in the perl migration you would like me to take a closer look at? [18:17] slangasek: how very odd, but I won't complain. I guess we should be prepared for somebody reporting it again during testing though [18:18] * slangasek nods [18:19] -queuebot:#ubuntu-release- Unapproved: i2p (bionic-proposed/universe) [0.9.34-1 => 0.9.34-1ubuntu1] (no packageset) [18:19] -queuebot:#ubuntu-release- Unapproved: accepted i2p [source] (bionic-proposed) [0.9.34-1ubuntu1] [18:19] mdeslaur, I don't know, I think they all need care, but some of them are regressed in release so we might even ask to blacklist? [18:20] I'll take a closer look tomorrow maybe [18:31] bdmurray: hi there, mind letting snapcraft 2.41/2.41+17.10 into -updates ? [18:32] there's an ubuntu-image error on s390x on artful which looks related to snapd and not snapcraft itself [18:32] -queuebot:#ubuntu-release- Unapproved: accepted shim-signed [source] (bionic-proposed) [1.34] [18:33] sergiusens: its only been in -proposed for a day. Is there a reason to waive the 7 day wait period? [18:34] bdmurray: the "if it survives its own autopkgtests, it must be good" reason [18:35] bdmurray: we have an exception https://wiki.ubuntu.com/SnapcraftUpdates [18:35] slangasek: Is that a new reason? [18:35] bdmurray: it's pretty much meant to be a standing reason in the case of snapcraft, from my perspective. I don't recall if it was captured on the above wiki [18:36] slangasek: oops, it is and I lasted updated that page [18:36] :) [18:43] sergiusens: Could you elaborate on the ubuntu-image error being related to snapd? [18:45] bdmurray: it seems to be an error coming from `snap prepare`, could be store hiccup as well https://paste.ubuntu.com/p/Y6fdvK32Zk/ [18:45] but it is not from snapcraft :-) [18:52] -queuebot:#ubuntu-release- Unapproved: accepted dkms [source] (bionic-proposed) [2.3-3ubuntu7] [18:53] bdmurray: can you followup with kyrofa, I need to go offline for a bit [18:53] sergiusens: I released it [18:53] oh, ty [19:01] nfct v1.4.4: netlink error: Device or resource busy [19:01] >_< [19:08] Final Freeze is in two hours, aye? [19:13] Hum, the contents of https://wiki.ubuntu.com/FinalFreeze don't seem to be current. [19:14] log4cxx autopkgtest failure impressive, declares a test that depends on a binary package that's NBS from its own source [19:16] so passed in -proposed, migrated to devel, NBS cleanup done, test fails. :P [19:19] -queuebot:#ubuntu-release- Unapproved: log4cxx (bionic-proposed/universe) [0.10.0-13ubuntu1 => 0.10.0-13ubuntu2] (no packageset) [19:20] -queuebot:#ubuntu-release- Unapproved: accepted log4cxx [source] (bionic-proposed) [0.10.0-13ubuntu2] [19:22] cyphermox: netplan.io/0.35/amd64 test failure on glibc [19:23] doko: do you know why mercurial autopkgtests are now running 3h instead of 1h and hitting timeouts? [19:24] cyphermox: I thought you were dropping this test_mix_bridge_on_bond test a long time ago due to it being racy [19:25] slangasek: Might witty be a candidate for removal from devel-proposed? It's FTBFS in Ubuntu (with an associated RC bug in Debian) and piuparts in Debian also failed. [19:26] * tsimonq2 contacts the Debian MIA Team about the maintainer. [19:31] tsimonq2: yes; question is why doko didn't remove it from -proposed as well when he removed it from release. But the RC bug in Debian does not look "associated". [19:32] slangasek: Ah, OK. [19:32] anyway, removing now [19:33] tsimonq2: fwiw the build failure in Ubuntu is specific to the boost transition that has yet to start in Debian [19:33] slangasek: I want to, but late in cycle didn't seem the right moment to do extra changes like this [19:33] slangasek: Thanks. [19:33] cyphermox: when we talked about it it was not late in cycle [19:33] it's definitely a duplicate test, but having the intersection of (enough time to look and re-test) + (right moment) didn't work [19:33] I know [19:33] cyphermox: and there is no wrong time to drop a broken test [19:34] slangasek: xwallpaper seems like a candidate for extra-removals.txt; it's depwait on nonexisting (in Ubuntu) boost packages. [19:34] I don't want to drop it and find out the other mix_bridge_on_bond_vlan gets flaky then [19:34] cyphermox: ok. [19:34] because I suspect it's not flaky, just bad environment setup/cleanup [19:34] and it takes time to investigate, never quite reaching the top of my list [19:35] tsimonq2: no, it's dep-wait on doko cleaning up jpeg in Ubuntu to not be inconsistent with Debian; so not fit for extra-removals [19:35] slangasek: ack [19:36] slangasek: I'll stage the change now in git so it's ready for the very next upload [19:36] doko: speaking of which, it seems you've not committed anything to extra-removals.txt, nor given me the list you said you would [19:43] node-d3-format might migrate now; it was FTBFS due to a failed upload(?) [19:48] node-d3-format> Er, wat? [19:48] slangasek: That could need some sort of AA cleanup ^ [19:49] It's never been in the release pocket it seems, and I can't find the epoch in the publishing history. [19:49] glibc autopkgtest regressions resolved or badtested or in progress [19:50] tsimonq2: did you check if a binary of this name exists from another source? [19:50] node-d3-hierarchy and node-d3-request are depwait on node-d3-dsv which is depwait on node-csv-spectrum and that seems to be in neither Debian or Ubuntu, curious; perhaps *these* are candidates for removal? :) [19:50] slangasek: Double checking. [19:50] (d3-format) [19:50] (yep) [19:51] the newer node-d3-format package is fail-to-upload in Debian also [19:51] Debian bug 894532 is a mess [19:51] Debian bug 894532 in src:node-d3-format "node-d3-format: Duplicates exisitng node-d3-format binary package" [Serious,Open] http://bugs.debian.org/894532 [19:52] Ah. Nice one jbicha [19:53] slangasek: So, do we just leave node-d3-format? :) [19:53] tsimonq2: it will never migrate without a sourceful fix. I'll nuke it from -proposed [19:54] ack [19:55] slangasek: What about the node-csv-spectrum issue? [19:56] tsimonq2: did you check if it's in the NEW queue? [19:56] tsimonq2: (debian new) [19:57] Good point. sec [19:57] Indeed it is... [19:57] slangasek: sorry for slow response. Glad that my analysis is right, hopefully someone can fix the Perl stuff soon, because that's probably going to hold up a bunch of things. And a lot of things in it show as regressions now. [19:58] s/a lot/a bunch/ === sergiusens_ is now known as sergiusens [19:59] coreycb: Debian now has python3-neutron but Ubuntu does not, which blocks updating of networking-arista. I don't suppose that's trivially fixable for release? [19:59] slangasek: So then the correct course of action is to poke Debian to get that through then sync? Or would you prefer a different solution? [19:59] coreycb: (also, networking-arista in bionic currently fails to build) [20:00] tsimonq2: poking Debian about node packages in NEW is not worthwhile; and I don't care about any of the node stuff currently stuck in -proposed. I think we should be focused on the things in -proposed that are actually useful to get unstuck and migrated before we need to start building candidate images [20:00] tsimonq2: which means only those things in -proposed that are 16 days old or newer [20:00] ack [20:01] (like, in principle it would be nice to zero out the backlog in -proposed, but now is not the time) [20:01] Got it. [20:07] -queuebot:#ubuntu-release- Unapproved: ubuntu-mate-meta (bionic-proposed/universe) [1.222 => 1.223] (ubuntu-mate) [20:10] -queuebot:#ubuntu-release- New source: candid (bionic-proposed/primary) [1.0.0~alpha+201804191824-24b36a9-0ubuntu1] [20:12] seb128: do you plan to follow through on the indicator-sound ftbfs? Was previously on the list of test rebuild failures [20:26] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (bionic-proposed/main) [2.522 => 2.524] (desktop-core) [20:30] doko: your puppet 5.4.0-2ubuntuX fails autopkgtests [20:31] slangasek: i think i'm supposed to be investigating it -- i think we should revert it back to the ubuntu1 level [20:31] slangasek: the ubuntu dep8 env is different from debian's [20:31] nacc: the autopkgtests failed with ubuntu1 also [20:31] slangasek: ok, i'll need to look [20:35] -queuebot:#ubuntu-release- Unapproved: ubuntu-budgie-meta (bionic-proposed/universe) [0.31 => 0.32] (personal-fossfreedom, ubuntu-budgie) [20:36] jbicha: I guess you have no particular interest in pgbackrest, right, you were just syncing new version to see if it might fix the already brokenness in -proposed? [20:37] jbicha: (might be worth a bug report to Debian as they probably don't know the package is broken on armhf?) [20:37] -queuebot:#ubuntu-release- New: rejected candid [source] (bionic-proposed) [1.0.0~alpha+201804191824-24b36a9-0ubuntu1] [20:39] slangasek: in case i'm asleep before you get to it, ocrmypdf fails autopkgtest only on s390x, but it is not in -release, so is not a regression? but fixed by tesseract sync, not yet accepted (s390x autopkgtest passed in my PPA) [20:40] ginggs: oh, there's a fixed tesseract? looking, thanks [20:42] -queuebot:#ubuntu-release- Unapproved: accepted tesseract [sync] (bionic-proposed) [4.00~git2288-10f4998a-2] [20:42] slangasek: ta! [20:49] doko: you dropped Ubuntu delta when syncing rails, regressing xnox's sdoc fix; are you fixing up? [20:51] slangasek, indicator-sound is on our list of things to look at yes [20:51] seb128: ok cheers [20:53] doko: what's the path forward on LP: #1762175? java-common and octave would both unblock at the same time anyway if octave-io and octave-symbolic/i386 autopkgtests were fixed [20:53] Launchpad bug 1762175 in octave (Ubuntu) "keep java-common pointing to OpenJDK in -proposed" [Undecided,New] https://launchpad.net/bugs/1762175 [20:57] -queuebot:#ubuntu-release- Unapproved: httping (bionic-proposed/universe) [2.5-1.1 => 2.5-2] (no packageset) (sync) [20:57] -queuebot:#ubuntu-release- Unapproved: accepted httping [sync] (bionic-proposed) [2.5-2] [20:58] Would someone be good enough to let ubuntu-mate-meta 1.223 through please. [20:59] Wimpress: are you sure you wouldn't rather have an ubuntu-mate-mate [20:59] yes-mate [20:59] ubuntu-mutu-mutu [21:00] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-mate-meta [source] (bionic-proposed) [1.223] [21:00] That has a certain ring to it. [21:00] slangasek: Thank you. [21:00] slangasek: I'm sure fossfreedom would like ubuntu-budgie-meta 0.32 leeting in too. [21:01] We're both seeding the same package. [21:07] slangasek: fwiw, octave-symbolic is flaky everywhere [21:09] ginggs: ah ok [21:09] slangasek: ok, i remember this being relatively hard to diagnose earlier. It has to do with the network configuration of the dep8 runners ... hostnames, and such. For some reason, in Debian's env 'it just works', but in LP's it does not. And it's not trivial to reproduce the LP env at home (and if I just use autopkgtest with LXD, it passes locally, with or without our delta) [21:12] slangasek: let me see i might have fixes actually (it looks like some of the tests maybe moved upstream) [21:15] slangasek: lol ... fubar merge [21:15] completely completely wrong [21:15] slangasek: fixing it up now [21:15] doko: tsk tsk :) [21:21] acheronuk, I dont know, Laney was going to look at it, but dont think he has and its now super late in the cycle [21:23] thanks. not greatly fussed. was just curious [21:28] acheronuk, probably it will happen when CC opens [21:29] slangasek: uploading a fix [21:30] nacc: cheers [21:30] -queuebot:#ubuntu-release- Unapproved: puppet (bionic-proposed/universe) [5.4.0-2ubuntu2 => 5.4.0-2ubuntu3] (no packageset) [21:31] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-budgie-meta [source] (bionic-proposed) [0.32] [21:31] -queuebot:#ubuntu-release- Unapproved: accepted puppet [source] (bionic-proposed) [5.4.0-2ubuntu3] [21:32] slangasek: afaict, some of that delta will always need to exist (there's a sysv-init specific test). I think I can send the rest of it to Debian. I'll try and do that tomorrow. [21:36] All the s390x builders seem to be stuck in Cleaning. [21:37] Odd_Bloke: flagged to LP [21:37] Danke. [21:38] what does it say that my fingers tried to autocomplete 'pyfai' to 'pyfail'? [21:39] I was told on s390x "I/O error trying to launch instances, won't be trivial to resolve, may take until tomorrow" [21:39] :/ [21:40] cjwatson: So, the one thing I did change was to seed python2 back onto their live image (by seeding samba-common, to work around it not being there due to no-follow-recommends), which had the side-effect of making pluininstall stop whining about pyversions not being there, but I swear I tested an image after that change and it still broke. [21:40] cjwatson: I can't think of anything else that would have magically fixed things. [21:41] cjwatson: (I can't see how that would have magically fixed things either, mind you) [21:52] jbicha: cacti 1.1.37+ds1-1 that you synced has failing autopkgtests in Debian and Ubuntu; there's a 1.1.38 in Debian that passes; should we sync it? [21:58] -queuebot:#ubuntu-release- Unapproved: shim-signed (bionic-proposed/main) [1.34 => 1.34.1] (core) [22:06] yes the new cacti version should pass, syncing [22:06] -queuebot:#ubuntu-release- Unapproved: cacti (bionic-proposed/universe) [1.1.37+ds1-1 => 1.1.38+ds1-1] (no packageset) (sync) [22:07] -queuebot:#ubuntu-release- Unapproved: accepted cacti [sync] (bionic-proposed) [1.1.38+ds1-1] [22:09] slangasek, trumping your livecd-rootfs upload; my maas hook was tested by building the subiquity livefs in my ppa at https://launchpad.net/~xnox/+livefs/ubuntu/bionic/ubuntu-server-live/+build/129934 which is success, and did the right thing. Testing my subiquity changes on top of that now. [22:09] did someone say drumpf? [22:11] * LocutusOfBorg feels lintian syncy to make perl migrate, is trying in his ppa [22:12] -queuebot:#ubuntu-release- Unapproved: accepted shim-signed [source] (bionic-proposed) [1.34.1] [22:13] -queuebot:#ubuntu-release- Unapproved: rejected livecd-rootfs [source] (bionic-proposed) [2.523] [22:15] LocutusOfBorg: if you do it, it will need to be a merge because of Debian bug 895574 [22:15] Debian bug 895574 in src:lintian "lintian: binary-compiled-with-profiling-enabled test fails on Ubuntu's armhf" [Normal,Open] http://bugs.debian.org/895574 [22:16] -queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (bionic-proposed) [2.524] [22:17] -queuebot:#ubuntu-release- Unapproved: morris (bionic-proposed/universe) [0.2-3build1 => 0.2-4] (no packageset) (sync) [22:18] -queuebot:#ubuntu-release- Unapproved: grhino (bionic-proposed/universe) [0.16.1-3 => 0.16.1-4] (no packageset) (sync) [22:19] -queuebot:#ubuntu-release- Unapproved: accepted grhino [sync] (bionic-proposed) [0.16.1-4] [22:19] -queuebot:#ubuntu-release- Unapproved: accepted morris [sync] (bionic-proposed) [0.2-4] [22:19] infinity: Indeed - I have a fix for that bug locally, but I don't think it can possibly be related to this, so I'd rather commit it for post-bionic [22:19] jbicha, do you feel lintian mergy? :) [22:19] I won't be awake to click this link https://autopkgtest.ubuntu.com/request.cgi?release=bionic&arch=amd64&package=lintian&ppa=costamagnagianfranco/locutusofborg-ppa&trigger=lintian/2.5.83ubuntu1 [22:19] https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa [22:20] LocutusOfBorg: no :) [22:22] LocutusOfBorg, jbicha: regardless, lintian is clearly regressed in release; badtest hint added [22:24] Looking at the nature of the failures, I was blaming LP: #1764701 for the lintian regression until someone proves otherwise. [22:24] Launchpad bug 1764701 in gcc-7 (Ubuntu) "produces broken binary: Inconsistency detected by ld.so [regression gcc-7 7.3.0-15ubuntu2 => 7.3.0-16ubuntu2]" [High,New] https://launchpad.net/bugs/1764701 [22:27] Also, I think it's about time update_excuses.html grew some simple CSS to block tag all-green (or, I guess, all-green-or-yellow) pass lines with a toggle to not display them. [22:27] Scrolling through all the green to find the few red hurts. [22:29] could you kick the s390x builders? [22:29] we can kick them but that will only hurt our toes [22:29] don't kick them with your sandals please [22:29] Instance spawning isn't working, so the usual kind of kicking is futile [22:30] If they're just stuck in failed reset hell, I can smack them, but... See above from Colin. :) [22:30] qemu-img convert is complaining about I/O errors, which can't be good [22:30] I made a few suggestions in the relevant sysadmin channel, possibly clueless ones [22:31] Maybe we broke our mainframe and need to ask IBM for a new one. [22:32] broken image is more likely, but not clear why [22:32] maybe Michael's is having a sale on frames [22:32] anyway, I must sleep [22:34] slangasek: Hrm. I was going to correct you with "'frames", and now I'm not sure if the pun works better or worse using one form over the other. [22:34] slangasek: These are the things that keep me awake at night. [22:35] so... zfs doesn't work on 32-bit, right? therefore we should maybe not let a failing lxd/i386 autopkgtest block zfs [22:35] slangasek: ZFS modules don't exist on 32-bit kernels, but 32-bit userspace is meant to work against 64-bit kernels. [22:36] and are you meant to use 32-bit lxd on 64-bit kernels with zfs? [22:36] slangasek: Don't see why that wouldn't work, but the more relevant question is if this lxd failure even has anything to do with zfs. [22:37] * infinity retries for kicks. [22:37] BRB, quick run to the dry cleaner's before they close. [22:38] infinity: I already retried it too, let's race [22:54] slangasek: The part where the failed test took 3 times longer than previous successful tests is a bit suspect. [22:57] nacc: that leaves ruby-rspec-puppet autopkgtests blocking [23:27] infinity: looks like both the lxd tests pasts; not sure which of us won [23:28] now if make would just stop breaking systemd === infinity changed the topic of #ubuntu-release to: Released: Xenial 16.04.4, Artful 17.10 | Archive: final freeze | Bionic Release Coordination | Please don't upload things during freezes where you shouldn't, or be prepared to apologise to the release team | We accept payment in cash, check or beer | melius malum quod cognoscis [23:30] slangasek: Do we know anything about this kylin-video that hit NEW last week? [23:30] infinity: I don't [23:30] -queuebot:#ubuntu-release- Unapproved: accepted unattended-upgrades [source] (bionic-proposed) [1.1ubuntu1] [23:30] -queuebot:#ubuntu-release- New: accepted cpprest [sync] (bionic-proposed) [2.10.2-3] [23:33] -queuebot:#ubuntu-release- Unapproved: accepted gnome-session [source] (bionic-proposed) [3.28.1-0ubuntu2] [23:33] -queuebot:#ubuntu-release- Unapproved: accepted xorg [source] (bionic-proposed) [1:7.7+19ubuntu7] [23:33] Ugh, reviewing that nvidia upload looks "fun". [23:35] -queuebot:#ubuntu-release- Unapproved: accepted orca [source] (bionic-proposed) [3.28.0-3ubuntu1] [23:36] -queuebot:#ubuntu-release- Unapproved: accepted chrony [source] (bionic-proposed) [3.2-4ubuntu4] [23:39] -queuebot:#ubuntu-release- Unapproved: accepted unity-settings-daemon [sync] (bionic-proposed) [15.04.1+18.04.20180413-0ubuntu1] [23:40] -queuebot:#ubuntu-release- Unapproved: accepted open-vm-tools [source] (bionic-proposed) [2:10.2.0-3ubuntu3] [23:40] -queuebot:#ubuntu-release- Unapproved: accepted udisks2 [sync] (bionic-proposed) [2.7.6-3] [23:50] -queuebot:#ubuntu-release- Unapproved: gnome-video-arcade (bionic-proposed/universe) [0.8.8-2 => 0.8.8-2ubuntu1] (no packageset) [23:51] -queuebot:#ubuntu-release- Unapproved: accepted gnome-video-arcade [source] (bionic-proposed) [0.8.8-2ubuntu1]