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

Bug#443633: marked as done (db_4.6.19-1(m68k/unstable/washi): self-test FTBFS on m68k)

Your message dated Tue, 5 Apr 2011 18:10:33 +0200
with message-id <BANLkTikp1HFKrt+tuMs0s60Gt1GW7eiqfw@mail.gmail.com>
and subject line Bug#443633: db_4.6.19-1(m68k/unstable/washi): self-test FTBFS on m68k
has caused the Debian Bug report #443633,
regarding db_4.6.19-1(m68k/unstable/washi): self-test FTBFS on m68k
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 owner@bugs.debian.org

443633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=443633
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: db
Version: 4.6.19-1
Severity: important

db fails to build from source on m68k due to self-test errors. This
seems to have been a problem for the whole 4.6 series. 

What can I do to help debug this?



Here are selected excerpts from the buildd log.

| Automatic build of db_4.6.19-1 on washi by sbuild/m68k 85
| Build started at 20070918-2209
| ******************************************************************************


| ** Using build dependencies supplied by package:
| Build-Depends: tcl8.4-dev, procps [!hurd-i386], java-gcj-compat-dev [!m68k !mips !mipsel !arm !armeb !armel !hurd-i386 !kfreebsd-i386 !kfreebsd-amd64 !m32r]


| Checking correctness of source dependencies...
| Toolchain package versions: libc6-dev_2.5-11 linux-kernel-headers_2.6.18-7 gcc-4.1_4.1.2-15 g++-4.1_4.1.2-15 binutils_2.18~cvs20070812-1 libstdc++6-4.1-dev_4.1.2-15 libstdc++6_4.2.1-1


| Running Hsearch interface tests (18:38:34)
| ! grep ^FAIL obj/ALL.OUT
| FAIL: run_subsystem: env env007:  env66: mmap: Cannot allocate memory
| FAIL: error in ./TESTDIR/env012.log.p2 : ./TESTDIR/env012.log.p2:FAIL:23:19:53 (00:00:00) db_get: expected DATA1, got 
| FAIL: error in ./TESTDIR/env012.log.p2 : ./TESTDIR/env012.log.p2:FAIL:23:19:53 (00:00:00) ../dist/../test/envscript.tcl run: FAIL:23:19:53 (00:00:00) db_get: expected DATA1, got : pid 7605: expected 0, got 1
| FAIL: error in ./TESTDIR/env012.log.p3 : ./TESTDIR/env012.log.p3:FAIL:23:20:43 (00:00:00) db_get: expected DATA1, got 
| FAIL: error in ./TESTDIR/env012.log.p3 : ./TESTDIR/env012.log.p3:FAIL:23:20:43 (00:00:00) ../dist/../test/envscript.tcl run: FAIL:23:20:43 (00:00:00) db_get: expected DATA1, got : pid 7757: expected 0, got 1
| make: *** [build] Error 1
| ******************************************************************************
| Build finished at 20070919-2238
| FAILED [dpkg-buildpackage died]

A full buildd log is available at 

Other buildd logs may be available at 

Stephen R. Marenka     If life's not fun, you're not doing it right!

--- End Message ---
--- Begin Message ---
Old bug, db4.6 is now deprecated in unstable.

Ondřej Surý <ondrej@sury.org>

--- End Message ---

Reply to: