Package: kfreebsd-7
Version: 7.0-5
Severity: serious
User: [EMAIL PROTECTED]
Usertags: qa-ftbfs-20081006 qa-ftbfs
Justification: FTBFS on i386

Hi,

During a rebuild of all packages in a lenny chroot, your package failed
to build on i386.

Relevant part:
> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>= 4.1.0), bzip2, quilt, freebsd6-buildutils (>= 
> 6.2) [kfreebsd-i386 kfreebsd-amd64] | freebsd7-buildutils [kfreebsd-i386 
> kfreebsd-amd64], libdb4.4-dev | libdb-dev, flex-old | flex, libbsd-dev 
> [kfreebsd-i386 kfreebsd-amd64], gcc-4.3 [kfreebsd-i386 kfreebsd-amd64], 
> sharutils
> Checking for already installed source dependencies...
> debhelper: missing
> Using default version 7.0.15
> bzip2: already installed (1.0.5-1)
> quilt: missing
> libdb4.4-dev: missing
> libdb-dev: missing
> flex-old: missing
> flex: missing
> sharutils: missing
> Checking for source dependency conflicts...
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Package libdb4.4-dev is not available, but is referred to by another package.
> This may mean that the package is missing, has been obsoleted, or
> is only available from another source
> E: Package libdb4.4-dev has no installation candidate

The full build log is available from:
   http://newpeople.debian.org/~lucas/logs/2008/10/06

It is possible that your package builds fine in sid, but you should make sure
that your package also builds fine in lenny before the release.

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 containing a sid i386
environment.  Internet was not accessible from the build systems.

-- 
| Lucas Nussbaum
| [EMAIL PROTECTED]   http://www.lucas-nussbaum.net/ |
| jabber: [EMAIL PROTECTED]             GPG: 1024D/023B3F4F |



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to