From: James Page <james.page@ubuntu.com>
To: Gary Lowell <gary.lowell@inktank.com>
Cc: Sage Weil <sage@inktank.com>, Wido den Hollander <wido@widodh.nl>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Debian packaging question
Date: Thu, 13 Dec 2012 09:09:50 +0000 [thread overview]
Message-ID: <50C99B5E.9010006@ubuntu.com> (raw)
In-Reply-To: <95BEC6FE-ECFA-4106-BF1F-C4BD43819602@inktank.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 12/12/12 23:38, Gary Lowell wrote:
> I took your new rules file out for a spin. It built ok, but we
> still got the libcephfs-java_0.55.1-1precise_all.deb built despite
> the --binary-arch flag. The command used for the build is:
>
> sudo pbuilder build --binary-arch --debug --distribution precise
> --basetgz /srv/debian-base/precise.tgz --buildresult
> /tmp/release/0.55.1/ --debbuildopts '-j8 -b'
> /tmp/release/0.55.1/ceph_0.55.1-1precise.dsc
>
> And the log shows the -B option on dpkg-buildpackage:
>
> I: Building the package I: Running cd tmp/buildd/*/ && env
> PATH="/usr/lib/ccache:/usr/sbin:/usr/bin:/sbin:/bin"
> dpkg-buildpackage -us -uc -B -j8 -b -rfakeroot
I think that the "--debbuildopts '-j8 -b'" might be trouncing the
- --binary-arch flag - I'll get pbuilder setup and give it a test - I
normally use sbuild (for which the packaging changes did have the
desired effect).
- --
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/
iQIcBAEBCAAGBQJQyZteAAoJEL/srsug59jDJWkP/1zjLIrtuyju2ButhcouDcv3
zxST5h+vizA9CWhl8WGeckoi1aTUA1Xs1oYYnfBMJyWaSyZFinhI8L32kHw/7eau
fvzMHBFJaEl3CFCYBZK/D7SyRLIsVLEayQhpIJOyOofSDSw466br5A5v3o2M+MFZ
+bdVBZmfF/2xRZpNnM8n+Orm35V70ejifwhPF6LXjzjxL9L40ft3KTi9XLxuZ6De
lQorbGGQ/pFWaerNK2a3TPvLynsstLofeWYfwSywh0uDK22StABu+T29rxS9fr4d
y6GaND185Lakrux/bWbnPntQPTzYY/6w93PM+zzHwpwsAWokhsRSrn1aN4IH9qy1
e48wHRnuZl7263bG10FklIVqI6Mfk4WrtEiuZNM7O74bFSS2Xd5I418BQKoIwzaq
Kcg3AHaIC2eGUKtjUi/uljDIYowWXAI6JOFClNIgj69lS0cE3SdwXfwhnRTHX5vc
h5ku8gaYiejpnoNFXfJYC5W458TU0aXNaqecWCdX+gNOfYuntCDQSWCT4NDSaA92
VQJXyvn7UOz5qFY5jQ9J0lpCUlaIWa5TVpsT5RJmZLhDV8aR0t4EnaS7q4HI6uZ6
JZNY9j/EIwMAG5Oqf3dThi5tyxxgwQ6Qvvk9UIMdv9mWkw/jtKHZSWK0cyskbjK9
lM0og+k9EJHQtOa7yNj8
=dOQW
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-12-13 9:09 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
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 [this message]
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=50C99B5E.9010006@ubuntu.com \
--to=james.page@ubuntu.com \
--cc=ceph-devel@vger.kernel.org \
--cc=gary.lowell@inktank.com \
--cc=sage@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.