build missing

Asked by Mark Foster on 2009-08-30

I uploaded source changes for a backport of rubygems 1.3.1 from jaunty to hardy into the bitpusher team ppa.

when I build it on my amd64 system it created these files in /var/cache/pbuilder/result/

mfoster@sea-build-002:~/work/packages$ ls /var/cache/pbuilder/result/ | grep ruby
libgems-ruby_1.3.1-1~ppa1~hardy_amd64.changes
libgems-ruby_1.3.1-1~ppa1~hardy.diff.gz
libgems-ruby_1.3.1-1~ppa1~hardy.dsc
libgems-ruby_1.3.1.orig.tar.gz
rubygems_1.3.1-1~ppa1~hardy_all.deb
rubygems1.8_1.3.1-1~ppa1~hardy_all.deb
rubygems1.9_1.3.1-1~ppa1~hardy_all.deb
rubygems-doc_1.3.1-1~ppa1~hardy_all.deb

However after uploading it only builds i386 package which I do not understand. The control file says Architecture: all

Here is the upload message for reference.

mfoster@sea-build-002:~/work/packages$ dput bp-ppa libgems-ruby_1.3.1-1~ppa1~hardy_source.changes
Checking Signature on .changes
gpg: Signature made Sun 30 Aug 2009 11:03:01 AM PDT using DSA key ID ECA811FB
gpg: Good signature from "Mark Foster (Signing Key) <email address hidden>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 31A5 04D8 9EB9 78EB BE19 CCB2 3F23 AB10 ECA8 11FB
Good signature on /users/home/mfoster/work/packages/libgems-ruby_1.3.1-1~ppa1~hardy_source.changes.
Checking Signature on .dsc
gpg: Signature made Sun 30 Aug 2009 11:02:58 AM PDT using DSA key ID ECA811FB
gpg: Good signature from "Mark Foster (Signing Key) <email address hidden>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 31A5 04D8 9EB9 78EB BE19 CCB2 3F23 AB10 ECA8 11FB
Good signature on /users/home/mfoster/work/packages/libgems-ruby_1.3.1-1~ppa1~hardy.dsc.
Package includes an .orig.tar.gz file although the debian revision suggests
that it might not be required. Multiple uploads of the .orig.tar.gz may be
rejected by the upload queue management software.
Uploading to bp-ppa (via ftp to ppa.launchpad.net):
  libgems-ruby_1.3.1-1~ppa1~hardy.dsc: done.
  libgems-ruby_1.3.1.orig.tar.gz: done. libgems-ruby_1.3.1-1~ppa1~hardy.diff.gz: done. libgems-ruby_1.3.1-1~ppa1~hardy_source.changes: done. Successfully uploaded packages.
Not running dinstall.

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
2009-08-30
Last reply:
2009-08-31
Celso Providelo (cprov) said : #1

Mark,

Architecture-independent sources [1] are only built in a single architecture and the resulting binaries can be installed in any one. Launchpad/Ubuntu always use i386 for building arch-indep sources.

If you looks to the binaries produced in your PPA they will looks exactly the same as the one you've generated in your machine (<>_all.deb)

[1] http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Architecture

Can you help with this problem?

Provide an answer of your own, or ask Mark Foster for more information if necessary.

To post a message you must log in.