Re: Bug#24217: bigloo not stripped
severity 24217 normal
thanks
> /usr/bin/bigloo is a huge binary, nothing to object, but it is *much*
> bigger than it should be because it is not stripped.
But that has no effect other then using some extra diskspace. Yes,
not stripping a binary is a violation of policy. But it is nowhere
near release-critical.
<flamethrower on>
> Please, read my bug completely: I mark it as important so that the
> maintainer will be able to fix it
I did read your bugreport completely. But can you tell me why a maintainer
could not fix a normal bug? Making a normal bug release-critical as an excuse
to make Brian allow a fix into hamm sounds like a lame idea.
> I explicitly ask Brian White not to remove it from the distribution, but
> instead I ask him to allow a fixed bigloo to go into hamm.
You could also do that by making a NMU for this: it's a 1-line fix
in debian/rules, which takes less time then this absurd discussion
on the severity of a bugreport. This way you're not helping get hamm
ready.
</flamethrower>
Wichert.
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: