Bug#783876: Seriously, these binaries should be stripped by default

2016-04-21 Thread Steve McIntyre
On Fri, Apr 22, 2016 at 12:47:09AM +0200, Matthias Klose wrote: > >you didn't write about how much the netinst image exceeds the cd size. If it >helps, lto1 could be stripped by default, because it's not used by default >for package builds. Looking for about 70MB to (just) squeeze into 1 CD

Bug#783876: Seriously, these binaries should be stripped by default

2016-04-21 Thread Samuel Thibault
Matthias Klose, on Fri 22 Apr 2016 00:47:09 +0200, wrote: > >With separate -unstripped (or whatever) packages, they could be > >installed by admin choice in those situations. > > well, admin choice is usually not the default. So this would miss the buildds. Making the buildds install extra

Bug#783876: Seriously, these binaries should be stripped by default

2016-04-21 Thread Matthias Klose
On 22.04.2016 00:31, Steve McIntyre wrote: On Thu, Apr 21, 2016 at 11:40:34PM +0200, Matthias Klose wrote: So why does the netinst image need a compiler? It's been a feature for years that we include a compiler and kernel headers to allow people to build third party modules on amd64/i386.

Bug#783876: Seriously, these binaries should be stripped by default

2016-04-21 Thread Steve McIntyre
On Thu, Apr 21, 2016 at 11:31:46PM +0100, Steve McIntyre wrote: >On Thu, Apr 21, 2016 at 11:40:34PM +0200, Matthias Klose wrote: >> >>The unstripped binaries should be installed by default on porter boxes and >>buildds. Yes, this is a trade-off between (largely my) developer time, the >>ability

Bug#783876: Seriously, these binaries should be stripped by default

2016-04-21 Thread Steve McIntyre
On Thu, Apr 21, 2016 at 11:40:34PM +0200, Matthias Klose wrote: >Control: severity -1 important > >On 21.04.2016 19:28, Steve McIntyre wrote: >>Control: severity -1 serious >>Justification: wasting many megabytes of space and download > >sorry, I don't see this as a justification. > >>We're

Bug#783876: Seriously, these binaries should be stripped by default

2016-04-21 Thread Steve McIntyre
On Thu, Apr 21, 2016 at 11:23:41PM +0200, Matthias Klose wrote: >On 21.04.2016 20:08, Ondřej Surý wrote: >>>From reading the bug comments I can see both sides of the argument, so >>why we don't ship just two versions that would be exchangeable - one >>with symbols and one (default) stripped? >>

Processed: Re: Bug#783876: Seriously, these binaries should be stripped by default

2016-04-21 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #783876 [gcc-5] gcc-5: consider stripping lto1 / cc1 / cc1plus Severity set to 'important' from 'serious' -- 783876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783876 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#783876: Seriously, these binaries should be stripped by default

2016-04-21 Thread Matthias Klose
On 21.04.2016 20:08, Ondřej Surý wrote: From reading the bug comments I can see both sides of the argument, so why we don't ship just two versions that would be exchangeable - one with symbols and one (default) stripped? The stripped one would be installed by default and if you need to produce

Bug#783876: Seriously, these binaries should be stripped by default

2016-04-21 Thread Ondřej Surý
>From reading the bug comments I can see both sides of the argument, so why we don't ship just two versions that would be exchangeable - one with symbols and one (default) stripped? The stripped one would be installed by default and if you need to produce trace, you would install the second

Bug#783876: Seriously, these binaries should be stripped by default

2016-04-21 Thread Steve McIntyre
Control: severity -1 serious Justification: wasting many megabytes of space and download We're shipping broken toolchain packages that are intentionally too large, and this is causing issues elsewhere. The "netinst" CD image that we advertise to people as the default Debian image to use for most