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 majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
