From: James Page <james.page@ubuntu.com>
To: Gary Lowell <gary.lowell@inktank.com>
Cc: Wido den Hollander <wido@widodh.nl>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Debian packaging question
Date: Tue, 11 Dec 2012 10:06:33 +0000 [thread overview]
Message-ID: <50C705A9.1030603@ubuntu.com> (raw)
In-Reply-To: <0D99561D-3A0B-4766-9770-8A90E37B7A24@inktank.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 11/12/12 06:32, Gary Lowell wrote:
>>>
>>> I assume you are building with "dpkg-buildpackage" ?
>>>
>>> The manpage shows:
>>>
>>> "-B Specifies a binary-only build, limited to architecture
>>> dependent packages. Passed to dpkg-genchanges."
>>>
>>> "-A Specifies a binary-only build, limited to architecture
>>> independent packages. Passed to dpkg-genchanges."
>>>
>>> So on the i386 and amd64 machines you'd run with -B and sync
>>> them to ceph.com
>>>
>>> On one of the machines you'd also run with -A which should
>>> produce the architecture independent packages like
>>> libcephfs-java.
>>>
>>> That's the theory, I haven't tested it :)
>>>
>>> Wido
> Thanks Wido. We're using pbuilder, but it looks like it has
> similar options, or can pass an option string to dpkg_buildpackage.
> I'll do some testing.
"--binary-arch" will limit a pbuilder build to the target binary
architecture only; I would recommend you use this with the amd64 build
and build the arch: all packages out of the i386 build; this is what
happens in the official Ubuntu builders.
Cheers
James
- --
James Page
Ubuntu Core Developer
Debian Maintainer
james.page@ubuntu.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/
iQIcBAEBCAAGBQJQxwWpAAoJEL/srsug59jDCRcP/i7IEUboQANGevKBVsh4bIeV
PiHAJGyHX/ljEkxhCpVI2dKxJxW2d6oZDKHwJarZlrPmYxGV5GXdcRcDlR2Z5Qvt
MD0Hy8JnigJ+dvpo5pKLAFPA0HbKw/5bNyYhkLUwAyVjkPxhG2EEgbggUtQVgWjm
nNlsvgvV5czR8HKgKoqQvfNzP4vBpq5STLt3TFqG8qDxYbAQK9ZyBsJVpH710aCn
gALasDTODjY9AttadvYnJbjKoaIkgmlrGZbin5Zdy87XD41mG9HtlNKbAeJ2rAPM
BEDLcMAeg6BXSuu9sSUrgNl36UmEkwnDudMZzezin/ubhQXsHDfaDjd3Dgdl8brx
LsX5fziLPvWPdCs9LzAiPYiMPde9+911Wk/N3Jbf8mLL3M5/U/5sYv0M9SD70NGA
67JbktN66RApA0WV9IZqDOgGNLLImI+nXmlHNkGRlm9XFez2pVjYI0CSq0vZonYN
wU/ISi7V94AF6TAb7LxF8O8JDFBXlz2fHrFS9T2CLvb4jRP8TLFPHoWLRu+3lGbD
pdimZK9fd35XNdI/1167Yafj9A8VvNUgZcGFb4bc4u5GJsND+0S6khTI2ZStv2a8
SyXdh4LxRePB1TC/jpMV/JKjYktMU7dhGDWM6Phgod/gUUA/cyWU9ROXXukCV98M
CzC76vescwKVjRxBogR7
=N76U
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-12-11 10:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 5:19 Debian packaging question Gary Lowell
2012-12-11 5:34 ` Wido den Hollander
2012-12-11 6:32 ` Gary Lowell
2012-12-11 10:06 ` James Page [this message]
2012-12-11 23:00 ` Gary Lowell
2012-12-12 11:04 ` James Page
2012-12-12 15:44 ` Sage Weil
2012-12-12 21:12 ` James Page
2012-12-12 22:17 ` James Page
2012-12-12 23:38 ` Gary Lowell
2012-12-13 9:09 ` James Page
2012-12-14 4:38 ` Gary Lowell
2012-12-14 9:03 ` James Page
2012-12-11 5:34 ` Sage Weil
2012-12-11 6:38 ` Gary Lowell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50C705A9.1030603@ubuntu.com \
--to=james.page@ubuntu.com \
--cc=ceph-devel@vger.kernel.org \
--cc=gary.lowell@inktank.com \
--cc=wido@widodh.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox