/srv/irclogs.ubuntu.com/2022/05/17/#ubuntu-devel.txt

xypronI am looking for a sponsor for LP #196817409:55
ubottuLaunchpad bug 1968174 in u-boot (Ubuntu) "SiFive Unmatched: automatically booting via bootmgr from SATA drive fails" [Undecided, Confirmed] https://launchpad.net/bugs/196817409:55
seb128xypron, uploaded10:15
ahasenackmorning12:04
lxsameerhey folks, what tool do you use to build the official ubuntu live images?12:05
lxsameerlive-build?12:05
ahasenackcan anybody spot the error here? I can't: https://pastebin.ubuntu.com/p/3VfXVG7zH5/12:12
ahasenackgolang is so fast that even the error messages don't have time to appear?12:12
ogralxsameer, try https://git.launchpad.net/livecd-rootfs/tree/ ...12:13
ogra(that wraps combination of live-build and ubuntu-image to build the images)12:13
ogra+a12:14
lxsameerthank you12:14
ahasenacksarnold: I heard you have the whole archive locally, would it be easy for you to do a grep in debian/tests/* for all packages? ;)12:41
ahasenackI guess you have the debs, not the extracted sources12:41
ahasenackoh, this worked: https://codesearch.debian.net/search?q=ldap%5Ba-z%5D%2B+.*-h+path%3Adebian%2Ftests&literal=012:43
rbasaku-d-a@ moderation please12:48
cjwatsonrbasak: .12:49
rbasakThanks!12:50
xypronI am looking for a sponsor for LP #190787813:11
ubottuLaunchpad bug 1907878 in ifupdown (Ubuntu) "wrong var declaration in if-up.d/resolved (nm-dispatcher[54417]: /etc/network/if-up.d/resolved: 12: mystatedir: not found)" [Undecided, Confirmed] https://launchpad.net/bugs/190787813:11
seb128xypron, are you sure the change is right? what users wrote indicate that the return also needs to be changed to an exit? also I'm not familiar with the package but if those lines are there it's probably for a reason, did we figure out what they were meant to do to decide they are safe to remove?13:14
seb128schopin, hey, can I bother you with an openssl problem?13:15
enr0nahasenack: I have seen that issue with that golang package before on ppc64el. It appeared to be a memory-constraint issue, and we resolved it by adding the package to big_packages on ppc64el. Where are you seeing it?13:26
ahasenackenr0n: https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#libzstd on s390x13:26
enr0nahasenack: Yeah, maybe it needs to be added to big_packages for s390x as well then.13:28
xypronseb128: the deleted lines contain variable names. These were never exectued. But unless you use 'set -e' the lines were simply ignored.13:39
xypronseb128: on a system using ifupdown and NetworkManager I have tested with eth1, eth1.90, eth1:1 and found no issues.13:41
xypronseb128: the change only removes the lines that were not executed and does not change the logic of the scripts.13:41
seb128xypron, k13:44
seb128xypron, sponsored14:06
xypronseb128: thanks14:07
bdmurrayenr0n, ahasenack: I'll add golang-github-valyala-gozstd to big_packages for s390x and rerun the test14:20
ahasenackthanks bdmurray14:25
enr0nbdmurray: thanks!14:26
lxsameerhave you folks, ever created an ubuntu image only via live-build?14:39
ahasenackschopin: hi, what do you know about RC4 being disabled in openssl3?14:44
ahasenackI'm troubleshooting a crash in cyrus-sasl, and so far it looks like it's trying to use RC4 via openssl14:44
ahasenackin jammy and kinetic, this command shows an error trying to use rc4: echo -ne "test" | openssl rc4 -k test14:45
ahasenackin impish (openssl 1) it issues just the warning, but seems to work otherwise14:45
jawn-smithlxsameer: some of our images are created using only live-build commands, such as the unmatched images14:48
lxsameerjawn-smith: good one, but since live-build is in the ubuntu's repo i thought you support it14:49
ahasenackok, found three upstream issues, lots of changes ://14:52
jawn-smithlxsameer: our different images are built with many different tools, which is actually something we're actively working to unify. In the future ubuntu-image will be the tool to build all images, but for now there are many different tools14:53
jawn-smithThe HiFive Unmatched images are currently built with live-build, and there may be some others.14:54
lxsameerjawn-smith: is it part of the official ubuntu repo?14:58
jawn-smithlive-build? Yes live-build is in main14:58
lxsameer jawn-smith sorry i meant the live-build config, where can i find the live-build config for the unmatched image?15:00
seb128slyon, hey, systemd sort of question for you, https://launchpadlibrarian.net/601716367/buildlog_ubuntu-kinetic-amd64.network-manager_1.38.0-1ubuntu1_BUILDING.txt.gz is failing to build on kinetic15:19
seb128compared to the 1.36 previous build we had in J, systemd isn't getting installed, probably because it's part of the base image?15:20
seb128I didn't debug the test issue yet but it seems that is probably due to a missing /etc/machine-id15:20
seb128also the old log which installed systemd had15:21
seb128> Initializing machine ID from random generator.15:21
seb128which I guess might be missing in the case of the systemd as part of the preinstall env?15:22
jawn-smithlxsameer: ah I see. The Unmatched images are built with the config/build scripts here: https://git.launchpad.net/livecd-rootfs/tree/live-build/auto15:22
seb128cjwatson, ^ or is that a launchpad build issue?15:22
jawn-smithIt keys off of the SUBARCH environment variable with a value of "sifive_hifive_unmatched_fu740"15:22
slyonseb128: interesting. I'm sure why systemd shouldn't be installed..15:22
slyon*not sure15:22
jawn-smithThis is a really outdated/ugly build system that we're working to replace, just FYI lxsameer15:23
seb128slyon, it's in the build-depends so my guess is that it is preinstall on whatever image the builders are loading15:23
seb128preinstalled15:23
cjwatsonseb128: if there's a discrepancy in the base chroot, then that would be something for CPC - we just pull in what they build15:24
cjwatson(albeit irregularly)15:24
seb128cjwatson, are the buildds starting a container? like would that be a normal system start which should generate a machine-id ?15:24
cjwatsonseb128: chroot, not container15:24
cjwatsonwe might switch to a container at some point, but that would be quite a big change and there hasn't been a pressing need for it15:25
seb128cjwatson, is there anywhere I can see the CPC provided chroot content?15:25
slyonoh ok. it's pre-installed. But we didn't change anything wrt. machine-id recently, so I wonder how this might have changed now. might be related to the pre-installed image15:25
cjwatsonseb128: https://api.launchpad.net/devel/ubuntu/kinetic/amd64 has a link to it15:25
seb128cjwatson, thanks15:25
seb128slyon, well, the 22.04 build log shows systemd installed as part of the build-depends install, and the machine-id is generated at this time15:26
seb128so at least that part changed15:26
seb128having it preinstall it seems nothing in the chroot setup is creating a machine-id15:26
cjwatsonI don't believe it's intentional for systemd to be in the chroot; there may have been a dependency change that caused that15:26
seb128ack, I will check with cpc15:27
cjwatsonit's the buildd subproject in livecd-rootfs15:27
slyonack15:27
seb128cjwatson, side bug, that url has a chroot_url in http instead of https which firefox refuses to open, I will report a launchpad bug about it ;)15:27
cjwatsonhm we do install "init" for historical reasons, maybe I'm misremembering15:27
cjwatsonseb128: not a bug, api isn't typically expected to be used by browsers15:27
seb128ah, ok15:28
cjwatsonwe might change it for general politeness reasons15:28
cjwatsonyou can also use manage-chroot in ubuntu-archive-tools to grab it15:29
seb128thx15:29
seb128slyon, so that chroot archive has a 0 byte /etc/machine-id15:29
seb128which was the case in older series also, and systemd was also installed in the chroot15:32
cjwatsonIt might just be that buildd had to upgrade systemd from what the older chroot had15:32
seb128right, that's what I was just thinking15:32
seb128so maybe it is a regression in n-m tests not handling fine the 0 byte /etc/machine-id15:33
cjwatsonI suppose we could have buildd generate a machine-id and poke it in for chroot-based builds, though that doesn't answer why this wasn't needed before15:33
slyonso just coincidence that we had to upgrade systemd in JJ chroots? and something might have changed/broken that a while back?15:33
seb128which is boggus but doesn't seem a new issue15:34
slyonaccording to man machine-id(5): "If /etc/machine-id exists and is empty, a boot is not considered the first boot.  systemd will still bind-mount a file containing the actual machine-id over it and later try to commit it to disk (if /etc/is writable)."15:35
slyonthat bind-mount doesn't seem to happen here neither. Do you know if /etc/ is writable inside the chroot?15:35
cjwatsonI would be astonished if /etc weren't writable, but systemd won't be running in the chroot15:39
cjwatsonBecause it's a chroot, not a container15:40
seb128well, I guess it's not a new condition but just confuse n-m now15:40
seb128cjwatson, slyon, thanks for the replies!15:40
seb128I will dig a bit more into n-m changes after diner if gitlab is responding again15:41
=== gjolly_ is now known as gjolly
=== lfaraone_ is now known as lfaraone
=== beisner_ is now known as beisner
=== coreycb_ is now known as coreycb
enr0n_I am looking for someone to review/sponsor LP #197337716:08
ubottuLaunchpad bug 1973377 in gnudatalanguage (Ubuntu) "gnudatalanguage: small test_tic_toc tolerance" [Undecided, New] https://launchpad.net/bugs/197337716:08
teward!no dmb-ping is <reply>rbasak, sil2100, teward, bdmurray, kanashiro, seb128: DMB ping16:34
tewardsorry for the ping everyone16:34
xypronI am looking for a sponsor for LP #197378817:12
ubottuLaunchpad bug 1973788 in findutils (Ubuntu) "package findutils 4.9.0-3" [Undecided, Confirmed] https://launchpad.net/bugs/197378817:12
sarnoldahasenack: I've got some scripts that can unpack either the sources or binaries and run things over the results; I've also got the sources unpacked, but funny enough, searching through *all* of those is way slower than the scripts because those unpack only what's reachable via the lists, but I don't yet have a way to clean up no-longer-needed sources17:55
ahasenackok17:56
GunnarHjHi bdmurray, gnome-settings-daemon 42.1-1ubuntu2.1 was moved to jammy-updates about 10 hours ago, but I still don't see it available in jammy via "apt update". (I'm using the main server, so I assume it's not about propagation.) Known issue, or "just me"?19:18
jbichaI noticed that https://people.canonical.com/~ubuntu-archive/phased-updates.html was empty for jammy today but several things were promoted to jammy-updates early today19:21
GunnarHjjbicha: Yeah, I too got *some* updates, but not the one I mentioned.19:26
bdmurrayGunnarHj, jbicha: You can see the phased-update-percentage by looking up one of the binaries in LP. It's currently at 20%.20:03
bdmurrayhttps://launchpad.net/ubuntu/jammy/amd64/gnome-settings-daemon/42.1-1ubuntu2.120:03
jbichathe phased updates page is working for me now20:06
bdmurrayOr you can just look at the Packages file http://archive.ubuntu.com/ubuntu/dists/jammy-updates/main/binary-amd64/Packages.gz20:06
GunnarHjThanks, bdmurray, I take it that you say that this delay is normal. All is well then.20:08
=== mfo_ is now known as mfo

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