[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: FTBFS, error in .orig.tar.gz

On Tue, Aug 24, 2004 at 11:12:41PM -0700, Matt Kraai wrote:
> On Tue, Aug 24, 2004 at 09:35:16PM -0700, Thomas Bushnell BSG wrote:
> > See http://bugs.debian.org/264172.
> > 
> > So I don't know what is the standard way to force an upload of a new
> > .orig.tar.gz file.  
> > 
> > Most people don't see the bug, because we apt-get source as non-root,
> > so that tar unpackas without setting the setuid bit, and then the
> > package builds without errors.
> > 
> > But the orig.tar.gz does in fact have the setuid bit set, and this is
> > in fact a FTBFS error, and violates the release criterea for sarge.
> > 
> > So my preference is that someone tell me the right way to upload the
> > file, so that I can learn.  
> You can typically fix such problems without changing the tarball
> by adding
>  chmod -R u-s .
> to the clean target in debian/rules.

The problem is that clean doesn't need to be run. Policy says you should
be be able to build the package by just unpacking and then running
'debian/rules binary'.

Buildd's run clean first, but that isn't required, and a FTBFS when
clean isn't executed is still a FTBFS.


Jeroen van Wolffelaar
Jeroen@wolffelaar.nl (also for Jabber & MSN; ICQ: 33944357)

Attachment: pgp206zo_0jkr.pgp
Description: PGP signature

Reply to: