Re: Build Debian packages for multiple architectures
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 ni...@thykier.net: 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 debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51474d14.5040...@thykier.net -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAMS_SF+N7Vm4kOjC27i978dob7vK1xOp5f=zyÛSj_KsTXU=q...@mail.gmail.com
Re: Build Debian packages for multiple architectures
On Tue, Mar 19, 2013 at 11:06:55PM +0200, Andrii Senkovych wrote: 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 You don't need mergechanges when uploading to an own reprepro repository: you can put architectures in as they build. -- ᛊᚨᚾᛁᛏᚣ᛫ᛁᛊ᛫ᚠᛟᚱ᛫ᚦᛖ᛫ᚹᛖᚨᚲ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130320011440.gb20...@angband.pl
Build Debian packages for multiple architectures
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? Some time ago I've tried to manage my own debian repository with reprepro. I had almost no problems when repository contained packages with arch 'any'. Usually I just build packages on my machine and upload the results to the repository with dupload tool. However when there appeared packages that should be built for any supported architecture, some questions raised. It is certain that I still could build amd64 and i386 packages on my own machine. I realized I could upload source packages separately from the binary ones that simplified things a little. For example, if source package provides one binary package with arch 'any' and another one with 'all', I could upload it to the repository in two steps: 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 Everything's good in theory, but when I actually did this, all binary-only uploads included both arch-specific and arch-independent packages. This led to conflicts during upload phase because the repository already included binary packages with arch=all, but with different checksums. I have tried all sorts of dpkg-buildpackage flags with no success. After all these efforts I decided to ask you. So, the question is: how should I build packages for multiple architectures without such problems? Thank you. -- Best regards, Andrii Senkovych -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAMS_SF+pEK7soJdr7AYzHfDHdQ+tY12_rZLtBDQwpvf=dmv...@mail.gmail.com
Re: Build Debian packages for multiple architectures
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. -- ᛊᚨᚾᛁᛏᚣ᛫ᛁᛊ᛫ᚠᛟᚱ᛫ᚦᛖ᛫ᚹᛖᚨᚲ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130318171514.ga4...@angband.pl
Re: Build Debian packages for multiple architectures
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 debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51474d14.5040...@thykier.net
