Re: Failed to create sbuild chroot for cross-compiling

2018-08-28 Thread Cyril Brulebois
Paul Wise (2018-08-26): > I don't think it is a good idea to upload packages you haven't > test-built yourself, so this seems like a very good default for > sbuild to have. FYI that's been fine for many years for packages like arch-specific bootloaders that are receiving l10n translations, which

Re: Failed to create sbuild chroot for cross-compiling

2018-08-27 Thread Sean Whitton
Hello, On Mon 27 Aug 2018 at 03:13PM GMT, Holger Wansing wrote: > Ok guys, in that case someone should overwork that wiki page, > since it says exactly this!!! > I have just quoted what I read there! I've fixed it -- thanks. > /me as new DM getting totally confused with all this, one person >

Re: Failed to create sbuild chroot for cross-compiling

2018-08-27 Thread Holger Wansing
Hi, Paul Wise wrote: > On Sun, Aug 26, 2018 at 4:42 PM, Holger Wansing wrote: > > > Raphael and you told me to not built the package here locally, but just > > do a source-only upload. > > In general, one should build locally and do a source-only upload. This > is so that you confirm the build

Re: Failed to create sbuild chroot for cross-compiling

2018-08-27 Thread Holger Wansing
Am Montag, 27. August 2018 schrieb Sean Whitton: > Hello, > > On Mon 27 Aug 2018 at 12:52PM +0200, Holger Wansing wrote: > > > And according to https://wiki.debian.org/SourceOnlyUpload > > source-only uploads are recommended now and are recommended to be done with > > pbuilder or sbuild. > > I

Re: Failed to create sbuild chroot for cross-compiling

2018-08-27 Thread Sean Whitton
Hello, On Mon 27 Aug 2018 at 12:52PM +0200, Holger Wansing wrote: > And according to https://wiki.debian.org/SourceOnlyUpload > source-only uploads are recommended now and are recommended to be done with > pbuilder or sbuild. I don't think this statement is really true. What's recommended is th

Re: Failed to create sbuild chroot for cross-compiling

2018-08-27 Thread Holger Wansing
Hi, Am Montag, 27. August 2018 schrieb Johannes Schauer: > Quoting Holger Wansing (2018-08-25 20:30:15) > > The manpage of sbuild-createchroot contains commandline examples for several > > use cases, but not for cross-compiling. > > yes, because sbuild-createchroot has nothing to do with cross-c

Re: Failed to create sbuild chroot for cross-compiling

2018-08-27 Thread Johannes Schauer
Hi, Quoting Holger Wansing (2018-08-25 20:30:15) > The manpage of sbuild-createchroot contains commandline examples for several > use cases, but not for cross-compiling. yes, because sbuild-createchroot has nothing to do with cross-compiling. chroots that you use to compile natively or cross with

Re: Failed to create sbuild chroot for cross-compiling

2018-08-27 Thread Holger Wansing
Hi, Raphael Hertzog wrote: > Hi, > > On Sun, 26 Aug 2018, Holger Wansing wrote: > > My intention was indeed, to do a source-only upload. But apparently > > sbuild builds the binary package nevertheless, even when told to prepare > > for a source-only upload. > > > > So the main point here is: d

Re: Failed to create sbuild chroot for cross-compiling

2018-08-27 Thread Raphael Hertzog
Hi, On Sun, 26 Aug 2018, Holger Wansing wrote: > My intention was indeed, to do a source-only upload. But apparently > sbuild builds the binary package nevertheless, even when told to prepare > for a source-only upload. > > So the main point here is: don't use sbuild, it's the wrong tool for this

Re: Failed to create sbuild chroot for cross-compiling

2018-08-26 Thread Paul Wise
On Sun, Aug 26, 2018 at 4:42 PM, Holger Wansing wrote: > Raphael and you told me to not built the package here locally, but just > do a source-only upload. In general, one should build locally and do a source-only upload. This is so that you confirm the build works and, by testing it manually, th

Re: Failed to create sbuild chroot for cross-compiling

2018-08-26 Thread Holger Wansing
Hi, Paul Wise wrote: > On Sun, Aug 26, 2018 at 4:12 PM, Holger Wansing wrote: > > > My intention was indeed, to do a source-only upload. But apparently > > sbuild builds the binary package nevertheless, even when told to prepare > > for a source-only upload. > > I don't think it is a good idea

Re: Failed to create sbuild chroot for cross-compiling

2018-08-26 Thread Paul Wise
On Sun, Aug 26, 2018 at 4:12 PM, Holger Wansing wrote: > My intention was indeed, to do a source-only upload. But apparently > sbuild builds the binary package nevertheless, even when told to prepare > for a source-only upload. I don't think it is a good idea to upload packages you haven't test-b

Re: Failed to create sbuild chroot for cross-compiling

2018-08-26 Thread Holger Wansing
Hi, Raphael Hertzog wrote: > Hi Holger, > > On Sat, 25 Aug 2018, Holger Wansing wrote: > > I need to get some debian-installer packages uploaded for s390x and mips. > > FTR, Holger is referring to packages which are built only on those > architectures (and that can't be built on amd64). > > >

Re: Failed to create sbuild chroot for cross-compiling

2018-08-25 Thread Paul Wise
On Sun, Aug 26, 2018 at 2:30 AM, Holger Wansing wrote: > I need to get some debian-installer packages uploaded for s390x and mips. I think it would be best to leave that to the buildds. > The manpage of sbuild-createchroot contains commandline examples for several > use cases, but not for cross-

Re: Failed to create sbuild chroot for cross-compiling

2018-08-25 Thread Raphael Hertzog
Hi Holger, On Sat, 25 Aug 2018, Holger Wansing wrote: > I need to get some debian-installer packages uploaded for s390x and mips. FTR, Holger is referring to packages which are built only on those architectures (and that can't be built on amd64). > Since I have no hardware for that archs, I susp

Failed to create sbuild chroot for cross-compiling

2018-08-25 Thread Holger Wansing
Hi all, I need to get some debian-installer packages uploaded for s390x and mips. Since I have no hardware for that archs, I suspect the way to go is to create a chroot for that archs, right? My hardware is amd64. I have a working sbuild chroot for amd64, for creation of that I followed https://