Bug#291631: cmp/diff/etc. lack PT_GNU_STACK header
On Mon, Jan 24, 2005 at 01:46:30AM +0100, Santiago Vila wrote:
> On Mon, 24 Jan 2005 allomber@math.u-bordeaux.fr wrote:
>
> > I made a statistic on my machine:
> > 1341 are '-' and 76 are '?' so less than 1% has the problem.
> >
> > More importantly, there are all binaries that have been build a long
> > time ago, with the exception of diffutils and rcs binaries.
> >
> > Since diffutils was uploaded the 19/01/2005 I see no explanation why
> > it has the problem unless the maintainer built it on top of woody.
> > (The gcc changes is dated Sun, 9 Nov 2003).
>
> That's the correct explanation, yes. It has never been a bug to build
> a package using stable if the dependencies are compatible with the
> ones in testing. In this case, Pre-Depends: libc6 (>= 2.2.4-4) is ok
> because sarge has 2.3.2.ds1-20 and libc6 is not in oldlibs.
Well, it is recommended to build in sid, also, I do think building in
woody is bad for several reasons:
- you do not ship what's in sarge, you cannot reproduce the build
because it was build with software not in sarge. This is often the
case in minor ways, but intentionally doing so seems awkward at best.
- only one architecture will have these older woody depends, all other
architectures not. I don't know what reason you have to build on
woody, but that's defeated by this buildd reason.
- Suppose one day after sarge is released a security update needs to be
made, and this package is suddenly build on sarge. There might be
weird bugs hiding there, since nobody tested it this way, only builded
on woody. I think it's very important to make sure security uploads
are not going to change the package in bad ways, and suddenly building
with a much different libc et al, and a different gcc with different
properties apparantly (this bug is directly caused by it) might be
resulting in such bad changes, we simply don't know, since it hasn't
been tested.
So, why do you really want to build this on woody, and not just build on
sid as everybody else does?
--Jeroen
--
Jeroen van Wolffelaar
Jeroen@wolffelaar.nl (also for Jabber & MSN; ICQ: 33944357)
http://Jeroen.A-Eskwadraat.nl
Reply to: