tiomap-dev team mailing list archive

[Colin Watson <cjwatson@xxxxxxxxxxxxx>]

This works as far as it goes, but it's worth noting that right now
Launchpad is running a version of dpkg that's too old to understand that
armhf matches any-arm, so this will currently only work for armel.  We
could backport dpkg if it's urgent, or just wait until Launchpad is
switched over to run on Ubuntu 12.04 LTS, which I've been given to
understand is probably a month or two away.

** Tags removed: qa-needstesting
** Tags added: qa-ok

-- 
You received this bug notification because you are a member of TI OMAP
Developers, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/917708

Title:
  Launchpad does not recognize Arch = any-arm

Status in Launchpad itself:
  Fix Committed

Bug description:
  hi,

  now that armel and armhf is supported, I tried to upload a package
  with Arch = any-arm, and my upload was rejected.  If i use Arch =
  armel armhf, it works as expected, but i got the feeling from the
  debian policy that any-arm should work.

  this was discussed on #ubuntu-dev:

  <ndec> hi. i have tried to use Arch = any-arm for some of our packages, and my upload are rejected in this case. If i use Arch = armel armhf, it works as expected, but i got the feeling from the debian policy that any-arm should work. Anyone can advise?
  <ndec> any-arm work when building locally with dpkg-buildpackage in armel or armhf root fs. it's just that the upload is rejected by LP
  <seb128> seems like soyuz doesn't handle that yet
  -*- ogra_ guesses soyuz just knows $(dpkg-architecture -L), any, all
  <cjwatson> It might be a bit naive about CPU aliases
  <cjwatson> It does know about any-i386, say, but -arm is a bit different
  <cjwatson> $ dpkg-architecture -aarmel -iany-arm; echo $?
  <cjwatson> 0
  <cjwatson> therefore IMO you should file a bug on Launchpad about this, yes
  <cjwatson> lib/lp/soyuz/pas.py:determineArchitecturesToBuild doesn't implement the full architecture alias handling

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/917708/+subscriptions