-queuebot:#ubuntu-release- Unapproved: zim (eoan-proposed/universe) [0.69.1-1 => 0.72.0-1] (no packageset) (sync)01:32
-queuebot:#ubuntu-release- Unapproved: accepted zim [sync] (eoan-proposed) [0.72.0-1]01:33
-queuebot:#ubuntu-release- Unapproved: variety (eoan-proposed/universe) [0.7.2-1 => 0.7.2-2] (no packageset) (sync)02:15
-queuebot:#ubuntu-release- Unapproved: accepted variety [sync] (eoan-proposed) [0.7.2-2]02:16
-queuebot:#ubuntu-release- Unapproved: livecd-rootfs (eoan-proposed/main) [2.619 => 2.620] (desktop-core)05:19
-queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (eoan-proposed) [2.620]05:20
-queuebot:#ubuntu-release- Unapproved: ghdl (eoan-proposed/universe) [0.35+git20181129+dfsg-4 => 0.35+git20181129+dfsg-4ubuntu1] (no packageset)05:47
-queuebot:#ubuntu-release- Unapproved: accepted ghdl [source] (eoan-proposed) [0.35+git20181129+dfsg-4ubuntu1]05:47
-queuebot:#ubuntu-release- Unapproved: golang-gopkg-lxc-go-lxc.v2 (eoan-proposed/universe) [0.0~git20190625.f4822c6-0ubuntu1 => 0.0+git20190625.f4822c6-1ubuntu1] (edubuntu)06:00
-queuebot:#ubuntu-release- Unapproved: accepted golang-gopkg-lxc-go-lxc.v2 [source] (eoan-proposed) [0.0+git20190625.f4822c6-1ubuntu1]06:01
-queuebot:#ubuntu-release- Unapproved: nftables (eoan-proposed/universe) [0.9.2-1ubuntu1 => 0.9.2-2] (no packageset) (sync)06:04
-queuebot:#ubuntu-release- Unapproved: accepted nftables [sync] (eoan-proposed) [0.9.2-2]06:04
-queuebot:#ubuntu-release- Unapproved: libapache2-mod-perl2 (eoan-proposed/main) [2.0.10-3ubuntu1 => 2.0.11-1ubuntu1] (ubuntu-server)06:09
infinityLocutusOfBorg: The mod_perl2 delta to use locales in build-deps is obsolete, we've had locales-all in Ubuntu for years now.06:17
-queuebot:#ubuntu-release- Unapproved: rejected libapache2-mod-perl2 [source] (eoan-proposed) [2.0.11-1ubuntu1]06:21
LocutusOfBorgso, reuploaded thanks06:40
-queuebot:#ubuntu-release- Unapproved: libapache2-mod-perl2 (eoan-proposed/main) [2.0.10-3ubuntu1 => 2.0.11-1ubuntu1] (ubuntu-server)06:40
-queuebot:#ubuntu-release- Unapproved: accepted libapache2-mod-perl2 [source] (eoan-proposed) [2.0.11-1ubuntu1]06:43
LocutusOfBorgI think we can now upstream the change in Debian... opening a bug06:44
infinityLocutusOfBorg: Sure.  If they take the change, don't bother syncing into eoan, since we'll be starting a perl transition in under a week in FF, may as well sync then.06:45
infinityFree rebuilds are a nice side-effect of syncs. :P06:45
LocutusOfBorgyep, this is the reason for me stopping syincing perl libraries...06:46
LocutusOfBorgI sync/merge only in case of CVE fixes now :)06:46
infinityreverse-depends -r unstable dwww06:47
infinityNot a lot of results there.06:47
infinityIt seems vaguely last century to have that dep at all.06:47
LocutusOfBorgyep :)06:48
jibelhi release team, happy release week06:48
jibelcould someone have a look at bug 1847898?06:48
ubot5bug 1847898 in ubiquity (Ubuntu) "System doesn't boot after installation - Legacy mode / 2 disks" [Critical,New] https://launchpad.net/bugs/184789806:48
infinityjibel: Not linked in the tracker?  Naughty.  That's where I was looking this morning.06:49
infinity(But yeah, I should check rls-ee* when I get into the office)06:49
jibelyeah, my fault been lazy during the w-e06:49
jibeldoing it now06:49
infinityjibel: I blame the last person to touch disk/fs-related stuff in ubiquity.06:53
infinityjibel: *stare*06:53
infinityBut actually, I have no idea.  Will spend more brainpower on it later.06:53
infinityjibel: If you can cook up a qemu reproducer, that might be nice, since I don't have a pile of laptops I can wipe out to try it on, and you're not coming in with that one to help. :P06:54
jibelinfinity, sure, i'll prepare something06:54
infinityjibel: Of course, if it can't be reproduced in qemu, it might be specific to that BIOS, and then I'm not sure where we are.06:55
jibelinfinity, I'll have a patch to ubiquity today to fix (or attempt to) bug 184774806:55
ubot5bug 1847748 in ubiquity (Ubuntu) "installer crashed - Cannot resolve path /dev/sdN - Failed to mount /target" [Critical,Triaged] https://launchpad.net/bugs/184774806:55
jibelit's an issue with the refresh of the partition table06:55
jibelinfinity, I cannot reproduce in a VM with 2 disks07:05
cpaelzerinfinity: dod you think this bug should be tagged for the release and/or tracker https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1847806 ?07:09
ubot5Launchpad bug 1847806 in debian-installer (Ubuntu) "eoan: ppc64el install on pseries-eoan VM fails to install" [Undecided,Incomplete]07:09
cpaelzerIt is (to me) not yet clear if it is eoan or the newer TCG that is broken - the former being more "eoan relese crit bug" the latter probably just being "pfff, tcg isn't important"07:10
cpaelzerso I'm unsure about marking that for the release Team or not07:10
infinitycpaelzer: Can it be reproduced with a machine set to P8?  And why on earth would we change our default VM to P9 when most of the hardware we have to run on is P8?07:16
infinity(And our ISA baseline is P8, etc)07:16
cpaelzerinfinity: I have the p8 run ongoing atm (slow as TCG is)07:16
cpaelzerprobably 20 minutes for that result07:16
cpaelzerinfinity: and we switch to P9 as that is what upstream did07:17
infinityUpstream isn't always right. :P07:17
cpaelzerthis is only happening (it seems) when you install ppc64le in qemu TCG (instruction emulation)07:17
infinityUnless they're trapping and perfectly emulating instructions, having our base VM type use a CPU that we can't run on the hardware we target is daft.07:17
infinityOh, if this doesn't happen at all under KVM, my carefactor is super low.07:18
cpaelzerwell p9 is supposed (tm) to be p8 compatible right :-)07:18
cpaelzerinfinity: we seem to agree on that, see my "pfff, tcg isn't important" above07:18
infinitycpaelzer: Sure, P9s are P8 compatible.   But if you boot on something that claims to be a P9, glibc will jump into P9 code.  If it fails to actually be a useful P9, it'll sigill.07:19
cpaelzeryep, that is exactly my assumption atm07:19
cpaelzerlike qemu enabling P9 by default as some tests worked and later a newer glibc started to run more exotic P9 code and -> sigill07:19
infinitycpaelzer: Anyhow, I'd still argue that having a default VM type of P9 in any mode, is probably premature, and moreso if it's also obviously broken.  So patches welcome to fix that.07:20
infinitycpaelzer: But probably also not RC if it doesn't affect real hardware, LPARs, or KVM, which is about 107% of real installations.07:20
cpaelzerI'd not object P9 being the default (in fact I prefer that it is the default), but I'd want it to work :-)07:21
cpaelzerThe bug might end up being pushed to IBM to fix TCG07:21
infinityIt's a weird default when KVM people are more likely to be P8 still.07:21
infinityThat might not be true in a year, but I suspect it is now.07:21
infinitySo emulated people should likely see the same baseline without asking for another.07:22
* infinity shrugs.07:22
cpaelzerTBH most people I talked and myself recently are clearly P9>P8 in terms of usage07:22
cpaelzeranyway, thanks for guidance on the "tag crit for Eoan or not"07:22
cpaelzerthat was the real question for now and we seem to agree that we don't have to do so07:22
infinityAgain, don't really care deeply about software emulation (from a release standpoint), though, so fix as you see appropriate for SRU (or opportunistic upload for final release if you're quick and it's simple)07:23
infinitycpaelzer: I'll concede that P9 hardware might have passed P8 hardware in sales.  And not everyone runs clouds like I do.  But in my world, if I have a mix of P8 and P9 in a cloud, I clamp all the VMs to the same CPU type to avoid going slowly insane.07:24
infinitycpaelzer: Though, if PPC qemu is as bad at that as x86 is, sometimes -cpu=host is the only way to avoid going insane from confusing bugs in the capability masking. P07:25
xnoxjibel: for the OEM from recovery install... Is there example gold image I can play way?07:49
xnoxOr like steps to recreate that config?07:49
jibelxnox, that's a question for mario07:50
jibelI don't have such image07:50
jibelI'll ask Taipei07:50
-queuebot:#ubuntu-release- Unapproved: freeipa (eoan-proposed/universe) [4.8.1-2 => 4.8.1-2ubuntu1] (no packageset)07:55
-queuebot:#ubuntu-release- Unapproved: accepted freeipa [source] (eoan-proposed) [4.8.1-2ubuntu1]07:56
Laneyinfinity: glib2.0> Just remove it for now08:06
Laneyif I can fix it then I can re-upload, no point in blocking other things on it though08:06
infinityLaney: Sure, we can remove.  Will need rebuilds of vte and gdk-pixbuf08:07
LaneyI love reubuilds08:07
LaneyI love spelling too08:08
xnoxjibel:  commented https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/184794408:14
ubot5Launchpad bug 1847944 in partman-auto (Ubuntu Eoan) "partman-auto 134ubuntu11 prevents installation from recovery partition" [Critical,Triaged]08:14
xnoxjibel:  i do wonder how recovery partition is created, i.e. is it still iso mount, or if it's ext408:15
xnoxjibel:  etc.08:15
jibelxnox, I'm trying to get you an iso, you'll have all the information you need.08:16
xnoxjibel:  tah08:18
xnoxinfinity:  https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1847944/coe fixing this?mments/1 how should i b08:19
ubot5Launchpad bug 1847944 in partman-auto (Ubuntu Eoan) "partman-auto 134ubuntu11 prevents installation from recovery partition" [Critical,Triaged]08:19
* xnox ponders life08:19
didrocksinfinity: so, we have an issue for ZFS with latest iso (ubiquity with manual mark-install for zfsutils-linux & zfs-initramfs). Both are listed in the livecd-rootfs remove file, so pure ext4 installation is good. However, zfs-initramfs is still purged on the final system08:19
didrocksinfinity: so, installation isn't bootable…08:19
-queuebot:#ubuntu-release- Unapproved: pygalmesh (eoan-proposed/universe) [0.4.0-1 => 0.4.0-1ubuntu1] (no packageset)08:20
infinitydidrocks: That shouldn't be the case...08:20
infinitydidrocks: Bug#?08:20
didrocksyeah, we double check with jibel and there is no typo in apt-install08:20
didrockslet me file one, just found it08:20
infinitydidrocks: Definitely 20191012?08:20
-queuebot:#ubuntu-release- Unapproved: accepted pygalmesh [source] (eoan-proposed) [0.4.0-1ubuntu1]08:20
didrocksinfinity: yes, and good ubiquity version manually checked08:20
didrocksI would expect anyway having both zfsutils-linux & zfs-initramfs or none of them08:21
didrocksnot just one08:21
xnoxdidrocks:  that sounds like the lvm / cryptsetup bug where we added mark everything as autoremoval and purge that as part of the install08:25
didrocksinfinity: let me redo a third install and get logs (I pressed enter on my terminal on the second one when ubiquity got the focus for "reboot now" :/)08:25
xnoxand like even if tools are "installed" one has to mark them as manually installed08:25
didrocksxnox: but infinity told that was fixed by Michael? (it's not done in a generic way?)08:25
didrocksbut yeah, smells like it08:25
xnoxyes infinity is saying so now to me08:26
infinityIt is very much done in a generic way.08:26
didrocksbug #184797008:26
ubot5bug 1847970 in ubiquity (Ubuntu) "20191012 does remove zfs-initramfs on targetted system" [Undecided,New] https://launchpad.net/bugs/184797008:26
didrocksI'll redo an install and attach logs08:26
didrockssee if I can find anything08:26
bdmurrayjibel: Have you seen bug 1847785?08:34
ubot5bug 1847785 in ubiquity (Ubuntu) "eoan: zfs install option - don't install on systems less than 4GB of memory" [High,Confirmed] https://launchpad.net/bugs/184778508:34
didrocksxnox: infinity: logs attached to bug #1847970, I can't find anything relevant in syslog or debug logs. Seems to be reliably reproducible on vm08:37
ubot5bug 1847970 in ubiquity (Ubuntu) "20191012 does remove zfs-initramfs on targetted system" [Undecided,New] https://launchpad.net/bugs/184797008:37
jibelbdmurray, yes08:41
jibelbdmurray, you're up early08:42
bdmurrayjibel: I'm in London. Why aren't you?08:42
xnoxjibel:  so i think we might have a fix, but will need the oem image to verify changes.08:44
jibelbdmurray, I am not08:45
=== andrewc is now known as Guest6870
jibelinfinity, bug 184789808:54
ubot5bug 1847898 in ubiquity (Ubuntu) "System doesn't boot after installation - Legacy mode / 2 disks" [Critical,New] https://launchpad.net/bugs/184789808:54
jibelinfinity, confirmed on another DELL machine08:54
sil2100rbalint: hey, I see that systemd ubuntu3 still has autopkgtest failures, looked at the knot-resolver one and it looked a bit weird09:08
sil2100rbalint: I don't know much about these packages but this failure looks like a regression? Like, it was previously treating the failed server query as a warning and now it's an error - can that be somehow related to systemd?09:10
infinitydidrocks: Just did an install here, and both get marked manual...09:11
infinityOh, wait, but that's not specifically what you claims.  It's not about auto/manual, but about the removal step removing one of them, right?09:12
jibelinfinity, yes, it removes zfs-initramfs09:12
didrocks /target doesn't have zfs-initramfs before rebooting09:14
didrocksand you can imagine that it doesn't go well then :p09:14
infinityHow do I mount this beast without rebooting?09:14
didrocksinfinity: zpool import -R /target /dev/vda6 (or whatever)09:16
didrockszpool import -R /target /dev/vda2 (bpool is on the second partition IIRC)09:16
didrocksyou mount grub as a traditional ext4 partition on the chroot if you want it as well09:16
infinitydidrocks: That didn't seem to work. :P09:20
didrocksinfinity: yeah, easier, it does still have the pool name in its cache, so:09:20
didrockszpool import -R /target rpool09:20
didrockszpool import -R /target bpool09:20
infinitydidrocks: That worked better.09:21
didrocksinfinity: and grub is on vda1 (as ext4)09:21
infinitydidrocks: So... zfs-initramfs is in /target too here.09:21
didrockshum, Wimpress confirmed on Mate…09:22
* infinity reboots after confirming that.09:22
sil2100rbalint: anyway, just in case I now re-ran amd64 against release only, maybe something else broke it09:22
didrocksno, it's not in my chroot here :/09:23
didrocksI kept the default by disabled installing ugprades09:23
didrocksthe iso is 2019101209:23
didrocks(legacy mode)09:24
didrocksinfinity: oh, the packaged is installed for dpkg, but the files aren't there09:26
Trevinhobdmurray: hey, do you have any clue why some of the top crashes in https://errors.ubuntu.com/?release=Ubuntu%2019.10&package=gnome-shell&period=month have no symbols?09:26
didrockshave you only checked dpkg status?09:26
infinitydidrocks: Hah.  Yes.  And that's speeeecial.  But I also know where that code lives, ish, so maybe I can hunt down WTF went wrong.09:26
didrocksinfinity: phew, better that we see the same thing :)09:26
didrockskeep me posted if you need any tests09:27
infinitydidrocks: I mean, I suspect we're seeing the same behaviour, because dpkg said it was there, but it doesn't reboot. :P09:29
-queuebot:#ubuntu-release- Unapproved: uim (eoan-proposed/universe) [1:1.8.8-4ubuntu2 => 1:1.8.8-5ubuntu1] (no packageset)09:29
didrocksgot it :)09:29
infinitydidrocks: Anyhow, the magic code to delete files without dpkg being involved might be doing something silly here as far as it interacts with the bit that mwhudson fixed.09:30
-queuebot:#ubuntu-release- Unapproved: accepted uim [source] (eoan-proposed) [1:1.8.8-5ubuntu1]09:30
didrocksyeah, sounds like it. I hope we can fix that without harcoding any file names…09:31
infinityDon't see why we wouldn't be able to.09:32
infinityI just need to remember where that mess is.  I had to learn it intimately a couple of cycles ago.09:32
didrocksso, it's not on the "filtering files to copy" part of ubiquity, but on the removal later on? (I thought the removal only had packages removal at this stage, but didn't dive too deep into it… fortunately it seems)09:33
-queuebot:#ubuntu-release- Unapproved: sdaps (eoan-proposed/universe) [1.9.7-0.1 => 1.9.7-0.2] (no packageset) (sync)09:34
-queuebot:#ubuntu-release- Unapproved: accepted sdaps [sync] (eoan-proposed) [1.9.7-0.2]09:35
-queuebot:#ubuntu-release- New binary: uim [amd64] (eoan-proposed/universe) [1:1.8.8-5ubuntu1] (no packageset)09:40
Laneyglib2.0 is passing when I'm running it manually (in scalingstack) now ¬_¬09:41
* Laney tries in a silo09:41
LocutusOfBorgplease accept that transitional package ^^ it fixes debian bug: #93958809:42
ubot5Debian bug 939588 in uim "uim package lacks 2 files" [Normal,Fixed] http://bugs.debian.org/93958809:42
Laneyinfinity: you mean scripts/install.py the blacklist stuff probably?09:45
* Laney remembers fiddling with this recently too09:45
rbalintsil2100, yes, systemd faced a few strange new regressions, looking09:48
Laneyit's excluded by that "Not copying" step09:52
-queuebot:#ubuntu-release- Unapproved: gnome-settings-daemon (eoan-proposed/main) [3.34.0-1ubuntu1 => 3.34.1-1ubuntu1] (ubuntu-desktop)09:59
=== andrewc is now known as Guest18566
infinityseb128: Why do you hate Laney and keep deleting his changelogs? :P10:09
infinityseb128: (re: g-s-d in unapproved)10:09
-queuebot:#ubuntu-release- Unapproved: gdk-pixbuf (eoan-proposed/main) [2.40.0+dfsg-1 => 2.40.0+dfsg-1build1] (core)10:09
-queuebot:#ubuntu-release- Unapproved: vte2.91 (eoan-proposed/main) [0.58.2-1ubuntu1 => 0.58.2-1ubuntu2] (ubuntu-desktop)10:09
seb128infinity, nothing personal, I just don't keep old changelog entries when merging :)10:10
Laneyseb128 is a rebaser rather than a merger10:10
seb128that's a way to state it ;)10:10
infinityseb128: I believe that's technically against our policy.  If only I could find said policy.10:10
infinity(it's also just confusing to read)10:11
-queuebot:#ubuntu-release- Unapproved: accepted gdk-pixbuf [source] (eoan-proposed) [2.40.0+dfsg-1build1]10:11
seb128next time I do a sync and do another upload on top saying "ups, restore change dropped by mistake"10:11
-queuebot:#ubuntu-release- Unapproved: accepted vte2.91 [source] (eoan-proposed) [0.58.2-1ubuntu2]10:11
* infinity smirks.10:12
-queuebot:#ubuntu-release- Unapproved: accepted gnome-settings-daemon [source] (eoan-proposed) [3.34.1-1ubuntu1]10:12
seb128thx for reviewing/approving!10:12
LaneyI think zsys-setup is marking the packages too late10:14
Laneythey're not in the list of packages to keep when ubiquity queries it10:14
seb128can someone mark ubuntu-drivers-common autopkgtests are invalid on i386? another one that tries to install kernel headers and fails now10:21
LaneyYeah that fixes it10:28
Laneyseb128: done10:32
infinityLaney: Oh nice, just reordering it to not be in the 'finalize' step fixes it, or..?10:32
Laneyinfinity: Yeah, just whack it at the end of the init bit10:32
LaneyI'll do a MP10:33
seb128Laney, thx10:33
infinityLaney: +1 from me if that's tested.10:33
infinityLaney: And thanks.10:33
infinityLaney: Are you coming in this afternoon or tomorrow or...?10:33
infinityubuntu-drivers-common should probably just enable multiarch to make the tests still work.10:34
infinityBut I guess badtesting works for now.10:34
infinityWhile we decide if it's a package that will get dropped anyway.10:34
infinityLaney: I don't think I need a formal MP for that, but if that workflow works for you, go for it.10:35
Laneyinfinity: Tomorrow10:36
LaneyOK, I'll just push it then10:36
LaneyNot uploading though, since it seems like there's going to be other fixes coming10:36
rbalintsil2100, i'm checking what broke with systemd, and i see many :amd64 packages in the i386 autopkgtest vm: https://pastebin.ubuntu.com/p/RNscBQhw8r/10:37
rbalintinfinity, ^10:38
infinityLaney: Lemme grab your commit and apply it to a live session here and make sure it DTRT for me too.10:38
infinityrbalint: Yes, and?10:39
rbalintas i see in the livecd-rootfs source we enable amd64 but don't pin amd64 packages down to prefer i38610:39
infinityrbalint: Pinning to prefer an arch isn't necessary.10:39
LaneyJust cut 'n' paste those two lines to above the "touch"10:39
infinityrbalint: Those are almost certainly all there because of linux-*10:40
rbalintinfinity, the problem i see is libsystemd0:amd64 in the vm, thus systemd does not upgrade10:40
infinityrbalint: "Thus systemd doesn't upgrade".  Why?10:40
infinityrbalint: Which test are you looking at?10:41
rbalintinfinity, systemd:i38610:41
infinityrbalint: Okay, so either an autopkgtest pinning bug or an apt bug (probably not an apt bug).10:42
rbalintinfinity, ok, looking a bit more10:43
infinityrbalint: It's being held back because they need to upgrade in lockstep, but there's no reason they shouldn't.10:43
rbalintinfinity, they are held back because also removing libdbus-glib-1-2:amd64 imo10:44
rbalintinfinity, and indeed, pinning is involved when pulling systemd from -proposed10:44
xnoxinfinity:  given a partition ie. sda1 is there a reliable way to find the parent device? i.e. sda ?10:45
infinityrbalint: I don't understand what you mean by that sentence. :P10:45
xnoxinfinity:  including things like nvmen0p1 -> nvmen0 stuff10:45
infinityxnox: Strip p?[0-9]* off the end?10:45
xnoxbut nothing in like /proc/* partition map?10:45
ograxnox, udisks2 has some knobs for that but that indeed means you need to have it available (i.e. not on server afaik)10:48
xnoxinfinity:  something like $ basename $(dirname $(find /sys/devices -name nvme0n1p5)) ?10:49
rbalintinfinity, let me check how it works in lxc then i come back with different sentences :o)10:49
LocutusOfBorgmissing build on arm64: diamond-aligner (from 0.9.22+dfsg-2)10:52
LocutusOfBorgthat package moved from arch:any to arch:all, and has not been cleaned up for 73 days... is something wrong on report tools?10:53
ginggsLocutusOfBorg: it's not arch:all, it's restricted to amd64 only, LP: #184635210:56
ubot5Launchpad bug 1846352 in diamond-aligner (Ubuntu) "Please remove diamond-aligner everywhere except amd64" [Undecided,New] https://launchpad.net/bugs/184635210:56
LocutusOfBorgoops thanks10:58
infinityxnox: $ for i in /sys/block/*/sda2; do [ -d "$i" ] && echo $(dirname $i); done10:58
-queuebot:#ubuntu-release- Unapproved: cctools (eoan-proposed/universe) [7.0.9-2 => 7.0.9-3] (no packageset) (sync)11:00
-queuebot:#ubuntu-release- Unapproved: ddd (eoan-proposed/universe) [1:3.3.12-5.1build4 => 1:3.3.12-5.2] (no packageset) (sync)11:01
-queuebot:#ubuntu-release- Unapproved: accepted cctools [sync] (eoan-proposed) [7.0.9-3]11:01
-queuebot:#ubuntu-release- Unapproved: accepted ddd [sync] (eoan-proposed) [1:3.3.12-5.2]11:01
-queuebot:#ubuntu-release- Unapproved: appstream (eoan-proposed/main) [0.12.8-1 => 0.12.9-1] (core) (sync)11:07
-queuebot:#ubuntu-release- Unapproved: highwayhash (eoan-proposed/universe) [0~git20190222.276dd7b-1 => 0~git20191002.0aaf66b-1] (no packageset) (sync)11:07
-queuebot:#ubuntu-release- Unapproved: accepted highwayhash [sync] (eoan-proposed) [0~git20191002.0aaf66b-1]11:07
-queuebot:#ubuntu-release- Unapproved: kylin-video (eoan-proposed/universe) [2.0.0-1 => 2.0.1-1] (ubuntukylin) (sync)11:08
-queuebot:#ubuntu-release- Unapproved: mlpack (eoan-proposed/universe) [3.1.1-1 => 3.2.1-1] (no packageset) (sync)11:08
-queuebot:#ubuntu-release- Unapproved: accepted mlpack [sync] (eoan-proposed) [3.2.1-1]11:08
-queuebot:#ubuntu-release- Unapproved: node-babel-plugin-transform-define (eoan-proposed/universe) [1.3.0-2 => 1.3.0-3] (no packageset) (sync)11:09
-queuebot:#ubuntu-release- Unapproved: node-graphlibrary (eoan-proposed/universe) [2.2.0+dfsg-1 => 2.2.0+dfsg-2] (no packageset) (sync)11:09
-queuebot:#ubuntu-release- Unapproved: accepted node-babel-plugin-transform-define [sync] (eoan-proposed) [1.3.0-3]11:09
-queuebot:#ubuntu-release- Unapproved: accepted node-graphlibrary [sync] (eoan-proposed) [2.2.0+dfsg-2]11:09
-queuebot:#ubuntu-release- Unapproved: node-grunt-legacy-log-utils (eoan-proposed/universe) [1.0.0-1 => 1.0.0-2] (no packageset) (sync)11:10
-queuebot:#ubuntu-release- Unapproved: accepted node-grunt-legacy-log-utils [sync] (eoan-proposed) [1.0.0-2]11:10
-queuebot:#ubuntu-release- Unapproved: node-grunt-legacy-util (eoan-proposed/universe) [1.0.0-1 => 1.0.0-2] (no packageset) (sync)11:11
-queuebot:#ubuntu-release- Unapproved: node-inquirer (eoan-proposed/universe) [3.3.0-2 => 3.3.0-3] (no packageset) (sync)11:11
-queuebot:#ubuntu-release- Unapproved: node-hash-sum (eoan-proposed/universe) [1.0.2-1 => 1.0.2-2] (no packageset) (sync)11:11
-queuebot:#ubuntu-release- Unapproved: node-object-key (eoan-proposed/universe) [0.2.0-2 => 0.2.0-3] (no packageset) (sync)11:11
-queuebot:#ubuntu-release- Unapproved: accepted node-grunt-legacy-util [sync] (eoan-proposed) [1.0.0-2]11:11
-queuebot:#ubuntu-release- Unapproved: accepted node-inquirer [sync] (eoan-proposed) [3.3.0-3]11:11
-queuebot:#ubuntu-release- Unapproved: node-source-map (eoan-proposed/universe) [0.7.0++dfsg2+really.0.6.1-3 => 0.7.0++dfsg2+really.0.6.1-4] (kubuntu) (sync)11:11
-queuebot:#ubuntu-release- Unapproved: accepted node-hash-sum [sync] (eoan-proposed) [1.0.2-2]11:11
-queuebot:#ubuntu-release- Unapproved: node-stats-webpack-plugin (eoan-proposed/universe) [0.6.1-1 => 0.7.0-1] (no packageset) (sync)11:11
-queuebot:#ubuntu-release- Unapproved: accepted node-object-key [sync] (eoan-proposed) [0.2.0-3]11:11
-queuebot:#ubuntu-release- Unapproved: node-terser (eoan-proposed/universe) [4.1.2-3 => 4.1.2-4] (no packageset) (sync)11:12
-queuebot:#ubuntu-release- Unapproved: node-webpack-merge (eoan-proposed/universe) [2.2.0-2 => 2.2.0-3] (no packageset) (sync)11:12
-queuebot:#ubuntu-release- Unapproved: accepted node-stats-webpack-plugin [sync] (eoan-proposed) [0.7.0-1]11:12
-queuebot:#ubuntu-release- Unapproved: accepted node-webpack-merge [sync] (eoan-proposed) [2.2.0-3]11:12
-queuebot:#ubuntu-release- Unapproved: accepted node-terser [sync] (eoan-proposed) [4.1.2-4]11:12
Laneysomeone turned auto-sync back on eh11:13
-queuebot:#ubuntu-release- Unapproved: patroni (eoan-proposed/universe) [1.6.0-1 => 1.6.0-4] (no packageset) (sync)11:13
-queuebot:#ubuntu-release- Unapproved: accepted patroni [sync] (eoan-proposed) [1.6.0-4]11:13
-queuebot:#ubuntu-release- Unapproved: python-dugong (eoan-proposed/universe) [3.7.4+dfsg-1 => 3.7.4+dfsg-2] (no packageset) (sync)11:14
infinityLaney: I believe LocutusOfBorg thinks he's autosync.11:14
-queuebot:#ubuntu-release- Unapproved: accepted python-dugong [sync] (eoan-proposed) [3.7.4+dfsg-2]11:14
LocutusOfBorgLaney, I'm syncing all the packages that are stuck in proposed because of build failures or test failures11:14
LocutusOfBorge.g. nodejs packages were stuck since long time, and now they have been fixed in debian11:15
-queuebot:#ubuntu-release- Unapproved: python-parameterized (eoan-proposed/universe) [0.6.1-2 => 0.7.0-1] (no packageset) (sync)11:15
LocutusOfBorgand some python packages have got testsuite fixes11:15
LocutusOfBorgis that a problem? I'm not syncing new features, and looking only to packages that are not migrating11:15
-queuebot:#ubuntu-release- Unapproved: accepted python-parameterized [sync] (eoan-proposed) [0.7.0-1]11:15
LocutusOfBorgits a *complete* manual thing...11:16
LocutusOfBorgsome of them still requires fixes, but they should mostly all migrate and finish some transitions, e.g. sdpa, node-loadsh autopkgtest failures, pytest migration11:19
LocutusOfBorgand something more11:19
LaneyNah, if you're actually verifying that things are getting fixed then it's cool. I was just joking.11:20
LaneySoooooooooooooooo I just ran glib2.0/i386 out of a bileto ppa and it worked.11:21
infinityLaney: Because of course it did...11:21
infinityLaney: We ran it a whole mess of times on the primary archive, I swear. :/11:22
Laneywell I was suspicious because it worked locally here too11:22
Laneyand on Friday it was failing for me here and on scalingstack11:22
infinityLaney: Is that a new build in the PPA, or a binary copy from primary?11:22
Laneythe latter11:23
infinityLaney: Well, now that the things it was blocking have built, we can just binary copy it back in and try harder...11:23
LaneyI think...11:23
Laneythat if we copy it back britney should find the previous results and not re-run the world11:24
infinityI believe that's true.11:24
infinityConfidence level of some on a scale of one to many.11:24
LaneyIt could be a pinning thing, as the primary archive runs will be running with --apt-pocket=proposed=src:glib2.011:26
LocutusOfBorginfinity, Laney thanks for understanding and confirming, to do that I do: grep all the packages that have " to " in the update excuses page and add packages that have "Regression", sum them and list | sort |uniq11:26
* Laney eyes the logs closer11:26
LocutusOfBorgand then compare with auto-sync log11:26
LocutusOfBorgfor all of them that are in both lists I find the reason for missing migration, and if the fix is in a new release I 99% discard the sync and look at the diff, or if it is rust I discard and so on11:27
LocutusOfBorgfor the ones that are actually fixing stuff without dropping python-foo and so on I sync11:27
LocutusOfBorgthe worst case is something that didn't migrate that is still not migrating11:28
LocutusOfBorgstuff like highwayhash will require some AA power to kick out arm64 I think, but at least now ppc64el is building fine11:30
LocutusOfBorgappstream if accepted can probably end the ldc transition nightmare11:32
bdmurrayxnox: Is bug 1845543 already fixed?11:40
ubot5bug 1845543 in subiquity "Failed attempts to umount cdrom" [Undecided,New] https://launchpad.net/bugs/184554311:40
-queuebot:#ubuntu-release- Unapproved: glib2.0 (eoan-proposed/main) [2.62.0-1 => 2.62.1-1] (core) (sync)11:46
-queuebot:#ubuntu-release- Unapproved: accepted appstream [sync] (eoan-proposed) [0.12.9-1]11:48
infinityLaney: +1 on the ubiquity change, hand-hacked install here went well.11:50
infinityLaney: What other changes were we waiting on?  Looks like jibel's landed.11:50
-queuebot:#ubuntu-release- Unapproved: pnetcdf (eoan-proposed/universe) [1.12.0-1 => 1.12.0-1ubuntu1] (no packageset)11:53
-queuebot:#ubuntu-release- Unapproved: accepted pnetcdf [source] (eoan-proposed) [1.12.0-1ubuntu1]11:54
jibelinfinity, nothing from me11:55
jibelI'm testing Laney's fix11:55
jibelit hsould be done soon11:55
-queuebot:#ubuntu-release- Unapproved: node-terser (eoan-proposed/universe) [4.1.2-4 => 4.1.2-4ubuntu1] (no packageset)11:56
bdmurrayjibel: The same one infinity already tested?11:57
-queuebot:#ubuntu-release- Unapproved: accepted node-terser [source] (eoan-proposed) [4.1.2-4ubuntu1]11:57
jibelbdmurray, yes11:58
jibeland it's a pass, so double confirmed11:58
bdmurrayjibel: okay, great11:59
jibelwell, the system even boots after installation11:59
jibeluh, booted on the wrong disk though.12:02
* jibel tries again12:02
ginggsinfinity: thanks for diamond-aligner removal!  there were a couple of others i filed, would you be able to look?12:11
infinityginggs: Yeah, I have the bug list open, will get there this afternoon.12:13
ginggsinfinity: ta!12:13
-queuebot:#ubuntu-release- New binary: linux-signed-oem [amd64] (bionic-proposed/main) [4.15.0-1059.68] (kernel)12:29
LocutusOfBorginfinity, proteinortho/arm64 unsatisfiable Depends: diamond-aligner12:39
-queuebot:#ubuntu-release- Unapproved: rejected glib2.0 [sync] (eoan-proposed) [2.62.1-1]12:40
-queuebot:#ubuntu-release- New: accepted linux-signed-oem [amd64] (bionic-proposed) [4.15.0-1059.68]12:41
infinityLocutusOfBorg: Oh joy, I should have looked before removing.  Whee.12:41
-queuebot:#ubuntu-release- Unapproved: accepted kylin-video [sync] (eoan-proposed) [2.0.1-1]12:41
-queuebot:#ubuntu-release- Unapproved: accepted node-source-map [sync] (eoan-proposed) [0.7.0++dfsg2+really.0.6.1-4]12:41
infinityLocutusOfBorg: Although, I don't see that in reverse-depends.  Curious...12:42
infinityLocutusOfBorg: Or is that in proposed only?12:42
infinityLooks like proposed only.12:42
infinityAnd it build-deps on diamond-aligner, so a quick rebuild will clear that up.12:43
infinityWould have been fine if I'd done the removal 11 days ago. :P12:43
LocutusOfBorgdo you want me to upload a rebuild?12:43
-queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (disco-proposed) [1.178.5]12:43
infinityLocutusOfBorg: Yeah, go for it.12:44
-queuebot:#ubuntu-release- Unapproved: proteinortho (eoan-proposed/universe) [6.0.8+dfsg-1 => 6.0.8+dfsg-1build1] (no packageset)12:46
-queuebot:#ubuntu-release- Unapproved: accepted proteinortho [source] (eoan-proposed) [6.0.8+dfsg-1build1]12:46
-queuebot:#ubuntu-release- Unapproved: accepted linux-firmware [source] (bionic-proposed) [1.173.11]12:47
LocutusOfBorginfinity, do you think you can do something for highwayhash/arm64? Debian has the same failure but didn't remove the binary yet12:50
LocutusOfBorgno rdeps, no care, double rc buggy12:51
ginggsshould LP: #1828409 really be won't fix?12:54
ubot5Launchpad bug 1828409 in htslib (Ubuntu) "please remove htslib on i386" [Undecided,Won't fix] https://launchpad.net/bugs/182840912:54
xnoxinfinity:  can you please review patches on https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/184794412:57
ubot5Launchpad bug 1847944 in partman-auto (Ubuntu Eoan) "partman-auto 134ubuntu11 prevents installation from recovery partition" [Critical,Triaged]12:57
xnoxinfinity:  you may want to pull partman-base to see more context, as to which block of code is being fixed up.12:57
xnoxbdmurray:  1845543 not fixed. Was attempted, regressed, reverted. Postponed to ff-series12:58
* xnox will try to test that code more now, with and without some of the preseed keys; and cdroms vs usb sticks.12:59
infinityLocutusOfBorg: I was very tempted to just fix it, but then I looked at the code and how upstream determines architectures and arch features and decided I really didn't care any more.13:07
LocutusOfBorglol same for me, there is an upstream issue about that, nobody cared so far13:07
LocutusOfBorgso fixing downstream might be a pita to maintain for no reasons13:07
Laneyinfinity: weren't you working on some partman things there?13:13
infinityLaney: Oh, Dmitri is.  See above.13:14
sil2100xnox: ok, looked at the partman patches13:14
LaneyYeah, so that's what I thought we were waiting for :-)13:14
sil2100xnox: looking good, I might just recommend break'ing after we find a partition in /sys/block/*/$block, or is there a reason to continue looking?13:14
sil2100Not a biggy anyway13:15
Laneyand the two disks thing?13:15
infinityThe two disks thing, I might have been waiting on jibel to give me a qemu reproducer.13:16
infinityUnless that happened and I missed it.13:16
cpaelzerinfinity: there was no message here with qemu in it since we last talked this morning13:19
-queuebot:#ubuntu-release- Unapproved: partman-base (eoan-proposed/main) [206ubuntu5 => 206ubuntu6] (core, i386-excludes)13:21
infinitycpaelzer: Your IRC client is full of lies:13:21
infinity00:54 < infinity> jibel: If you can cook up a qemu reproducer, ...13:21
infinity00:54 < jibel> infinity, sure, i'll prepare something13:21
cpaelzernope, we talked after this13:22
cpaelzerand I said nothing since then13:22
-queuebot:#ubuntu-release- Unapproved: rejected partman-base [source] (eoan-proposed) [206ubuntu6]13:22
infinitycpaelzer: Oh, I see what you mean.13:22
infinityYeah, he didn't give me a reproducer on IRC or in the bug,.13:22
cpaelzerwhich does not mean that the messages aren't full of lies :-)13:22
-queuebot:#ubuntu-release- Unapproved: glib2.0 (eoan-proposed/main) [2.62.0-1 => 2.62.1-1] (core) (sync)13:39
LaneyI'm assuming that was rejected because I forgot --include-binaries, can't see any mail about it13:41
infinityLaney: Almost certainly.13:44
-queuebot:#ubuntu-release- Unapproved: accepted glib2.0 [sync] (eoan-proposed) [2.62.1-1]13:45
LocutusOfBorgdid the proteinortho removal fail?13:55
infinityLocutusOfBorg: No?14:05
infinityHow would a removal fail?14:05
infinityOh, if by "removal" you mean "NBS cleanup", I haven't done that yet.14:06
sforsheeinfinity: linux-raspi2 is blocked in -proposed, it's not critical we get it updated for the release but would be nice to have it in sync with the master kernel if we can14:12
infinitysforshee: I know, I was going to let it migrate before the next raspi images build.14:12
sforsheeinfinity: great, ta14:12
LocutusOfBorgoh... ok :)14:31
-queuebot:#ubuntu-release- Unapproved: u-boot (eoan-proposed/main) [2019.07+dfsg-1ubuntu2 => 2019.07+dfsg-1ubuntu3] (core)14:35
-queuebot:#ubuntu-release- New binary: linux-signed-gke-5.0 [amd64] (bionic-proposed/universe) [5.0.0-1023.23~18.04.2] (kernel)14:35
sil2100infinity: u-boot fix for the ram issue sponsored ^14:36
-queuebot:#ubuntu-release- Unapproved: base-files (eoan-proposed/main) [10.2ubuntu6 => 10.2ubuntu7] (core)14:38
-queuebot:#ubuntu-release- Unapproved: accepted base-files [source] (eoan-proposed) [10.2ubuntu7]14:43
-queuebot:#ubuntu-release- Unapproved: accepted u-boot [source] (eoan-proposed) [2019.07+dfsg-1ubuntu3]14:44
* xnox twiddle thumbs15:01
-queuebot:#ubuntu-release- Unapproved: partman-auto (eoan-proposed/main) [134ubuntu11 => 134ubuntu12] (core, i386-excludes) (sync)15:05
-queuebot:#ubuntu-release- Unapproved: ubiquity (eoan-proposed/main) [19.10.19 => 19.10.20] (core) (sync)15:05
-queuebot:#ubuntu-release- Unapproved: partman-base (eoan-proposed/main) [206ubuntu5 => 206ubuntu6] (core, i386-excludes) (sync)15:05
-queuebot:#ubuntu-release- Unapproved: rejected partman-auto [sync] (eoan-proposed) [134ubuntu12]15:10
-queuebot:#ubuntu-release- Unapproved: rejected ubiquity [sync] (eoan-proposed) [19.10.20]15:10
-queuebot:#ubuntu-release- Unapproved: rejected partman-base [sync] (eoan-proposed) [206ubuntu6]15:10
-queuebot:#ubuntu-release- Unapproved: partman-auto (eoan-proposed/main) [134ubuntu11 => 134ubuntu12] (core, i386-excludes)15:15
-queuebot:#ubuntu-release- Unapproved: partman-base (eoan-proposed/main) [206ubuntu5 => 206ubuntu6] (core, i386-excludes)15:15
-queuebot:#ubuntu-release- Unapproved: ubiquity (eoan-proposed/main) [19.10.19 => 19.10.20] (core)15:16
xnoxsil2100:  ^^^15:19
-queuebot:#ubuntu-release- Unapproved: accepted partman-auto [source] (eoan-proposed) [134ubuntu12]15:22
-queuebot:#ubuntu-release- Unapproved: accepted partman-base [source] (eoan-proposed) [206ubuntu6]15:22
-queuebot:#ubuntu-release- Unapproved: sfcgal (eoan-proposed/universe) [1.3.7-2 => 1.3.7-2ubuntu1] (no packageset)15:26
-queuebot:#ubuntu-release- Unapproved: accepted ubiquity [source] (eoan-proposed) [19.10.20]15:27
-queuebot:#ubuntu-release- Unapproved: accepted sfcgal [source] (eoan-proposed) [1.3.7-2ubuntu1]15:27
patriciadominhello, I'd like to test Eoan with subiquity for ppc64le, but here it just points to kvm/guest test: Eoan Final -> Product (Ubuntu Server Subiquity) ->  Ubuntu Server Subiquity ppc64el : http://iso.qa.ubuntu.com/qatracker/milestones/407/builds15:28
patriciadominif someone could please give me the right URL ^15:29
patriciadominthe same also happens to arm64 ^15:30
=== andrewc is now known as Guest10781
sil2100xnox: ^15:32
xnoxpatriciadomin:  you can submit your test case under kvm/qemu, despite doing bare-metal install15:34
xnoxpatriciadomin:  currently we don't have arch specific install test cases, i.e. "Virtual CD-ROM" would make sense for a subiquity ppc64le test case15:34
patriciadominxnox: yes, but I'd like to test it in a baremetal not a guest15:34
=== Guest10781 is now known as acloke
aclokeacloke, xnox - does the lack of test cases in the ISO tracker for arm64 and ppc64el infer that we should prioritise testing for the "daily" d-i based images?15:36
aclokexnox, the d-i based installation methods appear to have a full list of test cases in the QA tracker for those archs15:36
patriciadominxnox: my point is there's no subiquity test cases there for arm64 and ppc64le15:37
xnoxpatriciadomin:  sil2100 is adding some now15:37
xnoxacloke:  i'm not your boss =)15:38
patriciadominah good many thanks xnox and sil210015:38
xnoxso i can't tell you what should be prioritised15:38
xnoxwe are planning to release everything listed in the manifest, and everything must be tested =15:38
aclokexnox, :-) Let me rephrase... Is the population of the ISO QA tracker indicative of the likely default installation engine for those archs?15:39
aclokexnox, thanks. Understood15:39
xnoxit's paper trail of all releasable artefacts, as a complete consistent set. that's all.15:40
xnox(with serial numbers, links to builds, etc)15:46
-queuebot:#ubuntu-release- New: accepted uim [amd64] (eoan-proposed) [1:1.8.8-5ubuntu1]15:52
LocutusOfBorginfinity, I see you did the same hint as me https://code.launchpad.net/~costamagnagianfranco/britney/hints-ubuntu/+merge/37386715:53
LocutusOfBorgcan you please merge the firewalld change and the alt-ergo one pretty please?15:53
LocutusOfBorgsighm the hammer didn't work completely it seems... missing build on i386: proteinortho (from 5.16.b+dfsg-1)15:55
sil2100plars: ok, so u-boot for arm64 should be built and published, could you take an arm64 image and try to update u-boot-rpi to version 2019.07+dfsg-1ubuntu3?15:57
sil2100plars: and see if you see your full 2GB of ram15:58
sil2100plars: the armhf one is built but not published yet15:58
-queuebot:#ubuntu-release- Unapproved: casper (eoan-proposed/main) [1.424 => 1.425] (desktop-core, ubuntu-server)16:00
rbalintbdmurray, ^16:01
rbalintbuilt package is in ppa:rbalint/scratch16:01
xnoxrbalint:  also, checkout me and infinity doing transfersal from partition to block device from this morning =)16:07
xnoxrbalint:  i do like that you used it one more way to find things16:09
xnoxrbalint:  also just in time =)16:10
-queuebot:#ubuntu-release- Unapproved: accepted casper [source] (eoan-proposed) [1.425]16:11
rbalintxnox, :-) will check the rollback :-)16:15
sil2100plars: I would assume the armhf version of u-boot should also be available now for testing, if anything16:21
tjaaltonafter installing eoan with zfs, I have no /var/lib/dpkg..16:25
tjaaltondid a dist-upgrade before running ubiquity16:26
sil2100plars: so today I need to EOD at point 18 because of dinner arrangements - could you give a sign to infinity once you give those a spin and confirm they're not breaking anything?16:27
sil2100(so in ~20 minutes I will be gone)16:27
infinitytjaalton: Wat?16:29
plarssil2100: sorry, had to step out for a bit but I’ll try it as soon as I get back and let him know16:29
LocutusOfBorgany AA please? https://bugs.launchpad.net/ubuntu/+source/qr-tools/+bug/184806716:29
ubot5Launchpad bug 1848067 in qr-tools (Ubuntu) "qr-tools: kick out from eoan " [Undecided,New]16:29
tjaaltoninfinity: exactly16:30
tjaaltonmaybe I'll try to repro with the pending image16:31
sil2100plars: no worries!16:31
sil2100plars: thank you!16:31
infinityLocutusOfBorg: No urge to pull in the py3 port instead?16:31
infinitytjaalton: I appear to have a /var/lib/dpkg on my test install here.16:41
infinitytjaalton: I'm not really sure how yours would go missing.16:41
infinityThough it is a separate mountpoint for some reason.16:41
infinityThis ZFS stuff is weird.16:41
sil2100xnox: hm, could you take a look and see what you think about LP: #1848069 ?16:43
ubot5Launchpad bug 1848069 in subiquity "Subiquity device probing failing on Huawei TaiShan 2280 v2" [Undecided,New] https://launchpad.net/bugs/184806916:43
-queuebot:#ubuntu-release- New: accepted linux-signed-gke-5.0 [amd64] (bionic-proposed) [5.0.0-1023.23~18.04.2]16:50
=== paride5 is now known as paride
bittinUpdating :)16:54
tjaaltoninfinity: newer image seemed to have the rpool for that, but doesn't seem to boot up16:57
tjaaltonafter install16:57
tjaaltoncan't find the rootfs16:59
infinitytjaalton: The current image needs the ubiquity from proposed to work.16:59
tjaaltonyep, works now17:07
LocutusOfBorgzbar is 80 days old... and sdaps waits for it... i'm trying to make some stuff migrate17:09
LocutusOfBorgpost eoan will need a kick anyway17:09
ahasenacktjaalton: I saw the same with the 20191012 deskto iso + zfs install17:43
ahasenackno boot, initramfs prompt only17:43
plarsinfinity: I tried the new u-boot on both armhf and arm64 with my rpi4 and I see the full amount of memory now17:44
ahasenackand subiquity is also busted, "Unfortunately probing for devices to intsall to failed."17:44
LocutusOfBorgautopkgtest for proteinortho/6.0.8+dfsg-1build1: amd64: Pass, arm64: Regression ♻ , armhf: Regression ♻ , i386: Regression ♻ , ppc64el: Regression ♻ , s390x: Regression ♻17:46
LocutusOfBorghint please? nbs removed some hours ago17:46
bdmurrayplars: that's good news, thanks for testing it!17:46
infinityLocutusOfBorg: "will need a kick".  No, post-eoan, the py3 port will likely land in Debian.  It's already upstream.17:52
infinityLocutusOfBorg: It's fine if it just doesn't migrate.  We don't need to remove packages just cause you don't want to fix them. :P17:53
xnoxmwhudson:  https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1847771 wanna dig into probert and curtin as to why it's trying to declare multipath key, on things that are paths but not actually multipathed into a map at all?17:55
ubot5Launchpad bug 1847771 in curtin (Ubuntu Eoan) "pathless nvme drive crashes block discovery" [Critical,New]17:55
xnoxmwhudson:  quite a few people are hitting this with various configs.17:55
xnoxinfinity: rbalint: maybe Casper code should change to shell based glob and test, as is done in partman-base now. Because we unmount filesystem, then try to use realpath from it... Which doesn't bwork unless we poke it into fscache. Better to use shell globs & builtins. Or poke the needed binaries into fscache.18:13
-queuebot:#ubuntu-release- Unapproved: pulseaudio (bionic-proposed/main) [1:11.1-1ubuntu7.3 => 1:11.1-1ubuntu7.4] (desktop-core, ubuntu-server)18:16
rbalintxnox, the new code uses only the _partition_ after umount, so unless /sys is unmounted it should work - and it worked in my tests (20191010 iso, with casper upgraded)18:59
infinityWorld re-spinning for all of today's updates/fixes.  New images should start posting in 30-60 minutes.19:43
-queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Eoan Final] has been updated (20191014)19:49
-queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Eoan Final] has been updated (20191014)19:49
-queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Eoan Final] has been updated (20191014)19:49
-queuebot:#ubuntu-release- Builds: Ubuntu Base i386 [Eoan Final] has been updated (20191014)19:49
-queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Eoan Final] has been updated (20191014)19:49
-queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Eoan Final] has been updated (20191014)19:49
-queuebot:#ubuntu-release- Builds: Ubuntu Server amd64 [Eoan Final] has been updated (20191014)19:58
-queuebot:#ubuntu-release- Builds: Ubuntu Server arm64 [Eoan Final] has been updated (20191014)19:58
-queuebot:#ubuntu-release- Builds: Ubuntu Server ppc64el [Eoan Final] has been updated (20191014)19:58
-queuebot:#ubuntu-release- Builds: Ubuntu Server s390x [Eoan Final] has been updated (20191014)19:58
-queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Eoan Final] has been updated (20191014)20:01
-queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Eoan Final] has been updated (20191014)20:03
-queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Eoan Final] has been updated (20191014)20:04
-queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Eoan Final] has been updated (20191014)20:05
-queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Eoan Final] has been updated (20191014)20:09
-queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Eoan Final] has been updated (20191014)20:10
mwhudsonxnox: yea will look20:10
-queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Eoan Final] has been updated (20191014)20:11
-queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi3 [Eoan Final] has been updated (20191014)20:16
-queuebot:#ubuntu-release- Builds: Ubuntu Server arm64+raspi3 [Eoan Final] has been updated (20191014)20:17
-queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Eoan Final] has been updated (20191014)20:24
rbalintxnox, but will look at what partman-base does now20:26
=== jdstrand_ is now known as jdstrand
mwhudsonhttps://code.launchpad.net/~mwhudson/curtin/+git/curtin/+merge/374103 <- for the block probe failures20:47
-queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Eoan Final] has been updated (20191014)20:47
-queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Eoan Final] has been updated (20191014)20:48
-queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Eoan Final] has been updated (20191014)20:48
-queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Eoan Final] has been updated (20191014)20:48
=== guiverc2 is now known as guiverc
-queuebot:#ubuntu-release- Unapproved: systemd (disco-proposed/main) [240-6ubuntu5.7 => 240-6ubuntu5.8] (core)23:00

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!