[03:53] -queuebot:#ubuntu-release- New binary: freedict-wikdict [amd64] (disco-proposed/universe) [2018.11.02-1] (no packageset) [05:17] -queuebot:#ubuntu-release- New binary: r-cran-fnn [s390x] (disco-proposed/none) [1.1.2.1-1] (no packageset) [05:17] -queuebot:#ubuntu-release- New binary: r-cran-fnn [amd64] (disco-proposed/none) [1.1.2.1-1] (no packageset) [05:17] -queuebot:#ubuntu-release- New binary: r-cran-fnn [ppc64el] (disco-proposed/none) [1.1.2.1-1] (no packageset) [05:19] -queuebot:#ubuntu-release- New binary: lemonldap-ng [amd64] (disco-proposed/universe) [2.0.0+ds-1] (no packageset) [05:19] -queuebot:#ubuntu-release- New binary: r-cran-fnn [i386] (disco-proposed/none) [1.1.2.1-1] (no packageset) [05:31] -queuebot:#ubuntu-release- New binary: r-cran-fnn [arm64] (disco-proposed/universe) [1.1.2.1-1] (no packageset) [05:31] -queuebot:#ubuntu-release- New binary: r-cran-fnn [armhf] (disco-proposed/universe) [1.1.2.1-1] (no packageset) [05:41] -queuebot:#ubuntu-release- New binary: linux-signed-azure-edge [amd64] (bionic-proposed/main) [4.18.0-1007.7~18.04.1] (no packageset) [05:42] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (cosmic-proposed/main) [4.18.0-1007.7] (kernel) [06:36] -queuebot:#ubuntu-release- New: accepted linux-signed-azure-edge [amd64] (bionic-proposed) [4.18.0-1007.7~18.04.1] [06:42] coreycb: hey! I'm looking at nova now (apologies, yesterday was a busy day) - I see that your SRU overwrites the already present in -proposed LP: #1744079 [06:42] Launchpad bug 1744079 in OpenStack Compute (nova) rocky "[SRU] disk over-commit still not correctly calculated during live migration" [Low,In progress] https://launchpad.net/bugs/1744079 [06:43] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (cosmic-proposed) [4.18.0-1007.7] [07:06] someone around that could promote libtspi1 from src.trousers based on bug 247590? [07:06] bug 247590 in trousers (Ubuntu) "main inclusion request: trousers" [Undecided,Fix released] https://launchpad.net/bugs/247590 [07:06] the dependency pulling it in main was very old, lost for B&C, but now back again [07:07] so I thnik all (old) paper work is done [07:07] just needs an AA to do that [07:07] maybe I should add a Disco task to the old MIR and set the AA's to the bug? [07:22] -queuebot:#ubuntu-release- New: accepted lemonldap-ng [amd64] (disco-proposed) [2.0.0+ds-1] [07:22] -queuebot:#ubuntu-release- New: accepted r-cran-fnn [arm64] (disco-proposed) [1.1.2.1-1] [07:22] -queuebot:#ubuntu-release- New: accepted r-cran-fnn [i386] (disco-proposed) [1.1.2.1-1] [07:22] -queuebot:#ubuntu-release- New: accepted r-cran-fnn [s390x] (disco-proposed) [1.1.2.1-1] [07:22] -queuebot:#ubuntu-release- New: accepted r-cran-fnn [amd64] (disco-proposed) [1.1.2.1-1] [07:22] -queuebot:#ubuntu-release- New: accepted r-cran-fnn [ppc64el] (disco-proposed) [1.1.2.1-1] [07:22] -queuebot:#ubuntu-release- New: accepted r-cran-fnn [armhf] (disco-proposed) [1.1.2.1-1] [07:23] -queuebot:#ubuntu-release- New: accepted freedict-wikdict [amd64] (disco-proposed) [2018.11.02-1] [07:23] -queuebot:#ubuntu-release- New: accepted r-cran-rcppannoy [amd64] (disco-proposed) [0.0.11-1] [07:23] -queuebot:#ubuntu-release- New: accepted r-cran-rcppannoy [armhf] (disco-proposed) [0.0.11-1] [07:23] -queuebot:#ubuntu-release- New: accepted r-cran-rcppannoy [ppc64el] (disco-proposed) [0.0.11-1] [07:23] -queuebot:#ubuntu-release- New: accepted piexif [amd64] (disco-proposed) [1.0.13-2] [07:23] -queuebot:#ubuntu-release- New: accepted r-cran-rcppannoy [i386] (disco-proposed) [0.0.11-1] [07:23] -queuebot:#ubuntu-release- New: accepted r-cran-rcppannoy [arm64] (disco-proposed) [0.0.11-1] [07:23] -queuebot:#ubuntu-release- New: accepted r-cran-rcppannoy [s390x] (disco-proposed) [0.0.11-1] [07:47] vorlon, infinity etc. could ypou assist into getting this change merged and uploaded? https://code.launchpad.net/~rikmills/ubiquity/+git/ubiquity/+merge/359785 [07:48] Kubuntu has not had a working daily iso for over a week now [07:50] looking [07:52] I built the change in my ppa and tested [07:53] acheronuk: uploaded [07:53] vorlon: great. thank you [08:01] vorlon: um. failed to build. needs the d-i update stuff run when making source? [08:02] tsimonq2: this mate-screensaver upload is a binary sync from https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa and I don't know the properties of this ppa to see that it's appropriate for binary copy to the main archive (since I'm not a member of the team). Either get me a non-binary upload to the queue, or get someone from the security team to sign off that this is an ok source [08:03] for copying? [08:03] acheronuk: hngh haaaate. ok. [08:06] * acheronuk agrees with vorlon on that ^^^ [08:07] * vorlon pines for the good old days of bzr-builddeb hooks [08:22] -queuebot:#ubuntu-release- New binary: linux-signed-gcp-edge [amd64] (bionic-proposed/main) [4.18.0-1005.6~18.04.1] (no packageset) [08:32] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp-edge [amd64] (bionic-proposed) [4.18.0-1005.6~18.04.1] [09:20] -queuebot:#ubuntu-release- Unapproved: rejected landscape-client [source] (cosmic-proposed) [18.01-0ubuntu4.1] [09:21] -queuebot:#ubuntu-release- Unapproved: rejected landscape-client [source] (bionic-proposed) [18.01-0ubuntu3.2] [09:23] -queuebot:#ubuntu-release- Unapproved: rejected landscape-client [source] (xenial-proposed) [16.03-0ubuntu2.16.04.5] [09:23] -queuebot:#ubuntu-release- Unapproved: rejected landscape-client [source] (trusty-proposed) [14.12-0ubuntu6.14.04.4] [09:33] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (disco-proposed) [4.19.0-8.9] [09:34] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (disco-proposed) [4.19.0-8.9] [09:45] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (bionic-proposed/main) [4.15.0-1036.38] (kernel) [09:45] -queuebot:#ubuntu-release- New source: egl-wayland (disco-proposed/primary) [1.1.1-0ubuntu1] [09:46] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (trusty-proposed/main) [4.15.0-1036.38~14.04.2] (kernel) [09:47] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (bionic-proposed) [4.15.0-1036.38] [09:47] -queuebot:#ubuntu-release- New binary: linux-signed-gcp [amd64] (bionic-proposed/main) [4.15.0-1026.27] (kernel) [09:47] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (trusty-proposed) [4.15.0-1036.38~14.04.2] [09:48] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp [amd64] (bionic-proposed) [4.15.0-1026.27] [10:16] -queuebot:#ubuntu-release- Unapproved: e2fsprogs (cosmic-proposed/main) [1.44.4-2 => 1.44.4-2ubuntu0.1] (core) [10:45] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (bionic-proposed/main) [4.15.0-43.46] (core, kernel) [10:46] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (bionic-proposed/main) [4.15.0-43.46] (core, kernel) [10:51] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (bionic-proposed) [4.15.0-43.46] [10:51] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (bionic-proposed) [4.15.0-43.46] [11:06] -queuebot:#ubuntu-release- Unapproved: update-notifier (xenial-proposed/main) [3.168.9 => 3.168.10] (ubuntu-desktop, ubuntu-server) [11:44] tjaalton, vorlon: ^ people started hitting this one with unattended-upgrades sru in xenial-proposed, it would be nice it we could fix this one before u-u gets to -updates [11:45] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (xenial-proposed/main) [4.15.0-1036.38~16.04.1] (kernel) [12:18] (disco-amd64)root@bionic:/# DEB_HOST_ARCH=ppc64el dpkg-buildflags --get CFLAGS [12:18] -g -O3 -g -O2 -fdebug-prefix-map=/=. -fstack-protector-strong -Wformat -Werror=format-security [12:18] vorlon: infinity: doko: looks like new dpkg broke ppc64el's CFLAGS [12:18] https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=d5374bc618310917557daa9c9ac2f4930515a0b2 [12:18] probably caused by that one [12:28] Laney: that for Libreoffice? I got to the patch with dpkg-buildflags --get CFLAGS in it, but couldn't see what change in dpkg may have been at fault [12:28] that's where I noticed it [12:28] * acheronuk nods [12:28] that one I linked :-) [12:29] Laney: ah, had not seen your comments in #ubuntu-desktop :) [12:29] linked it here too :P [12:29] but yeh [12:31] yeah, I saw in here, but didn't have the libreoffice context. hence men asking [12:31] *me asking [12:33] Aaaanyway. [12:34] sorry. I just idly looked at it earlier, and was pleased to see I got most of the way there [12:34] * acheronuk shuts up [12:37] I guess it's most correct for the Ubuntu hook to run the parent one first and then *append* its changes? [13:04] -queuebot:#ubuntu-release- Unapproved: accepted update-notifier [source] (xenial-proposed) [3.168.10] [13:04] rbalint: done [13:05] tjaalton, thanks! [13:33] -queuebot:#ubuntu-release- Unapproved: nova (bionic-proposed/main) [2:17.0.6-0ubuntu2 => 2:17.0.7-0ubuntu1] (openstack, ubuntu-server) [14:19] o/ archive admin, I sponsored d-i for mfo/ddstreet to support HTTPS using ca-certificates-udeb, but it FTBFS because it cannot locate ca-certificates-udeb (even after an attempt to rebuild w/ no change in disco) and then we figured out the udeb were missingin in main (http://archive.ubuntu.com/ubuntu/pool/main/c/ca-certificates/) but were found in universe instead (http://archive.ubuntu.com/ubuntu/pool/universe/c/ca-certificates/) and I [14:19] suspect to be the reason why d-i fails as it cannot get the universe udeb I guess ? thoughts ? what can be done to address this ? [14:19] related note: if we rebuild ca-certificates in a PPA, the udeb goes to main/, but on the normal LP builders, it's going to universe/ [14:25] Just a friendly ping on archive admin that I know and aware of : sil2100 stgraber vorlon infinity ^ [14:28] mfo ddstreet ^ [14:41] tjaalton: hi, I uploaded a new version of nova to the bionic queue per sil2100's comments on it yesterday. if you happen to have a chance to review it's ready. [15:02] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (xenial-proposed) [4.15.0-1036.38~16.04.1] [15:04] sil2100 stgraber volon infinity (and other archive admin) : I left you a more official comment on the public bug : https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807023/comments/23 [15:04] Ubuntu bug 1807023 in debian-installer (Ubuntu Disco) "installer stock images fail to validate any HTTPS certificates (ca-certificates missing)" [Medium,In progress] [15:04] mfo ddstreet ^ [15:04] slashd, ack. :) [15:42] vorlon: ack [16:18] Laney: syntactically correct. why can't LO handle that? but yes, -O2 is not correct [16:18] a bug in libreoffice, but that's not the point - that is why in here I didn't mention Libreoffice [16:18] before acheronu_k did anyway [16:19] anyway I submitted a potential patch [16:24] where? [16:25] BTS [16:28] man, bug#? [16:29] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915881 there ya go [16:29] Debian bug 915881 in libdpkg-perl "Ubuntu's custom build flags are overridden by Debian's" [Normal,Open] [16:31] \o/ [17:02] vorlon: Er, re-reading your earlier message, Adam might be able to attest to it. [17:02] infinity: ^ [17:02] mdeslaur maybe as well. [17:03] (mate-screensaver upload in Bionic queue is a copy from the security team PPA from binaries, he's asking if it's appropriate for a copy) [17:14] -queuebot:#ubuntu-release- New binary: tl-parser [s390x] (disco-proposed/universe) [0.0.0+git20180215.f49077de-1] (no packageset) [17:14] -queuebot:#ubuntu-release- New binary: tl-parser [ppc64el] (disco-proposed/universe) [0.0.0+git20180215.f49077de-1] (no packageset) [17:20] Laney: Grr, thanks for that catch. [17:33] No bother [17:42] -queuebot:#ubuntu-release- New binary: tl-parser [amd64] (disco-proposed/universe) [0.0.0+git20180215.f49077de-1] (no packageset) [17:55] Laney: Fix uploaded. [17:56] Laney: http://paste.ubuntu.com/p/vRVjxHwfpM/ if you're curious. [17:56] Cheers duck. [17:57] Might want to post that to the bug, if you're intending it to supersede the patch I posted there [17:57] * Laney went for "append and override" [17:57] Laney: Bug number? [17:57] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915881 [17:57] Debian bug 915881 in libdpkg-perl "Ubuntu's custom build flags are overridden by Debian's" [Normal,Open] [17:57] Linked it to d_oko just above [17:58] and X-Debbugs-Cced you :P [17:58] Laney: Ahh, haven't checked my mail today. :P [17:58] Laney: But also, append is icky there IMO. [17:59] Laney: I prefer the amd64 and ppc64el lines to actually be comparable, not one to be a mess of deciding which option came first. [17:59] * Laney shrugs [17:59] As I say, go ahead and post your better version if you like [17:59] Doing. [18:00] You could say it's icky having to go and update two places if the upstream default ever changes. [18:00] but I was going to let some reviewer decide [18:01] Quittin' time [18:01] updating a copyright file has removed my will to be at the computer [18:03] Laney: Yeah, in theory, that's super icky (and I agree). In practice, the Debian default of '-g -O2' hasn't changed in decades, so I'm not sure it's a deep concern. [18:04] Laney: But I'd also prefer the icky be under the hood than something that users have to deal with every day. [18:06] -queuebot:#ubuntu-release- New binary: tl-parser [arm64] (disco-proposed/universe) [0.0.0+git20180215.f49077de-1] (no packageset) [18:09] slashd: Promoted. I'll retry the builds when the publisher's done moving it around. [18:10] infinity: speaking of build flags, I was reading https://lwn.net/Articles/192624/ at the end of 1.0 there is a claim that all of Ubuntu builds with -Wl,-O1 [18:10] but that's not true, is it? [18:10] infinity, thanks a lot [18:10] ddstreet, mfo ^ fyi [18:12] jbicha: If it's true, it's being baked into the compiler or linker, but I don't *think* it is... [18:13] infinity, does the promotion done for each release we support atm also or just devel release ? [18:13] doko: can you confirm the answer to my -Wl,-O1 question? [18:14] slashd: Just disco. For other releases, it'll require some fiddling. [18:14] infinity, ack tks [18:14] ddstreet, mfo again fyi ^ [18:15] slashd: For bionic and cosmic, I'll have to copy ca-certificates to -updates, then do the promotion. For earlier releases, you need to SRU something that actually produces the package. ;) [18:16] slashd: Did you have SRUs in flight for b/c at least? [18:16] infinity, mfo has all the debdiff ready for sponsoring yes [18:16] https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1807023 [18:16] Ubuntu bug 1807023 in debian-installer (Ubuntu Disco) "installer stock images fail to validate any HTTPS certificates (ca-certificates missing)" [Medium,In progress] [18:18] slashd: Also, WTF: https://launchpad.net/ubuntu/+source/ca-certificates/20180409ubuntu0.19.04.1 [18:18] slashd: I see three names involved in that upload. That means three people thought things magically move between components on upload? :/ [18:18] slashd: Can we fix that? :) [18:19] infinity, I know thats my bad, I miss the ball on that one [18:20] infinity, how would you like me to fix this ? [18:20] slashd: I meant "can we fix the knowlege gap?" ... One person being confused is fair enough, three people sharing confusion is the sort of thing that turns into folklore. [18:20] infinity, yeah I guess we all learn from that don't worry that won't happen again [18:20] And that's how you get people who think -pipe makes compiled code faster. [18:21] slashd: Anyhow, I deleted that upload, we can all just pretend it didn't happen. :) [18:21] infinity, I appreciate it ;) [18:23] slashd: For future reference, as you've discovered, things move between components "because we say so", and we tend to do it based on reports telling us that it's needed (ie: because something in main now depends/build-depends on it) [18:24] slashd: In this case, step 1 wasn't going to happen because step 2 wasn't going to happen because d-i's udebs are held in main by a package that d-i itself produces, which is a bit chicken-and-eggy, so the poke was required. :) [18:25] slashd: For all things other than d-i, it happens as described, though. In that if something hits proposed that needs new build-deps, you don't need to bug us to promote, we have reports. But you might have to participate in MIR stuff, if it's a new source in main. [18:27] infinity, yeah that confirm I wasn't totally wrong ;p I pinged you cause I was expecting it didn't need an MIR due to the fact that the package was already in main (otherwise I would have done the necessary inside an LP), the ca-certificate rebuild was indeed a bad decision, I admit it, but again I learn a lesson out of it. [18:27] infinity, thanks again [18:27] infinity much thnx - for me the confusion was around ca-certificates being in main, while ca-certificates-udebs being in universe...didn't know that was possible [18:28] i thought the component referrend to the src pkg, not binary [18:28] ddstreet, everything is cleaned up now, and we all learn something so all good ;) [18:28] yep excellent stuff [18:29] infinity i'll wait to sru until bionic and cosmic have ca-certificates-udebs moved to main, and we do have patches to generate -udebs for t/x ready [18:30] ddstreet: Go ahead and do the d-i uploads to bionic and cosmic now, I'll clean up the mess when I review/accept them. [18:31] infinity ok will do, thnx [18:31] ddstreet: I need to do some bits on my end to import those changes to bzr as well, so may as well while it's fresh in my mind. [18:48] infinity i uploaded d-i to cosmic, but for bionic there's a pending d-i sru from lp #1789227 [18:48] Launchpad bug 1789227 in debian-installer (Ubuntu Bionic) "nvme devices namespace assigned to the wrong controller" [Undecided,Fix committed] https://launchpad.net/bugs/1789227 [18:48] which isn't verified yet [18:49] you want me to upload to bionic anyway and see if we can verify the pending sru before approving the new upload? [18:49] dannf: *poke* [18:49] infinity: yo [18:49] dannf: You have a month-old d-i SRU to bionic that's gumming up the works. [18:49] dannf: pls to be verifying. [18:49] -queuebot:#ubuntu-release- Unapproved: debian-installer (cosmic-proposed/main) [20101020ubuntu557 => 20101020ubuntu557.1] (core) [18:50] infinity: oh man, i hate gum [18:50] dannf: It's the worst. [18:52] infinity: i don't see it in -proposed [18:53] dannf: https://launchpad.net/ubuntu/+source/debian-installer/20101020ubuntu543.3 [18:53] infinity: oh, sorry - the Unapproved message below yours confused me [18:54] ddstreet: Go ahead and upload to bionic too. [18:54] will do thnx [18:56] cpaelzer you're looking at the autopkgtest failures for nova, right? re: "... NoSuchTableError: migration_tmp" [18:56] -queuebot:#ubuntu-release- Unapproved: debian-installer (bionic-proposed/main) [20101020ubuntu543.3 => 20101020ubuntu543.4] (core) [18:57] oh coreycb is now fixing it? [18:57] ddstreet: yes, i'll upload something in a bit [18:57] awesome thnx! [18:58] ddstreet: np bug 1807262 for reference [18:58] bug 1807262 in migrate (Ubuntu) "stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp" [High,Triaged] https://launchpad.net/bugs/1807262 [19:21] -queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (cosmic-proposed) [20101020ubuntu557.1] [19:26] dannf: Actually, I'm just going to accept ddstreet's upload on top of yours, since yours was just an ABI bump. If you can verify your fix with his version instead of yours, that'd be nice. [19:27] infinity: sorry, got interrupted w/ credit card company crap. i have definitely tested that installer version, so i'll mark it as verified. however, i can't say that it fixed the original issue associiated with the kernel. that's still waiting for the user to clarify [19:27] -queuebot:#ubuntu-release- Unapproved: accepted debian-installer [source] (bionic-proposed) [20101020ubuntu543.4] [19:28] dannf: Fair. So we know d-i didn't regress, we don't know if the kernel fixed the bug, but that's not d-i's concern. [19:28] right [19:28] * infinity nods. [19:29] ddstreet: Okay, cosmic and bionic both accepted and bzr branches fixed up to import those changes. [19:29] ddstreet: I'll need quick turnaround on bionic so it doesn't block d-i uploads needed for the point release. Less picky about other releases. [19:30] infinity no problem, should be able to verify today [19:30] Ta. [19:30] i'll upload for t/x monday, and ping you then about ca-certificates-udeb component for those [19:30] (we do have a patch to actually build -udeb for it for t/x) [19:31] ddstreet: ca-certificates-udeb will default to main for those two releases anyway, since it's a new package, and new binaries get the component of their source by default. [19:31] great, that makes it easier :) [19:31] thnx [19:32] mfo do you want to verify d-i for bionic (and c/d) or should i? ^ [19:33] ddstreet, i can verify them :) [19:33] thnx mfo! [19:33] (It's still building on amd64, but should be done within the hour) [19:33] alright. [19:34] * infinity writes an angry black metal song called "An Ode to Ell One Tee Eff and Why I'm Going to Burn Everything Down". [19:56] ddstreet: yes I looked at the bug [19:57] ddstreet: as libvirt is blocked by it [19:57] I see coreycb has handed you the bug reference [19:57] so you will know by know what was going on [19:57] cpaelzer yep one of my uploads too - sorry for highlighting you before i checked the recent updates in the bug [19:59] -queuebot:#ubuntu-release- New binary: linux-signed-gcp [amd64] (xenial-proposed/main) [4.15.0-1026.27~16.04.1] (kernel) [20:34] infinity: Since vorlon doesn't have access to verify the validity of that mate-screensaver binary + source sync to Bionic, could yyou review? [20:35] Doesn't have access? [20:36] Oh, doesn't have access to the PPA's properties. [20:37] vorlon: For reference, ubuntu-security-proposed is the security team's "build here, then copy to proposed" PPA for security updates that need more love, aren't embargoed, etc. It's a valid binary copy source. [20:39] tsimonq2: vorlon did leave a comment on the bug, though, which should be addressed. [20:41] tsimonq2: E:NoTestCases, E:NeedsMoreExploratoryTesting [20:41] (to summarize) [20:41] I think the test case complaint was his confusion about where "see also" was pointing. [20:41] But the other is valid. [20:41] infinity: to be fair for SRUs I"d still ilke to see at least *one* documented test case in the bug, but I'm picky :P [20:42] (my opinion in the matter is also irrelevant but still) [20:42] teward: There is one. [20:43] infinity: missed it because the steps looked repeated with the wall of text detailed test case oopsies :| [20:43] *needs more coffee* [21:09] infinity: I was not confused about where "see also" was pointing, I simply consider it wrong to have such "see also"s in an SRU template because they introduce opportunity for error or ambiguity [21:13] vorlon: Maybe I misread your intent, then. I often do similar things (see ten lines below in the original report) to avoid a mess of copy and paste. [21:58] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [ppc64el] (bionic-proposed/main) [4.18.0-13.14~18.04.1] (kernel) [22:01] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (bionic-proposed/main) [4.18.0-13.14~18.04.1] (kernel)