Niels, Adam, thanks. Do I understand correctly that the following workflow is sufficient?
1) developer uploads source package (generated with dpkg-buildpackage -S) 2) binary packages with together arch=all is performed on a single architecture (using dpkg-buildpackage -b) 3) binary-only packages are built for other architectures (dpkg-buildpackage -B) 4) if the package builds successfull on all architectures — merge *.changes file into a single one (using mergechanges) and all files are uploaded to the repository Thanks, I didn't know about mergechanges script. -- Best regards, Andrii Senkovych 2013/3/18 Niels Thykier <[email protected]>: > On 2013-03-18 18:15, Adam Borowski wrote: >> On Mon, Mar 18, 2013 at 06:17:01PM +0200, Andrii Senkovych wrote: >>> Hello, debian-mentors >>> >>> I'm sorry in advance if this is the wrong list to ask. >>> >>> TL;DR: how to build and upload properly packages that provide >>> both arch=all and arch=any binary packages without conflicts like >>> "file already exists with different checksum" during upload >>> stage? >> >>> 1) upload source package ond binary packages for one arch (this >>> upload seems to include the packages with 'all' arch as well) 2) >>> upload binary packages for all other architectures >> >>> So, the question is: how should I build packages for multiple >>> architectures without such problems? >> >> dpkg-buildpackage -B >> >> This runs only the binary-arch target but not the rest. >> > > Also, see mergechanges(1) from devscripts, which can you from signing > several changes files. > > ~Niels > > > > -- > To UNSUBSCRIBE, email to [email protected] > with a subject of "unsubscribe". Trouble? Contact [email protected] > Archive: http://lists.debian.org/[email protected] > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/CAMS_SF+N7Vm4kOjC27i978dob7vK1xOp5f=zyÛ[email protected]
