Your message dated Fri, 09 Jun 2006 07:32:13 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#370808: fixed in samhain 2.2.0-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: samhain
Version: 2.2.0-1
Severity: serious

Hello,

There was an error while trying to autobuild your package:

> ./src/sh_tiger1_64.c:375: error: inconsistent operand constraints in an 'asm'
> ./src/sh_tiger1_64.c:375: error: inconsistent operand constraints in an 'asm'
> ./src/sh_tiger1_64.c:375: error: inconsistent operand constraints in an 'asm'
> ./src/sh_tiger1_64.c:375: error: inconsistent operand constraints in an 'asm'
> ./src/sh_tiger1_64.c:375: error: inconsistent operand constraints in an 'asm'
> ./src/sh_tiger1_64.c:375: error: inconsistent operand constraints in an 'asm'
> ./src/sh_tiger1_64.c:375: error: inconsistent operand constraints in an 'asm'
> ./src/sh_tiger1_64.c:375: error: inconsistent operand constraints in an 'asm'
> ./src/sh_tiger1_64.c:375: error: inconsistent operand constraints in an 'asm'
> ./src/sh_tiger1_64.c:375: error: inconsistent operand constraints in an 'asm'
> ./src/sh_tiger1_64.c:375: error: inconsistent operand constraints in an 'asm'
> ./src/sh_tiger1_64.c:375: error: inconsistent operand constraints in an 'asm'
> make[1]: *** [sh_tiger_i.o] Error 1
> make[1]: Leaving directory `/build/buildd/samhain-2.2.0'
> make: *** [build-stamp] Error 2

A full build log can be found at:
http://buildd.debian.org/build.php?arch=amd64&pkg=samhain&ver=2.2.0-1

Best regards
Frederik Schueler



--- End Message ---
--- Begin Message ---
Source: samhain
Source-Version: 2.2.0-2

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

samhain_2.2.0-2.diff.gz
  to pool/main/s/samhain/samhain_2.2.0-2.diff.gz
samhain_2.2.0-2.dsc
  to pool/main/s/samhain/samhain_2.2.0-2.dsc
samhain_2.2.0-2_i386.deb
  to pool/main/s/samhain/samhain_2.2.0-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.
Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]> (supplier of updated 
samhain 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: Fri,  9 Jun 2006 16:15:08 +0200
Source: samhain
Binary: samhain
Architecture: source i386
Version: 2.2.0-2
Distribution: unstable
Urgency: low
Maintainer: Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]>
Changed-By: Javier Fernandez-Sanguino Pen~a <[EMAIL PROTECTED]>
Description: 
 samhain    - Data integrity and host intrusion alert system
Closes: 370808
Changes: 
 samhain (2.2.0-2) unstable; urgency=low
 .
   * Include patch provided by upstream fix build issues in amd64 with
     gcc 4.1 (Closes: #370808)
Files: 
 b4ca97f42ca2fd95289206690be1ed9f 737 admin optional samhain_2.2.0-2.dsc
 078f9ebae2c9d408fabdbb737e0f1cee 109758 admin optional samhain_2.2.0-2.diff.gz
 0b44d7e266949027cf3970a62965ff21 853060 admin optional samhain_2.2.0-2_i386.deb

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

iQCVAwUBRImDJvtEPvakNq0lAQJkmQP9Ejik5nXvXeh5Oy2xA2EWjt46Dwg4ogJy
6FB1YsTdo79gqvQcOGpS3S5lnHdwCbs5JsT7VWMiwicdWK3B73CwB2ZHOniQ3rQ/
pHV/tq3qIAWeVy2DjluXIlIE6IUULqCQGDuLHCGvQ4/VwZ/xx3rDJH5eyWYlEZFI
Zhgtn3VSFDk=
=QDdh
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to