Your message dated Sun, 11 Jun 2006 09:05:58 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#368812: fixed in rafkill 1.2.1-2
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: rafkill
Version: 1.2.1-1
Severity: serious

The rafkill package is failing to build on those architectures whose
autobuilders use sudo as rootcmd (alpha/mips/mipsel), because the clean
target is apparently not clean:

[...]
scons prefix=install bin=bin
scons: Reading SConscript files ...
Use 'scons -h' for help

scons: *** Error writing options to file: rafkill.conf
[Errno 13] Permission denied: 'rafkill.conf'
File "SConstruct", line 15, in ?
make: *** [build-stamp] Error 2
[...]

A full build log can be found at
<http://buildd.debian.org/fetch.php?pkg=rafkill&arch=alpha&ver=1.2.1-1&stamp=1147768591&file=log>.


Apparently, the clean target leaves around a rafkill.conf file that it
should not, and because the clean target is run under $rootcmd, this leaves
the build target unable to overwrite it.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
[EMAIL PROTECTED]                                   http://www.debian.org/

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message ---
Source: rafkill
Source-Version: 1.2.1-2

We believe that the bug you reported is fixed in the latest version of
rafkill, which is due to be installed in the Debian FTP archive:

rafkill-data_1.2.1-2_all.deb
  to pool/main/r/rafkill/rafkill-data_1.2.1-2_all.deb
rafkill_1.2.1-2.diff.gz
  to pool/main/r/rafkill/rafkill_1.2.1-2.diff.gz
rafkill_1.2.1-2.dsc
  to pool/main/r/rafkill/rafkill_1.2.1-2.dsc
rafkill_1.2.1-2_i386.deb
  to pool/main/r/rafkill/rafkill_1.2.1-2_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sam Hocevar (Debian packages) <[EMAIL PROTECTED]> (supplier of updated rafkill 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sun, 11 Jun 2006 17:18:23 +0200
Source: rafkill
Binary: rafkill-data rafkill
Architecture: source i386 all
Version: 1.2.1-2
Distribution: unstable
Urgency: low
Maintainer: Debian allegro packages maintainers <[EMAIL PROTECTED]>
Changed-By: Sam Hocevar (Debian packages) <[EMAIL PROTECTED]>
Description: 
 rafkill    - vertical shoot'em-up similar to Raptor: Call of the Shadows
 rafkill-data - graphics and audio data for rafkill
Closes: 368812
Changes: 
 rafkill (1.2.1-2) unstable; urgency=low
 .
   * debian/rules:
     + Properly clean the build tree in the clean rule, thanks to Damyan Ivanov
       (Closes: #368812).
Files: 
 4bece0e6c0de82d9d7a9ffd4e21b8455 750 games optional rafkill_1.2.1-2.dsc
 efa47e16df5e40042d003f9fc40c76d6 122758 games optional rafkill_1.2.1-2.diff.gz
 c736b8595e97efca56787a0414362ada 6039526 games optional 
rafkill-data_1.2.1-2_all.deb
 16bcec5a6a83927744916d8edbe2c5da 149910 games optional rafkill_1.2.1-2_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFEjDdJfPP1rylJn2ERAnoCAJ9hW4qwgkqIiybcGDzBr8SLKQKPDQCeNCLz
sXpvqQoAI3a9M7yDfOcGSPU=
=G05l
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to