From: Wido den Hollander <wido@widodh.nl>
To: Gary Lowell <gary.lowell@inktank.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>,
James Page <james.page@ubuntu.com>
Subject: Re: Debian packaging question
Date: Tue, 11 Dec 2012 13:34:29 +0800 [thread overview]
Message-ID: <50C6C5E5.6010107@widodh.nl> (raw)
In-Reply-To: <B29C14E0-EFB2-4F4C-A1CA-481CB3F7AC39@inktank.com>
Hi,
On 12/11/2012 01:19 PM, Gary Lowell wrote:
> Hi -
>
> I'm looking for advice on debian multiple architecture repositories. To date we have been building ceph debian packages on two different machines for the i386 and amd64 platforms, rsyncing the results to a common directory on the build host, then putting the results together using the reprepro command to push out to ceph.com. As all the packages are architecture=linux-any, the arch is embedded in the file names and we don't have any collisions.
>
> The new libcephfs-java, which is architecture=all, ends up being built twice with the same resulting file name, but different checksums depending on where it was built. Not unexpectedly, reprepro complains about this.
>
> I know just enough about debian packaging to be a danger to myself and others. I can see how to fix up the checksums after the fact, but what is the right way to fix the problem ?
>
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,
> Gary
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2012-12-11 5:34 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 [this message]
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
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=50C6C5E5.6010107@widodh.nl \
--to=wido@widodh.nl \
--cc=ceph-devel@vger.kernel.org \
--cc=gary.lowell@inktank.com \
--cc=james.page@ubuntu.com \
/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.