reopen 264172 severity 264172 important thanks On Wed, Aug 25, 2004 at 01:40:50AM -0700, Thomas Bushnell BSG wrote: > Jeroen van Wolffelaar <[EMAIL PROTECTED]> writes: > > > 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. > > Then there is no fix which conforms to policy.
Policy: | 4.7 Restrictions on objects in source packages | | The source package may not contain any hard links[19], device special | files, sockets or setuid or setgid files.[20] So you need to repack, as somebody else already suggested, and upload 0.6+2.nosetgid-0.1 (or something equivalent). Note that this issue isn't in the RM's sarge-release-policy, that policy is less strict, it only requires packages to be able to _autobuild_, that is, build fine in a normal autobuild environment (non-root, sane environment, and _with_ clean executed first). Since this 'only' violates Debian's package policy, the bug is still present, but severity important. --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl
