Bug#688330: gcc-4.7-base: WTF are you doing to the binary packages?

[Thorsten Glaser <tg@mirbsd.de>]

Philipp Kern dixit:

>I think you could work on your politeness and adjust the tone of your
>mails.

Right. I know that formulating is not one of my better skills.

>I don't think Matthias had an malicious intent here, to hurt you and
>induce suffering.

Yes, of course not.

>I think it was merely a
>human mistake of believing that a simple changelog mistake can be
>fixed after a quite long gcc build.

Well, this is not the first time I noticed it, and M-A only made it
visible. I cannot help but wonder what else things are done to the
packages that were not built from source. Of course, people uploading,
for example, binaries for multiple architectures at once are even more
suspicious (especially when the source FTBFS on all buildds then and it
doesn’t get fixed for weeks)…

I’m sorry Matthias for singling you out, but this was just an instance
where I noticed it as repeated issue with gcc-* packages. And, one has
to admit, wondering about the what-else is not _that_ far a mental jump.

(Especially after getting told off by the backports ftpmasters for
daring to upload a package built on a Xen or KVM, don’t remember,
guest. I’m now always taking care to build my packages for Debian
on bare metal and in as clean and minimal an environment as possible.)

bye,
//mirabilos
-- 
<Natureshadow> Dann mach ich git annex copy --to shore und fertig ist das
<Natureshadow> das ist ja viel cooler als ownCloud ...
<mirabilos> sag ich doch
<Natureshadow> ja wieso stimmt das denn immer was du sagst ...