Actually, another part of my grep search produced the following, which seems to suggest that an older version of libwayland-client0 is being used:
parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.mips64el: https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_mips64el.deb parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.arm64: https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_arm64.deb parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.i386: https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_i386.deb parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.armel: https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_armel.deb parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.mipsel: https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_mipsel.deb parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.arm: https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_armhf.deb parts/chromium/build/build/linux/sysroot_scripts/generated_package_lists/bullseye.amd64: https://snapshot.debian.org/archive/debian/20220331T153654Z/pool/main/w/wayland/libwayland-client0_1.18.0-2~exp1.1_amd64.deb At least that's the way I read it. rday On Thu, Aug 18, 2022 at 3:43 PM Robert Day <robert....@canonical.com> wrote: > A comprehensive grep includes the lines: > > parts/launcher/state/build: - libwayland-client0=1.20.0-1 > parts/va-drivers/state/build: - libwayland-client0=1.20.0-1 > parts/pipewire/state/build: - libwayland-client0=1.20.0-1 > parts/chromium-build/state/build: - libwayland-client0=1.20.0-1 > parts/manpage/state/build: - libwayland-client0=1.20.0-1 > > Oh, wait, there we > go: > parts/chromium/build/chrome/installer/linux/debian/dist_package_versions.json > appears to be a version manifest that does not include anything for 22.04. > Does that sound like the problem? > > P.S. Thanks for your patience with all of this. > > On Thu, Aug 18, 2022 at 3:30 PM Nathan Teodosio < > 1986...@bugs.launchpad.net> wrote: > >> What is libwayland-client0 version in your logs? Focal has 1.18.0, but >> >> wayland-1.21.0/debian/libwayland-client0.symbols: >> wl_proxy_marshal_flags@Base 1.20.0 >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1986925 >> >> Title: >> [snap] Trying to build chromium snap for core22: pkg-config fails. >> >> Status in chromium-browser package in Ubuntu: >> New >> >> Bug description: >> I checked out the "dev" branch of chromium-browser from launchpad and >> did what seemed necessary to update snapcraft.yaml to build with >> snapcraft 7 for core22. The only change of any significance was to >> change the extension from "gnome-3-38" to the core22-specific "gnome" >> extension. I started the build and it ran for quite some time (in a >> persistent 22.04 LXD container) until: >> >> 2022-08-18 09:11:00.869 :: + OUT=out/Release >> >> 2022-08-18 09:11:00.869 :: + mkdir -p out/Release >> >> 2022-08-18 09:11:00.888 :: + cp >> /root/snaps/snap-from-source/stage/build/args.gn out/Release/ >> >> 2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']' >> >> 2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']' >> >> 2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig >> >> 2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc >> >> 2022-08-18 09:11:00.935 :: + cd - >> >> 2022-08-18 09:11:00.935 :: >> /root/snaps/snap-from-source/parts/chromium/build >> >> 2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release >> >> 2022-08-18 09:11:07.112 :: ERROR at >> //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit >> code. >> >> 2022-08-18 09:11:07.112 :: pkgresult = >> exec_script(pkg_config_script, args, "value") >> 2022-08-18 09:11:07.113 :: ^---------- >> >> 2022-08-18 09:11:07.113 :: Current dir: >> /root/snaps/snap-from-source/parts/chromium/build/out/Release/ >> 2022-08-18 09:11:07.113 :: Command: python3 >> /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py >> -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb >> >> 2022-08-18 09:11:07.113 :: Returned 1. >> >> 2022-08-18 09:11:07.113 :: stderr: >> >> 2022-08-18 09:11:07.113 :: >> >> 2022-08-18 09:11:07.113 :: Could not run pkg-config. >> >> 2022-08-18 09:11:07.113 :: >> >> 2022-08-18 09:11:07.113 :: See >> //third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called. >> 2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") { >> >> 2022-08-18 09:11:07.113 :: ^---------------------- >> >> 2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file >> to be included. >> 2022-08-18 09:11:07.114 :: >> "//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan", >> 2022-08-18 09:11:07.114 :: >> ^----------------------------------------------------------- >> 2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with >> code 1. >> Review the scriptlet and make sure it's correct. >> >> I verified that the pkg-config utility is installed in the container; >> I can only suspect that this error is related to switching to the >> core22 gnome extension. I am open to suggestions. >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+subscriptions >> >> -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1986925 Title: [snap] Trying to build chromium snap for core22: pkg-config fails. Status in chromium-browser package in Ubuntu: New Bug description: I checked out the "dev" branch of chromium-browser from launchpad and did what seemed necessary to update snapcraft.yaml to build with snapcraft 7 for core22. The only change of any significance was to change the extension from "gnome-3-38" to the core22-specific "gnome" extension. I started the build and it ran for quite some time (in a persistent 22.04 LXD container) until: 2022-08-18 09:11:00.869 :: + OUT=out/Release 2022-08-18 09:11:00.869 :: + mkdir -p out/Release 2022-08-18 09:11:00.888 :: + cp /root/snaps/snap-from-source/stage/build/args.gn out/Release/ 2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']' 2022-08-18 09:11:00.922 :: + '[' amd64 = armhf ']' 2022-08-18 09:11:00.922 :: + cd /usr/lib/x86_64-linux-gnu/pkgconfig 2022-08-18 09:11:00.922 :: + ln -s libdrm.pc libdrm-uninstalled.pc 2022-08-18 09:11:00.935 :: + cd - 2022-08-18 09:11:00.935 :: /root/snaps/snap-from-source/parts/chromium/build 2022-08-18 09:11:00.935 :: + out/Release/gn gen out/Release 2022-08-18 09:11:07.112 :: ERROR at //build/config/linux/pkg_config.gni:104:17: Script returned non-zero exit code. 2022-08-18 09:11:07.112 :: pkgresult = exec_script(pkg_config_script, args, "value") 2022-08-18 09:11:07.113 :: ^---------- 2022-08-18 09:11:07.113 :: Current dir: /root/snaps/snap-from-source/parts/chromium/build/out/Release/ 2022-08-18 09:11:07.113 :: Command: python3 /root/snaps/snap-from-source/parts/chromium/build/build/config/linux/pkg-config.py -p /snap/gnome-3-38-2004/current/usr/bin/pkg-config x11-xcb 2022-08-18 09:11:07.113 :: Returned 1. 2022-08-18 09:11:07.113 :: stderr: 2022-08-18 09:11:07.113 :: 2022-08-18 09:11:07.113 :: Could not run pkg-config. 2022-08-18 09:11:07.113 :: 2022-08-18 09:11:07.113 :: See //third_party/swiftshader/src/Vulkan/BUILD.gn:69:5: whence it was called. 2022-08-18 09:11:07.113 :: pkg_config("x11-xcb") { 2022-08-18 09:11:07.113 :: ^---------------------- 2022-08-18 09:11:07.114 :: See //BUILD.gn:529:7: which caused the file to be included. 2022-08-18 09:11:07.114 :: "//third_party/swiftshader/src/Vulkan:swiftshader_libvulkan", 2022-08-18 09:11:07.114 :: ^----------------------------------------------------------- 2022-08-18 09:11:07.243 'override-build' in part 'chromium' failed with code 1. Review the scriptlet and make sure it's correct. I verified that the pkg-config utility is installed in the container; I can only suspect that this error is related to switching to the core22 gnome extension. I am open to suggestions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1986925/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp