** Description changed: [Impact] * Local package build attempts on riscv64 platform as well as cloud image builds for riscv64 on Hirsute were affected by inability to resolve correct golang dependencies. Allowing debian/control and package Makefiles to ignore building and packaging ubuntu-advantage-tools' golang hook binary allows for package builds to succeed with minimal impact to usability and user-messaging. [Test Plan] 1. Run sbuild --resolve-alternatives --dist=focal --arch=riscv64 to confirm package build success and does not include golang dependencies or /usr/lib/ubuntu-advantage/apt-esm-json-hook dpkg-deb -c *riscv64.deb | grep hook # expect only apt-esm-hook - - 2. Upload to ppa:ua-client/staging which is set to build both powerpc and riscv64 platforms by default and ensure no package build failures. + 2. Upload to ppa:ua-client/staging which is set to build both powerpc + and riscv64 platforms by default and ensure no package build failures. 3. Ensure go APT hook is still built and included in binary package as /usr/lib/ubuntu-advantage/apt-esm-json-hook and adds golang depends dpkg-deb -c *amd64.deb | grep hook # expect both apt-esm-hook & apt-esm-json-hook 4. Test functionality of go json hook on Focal amd64: 4a. get token from ubuntu.com/advantage 4b. ua attach <token_from_4a> 4c ua disable esm-infra 4d apt upgrade # check output for esm-infra package updates available. [Where problems could occur] * This is a low risk update as most problems will occur at package build time. * Accidental exclusion of /usr/lib/ubuntu-advantage/apt-esm-json-hook only results in the absence of a single informative message during `apt upgrade` or `apt dist-upgrade` which would describe detailed source for where package updates are originating: "1 standard security update, 1 esm-infra update and 2 esm-apps updates" * Without a packaged json hook, the message will be absent and no tracebacks or non-zero exits from APT + + * [racb] Mutating the Build-Depends line could cause alternatives to be + resolved differently on the buildds, resulting in toolchain changes that + might result in different sets of build failures or different build + output causing functional issues. [Other Info] [Original Description] Unable to sbuild focal 27.0~20.04.1 package on riscv64 cpu arch sbuild errors on build dependency errors w/ golang package: .... or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-main-dummy : Depends: golang but it is not going to be installed E: Unable to correct problems, you have held broken packages. apt-get failed. E: Package installation failed Not removing build depends: cloned chroot in use Keeping session: focal-riscv64-484fa0a7-506e-4b64-b7b8-9c5b454e8f77 E: Failed to explain bd-uninstallable +------------------------------------------------------------------------------+ | Summary | +------------------------------------------------------------------------------+ Build Architecture: riscv64 Build Type: binary Build-Space: n/a Build-Time: 0 Distribution: focal Fail-Stage: explain-bd-uninstallable Host Architecture: riscv64 Install-Time: 0 Job: ../out/ubuntu-advantage-tools_27.0~20.04.1.dsc Machine Architecture: amd64 Package: ubuntu-advantage-tools Package-Time: 0 Source-Version: 27.0~20.04.1 Space: n/a Status: given-back Version: 27.0~20.04.1
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927795 Title: 27.0 package build failures focal riscv64 architecture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1927795/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
