Public bug reported:

Since runc/1.1.12+ds1-2ubuntu1 (from Noble onwards), the src:runc is
expected to not successfully build on non-amd64 architectures. The delta
used to be bigger to remove the application binary package which is now
shipped by src:runc-app in Ubuntu. In the mentioned version, the big
delta was replaced by the usage of a non-default build profile to avoid
building the application binary package. The side-effect is that now
src:runc FTBFS in all non-amd64 architectures, because in those
architectures no binary package is generated (build profiles do not
avoid triggering builds).

The golang-github-opencontainers-runc-dev binary package is arch:all and
building it on amd64 is enough, but the runc binary package (which is
still in src:runc but with a non-default build profile) is arch:any, so
there is an attempt to build it everywhere. Due to what was mentioned
above, the build is triggered in all arches because the source package
contains a arch:any binary, but the non-default build profile makes the
runc binary package do not build, and in non-amd64 the golang-github-
opencontainers-runc-dev binary package (arch:all) is also not built,
which causes a source package providing no binary (leading to build
failures).

This can be revisited but maintenance-wise this is the easiest approach,
since the delta from Debian is smaller. However, we need to live with
multiple build failures, which is also not nice.

P.S.: The build failures are not causing any harm, it is just annoying
to see them all the time.

** Affects: runc (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2082086

Title:
  Expect build failure on non-amd64 architectures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/runc/+bug/2082086/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to