Your message dated Wed, 24 Feb 2010 03:06:37 +0100 with message-id <2010-02-24t02-41...@devnull.michael-prokop.at> and subject line fixed with upload of 3.5.7+dfsg-2 has caused the Debian Bug report #562436, regarding afflib: FTBFS: CANNOT CREATE /tmp/blanke.aff 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 562436: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562436 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: afflib Version: 3.5.4+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: qa-ftbfs-20091223 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[3]: Entering directory > `/build/user-afflib_3.5.4+dfsg-1-amd64-yETb52/afflib-3.5.4+dfsg/tools' > === MAKING THE TEST FILES === > Making the random ISO rawevidence.iso > -rw-r--r-- 1 user sbuild 53761456 Dec 23 23:27 rawevidence.iso > MD5(rawevidence.iso)= 5bd7e437809fd79c793de093eab1fcf2 > ==== AFSIGN TEST === > Making X.509 keys > Generating a 1024 bit RSA private key > .......................++++++ > ................++++++ > writing new private key to 'agent.pem' > ----- > Generating a 1024 bit RSA private key > .................................++++++ > ..........++++++ > writing new private key to 'analyst.pem' > ----- > Generating a 1024 bit RSA private key > ............................++++++ > ...................................++++++ > writing new private key to 'archives.pem' > ----- > Making an AFF file to sign > TERM environment variable not set. > Initial AFF file > TERM environment variable not set. > FAIL: test_signing.sh > ==== AFRECOVERY TEST === > Make an X509 key > Generating a 1024 bit RSA private key > ..++++++ > .........................++++++ > writing new private key to '/tmp/recovery.pem' > ----- > Making the random ISO /tmp/recovery.iso > -rw-r--r-- 1 user sbuild 53761456 Dec 23 23:27 /tmp/recovery.iso > MD5(/tmp/recovery.iso)= b1d1e59edded9a645bbb514ce1b7e3da > SIGNING /tmp/recovery.iso > -rw------- 1 user sbuild 16784355 Dec 23 23:27 /tmp/recovery.afm > -rw-r--r-- 1 user sbuild 53761456 Dec 23 23:27 /tmp/recovery.iso > VERIFYING SIGNATURE > expat error: no element found at line 67 > > Filename: /tmp/recovery.afm > # Segments signed and Verified: 13 > # Segments unsigned: 0 > # Segments with corrupted signatures: 0 > > SIGNING CERTIFICATE : > Subject: CN=Mr. Recovery, emailaddress=recov...@investiations.com > Issuer: CN=Mr. Recovery, emailaddress=recov...@investiations.com > > > Number of custody chains: 1 > --------------------- > Signed Bill of Material #1: > > SIGNING CERTIFICATE : > Subject: CN=Mr. Recovery, emailaddress=recov...@investiations.com > Issuer: CN=Mr. Recovery, emailaddress=recov...@investiations.com > > Date: 2009-12-23T23:27:05 > Notes: > > --------------------- > > EVIDENCE FILE VERIFIES. > CORRUPTING FILE recovery.iso > 0+1 records in > 0+1 records out > 8 bytes (8 B) copied, 7.62527 s, 0.0 kB/s > ATTEMPTING RECOVERY > /tmp/recovery.afm has a bad signature > Attempting to repair page0 > Page page0 successfully repaired > expat error: no element found at line 67 > > Filename: /tmp/recovery.afm > # Segments signed and Verified: 13 > # Segments unsigned: 0 > # Segments with corrupted signatures: 0 > > SIGNING CERTIFICATE : > Subject: CN=Mr. Recovery, emailaddress=recov...@investiations.com > Issuer: CN=Mr. Recovery, emailaddress=recov...@investiations.com > > > Number of custody chains: 1 > --------------------- > Signed Bill of Material #1: > > SIGNING CERTIFICATE : > Subject: CN=Mr. Recovery, emailaddress=recov...@investiations.com > Issuer: CN=Mr. Recovery, emailaddress=recov...@investiations.com > > Date: 2009-12-23T23:27:05 > Notes: > > --------------------- > > EVIDENCE FILE VERIFIES. > MAKING SURE THAT THE MD5 HAS NOT CHANGED > ALL TESTS PASS > PASS: test_recovery.sh > === MAKING THE TEST FILES == > Making the random ISO /tmp/blank.iso > -rw-r--r-- 1 user sbuild 53761456 Dec 23 23:27 /tmp/blank.iso > MD5(/tmp/blank.iso)= a7edb11e279bd6c78893b4edc053dd1c > TERM environment variable not set. > TERM environment variable not set. > CANNOT CREATE /tmp/blanke.aff > Permission error prevents test from continuing. > PASS: test_passphrase.sh > === Putting a new metadata segment into blank.aff === > /tmp/blank.aff: 536 bytes transfered in 0.00 seconds. xfer rate: 35.73 > MBytes/sec > afsegment worked! > PASS: test_afsegment.sh > PASS: test_crypto.sh > make[3]: *** [check-TESTS] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2009/12/23/afflib_3.5.4+dfsg-1_lsid64.buildlog A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |
--- End Message ---
--- Begin Message ---Looking at https://buildd.debian.org/~luk/status/package.php?p=afflib&suite=unstable the FTBFS issues of afflib (#549832, #552049, #562436, #570658) have been fixed with upload of 3.5.7+dfsg-2. regards, -mika-signature.asc
Description: Digital signature
--- End Message ---
_______________________________________________ forensics-devel mailing list forensics-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/forensics-devel