=== guiverc_d is now known as guiverc | ||
-queuebot:#ubuntu-release- Unapproved: rejected snapcraft [source] (bionic-proposed) [2.42+18.04.1] | 09:24 | |
-queuebot:#ubuntu-release- Unapproved: snapcraft (bionic-proposed/universe) [2.42+18.04 => 2.42+18.04.1] (no packageset) | 09:25 | |
-queuebot:#ubuntu-release- Unapproved: accepted snapcraft [source] (bionic-proposed) [2.42+18.04.1] | 09:26 | |
juliank | Laney: https://code.launchpad.net/~juliank/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/344818 | 09:30 |
---|---|---|
Laney | ♥ | 09:30 |
-queuebot:#ubuntu-release- Unapproved: nplan (xenial-proposed/universe) [0.32~16.04.4 => 0.32~16.04.5] (no packageset) | 14:03 | |
-queuebot:#ubuntu-release- Unapproved: s390-tools (xenial-proposed/main) [1.34.0-0ubuntu8.5 => 1.34.0-0ubuntu8.6] (no packageset) | 15:00 | |
bdmurray | infinity: Should bug 1767610 about an .img file on releases.ubuntu.com be addressed? | 15:31 |
ubot5 | bug 1767610 in Ubuntu "Wrong server image ubuntu-18.04-live-server-amd64.img ?" [Undecided,New] https://launchpad.net/bugs/1767610 | 15:31 |
sil2100 | cyphermox: hey! Could you take a look at https://bugs.launchpad.net/maas/+bug/1437353 and say if the verification provided is enough to make sure the bug is fixed and no regressions introduced? | 17:18 |
ubot5 | Launchpad bug 1437353 in maas-images "UEFI network boot hangs at grub for adapter 82599ES 10-Gigabit SFI/SFP+" [High,Triaged] | 17:18 |
sil2100 | Since without context the verification comment doesn't give me enough information about whether it was tested against the affected hardware | 17:19 |
sil2100 | cyphermox: I suppose you might have a better idea if that's indeed enough | 17:20 |
cyphermox | sil2100: hard to say, I can't test this on my own | 17:25 |
cyphermox | sil2100: I read at the end of their comment "Our CI completed successfully with this."; I expect this means they ran the test | 17:25 |
cyphermox | ie booted on a system that would otherwise be affected | 17:26 |
cyphermox | I'm asking... | 17:26 |
sil2100 | cyphermox: ok, hm, let me try getting clarification if the system had the required hardware | 17:26 |
sil2100 | Ok | 17:26 |
sil2100 | If you're doing that then excellent | 17:26 |
-queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (artful-proposed) [1.169.4] | 17:29 | |
bdmurray | sil2100: Can you do anything about bug 1767610? | 17:38 |
ubot5 | bug 1767610 in Ubuntu "Wrong server image ubuntu-18.04-live-server-amd64.img ?" [Undecided,New] https://launchpad.net/bugs/1767610 | 17:38 |
-queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (xenial-proposed) [1.157.18] | 17:39 | |
sil2100 | bdmurray: looking | 17:39 |
sil2100 | bdmurray: hmm, I guess I could try that, should just be a matter of removing the symlink and refreshing the md5sum files | 17:45 |
sil2100 | I'll look into that later today or tomorrow in the morning though since I was about to move for some dinner now | 17:46 |
sil2100 | Wonder how that symlink got created in the first place | 17:46 |
* sil2100 suspends temporarily | 17:47 | |
infinity | bdmurray: Having the .iso duplicated at a .img was a Mark request many releases ago. It's been like that since xenial. | 18:02 |
infinity | bdmurray: Not saying I agree with it (nor that I'm sure he'd notice if I rolled it back and pretended it never happened), but yeah, hardly new. | 18:02 |
bdmurray | infinity: ah okay | 18:06 |
-queuebot:#ubuntu-release- Unapproved: rejected nplan [source] (xenial-proposed) [0.32~16.04.5] | 20:19 | |
-queuebot:#ubuntu-release- Unapproved: gnome-initial-setup (bionic-proposed/main) [3.28.0-2ubuntu6 => 3.28.0-2ubuntu7] (ubuntugnome) | 23:48 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!