Bug#787956: raising the severity, prevents usage of the multilib packages

2017-01-09 Thread Mark Brown
On Sat, Jan 07, 2017 at 11:15:51AM +0100, Matthias Klose wrote: > multiarch is not yet ready; you can't build it on the buildds, you can't > depend > on foreign architectures on the buildds. If you want to spend some time > working > on this, it would be appreciated, but until then I think

Bug#787956: raising the severity, prevents usage of the multilib packages

2017-01-07 Thread Matthias Klose
On 06.01.2017 15:47, Mark Brown wrote: > On Fri, Jan 06, 2017 at 08:48:06AM +0100, Matthias Klose wrote: >> On 05.12.2016 18:50, Mark Brown wrote: > >>> As we have been discussing it is still not clear to me if I should fix >>> or remove the multilib packages since it is still not clear to me

Bug#787956: raising the severity, prevents usage of the multilib packages

2017-01-06 Thread Mark Brown
On Fri, Jan 06, 2017 at 08:48:06AM +0100, Matthias Klose wrote: > On 05.12.2016 18:50, Mark Brown wrote: > > As we have been discussing it is still not clear to me if I should fix > > or remove the multilib packages since it is still not clear to me that > > there is a sensible use case for them.

Bug#787956: raising the severity, prevents usage of the multilib packages

2017-01-05 Thread Matthias Klose
On 05.12.2016 18:50, Mark Brown wrote: > On Mon, Dec 05, 2016 at 06:24:46PM +0100, Matthias Klose wrote: >> On 05.12.2016 18:14, Mark Brown wrote: > >>> I am suggesting that since nothing except for the multlib D runtime >>> packages needs a multilib zlib and there seems to be a very limited use

Bug#845793: Bug#787956: raising the severity, prevents usage of the multilib packages

2016-12-05 Thread Mark Brown
On Mon, Dec 05, 2016 at 06:24:46PM +0100, Matthias Klose wrote: > On 05.12.2016 18:14, Mark Brown wrote: > > I am suggesting that since nothing except for the multlib D runtime > > packages needs a multilib zlib and there seems to be a very limited use > > case for them it seems better to just

Bug#787956: raising the severity, prevents usage of the multilib packages

2016-12-05 Thread Matthias Klose
On 05.12.2016 18:14, Mark Brown wrote: > On Mon, Dec 05, 2016 at 04:40:29PM +0100, Matthias Klose wrote: >> On 05.12.2016 11:29, Mark Brown wrote: >>> On Wed, Nov 30, 2016 at 03:31:59PM +0100, Matthias Klose wrote: > it's available in the GCC packages for a while now. > >>> Sure, but

Bug#787956: raising the severity, prevents usage of the multilib packages

2016-12-05 Thread Mark Brown
On Mon, Dec 05, 2016 at 04:40:29PM +0100, Matthias Klose wrote: > On 05.12.2016 11:29, Mark Brown wrote: > > On Wed, Nov 30, 2016 at 03:31:59PM +0100, Matthias Klose wrote: > >> it's available in the GCC packages for a while now. > > Sure, but there's a bunch more stuff needed. > sorry, I don't

Bug#845793: Bug#787956: raising the severity, prevents usage of the multilib packages

2016-12-05 Thread Matthias Klose
On 05.12.2016 11:29, Mark Brown wrote: > On Wed, Nov 30, 2016 at 03:31:59PM +0100, Matthias Klose wrote: >> On 30.11.2016 13:45, Mark Brown wrote: > >>> Well, there's a bunch of questions there - people seem generally >>> negative on x32 and the use cases for multilib with tooling for early >>>

Bug#787956: raising the severity, prevents usage of the multilib packages

2016-12-05 Thread Matthias Klose
ping? On 30.11.2016 15:31, Matthias Klose wrote: > On 30.11.2016 13:45, Mark Brown wrote: >> On Tue, Nov 29, 2016 at 02:00:48PM +0100, Matthias Klose wrote: >>> On 28.11.2016 19:42, Mark Brown wrote: On Sat, Nov 26, 2016 at 08:59:34PM +0100, Matthias Klose wrote: >> Which apparently

Bug#787956: raising the severity, prevents usage of the multilib packages

2016-12-05 Thread Mark Brown
On Wed, Nov 30, 2016 at 03:31:59PM +0100, Matthias Klose wrote: > On 30.11.2016 13:45, Mark Brown wrote: > > Well, there's a bunch of questions there - people seem generally > > negative on x32 and the use cases for multilib with tooling for early > > boot and so on don't seem to apply in any

Bug#787956: raising the severity, prevents usage of the multilib packages

2016-11-30 Thread Matthias Klose
On 30.11.2016 13:45, Mark Brown wrote: > On Tue, Nov 29, 2016 at 02:00:48PM +0100, Matthias Klose wrote: >> On 28.11.2016 19:42, Mark Brown wrote: >>> On Sat, Nov 26, 2016 at 08:59:34PM +0100, Matthias Klose wrote: > >>> Which apparently changed at some point in the toolchain, probably quite >>>

Bug#787956: raising the severity, prevents usage of the multilib packages

2016-11-30 Thread Mark Brown
On Tue, Nov 29, 2016 at 02:00:48PM +0100, Matthias Klose wrote: > On 28.11.2016 19:42, Mark Brown wrote: > > On Sat, Nov 26, 2016 at 08:59:34PM +0100, Matthias Klose wrote: > > Which apparently changed at some point in the toolchain, probably quite > > some time ago, but fortunately we'd actually

Bug#787956: raising the severity, prevents usage of the multilib packages

2016-11-29 Thread Matthias Klose
On 28.11.2016 19:42, Mark Brown wrote: > On Sat, Nov 26, 2016 at 08:59:34PM +0100, Matthias Klose wrote: >> On 26.11.2016 20:35, Mark Brown wrote: >>> On Sat, Nov 26, 2016 at 07:52:26PM +0100, Matthias Klose wrote: On 26.11.2016 19:42, Mark Brown wrote: > On Sat, Nov 26, 2016 at

Bug#787956: raising the severity, prevents usage of the multilib packages

2016-11-29 Thread Matthias Klose
On 28.11.2016 20:00, Mark Brown wrote: > On Sun, Nov 27, 2016 at 06:39:22PM +0200, Sami Liedes wrote: > >> It seems to me that Mark is saying that this is not even supposed to >> work with lib32z1-dev installed, but rather you should have >> zlib1g-dev:i386 installed (and not doing so is user

Bug#787956: raising the severity, prevents usage of the multilib packages

2016-11-28 Thread Mark Brown
On Sun, Nov 27, 2016 at 06:39:22PM +0200, Sami Liedes wrote: > It seems to me that Mark is saying that this is not even supposed to > work with lib32z1-dev installed, but rather you should have > zlib1g-dev:i386 installed (and not doing so is user error). Right, that's now the expected way for

Bug#787956: raising the severity, prevents usage of the multilib packages

2016-11-28 Thread Mark Brown
On Sat, Nov 26, 2016 at 08:59:34PM +0100, Matthias Klose wrote: > On 26.11.2016 20:35, Mark Brown wrote: > > On Sat, Nov 26, 2016 at 07:52:26PM +0100, Matthias Klose wrote: > >> On 26.11.2016 19:42, Mark Brown wrote: > >>> On Sat, Nov 26, 2016 at 03:56:21PM +0100, Matthias Klose wrote: > >> This

Bug#787956: raising the severity, prevents usage of the multilib packages

2016-11-27 Thread Sami Liedes
On Sat, Nov 26, 2016 at 08:59:34PM +0100, Matthias Klose wrote: > > Can you please provide a clear, from first steps description of what's > > needed and why? > > again, here is the example which you removed: > [...] >^ > compilation terminated. > > The example fails because

Bug#787956: raising the severity, prevents usage of the multilib packages

2016-11-26 Thread Matthias Klose
On 26.11.2016 20:35, Mark Brown wrote: > On Sat, Nov 26, 2016 at 07:52:26PM +0100, Matthias Klose wrote: >> On 26.11.2016 19:42, Mark Brown wrote: >>> On Sat, Nov 26, 2016 at 03:56:21PM +0100, Matthias Klose wrote: > >>> Please allow at least a little time for a response, I've no real idea >>>

Bug#787956: raising the severity, prevents usage of the multilib packages

2016-11-26 Thread Mark Brown
On Sat, Nov 26, 2016 at 07:52:26PM +0100, Matthias Klose wrote: > On 26.11.2016 19:42, Mark Brown wrote: > > On Sat, Nov 26, 2016 at 03:56:21PM +0100, Matthias Klose wrote: > > Please allow at least a little time for a response, I've no real idea > > what you're even asking for here. > well, I

Bug#787956: raising the severity, prevents usage of the multilib packages

2016-11-26 Thread Matthias Klose
reopen 787956 thanks On 26.11.2016 19:42, Mark Brown wrote: > On Sat, Nov 26, 2016 at 03:56:21PM +0100, Matthias Klose wrote: > >> Control: severity -1 serious > > This appears to be some random bug that's a user error and should've > been closed after the initial discussion with the submitter

Bug#787956: raising the severity, prevents usage of the multilib packages

2016-11-26 Thread Matthias Klose
Control: severity -1 serious Hi, now that libgphobos, the gdc's D runtime library is built as a shared library, I'd like to use the still present multilib builds. There is currently a fall-back to embed the library, but that doesn't sound as clean as using the multilib packages. Dropping the