Bug#566398: [buildd-tools-devel] Bug#566398: Bug#566398: sbuild: Generates .changes file with wrong arch.
On Sat, Jan 23, 2010 at 01:57:50PM +, Roger Leigh wrote: On Sat, Jan 23, 2010 at 12:56:00PM +0100, Kurt Roeckx wrote: All my i386 uploads got rejected, because I have filenames like: ffmpeg_0.5+svn20090706-5_amd64.changes instead of: ffmpeg_0.5+svn20090706-5_i386.changes sbuild is called with the proper --arch=i386. The architecture used is determined by dpkg --print-architecture inside the chroot. In your case, it must be returning amd64 for some reason. I doubt that: pk...@puccini:~$ sudo -u buildd schroot -c sid-i386-sbuild -u root -d /root -- dpkg --print-architecture I: [sid-i386-sbuild-bd3bc9da-cfdd-4650-9b71-d07a3168a5f4 chroot] (buildd-root) Running command: dpkg --print-architecture i386 And that worked until the most recent sbuild/buildd were deployed, before it worked just fine. Kind regards, Philipp Kern -- .''`. Philipp KernDebian Developer : :' : http://philkern.de Stable Release Manager `. `' xmpp:p...@0x539.de Wanna-Build Admin `-finger pkern/k...@db.debian.org signature.asc Description: Digital signature
Bug#566398: [buildd-tools-devel] Bug#566398: Bug#566398: sbuild: Generates .changes file with wrong arch.
On Sat, Jan 23, 2010 at 03:18:02PM +0100, Philipp Kern wrote: On Sat, Jan 23, 2010 at 01:57:50PM +, Roger Leigh wrote: On Sat, Jan 23, 2010 at 12:56:00PM +0100, Kurt Roeckx wrote: All my i386 uploads got rejected, because I have filenames like: ffmpeg_0.5+svn20090706-5_amd64.changes instead of: ffmpeg_0.5+svn20090706-5_i386.changes sbuild is called with the proper --arch=i386. The architecture used is determined by dpkg --print-architecture inside the chroot. In your case, it must be returning amd64 for some reason. I doubt that: pk...@puccini:~$ sudo -u buildd schroot -c sid-i386-sbuild -u root -d /root -- dpkg --print-architecture I: [sid-i386-sbuild-bd3bc9da-cfdd-4650-9b71-d07a3168a5f4 chroot] (buildd-root) Running command: dpkg --print-architecture i386 And that worked until the most recent sbuild/buildd were deployed, before it worked just fine. This is odd. I'll do some checking when I get home from work. The result of dpkg --print-architecture is what's used when opening the log, so they should not be able to differ. This code hasn't changed recently. Could you check the name of the temporary build directory under /build. This also has the arch name in the filename; can you confirm this is also incorrect? If you run sbuild with --debug, it should print out the value of each variable being set. If you grep for 'Arch', does this get set once or multiple times; is it being assigned the correct value? Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `-GPG Public Key: 0x25BFB848 Please GPG sign your mail. signature.asc Description: Digital signature
Bug#566398: [buildd-tools-devel] Bug#566398: Bug#566398: sbuild: Generates .changes file with wrong arch.
On Sat, Jan 23, 2010 at 03:19:51PM +, Roger Leigh wrote: On Sat, Jan 23, 2010 at 03:18:02PM +0100, Philipp Kern wrote: On Sat, Jan 23, 2010 at 01:57:50PM +, Roger Leigh wrote: On Sat, Jan 23, 2010 at 12:56:00PM +0100, Kurt Roeckx wrote: All my i386 uploads got rejected, because I have filenames like: ffmpeg_0.5+svn20090706-5_amd64.changes instead of: ffmpeg_0.5+svn20090706-5_i386.changes sbuild is called with the proper --arch=i386. The architecture used is determined by dpkg --print-architecture inside the chroot. In your case, it must be returning amd64 for some reason. I doubt that: pk...@puccini:~$ sudo -u buildd schroot -c sid-i386-sbuild -u root -d /root -- dpkg --print-architecture I: [sid-i386-sbuild-bd3bc9da-cfdd-4650-9b71-d07a3168a5f4 chroot] (buildd-root) Running command: dpkg --print-architecture i386 And that worked until the most recent sbuild/buildd were deployed, before it worked just fine. This is odd. I'll do some checking when I get home from work. The result of dpkg --print-architecture is what's used when opening the log, so they should not be able to differ. This code hasn't changed recently. Could you check the name of the temporary build directory under /build. This also has the arch name in the filename; can you confirm this is also incorrect? If you run sbuild with --debug, it should print out the value of each variable being set. If you grep for 'Arch', does this get set once or multiple times; is it being assigned the correct value? The problem does not seem to be when building, but when I send back a signed .changes file. There are i386.changes files in the build dir, but they end up as amd64.changes after signing. Kurt -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#566398: [buildd-tools-devel] Bug#566398: Bug#566398: sbuild: Generates .changes file with wrong arch.
On Sat, Jan 23, 2010 at 05:02:08PM +0100, Kurt Roeckx wrote: On Sat, Jan 23, 2010 at 03:19:51PM +, Roger Leigh wrote: On Sat, Jan 23, 2010 at 03:18:02PM +0100, Philipp Kern wrote: On Sat, Jan 23, 2010 at 01:57:50PM +, Roger Leigh wrote: On Sat, Jan 23, 2010 at 12:56:00PM +0100, Kurt Roeckx wrote: All my i386 uploads got rejected, because I have filenames like: ffmpeg_0.5+svn20090706-5_amd64.changes instead of: ffmpeg_0.5+svn20090706-5_i386.changes sbuild is called with the proper --arch=i386. The architecture used is determined by dpkg --print-architecture inside the chroot. In your case, it must be returning amd64 for some reason. I doubt that: pk...@puccini:~$ sudo -u buildd schroot -c sid-i386-sbuild -u root -d /root -- dpkg --print-architecture I: [sid-i386-sbuild-bd3bc9da-cfdd-4650-9b71-d07a3168a5f4 chroot] (buildd-root) Running command: dpkg --print-architecture i386 And that worked until the most recent sbuild/buildd were deployed, before it worked just fine. This is odd. I'll do some checking when I get home from work. The result of dpkg --print-architecture is what's used when opening the log, so they should not be able to differ. This code hasn't changed recently. Could you check the name of the temporary build directory under /build. This also has the arch name in the filename; can you confirm this is also incorrect? If you run sbuild with --debug, it should print out the value of each variable being set. If you grep for 'Arch', does this get set once or multiple times; is it being assigned the correct value? The problem does not seem to be when building, but when I send back a signed .changes file. There are i386.changes files in the build dir, but they end up as amd64.changes after signing. Ah OK, so it's on the buildd side in that case. I'll CC he, since he has been working on the buildd side recently. It may be that buildd uses the default ARCH in the config, which is typically the host arch. I'm not entirely sure how the new buildd config copes with multiple arches, so I'll defer to he here. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `-GPG Public Key: 0x25BFB848 Please GPG sign your mail. signature.asc Description: Digital signature
