| -queuebot:#ubuntu-release- Unapproved: accepted grub2 [source] (bionic-proposed) [2.02-2ubuntu8.12] | 00:14 | |
| -queuebot:#ubuntu-release- Unapproved: grub2 (bionic-proposed/main) [2.02-2ubuntu8.12 => 2.02-2ubuntu8.12] (core) | 00:37 | |
| -queuebot:#ubuntu-release- Unapproved: grub2-signed (bionic-proposed/main) [1.93.12 => 1.93.13] (core) | 00:48 | |
| -queuebot:#ubuntu-release- Unapproved: grub2 (bionic-proposed/main) [2.02-2ubuntu8.12 => 2.02-2ubuntu8.12] (core) | 00:49 | |
| -queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (bionic-proposed) [2.02-2ubuntu8.12] | 01:04 | |
| -queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (bionic-proposed) [2.02-2ubuntu8.12] | 01:04 | |
| -queuebot:#ubuntu-release- Unapproved: accepted grub2-signed [source] (bionic-proposed) [1.93.13] | 01:05 | |
| -queuebot:#ubuntu-release- New binary: libgpuarray [s390x] (disco-proposed/universe) [0.7.6-2] (no packageset) | 05:15 | |
| -queuebot:#ubuntu-release- New binary: libgpuarray [ppc64el] (disco-proposed/universe) [0.7.6-2] (no packageset) | 05:17 | |
| -queuebot:#ubuntu-release- New binary: libgpuarray [amd64] (disco-proposed/universe) [0.7.6-2] (no packageset) | 05:19 | |
| -queuebot:#ubuntu-release- New binary: libgpuarray [i386] (disco-proposed/universe) [0.7.6-2] (no packageset) | 05:19 | |
| -queuebot:#ubuntu-release- New binary: libgpuarray [arm64] (disco-proposed/universe) [0.7.6-2] (no packageset) | 05:36 | |
| -queuebot:#ubuntu-release- New binary: libgpuarray [armhf] (disco-proposed/universe) [0.7.6-2] (no packageset) | 05:37 | |
| vorlon | cyphermox: sorry, I guess I failed to let you know I had accepted the fixed grub2 in bionic-proposed; were you still looking at verification today? | 06:13 |
|---|---|---|
| vorlon | cyphermox: if you can get grub2 verified first thing in the morning, I will still release it and (be on call for regressions this weekend)( | 06:54 |
| -queuebot:#ubuntu-release- New: accepted libgpuarray [amd64] (disco-proposed) [0.7.6-2] | 07:03 | |
| -queuebot:#ubuntu-release- New: accepted libgpuarray [armhf] (disco-proposed) [0.7.6-2] | 07:03 | |
| -queuebot:#ubuntu-release- New: accepted libgpuarray [arm64] (disco-proposed) [0.7.6-2] | 07:03 | |
| -queuebot:#ubuntu-release- New: accepted libgpuarray [i386] (disco-proposed) [0.7.6-2] | 07:03 | |
| -queuebot:#ubuntu-release- New: accepted libgpuarray [s390x] (disco-proposed) [0.7.6-2] | 07:03 | |
| -queuebot:#ubuntu-release- New: accepted libgpuarray [ppc64el] (disco-proposed) [0.7.6-2] | 07:03 | |
| -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (bionic-proposed/main) [4.18.0-15.16~18.04.1] (kernel) | 08:03 | |
| -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (cosmic-proposed/main) [4.18.0-15.16] (core, kernel) | 08:03 | |
| -queuebot:#ubuntu-release- New binary: linux-signed-hwe [ppc64el] (bionic-proposed/main) [4.18.0-15.16~18.04.1] (kernel) | 08:04 | |
| -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (cosmic-proposed/main) [4.18.0-15.16] (core, kernel) | 08:04 | |
| -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (bionic-proposed) [4.18.0-15.16~18.04.1] | 08:06 | |
| -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (cosmic-proposed) [4.18.0-15.16] | 08:06 | |
| -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [ppc64el] (bionic-proposed) [4.18.0-15.16~18.04.1] | 08:06 | |
| -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (cosmic-proposed) [4.18.0-15.16] | 08:06 | |
| -queuebot:#ubuntu-release- New binary: gcc-9-cross-ports [ppc64el] (disco-proposed/universe) [0ubuntu2] (no packageset) | 08:53 | |
| tjaalton | infinity: just fyi that I'm looking into bug 1815172 which seems a showstopper for MATE, though it was only filed today.. booting the 32bit image seems to fail on my hw too so I'll bisect it if nothing else.. | 10:15 |
| ubot5 | bug 1815172 in mesa (Ubuntu Cosmic) "Black screen on skylake after 18.0 => 18.2 update" [Undecided,New] https://launchpad.net/bugs/1815172 | 10:15 |
| tjaalton | upstream is on it too | 10:15 |
| apw | tjaalton, try the kernle in -proposed | 10:24 |
| tjaalton | apw: ok.. | 10:27 |
| apw | tjaalton, i assuem we are talking linux-hwe here ... there is a quick respin in there, which will be going out RSN | 10:28 |
| tjaalton | apw: actually no.. stock bionic | 10:28 |
| apw | the bionic one is worth chceking your image is up to date | 10:29 |
| smb | tjaalton, could that have been the kernel with the DP MST issue which we had a follow-up already? | 10:29 |
| tjaalton | smb: no that was an issue with external monitors, in this case the xserver just fails with an error from the i965 dri driver | 10:30 |
| tjaalton | though with the live image it ends up trying to respawn the session, essentially killing it | 10:30 |
| tjaalton | only mate/lightdm seem affected so far | 10:30 |
| smb | tjaalton, live image would use the cosmic kernel which has the i915 crash, no? | 10:30 |
| tjaalton | ok if there's an actual crash then yes | 10:31 |
| tjaalton | I'll still install it with nomodeset and debug this other issue just in case :) | 10:31 |
| -queuebot:#ubuntu-release- New: rejected gcc-9-cross-ports [ppc64el] (disco-proposed) [0ubuntu2] | 10:31 | |
| tjaalton | the bugreport was with stock kernel | 10:32 |
| tjaalton | could be I'm not able to reproduce it after all, we'll see | 10:32 |
| smb | tjaalton, at least one of the reporter had enough info to show that without the revert there is an oops early on. So no inteldrmfb and no X | 10:33 |
| tjaalton | ah that gen4 thing? this is with kabylake.. | 10:33 |
| tjaalton | so gen9 | 10:33 |
| smb | tjaalton, ah ok... so maybe yet something different. Intel quality | 10:35 |
| tjaalton | oh well, 64bit mate image works fine on this | 10:49 |
| -queuebot:#ubuntu-release- New binary: gcc-9-cross-ports [ppc64el] (disco-proposed/universe) [0ubuntu3] (no packageset) | 11:40 | |
| tjaalton | and installing 32bit results in a broken grub/efi | 11:58 |
| === kstenerud90 is now known as kstenerud | ||
| -queuebot:#ubuntu-release- New binary: gcc-9-cross [ppc64el] (disco-proposed/universe) [0ubuntu2] (no packageset) | 12:25 | |
| cyphermox | vorlon: I did check it very very late last night; I'm going to retest now to be able to write it down in the bugs | 13:37 |
| cyphermox | tjaalton: what do you mean broken grub/efi on 32bit? | 13:37 |
| tjaalton | cyphermox: nevermind, fixed already. it's a bad idea to mix efi/legacy installs on the same disk :) | 13:55 |
| cyphermox | well, on the same install it's supposed to work... so we need to make sure it didn't get broken somehow | 13:57 |
| tjaalton | it drops to grub shell, until grub-install is run from an efi partition | 13:59 |
| -queuebot:#ubuntu-release- New binary: gcc-9-cross-ports [arm64] (disco-proposed/universe) [0ubuntu3] (no packageset) | 14:00 | |
| oSoMoN | doko, re https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921683 , when are you planning on syncing the new firebird3.0 ? | 14:12 |
| ubot5 | Debian bug 921683 in firebird3.0 "firebird 3.0 has unsatisfiable dependency on libicu" [Serious,Fixed] | 14:12 |
| oSoMoN | this is preventing LO builds | 14:12 |
| -queuebot:#ubuntu-release- New binary: gcc-9-cross [i386] (disco-proposed/universe) [0ubuntu2] (no packageset) | 14:21 | |
| cyphermox | tjaalton: but it's a separate install? | 14:27 |
| tjaalton | cyphermox: two partitions, one that was installed with efi, the other with legacy booted 32bit image. after the 32bit install grub is confused | 14:29 |
| cyphermox | ok | 14:35 |
| doko | oSoMoN: I have nothing to do with that except for filing that bug report. autosyncs are still enabled | 14:43 |
| -queuebot:#ubuntu-release- New: rejected gcc-9-cross-ports [arm64] (disco-proposed) [0ubuntu3] | 14:43 | |
| -queuebot:#ubuntu-release- New: rejected gcc-9-cross [i386] (disco-proposed) [0ubuntu2] | 14:43 | |
| -queuebot:#ubuntu-release- New: rejected gcc-9-cross-ports [ppc64el] (disco-proposed) [0ubuntu3] | 14:43 | |
| -queuebot:#ubuntu-release- New: rejected gcc-9-cross [ppc64el] (disco-proposed) [0ubuntu2] | 14:43 | |
| oSoMoN | doko, right, do you happen to know when we can expect the auto-sync to happen? | 14:47 |
| cjwatson | $ ssh -t snakefruit sudo -iu ubuntu-archive crontab -l | grep auto-sync | 14:49 |
| cjwatson | 0 5,11,17,23 * * * http_proxy=http://squid.internal:3128/ PYTHONPATH=/home/ubuntu-archive/python auto-sync --log-directory ~/public_html/auto-sync --batch | 14:49 |
| oSoMoN | cjwatson, thanks | 14:56 |
| -queuebot:#ubuntu-release- Unapproved: cockpit (cosmic-backports/universe) [184-1~ubuntu18.10.1 => 187-1~ubuntu18.10.1] (no packageset) | 14:57 | |
| -queuebot:#ubuntu-release- Unapproved: cockpit (bionic-backports/universe) [184-1~ubuntu18.04.1 => 187-1~ubuntu18.04.1] (no packageset) | 14:58 | |
| -queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (cosmic-backports) [187-1~ubuntu18.10.1] | 14:59 | |
| -queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (bionic-backports) [187-1~ubuntu18.04.1] | 14:59 | |
| -queuebot:#ubuntu-release- Unapproved: courier-authlib (bionic-proposed/universe) [0.68.0-4build1 => 0.68.0-4ubuntu0.1] (no packageset) | 15:07 | |
| -queuebot:#ubuntu-release- Unapproved: libbpp-core (bionic-proposed/universe) [2.4.0-3 => 2.4.0-3ubuntu0.1] (no packageset) | 15:07 | |
| -queuebot:#ubuntu-release- Unapproved: libbpp-seq (bionic-proposed/universe) [2.4.0-2 => 2.4.0-2ubuntu0.1] (no packageset) | 15:07 | |
| -queuebot:#ubuntu-release- Unapproved: ucommon (bionic-proposed/universe) [7.0.0-12 => 7.0.0-16ubuntu0.1] (no packageset) | 15:07 | |
| -queuebot:#ubuntu-release- Unapproved: fswatch (bionic-proposed/universe) [1.11.2+repack-10 => 1.11.2+repack-10ubuntu0.1] (no packageset) | 15:07 | |
| -queuebot:#ubuntu-release- Unapproved: libcec (bionic-proposed/universe) [4.0.2+dfsg1-2ubuntu1 => 4.0.2+dfsg1-2ubuntu1.1] (no packageset) | 15:07 | |
| -queuebot:#ubuntu-release- Unapproved: libbpp-seq-omics (bionic-proposed/universe) [2.4.0-2 => 2.4.0-2ubuntu0.1] (no packageset) | 15:07 | |
| -queuebot:#ubuntu-release- Unapproved: libgda5 (bionic-proposed/universe) [5.2.4-9 => 5.2.4-9ubuntu0.1] (no packageset) | 15:10 | |
| -queuebot:#ubuntu-release- Unapproved: rejected courier-authlib [source] (bionic-proposed) [0.68.0-4ubuntu0.1] | 15:12 | |
| -queuebot:#ubuntu-release- Unapproved: rejected libbpp-core [source] (bionic-proposed) [2.4.0-3ubuntu0.1] | 15:12 | |
| -queuebot:#ubuntu-release- Unapproved: rejected libbpp-seq [source] (bionic-proposed) [2.4.0-2ubuntu0.1] | 15:12 | |
| -queuebot:#ubuntu-release- Unapproved: rejected ucommon [source] (bionic-proposed) [7.0.0-16ubuntu0.1] | 15:12 | |
| -queuebot:#ubuntu-release- Unapproved: rejected fswatch [source] (bionic-proposed) [1.11.2+repack-10ubuntu0.1] | 15:12 | |
| -queuebot:#ubuntu-release- Unapproved: rejected libcec [source] (bionic-proposed) [4.0.2+dfsg1-2ubuntu1.1] | 15:12 | |
| -queuebot:#ubuntu-release- Unapproved: rejected libbpp-seq-omics [source] (bionic-proposed) [2.4.0-2ubuntu0.1] | 15:12 | |
| -queuebot:#ubuntu-release- Unapproved: accepted libgda5 [source] (bionic-proposed) [5.2.4-9ubuntu0.1] | 15:15 | |
| -queuebot:#ubuntu-release- Unapproved: accepted courier-authlib [source] (bionic-proposed) [0.68.0-4ubuntu0.1] | 15:31 | |
| slashd | tjaalton, vorlon or any SRU vanguard : A user is complaining the pci.ids list in pciutils need update (no LP bug created yet). A few device id he is using has been added after xenial. Would it be okay if I SRU an update of pci.ids base on upstream --> https://github.com/pciutils/pciutils/commit/701fdd1e | 15:38 |
| slashd | in Xenial ^ sorry | 15:38 |
| -queuebot:#ubuntu-release- Unapproved: accepted fswatch [source] (bionic-proposed) [1.11.2+repack-10ubuntu0.1] | 15:39 | |
| -queuebot:#ubuntu-release- Unapproved: accepted libbpp-core [source] (bionic-proposed) [2.4.0-3ubuntu0.1] | 15:44 | |
| -queuebot:#ubuntu-release- Unapproved: accepted libbpp-seq [source] (bionic-proposed) [2.4.0-2ubuntu0.1] | 15:47 | |
| -queuebot:#ubuntu-release- New binary: gcc-9-cross-ports [ppc64el] (disco-proposed/universe) [0ubuntu4] (no packageset) | 15:49 | |
| -queuebot:#ubuntu-release- Unapproved: accepted libbpp-seq-omics [source] (bionic-proposed) [2.4.0-2ubuntu0.1] | 15:54 | |
| -queuebot:#ubuntu-release- Unapproved: accepted libcec [source] (bionic-proposed) [4.0.2+dfsg1-2ubuntu1.1] | 15:57 | |
| slashd | tjaalton, vorlon : I have filed a bug to document the discussion in the right place : https://launchpad.net/bugs/1815212 | 15:58 |
| ubot5 | Ubuntu bug 1815212 in pciutils (Ubuntu) "Update pci.ids for pciutils (xenial)" [Undecided,New] | 15:58 |
| -queuebot:#ubuntu-release- Unapproved: apt (trusty-proposed/main) [1.0.1ubuntu2.19 => 1.0.1ubuntu2.20] (core) | 16:06 | |
| -queuebot:#ubuntu-release- Unapproved: ucommon (bionic-proposed/universe) [7.0.0-12 => 7.0.0-12ubuntu0.1] (no packageset) | 16:23 | |
| -queuebot:#ubuntu-release- Unapproved: rejected ucommon [source] (bionic-proposed) [7.0.0-16ubuntu0.1] | 16:24 | |
| -queuebot:#ubuntu-release- Unapproved: ucommon (bionic-proposed/universe) [7.0.0-12 => 7.0.0-12ubuntu0.1] (no packageset) | 16:25 | |
| -queuebot:#ubuntu-release- Unapproved: rejected ucommon [source] (bionic-proposed) [7.0.0-12ubuntu0.1] | 16:40 | |
| -queuebot:#ubuntu-release- Unapproved: accepted ucommon [source] (bionic-proposed) [7.0.0-12ubuntu0.1] | 16:41 | |
| tjaalton | slashd: sorry, i've spent all day on the i915 regression triggered by mesa update | 17:02 |
| -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (disco-proposed/main) [4.19.0-13.14] (core, kernel) | 17:02 | |
| -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (disco-proposed/main) [4.19.0-13.14] (core, kernel) | 17:02 | |
| tjaalton | apw, smb, infinity: so, mesa enabled softpin for the intel dri driver, which should work on gen8+ gpu's on kernels 4.5 and up, but there are two patches on 4.20 that would be needed to fix issues when running a 32bit install on those. best to revert the mesa change for 18.04.2 image and pull the kernel commits later (for both 4.15 and 4.18) | 17:03 |
| tjaalton | it's a oneliner to revert | 17:04 |
| smb | tjaalton, I am in favour or anything that does not require another "quick" kernel spin | 17:04 |
| tjaalton | yeah :) | 17:05 |
| -queuebot:#ubuntu-release- New binary: linux-signed [arm64] (disco-proposed/main) [4.19.0-13.14] (core, kernel) | 17:05 | |
| slashd | tjaalton, no problem, if vorlon doesn't answer today, I'll ping sil2100 on Monday | 17:07 |
| -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (disco-proposed) [4.19.0-13.14] | 17:11 | |
| -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (disco-proposed) [4.19.0-13.14] | 17:12 | |
| -queuebot:#ubuntu-release- New: accepted linux-signed [arm64] (disco-proposed) [4.19.0-13.14] | 17:12 | |
| -queuebot:#ubuntu-release- Unapproved: sssd (xenial-proposed/main) [1.13.4-1ubuntu1.12 => 1.13.4-1ubuntu1.13] (kubuntu, ubuntu-desktop, ubuntu-server) | 17:16 | |
| -queuebot:#ubuntu-release- New binary: rust-sniffglue [amd64] (disco-proposed/universe) [0.8.2-4] (no packageset) | 17:16 | |
| -queuebot:#ubuntu-release- New binary: rust-sniffglue [i386] (disco-proposed/universe) [0.8.2-4] (no packageset) | 17:19 | |
| -queuebot:#ubuntu-release- New: accepted rust-sniffglue [amd64] (disco-proposed) [0.8.2-4] | 17:54 | |
| -queuebot:#ubuntu-release- New: accepted rust-sniffglue [i386] (disco-proposed) [0.8.2-4] | 17:54 | |
| infinity | tjaalton: So, I have a new mesa on the way? | 17:56 |
| tjaalton | infinity: yes, waiting for feedback if it fixes the issue.. | 17:58 |
| * infinity nods. | 17:59 | |
| tjaalton | infinity: I forget, should I include the current-proposed changelog for the new upload? | 18:20 |
| tjaalton | or does it spam all the bugs | 18:20 |
| infinity | tjaalton: No! This should be an upload based on -updates. | 18:20 |
| infinity | tjaalton: Not based on -proposed. | 18:21 |
| tjaalton | ah | 18:21 |
| infinity | tjaalton: This is not a way to sneak in a new upstream. :P | 18:21 |
| tjaalton | where should I upload that then | 18:21 |
| tjaalton | proposed has 18.2.8 already | 18:21 |
| infinity | tjaalton: To the queue. I'll just delete 18.2.8 and undelete it after this one's verified and promoted. | 18:21 |
| tjaalton | ok | 18:21 |
| tjaalton | 18.2.8 fixes regressions too | 18:22 |
| tjaalton | but anyway | 18:22 |
| tjaalton | I need a new branch :P | 18:23 |
| tjaalton | for cosmic I'll base it on the current one | 18:23 |
| infinity | tjaalton: It may well fix things, but does it have even remotely enough testing for us to just drop it in right before a point release? | 18:23 |
| tjaalton | dunno, cert folks are off | 18:24 |
| infinity | Yeah, I'll go with "no" then. | 18:24 |
| infinity | It can always land a week or three after, and that's fine. | 18:24 |
| tjaalton | sure | 18:25 |
| tjaalton | but the same question for cosmic then | 18:25 |
| tjaalton | full changelog or just this change | 18:25 |
| infinity | Just this change. The previous one is already in updates. | 18:25 |
| tjaalton | so you'll delete 18.2.8 from there as well? | 18:26 |
| infinity | I'll delete 18.2.8 from proposed, accept 18.2.2+newfix, you verify, I promote, then I undelete 18.2.8. | 18:26 |
| tjaalton | but surely cosmic could be different? | 18:27 |
| infinity | Hrm. Oh, I missed the "cosmic" thing up there. Sorry. | 18:27 |
| infinity | Oh, no. Same thing for cosmic, if you want to rapidly turn around this same fix. | 18:27 |
| tjaalton | noone using cosmic has complained so far, and the installer is what it is | 18:28 |
| infinity | Though, I think cosmic and bionic weren't perfectly in sync, cause you had an extra commit on bionic. I think? | 18:28 |
| tjaalton | so it's mostly about being on par with bionic | 18:28 |
| infinity | It's been a while since I reviewed that. | 18:28 |
| infinity | * intel-whl-aml-cfl-ids.diff: Add missing i965 pci-id's (LP: #1789924) | 18:29 |
| ubot5 | Launchpad bug 1789924 in mesa (Ubuntu Cosmic) "Missing Intel GPU pci-id's" [Undecided,Fix committed] https://launchpad.net/bugs/1789924 | 18:29 |
| infinity | Yeah, that was only in bionic. | 18:29 |
| tjaalton | yeah that one | 18:29 |
| infinity | Up to you what you do with cosmic, IMO. | 18:29 |
| tjaalton | I'll slap it on top of 18.2.8 | 18:30 |
| infinity | Either base it on 18.2.8 in proposed, or on 18.2.2 in release, + the PCI ID thing. | 18:30 |
| infinity | I can adapt to either. | 18:30 |
| tjaalton | but then, -v"18.2.2" or not?-) | 18:30 |
| infinity | I have no intention of releasing the cosmis one the same day you upload it, so caution is less important. | 18:30 |
| tjaalton | right, it can wait | 18:30 |
| infinity | Oh, right. Yeah, that would be v18.2.2 indeed. | 18:31 |
| tjaalton | :) | 18:31 |
| tjaalton | thanks | 18:31 |
| -queuebot:#ubuntu-release- Unapproved: mesa (cosmic-proposed/main) [18.2.8-0ubuntu0~18.10.1 => 18.2.8-0ubuntu0~18.10.2] (core, xorg) | 18:32 | |
| infinity | tjaalton: bionic-proposed one deleted, you can upload that now. | 18:36 |
| tjaalton | uploaded | 18:36 |
| -queuebot:#ubuntu-release- Unapproved: mesa (bionic-proposed/main) [18.2.2-0ubuntu1~18.04.1 => 18.2.2-0ubuntu1~18.04.2] (core, xorg) | 18:37 | |
| tjaalton | there | 18:37 |
| vorlon | slashd: I'm pretty sure we've historically done updates of the pci.ids data in pciutils, yes | 18:40 |
| vorlon | it might even be called out as an SRU exception? | 18:40 |
| -queuebot:#ubuntu-release- Unapproved: accepted mesa [source] (bionic-proposed) [18.2.2-0ubuntu1~18.04.2] | 18:40 | |
| infinity | It is, I think? Tim used to do those, not sure who's picked up that ball. | 18:40 |
| vorlon | slashd: as listed under https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases | 18:40 |
| slashd | vorlon, infinity tks will start working on it then | 18:41 |
| infinity | tjaalton: Both accepted. If you can hunt down some way to verify bionic ASAP, that would be lovely. | 18:41 |
| -queuebot:#ubuntu-release- Unapproved: accepted mesa [source] (cosmic-proposed) [18.2.8-0ubuntu0~18.10.2] | 18:41 | |
| tjaalton | infinity: tomorrow | 18:43 |
| tjaalton | I mean, it'll get verified tomorrow | 18:44 |
| slashd | vorlon, I also puzzle what would be the good practice, SRU the pci.ids or leave the user the decision to use update-pciids which does it automatically | 18:51 |
| infinity | slashd: That second option isn't a great one, for many reasons. | 18:52 |
| vorlon | slashd: ^^ I concur | 18:52 |
| slashd | infinity, vorlon I agree but prefered to ask ;) tks again | 18:52 |
| infinity | slashd: The two that come to mind is (a) it alters a dpkg-managed file in /usr/share and (b) it's an entirely unchecked random download over http. | 18:52 |
| infinity | In fact, I'm a bit shocked we even ship that script at all, or haven't at least neutered it in some way. | 18:53 |
| infinity | That's just begging for an injection attack where intentionally-corrupted pci.ids data exploits something goofy in a library that reads it. | 18:54 |
| slashd | infinity, good point | 18:55 |
| infinity | If we were to give that as an option, we'd need to alter the script (and things that read that data) to use a second user-writable location in /var, and we'd need upstream to provide a signed/verifiable source we can pull from. | 18:56 |
| infinity | But I think "stop shipping the script on the PATH" is a saner plan. | 18:56 |
| slashd | infinity, want me to take benefit of my xenial sru to get rid of it in stable release ? | 18:57 |
| infinity | slashd: Maybe get some input from someone like mdeslaur or sarnold to see if they think I'm being overly paranoid, but I think having a script on path that downloads random junk over http and slams it in a file in /usr/share that gets read by dozens of other binaries is pretty sketchy. | 18:58 |
| infinity | slashd: So I'd be +1 on just nuking it. | 18:58 |
| slashd | infinity, ack will try to have a ACK for security team as well, but sound like a good plan | 18:59 |
| infinity | slashd: Or moving it to /use/share/doc/pciutils/examples | 18:59 |
| slashd | infinity, vorlon ok thanks a lot for your help | 19:00 |
| mdeslaur | oh ew ew ew ew | 19:00 |
| mdeslaur | yeah, moving it to examples would be a good idea | 19:01 |
| slashd | mdeslaur, ack tks | 19:01 |
| infinity | I love when an innocent question leads down a "WTF, why is that a thing" rabbit hole. | 19:03 |
| infinity | I guess back when we trusted the internet to not be full of big meanie-pantses, it sort of made sense. | 19:03 |
| infinity | It does, at least, validate header and footer, to make sure the download completed. It just makes no attempt to validate everything in between for malicious MITM badness. :) | 19:04 |
| infinity | (For the record, I miss that naive and trusting world a lot) | 19:05 |
| mdeslaur | I suspect if we went through the MIR process for everything currently in main, a lot of stuff wouldn't pass :) | 19:06 |
| infinity | mdeslaur: Well, the first step is identifying if we think something has an attack profile that warrants a security audit, and most things don't get that box ticket. | 19:07 |
| infinity | ticked, even. | 19:07 |
| infinity | mdeslaur: If we skipped that question and audited EVERYTHING, it would (a) take a few decades, but also (b) probably end in tears. | 19:07 |
| mdeslaur | If we start with the kernel, we wouldn't need to do any of the other packages ;) | 19:08 |
| infinity | *snort* | 19:08 |
| infinity | To be fair, at least from a static-analysis-can-fix-it code quality perspective, cking already kinda does that. | 19:09 |
| infinity | He's dedicated large portions of his adult life to cleaning up compiler and static analysis warnings in the kernel, with some success. | 19:09 |
| infinity | So, probably a lot of potential CVEs fixed before anyone found a way to exploit them. | 19:10 |
| mdeslaur | yeah | 19:11 |
| -queuebot:#ubuntu-release- New binary: gcc-9-cross-ports [arm64] (disco-proposed/universe) [0ubuntu4] (no packageset) | 19:11 | |
| vorlon | cyphermox: cosmic verification coming also? | 19:12 |
| -queuebot:#ubuntu-release- New binary: gcc-9-cross [ppc64el] (disco-proposed/universe) [0ubuntu3] (no packageset) | 19:22 | |
| cyphermox | yup | 19:22 |
| bdmurray | cjwatson: Your livecd-rootfs upload in the SRU queue for bionic doesn't have a bug reference. Could you add one so the update doesn't get stuck in -proposed? | 19:27 |
| cjwatson | Oh right. Will do, not right now. | 19:29 |
| bdmurray | cjwatson: okay, in the meantime I'll reject it | 19:29 |
| -queuebot:#ubuntu-release- Unapproved: rejected livecd-rootfs [source] (bionic-proposed) [2.525.17] | 19:32 | |
| -queuebot:#ubuntu-release- Unapproved: rejected snapd-glib [source] (cosmic-proposed) [1.45-0ubuntu0.18.10.0] | 19:34 | |
| -queuebot:#ubuntu-release- Unapproved: linux-firmware (cosmic-proposed/main) [1.175.1 => 1.175.2] (core, kernel) | 19:58 | |
| -queuebot:#ubuntu-release- Unapproved: python-networkx (bionic-proposed/main) [1.11-1ubuntu2 => 1.11-1ubuntu3] (ubuntu-server) | 19:59 | |
| -queuebot:#ubuntu-release- Unapproved: accepted gtk+3.0 [source] (cosmic-proposed) [3.24.4-0ubuntu1] | 20:05 | |
| -queuebot:#ubuntu-release- Unapproved: linux-firmware (bionic-proposed/main) [1.173.3 => 1.173.4] (core, kernel) | 20:07 | |
| vorlon | tyhicks: I see initramfs-tools is still stalled in cosmic because it's unreviewable by most of the SRU team. Did you still want to get apw to review, or should I reject this one and let you do a sourceful reupload? | 20:13 |
| infinity | Oh. | 20:23 |
| infinity | I can review that. | 20:23 |
| infinity | Not sure why it was built in a security PPA originally, though. :P | 20:24 |
| -queuebot:#ubuntu-release- Unapproved: rejected snapd [source] (cosmic-proposed) [2.37.2+18.10] | 20:27 | |
| -queuebot:#ubuntu-release- Unapproved: accepted initramfs-tools [sync] (cosmic-proposed) [0.131ubuntu15.1] | 20:33 | |
| tjaalton | infinity: mesa verified on bionic | 21:14 |
| -queuebot:#ubuntu-release- Unapproved: accepted u-boot [source] (cosmic-proposed) [2018.07~rc3+dfsg1-0ubuntu2~18.10.1] | 21:16 | |
| vorlon | cpaelzer: libpam-mount, you appear to have added autopkgtests in SRU but these are still missing in devel | 21:22 |
| -queuebot:#ubuntu-release- Unapproved: accepted chkrootkit [source] (cosmic-proposed) [0.52-2ubuntu0.18.10.1] | 21:25 | |
| infinity | tjaalton: Excellent. And 18.2.8 copied back in. | 21:47 |
| infinity | tjaalton: Oh, but I guess 18.2.8 also needs this patch, same as it did in cosmic. | 21:48 |
| infinity | s/patch/revert/ | 21:48 |
| infinity | tjaalton: So, one of those would be nice at some point. :) | 21:48 |
| -queuebot:#ubuntu-release- New binary: gcc-9-cross [i386] (disco-proposed/universe) [0ubuntu3] (no packageset) | 21:52 | |
| tjaalton | infinity: should I bump the minor version for that (~18.04.2) | 21:56 |
| infinity | tjaalton: Given that's how you did cosmic, that seems like the path of least confusion. | 21:58 |
| tyhicks | infinity: thanks for the initramfs-tools review | 22:01 |
| tyhicks | infinity: it was built in a security PPA because it needs to go to cosmic-security after it receives SRU testing | 22:01 |
| -queuebot:#ubuntu-release- Unapproved: mesa (bionic-proposed/main) [18.2.8-0ubuntu0~18.04.1 => 18.2.8-0ubuntu0~18.04.2] (core, xorg) | 22:07 | |
| -queuebot:#ubuntu-release- Unapproved: partman-efi (cosmic-proposed/main) [71ubuntu4 => 71ubuntu4.1] (core) | 22:08 | |
| vorlon | tyhicks: would fit the workflow better if such things could be built in a public security ppa | 22:09 |
| tyhicks | vorlon: yes, I'll make sure of that next time | 22:11 |
| tjaalton | infinity: on the queue now, guess it'll spam that bug once more but so be it | 22:12 |
| tyhicks | vorlon: there's a lot of backstory here about how I did originally build it in a public security ppa, then had to respin it with a small change, and built it in a different (private) PPA just so that infinity doesn't get pissed at me for burning a version number... so I guess it is fitting that he ended up doing the review :) | 22:13 |
| vorlon | :) | 22:15 |
| tjaalton | infinity: there's also the libx11 update with a single cherry-pick | 22:15 |
| infinity | tyhicks: Eh, the kernel team goes through version numbers like toilet paper, I'm sure it would have been fine for initramfs-tools too. :P | 22:26 |
| infinity | tyhicks: But yeah, in future, for non-embargoed stuff, ubuntu-security-proposed or canonical-kernel-team would both have been less headache for people who aren't me. | 22:27 |
| tyhicks | huh, I didn't think about canonical-kernel-team being configured as a security ppa but it obviously is | 22:32 |
| cjwatson | rejecting my own xenial livecd-rootfs upload for the same reason as bdmurray rejected the bionic one | 22:37 |
| -queuebot:#ubuntu-release- Unapproved: rejected livecd-rootfs [source] (xenial-proposed) [2.408.43] | 22:37 | |
| -queuebot:#ubuntu-release- Unapproved: accepted pkgbinarymangler [source] (bionic-proposed) [138.18.04.1] | 22:44 | |
| -queuebot:#ubuntu-release- New binary: rust-wasm-bindgen-backend [ppc64el] (disco-proposed/universe) [0.2.33-1] (no packageset) | 22:53 | |
| -queuebot:#ubuntu-release- New binary: rust-wasm-bindgen-backend [s390x] (disco-proposed/universe) [0.2.33-1] (no packageset) | 22:53 | |
| -queuebot:#ubuntu-release- Unapproved: accepted gtk+3.0 [source] (bionic-proposed) [3.22.30-1ubuntu2] | 22:55 | |
| -queuebot:#ubuntu-release- New binary: rust-wasm-bindgen-backend [amd64] (disco-proposed/universe) [0.2.33-1] (no packageset) | 22:55 | |
| -queuebot:#ubuntu-release- New binary: rust-wasm-bindgen-backend [armhf] (disco-proposed/universe) [0.2.33-1] (no packageset) | 22:55 | |
| -queuebot:#ubuntu-release- New binary: rust-wasm-bindgen-backend [arm64] (disco-proposed/universe) [0.2.33-1] (no packageset) | 22:55 | |
| -queuebot:#ubuntu-release- New binary: rust-wasm-bindgen-backend [i386] (disco-proposed/universe) [0.2.33-1] (no packageset) | 22:55 | |
| -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (xenial-proposed/main) [2.408.42 => 2.408.43] (desktop-core) | 22:57 | |
| -queuebot:#ubuntu-release- New: accepted rust-wasm-bindgen-backend [amd64] (disco-proposed) [0.2.33-1] | 22:58 | |
| -queuebot:#ubuntu-release- New: accepted rust-wasm-bindgen-backend [armhf] (disco-proposed) [0.2.33-1] | 22:58 | |
| -queuebot:#ubuntu-release- New: accepted rust-wasm-bindgen-backend [arm64] (disco-proposed) [0.2.33-1] | 22:58 | |
| -queuebot:#ubuntu-release- New: accepted rust-wasm-bindgen-backend [i386] (disco-proposed) [0.2.33-1] | 22:58 | |
| -queuebot:#ubuntu-release- New: accepted rust-wasm-bindgen-backend [s390x] (disco-proposed) [0.2.33-1] | 22:58 | |
| -queuebot:#ubuntu-release- New: accepted rust-wasm-bindgen-backend [ppc64el] (disco-proposed) [0.2.33-1] | 22:59 | |
| -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (bionic-proposed/main) [2.525.16 => 2.525.17] (desktop-core) | 22:59 | |
| cjwatson | bdmurray: livecd-rootfs reuploaded for xenial and bionic; thanks for catching that | 22:59 |
| -queuebot:#ubuntu-release- Unapproved: accepted busybox [source] (bionic-proposed) [1:1.27.2-2ubuntu3.1] | 23:03 | |
| -queuebot:#ubuntu-release- New binary: rust-wasm-bindgen-macro-support [s390x] (disco-proposed/universe) [0.2.33-1] (no packageset) | 23:07 | |
| -queuebot:#ubuntu-release- New binary: rust-wasm-bindgen-macro-support [amd64] (disco-proposed/universe) [0.2.33-1] (no packageset) | 23:08 | |
| -queuebot:#ubuntu-release- New binary: rust-wasm-bindgen-macro-support [i386] (disco-proposed/universe) [0.2.33-1] (no packageset) | 23:10 | |
| -queuebot:#ubuntu-release- New binary: rust-wasm-bindgen-macro-support [arm64] (disco-proposed/universe) [0.2.33-1] (no packageset) | 23:11 | |
| -queuebot:#ubuntu-release- New binary: rust-wasm-bindgen-macro-support [armhf] (disco-proposed/universe) [0.2.33-1] (no packageset) | 23:12 | |
| -queuebot:#ubuntu-release- New: accepted rust-wasm-bindgen-macro-support [armhf] (disco-proposed) [0.2.33-1] | 23:14 | |
| -queuebot:#ubuntu-release- New: accepted rust-wasm-bindgen-macro-support [amd64] (disco-proposed) [0.2.33-1] | 23:14 | |
| -queuebot:#ubuntu-release- New: accepted rust-wasm-bindgen-macro-support [i386] (disco-proposed) [0.2.33-1] | 23:14 | |
| -queuebot:#ubuntu-release- New: accepted rust-wasm-bindgen-macro-support [arm64] (disco-proposed) [0.2.33-1] | 23:14 | |
| -queuebot:#ubuntu-release- New: accepted rust-wasm-bindgen-macro-support [s390x] (disco-proposed) [0.2.33-1] | 23:14 | |
| -queuebot:#ubuntu-release- New binary: spatialindex [s390x] (disco-proposed/universe) [1.9.0-1] (no packageset) | 23:17 | |
| === valorie is now known as Guest28880 | ||
| -queuebot:#ubuntu-release- Unapproved: accepted chkrootkit [source] (bionic-proposed) [0.52-1ubuntu0.1] | 23:17 | |
| -queuebot:#ubuntu-release- New binary: spatialindex [ppc64el] (disco-proposed/universe) [1.9.0-1] (no packageset) | 23:20 | |
| -queuebot:#ubuntu-release- New binary: spatialindex [amd64] (disco-proposed/universe) [1.9.0-1] (no packageset) | 23:26 | |
| -queuebot:#ubuntu-release- New binary: rust-wasm-bindgen-macro [s390x] (disco-proposed/universe) [0.2.33-1] (no packageset) | 23:28 | |
| -queuebot:#ubuntu-release- New binary: spatialindex [i386] (disco-proposed/universe) [1.9.0-1] (no packageset) | 23:28 | |
| -queuebot:#ubuntu-release- New binary: rust-wasm-bindgen-macro [amd64] (disco-proposed/universe) [0.2.33-1] (no packageset) | 23:29 | |
| -queuebot:#ubuntu-release- New binary: rust-wasm-bindgen-macro [i386] (disco-proposed/universe) [0.2.33-1] (no packageset) | 23:33 | |
| -queuebot:#ubuntu-release- New binary: gnss-sdr [amd64] (disco-proposed/universe) [0.0.10-3] (no packageset) | 23:39 | |
| -queuebot:#ubuntu-release- New binary: gnss-sdr [i386] (disco-proposed/universe) [0.0.10-3] (no packageset) | 23:55 | |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!