/srv/irclogs.ubuntu.com/2020/03/06/#ubuntu-release.txt

=== s8321414_ is now known as s8321414
=== s8321414_ is now known as s8321414
=== popey7 is now known as popey
vorlonEickmeyer: you'll need to pick up the changes from ubuntustudio-default-settings 0.74ubuntu1 that was uploaded by doko06:44
LocutusOfBorgkanashiro, hello, thanks for the ppa upload, but I was meaning "from the next one" :) I don't care about binaries, because copying them from ppa is forbidden, I care about sources and diffs :D07:25
LocutusOfBorgand also, it might be even easier for you to upload it instead of opening a bug each time07:25
-queuebot:#ubuntu-release- Unapproved: accepted fwupd [amd64] (focal-proposed) [1.3.9-1]09:14
-queuebot:#ubuntu-release- Unapproved: accepted fwupd [armhf] (focal-proposed) [1.3.9-1]09:14
-queuebot:#ubuntu-release- Unapproved: accepted fwupd [arm64] (focal-proposed) [1.3.9-1]09:14
dokobryce: is it still planned to remove php7.3 in focal? in this case I'm suggestion to just ignore the failed autopkg tests triggered by php7.3, which are also run by php7.409:22
-queuebot:#ubuntu-release- Unapproved: livecd-rootfs (xenial-proposed/main) [2.408.57 => 2.408.58] (desktop-core)09:30
vorlondoko: fwiw I pinged bryce in another channel about this as well, and I've set the skiptest hint now, as there should be plenty of time for him to object today before the icu transition is actually going to go through09:37
-queuebot:#ubuntu-release- Unapproved: accepted ubuntu-image [source] (eoan-proposed) [1.9+19.10ubuntu1]10:15
-queuebot:#ubuntu-release- Unapproved: accepted livecd-rootfs [source] (xenial-proposed) [2.408.58]10:18
-queuebot:#ubuntu-release- Unapproved: accepted ubuntu-image [source] (bionic-proposed) [1.9+18.04ubuntu1]10:23
-queuebot:#ubuntu-release- Unapproved: accepted ubuntu-image [source] (xenial-proposed) [1.9+16.04ubuntu1]10:26
kanashirolocutus_, ack :)11:24
=== M_hc[m] is now known as _hc
ahasenackhi release team, bind9 and bind9-libs are stuck because of the kernel (https://launchpad.net/bugs/1865025), via debian-installer. Is this something we could migrate manually, since debian-installer isn't used in a live system, or is that worse?12:38
ubot5Ubuntu bug 1865025 in Kernel SRU Workflow regression-testing "focal/linux: 5.4.0-17.21 -proposed tracker" [Medium,In progress]12:38
vorlonahasenack: well it would break buildability of the classic server ISOs, and I expect it would break netboot images as well12:51
ahasenackok :(12:51
ahasenackI'm just anxious that these big bind9 changes haven't seen "real world" use yet12:52
=== cpaelzer__ is now known as cpaelzer
cpaelzerhiho, I know someone has done it in the past for openstack test cases but I forgot the buzzwords to search for. I'm looking for how to mark a test as huge.12:58
ahasenackI know, I know!12:58
cpaelzertel lme please12:58
cpaelzeras I have debugged a case in our proposed migration down to a OOM12:58
ahasenackI have to check my swap file, just a moment12:58
* cpaelzer is eagerly waiting for ahasenack to come back with his notes12:59
ahasenackhave to do some sleuthing, it all started with a hint branch12:59
cpaelzerok that seems to be the natural place12:59
ahasenackcpaelzer: https://code.launchpad.net/~ahasenack/britney/hint-mysql8-arm64/+merge/37958212:59
ahasenackcpaelzer: check steve's response, and mine13:00
ahasenackcpaelzer: oh, and https://code.launchpad.net/~ahasenack/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/379592 for a direct route13:00
cpaelzeryeah and I see nova in the list as I remembered :-)13:01
cpaelzerthanks a lot ahasenack13:01
cpaelzerthat is for python-cffi which is blocking python3-defaults so I guess people will be happy13:02
cpaelzerthere will soon be an MP and more details in my proposed migration status mail ...13:03
cpaelzerahasenack: look at the dir I already found this repo ~/work/britney/autopkgtest-cloud :-)13:03
cpaelzermakes sense13:03
ahasenackwe organize our directories per the solution, not the problem :)13:04
ahasenackoh, this autopkgtest-cloud should have been in the "what I learned" column of our retrospective13:04
cpaelzerahasenack: yeah13:04
cpaelzerespecially since over the last two years I now learned it thrice I think13:04
cpaelzerahasenack: here is it https://code.launchpad.net/~paelzer/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/38036213:18
cpaelzeractually vorlon if you are still around you might want to look at this MP ^^13:18
cpaelzerI saw you re-ran python-cffi tests as well13:18
vorloncpaelzer: so the tests are running out of memory?13:33
vorloncpaelzer: merged and deployed; feel free to retry the tests now13:54
=== msalvatore_ is now known as msalvatore
MirvI have a vague memory that getting MIR approved source package's binary package to main did not involve formal process and I could ask here?14:00
MirvCould I get libenchant-2-voikko into main? I've added it to language-selector at https://launchpad.net/ubuntu/+source/language-selector/0.201 but it's not getting installed by default presumably due to it being still in universe.14:01
Mirv(yes, found at 1859601 that binaries don't generally have to go through MIR process)14:03
Mirvdidrocks: ^ maybe you can help with that if you happen to be around, or then I'll just wait and ping someone next week14:04
vorlonMirv: it isn't showing up as a mismatch on https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed14:05
Mirvvorlon: right, that's another topic - if it's only language selector that is pulling it in, it's not showing as package dependency problem14:06
vorlonMirv: is there a seed that things referenced by language-selector are normally added to?14:07
vorlonlibenchant-voikko is in the supported seed14:08
vorlonso I guess it needs adding there?14:08
Mirvright, seeds, those I had forgotten about. correct, then. I see if I can do a MR.14:10
vorlonand should libenchant-voikko be dropped, in favor of libenchant-2-voikko?  is this a swap?14:11
Mirvthe transition isn't 100% complete, enchant 1 is still in default installation, so maybe not for 20.04 yet14:16
vorlonMirv: so in what cases is language-selector installing -2- instead of libenchant-voikko?14:18
MirvI'm trying to update myself on this topic.. it seems my installation was outdated. It seems default installation no longer installs enchant 1, but eg abiword does want it. Enchant 1 is in main, but maybe nothing in main depends on it anymore.. but this goes a bit out of voikko topic.14:22
Mirvvorlon: It's currently trying to install plugins for both enchant 2 and enchant 1. I think it'd be alright if enchant 1 would not be automatically installed during installation, but suggested after installation by Language Support when universe repo is enabled.14:23
Mirv(in the case Enchant 1 would be demoted to universe)14:23
MirvThat would mean I could both add -2- to seeds and remove the version 1 from there, as the latter is a useful package but not required in default installation.14:24
* vorlon nods14:24
Mirvok done the change add https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=6901c478d792124c2fe3cf2289daac94ec245644 - please review, I feel shaky at using my superpowers which I don't do daily these days14:31
vorlonMirv: lgtm14:32
-queuebot:#ubuntu-release- Unapproved: accepted crash [source] (bionic-proposed) [7.2.8-1ubuntu0.18.04.1]14:48
Eickmeyervorlon, doko: Ok, then please reject 0.76 hanging around in proposed.14:59
Eickmeyerdoko: To answer your question, I was unaware you did anything because we do everything using git, and there were no changes there.15:01
cpaelzerthanks vorlon, I re-scheduled the tests that formerly failed15:09
cpaelzerwill check somewhen later if they succeed now as intended15:09
Eickmeyervorlon: nm, I guess it'll just supercede anyhow.15:15
wxlthere's some weird stuff going on with our lubuntu daily. should i just assume this is some sort of blip and restart? https://launchpadlibrarian.net/468001105/buildlog_ubuntu_focal_amd64_lubuntu_BUILDING.txt.gz similar issue in budgie btw https://launchpadlibrarian.net/467987391/buildlog_ubuntu_focal_amd64_ubuntu-budgie_BUILDING.txt.gz16:56
RikMillssome kubuntu 20.04 users have reported the same error. looks like the last plymouth upload16:57
wxlon upgrade?16:58
RikMillsyes, they pasted this error https://paste.ubuntu.com/p/wDSsdSh2YQ/16:58
RikMillsI'm going to update a VM to see shortly16:58
wxllooks like that file was added here https://launchpadlibrarian.net/467954305/plymouth_0.9.4git20200109-0ubuntu3.3_0.9.4git20200109-0ubuntu5.diff.gz17:01
RikMillswxl: I get this: https://i.imgur.com/hK2eEFX.png17:02
wxllooks similar17:02
RikMillslooks like seb128 has already logged off IRC for the day17:02
wxlthat file most definitely does not exist17:07
RikMillsI guess it wouldn't, as a flavour would not have the ubuntu log plymouth theme installed17:10
RikMills*log17:10
RikMills*logo17:10
RikMillsffs17:10
* RikMills blames new keyboard....17:11
wxlno, i mean that image does not exist in the package17:11
wxlso we added a reference in rules to install a file that doesn't exist17:11
wxlthat change should really be reverted until someone can actually add the right image XD17:11
franksmcbRikMills we are seeing that plymouth error in Ubuntu MATE17:11
RikMillsthere is a /usr/share/plymouth/themes/spinner/watermark.png installed by the plymouth deb17:16
franksmcbhttps://bugs.launchpad.net/ubuntu-mate/+bug/186637717:18
ubot5Ubuntu bug 1866377 in Ubuntu MATE "update-initramfs fails on plymouth hook" [Undecided,New]17:18
wxlthat's the problem file RikMills17:18
RikMillswxl: I think it is more that the target dir of the copy command does not exist?17:38
wxlit's the file itself17:39
RikMillsno17:39
wxl??17:40
RikMillswxl: cp /usr/share/plymouth/ubuntu-logo.png "${DESTDIR}/usr/share/plymouth/themes/spinner/watermark.png"17:41
RikMillsubuntu-logo.png exists17:42
RikMillsif ${DESTDIR}/usr/share/plymouth/themes/spinner/ does not exist, you would get the error in the upgrade17:42
wxloh derp i didn't read that right17:43
wxlyou're right RikMills it's the target dir17:48
cpaelzervorlon: python-cffi now passed on all arches - no more blocking itself and python3-defaults18:27
cpaelzerjust FYI, thank for merging the big_packages MP18:27
tumbleweedcpaelzer: how did you get it passing?18:46
ginggstumbleweed: https://git.launchpad.net/autopkgtest-cloud/commit/?id=c47f5e879fa836425d950053b6bf12859859152719:02
tumbleweedaha, thanks19:03
tumbleweedI *knew* it had to be something infra...19:03
tumbleweednot sure what test is that huge, though19:03
EickmeyerRikMills, wxl: Same with Ubuntu Studio. ISO FTB.19:27
kanashirohi, chef and some related packages were removed from Debian testing as per maintainer request: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=95279219:39
ubot5Debian bug 952792 in release.debian.org "RM: chef/13.8.7-6" [Normal,Open]19:39
kanashirowe also have some issues with chef and ruby 2.719:39
kanashiroshould we follow Debian and remove them as well?19:39
tumbleweedyes19:47
brycedoko yep removing 7.3 is the plan, and do feel free to skip anything as needed to resolve icu, I suspect getting that transition completed is a much higher priority.19:49
dokobryce: it would be nice if yould look the php-horde-* test failures triggered by php7.419:51
ahasenack"yould" "you could"? :)19:52
kanashiroI just talked one of the chef maintainers in Debian and he said that he will try to fix it this weekend, let's wait until Monday and if he has those packages fixed I'll request a FFe19:52
dokolate here ... sprint finished ;p19:52
brycedoko, yep it's on our list, cpaelzer had looked at them a couple days ago19:52
brycefor some reason those didn't show up on the ben-generated report, nor in the excuses page but I remembered they were problems with php7.2->7.319:53
dokoUnpacking libc6:amd64 (2.31-0ubuntu1) over (2.30-0ubuntu3) ...21:14
dokoSetting up libc6:amd64 (2.31-0ubuntu1) ...21:14
doko/usr/bin/perl: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory21:14
dokodpkg: error processing package libc6:amd64 (--configure):21:14
doko installed libc6:amd64 package post-installation script subprocess returned error exit status 12721:14
dokoErrors were encountered while processing:21:14
doko libc6:amd6421:14
dokoE: Sub-process /usr/bin/dpkg returned an error code (1)21:14
dokovorlon: so every autopkg test fails now, and there's nothing that pulls in libcrypt121:21
dokoI assume we can cancel almost all running autopkg tests21:22
juliankdoko: sounds like libc6 must predepend on libcrypt121:26
juliankor depends, i'm not sure21:26
dokoI uploaded perl to pick up that dependency, but getting all those tests passing quicky doesn't seem to be possible, so I'm uploading base-files to depend on libcrypt1, planning to copy that to the release pocket21:32
dokojuliank: it has the dependency, but almost all autopkg tests are picking up the glibc from the release pocket21:33
juliankdoko: I don't understand, glibc in release pocket ships libcrypto1, so that should be fine; and if libc6 from proposed depends on libcrypto1 it should be fine too21:34
dokohmm21:36
dokohttps://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/3/389-ds-base/20200306_162651_f9385@/log.gz21:37
dokoit unpacks libcrypt1 before updating libc621:37
juliankdoko: right, but it might need running ldconfig between those steps to make it pick it up in the ld.so cache21:38
dokojust wondering why that wasn't see in unstaböe21:39
dokoseen even21:39
juliankdoko: so libcrypt1 needs to be configured before libc6, aka libc6 needs to pre-depend on libcrypto1 (or run ldconfig in its preinst)21:39
juliankrunning ldconfig in the preinst should be easier21:39
juliankit at least avoids a pre-depends at the bottom layer of the dependency tree21:40
juliankdoko: oh but it is configured21:41
juliankdoko: oh, but the ldconfig call is done by triggers, it probably has not been executed at that point?21:44
juliankanyway, seems a bit odd21:45
dokoyep, but why doesn't it fail in unstable? I was looking for some version tests which I didn't update, but can't find anything21:45
julianki don't really know21:46
dokosomething to investigate before the release ...21:50
juliankdoko: I played around locally, upgrading libc6 (which instlaled libcrypt1), and it configured fine21:55
juliankso ... confused21:55
dokolibxcrypt should never have migrated to the release pocket with the wrong breaks/replaces, but it was a debian sync :-/22:07
dokojuliank: so calling ldconfig in the preinst unconditionally sounds like an appropriate fix, when updating to the current version. but not now. I'll look at that tomorrow again22:14
juliankdoko: not unconditionally, but on first upgrade to version depending on libcrypt1 should be ok22:15
juliankBut maybe you meant that22:15
dokoyep, that's what I mean22:15
juliankOk22:15
juliankIt's late22:15
dokothe pre-depends wouldn't work with the current breaks/replaces in libcrypt122:24
dokojuliank: https://launchpad.net/~doko/+archive/ubuntu/toolchain/+sourcepub/11045520/+listing-archive-extra  now building, will check tomorrow22:35
xnoxdoko:  and do just execute the ldconfig with LDCONFIG_NOTRIGGER=1 environment variable to actually force the ldconfig to happen.22:51

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