Andreas Tille <[EMAIL PROTECTED]> writes: > sure I can fix this, but are you really sure. I just builded the > package in pbuilder. Does this mean that pbuilder is broken if it > did not ask for man-db? Is this perhaps a pbuilder bug?
More likely an artifact of continuing to use a chroot you initially created a long time ago: debootstrap supports two [relevant] modes of operation: regular and --variant=buildd. (There's also a --variant=fakechroot.) The regular mode is designed to set up base systems for direct human use, and therefore pulls in Priority: important packages such as man-db in addition to essential and Priority: required packages; the buildd mode, however, merely pulls in required and (build-)essential packages, leaving out man-db. The autobuilders use the latter setup, as do recently created pbuilder chroots (at least with the default configuration); however, if you created your chroot years ago and have merely been incrementally updating it since, it is likely to contain extraneous installations of Priority: important packages (not to mention older compiler versions and other cruft, due to the absence of any form of garbage collection). > BTW, I will have low bandwidth connection until Thursday - if you need > the fix soon - feel free to NMU. Thanks, but I don't need it too urgently, so I'm content to wait for an MU. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) Finger [EMAIL PROTECTED] (NOT a valid e-mail address) for more info. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
