[Bug 730622] Re: no way to specify all architectures

Sam Brightman 730622 at bugs.launchpad.net
Sun May 21 10:33:05 UTC 2017


I can't remember the context from 6 years ago. I believe there was
nothing unsupported about it; trying to build a package for a non-host
architecture. debhelper not actually building all when told to made this
harder, and especially harder to automate.

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

Title:
  no way to specify all architectures

Status in debhelper package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: debhelper

  It used to be that by default all packages are selected. However,
  getpackages('both') is called from init(), which does not select
  packages for architectures other than the build architecture. The old
  behaviour of calling getpackages() should be used (no parameter, to
  get all of them). This is line 79 in Dh_Lib.pm. There was a recent
  change claiming that the new behaviour was more desirable to reduce
  the size of debian/rules. However, it seems that the -s option already
  covers the situation of smartly detecting compatibility.

  Furthermore, I would also debate whether the new design of -a not
  allowing architectures that don't match the current one is correct.
  Wanting architecture-dependent packages says nothing about whether you
  want them to match. Again, there is already a -s option. Now there is
  a different default too. Making a third change to -a behaviour means
  there is no way to specify building all architectures.

  Perhaps it should also be an error rather than warning to ask for
  packages that do not exist, or if there are no packages found?

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



More information about the foundations-bugs mailing list