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

build-dependencies inconsistent in testing

Consider this:

pooh% apt-cache show build-essential dpkg-dev 
Package: build-essential
Priority: optional
Section: devel
Installed-Size: 48
Maintainer: Antti-Juhani Kaijanaho <ajk@debian.org>
Architecture: i386
Version: 4
Depends: libc6-dev | libc-dev, gcc, g++, make, dpkg-dev (>=
Filename: dists/woody/main/binary-i386/devel/build-essential_4.deb


Package: dpkg-dev
Priority: standard
Section: utils
Installed-Size: 364
Maintainer: Wichert Akkerman <wakkerma@debian.org>
Architecture: all
Source: dpkg
Replaces: dpkgname, dpkg (<<, dpkg-doc-ja
Depends: perl5, cpio (>= 2.4.2-2), patch (>= 2.2-1), make, binutils
Recommends: c-compiler
Suggests: gnupg, debian-keyring
Conflicts: dpkgname
Filename: pool/main/d/dpkg/dpkg-dev_1.8.3.1_all.deb


This makes it rather difficult to build a chroot testing environment
that makes senes :/

Is the dependency in build-essentials wrong or did this package just
get through by accident?


"Farcical aquatic ceremonies are no basis for a system of government!"

Reply to: