Todd A. Jacobs wrote: > Some of the variants fail when run using sudo, instead of when logged in as > root. In particular, buildd and the standard install will fail, while minbase > will succeed. > > $ sudo debootstrap --arch=i386 --variant=buildd --include=sudo,locales,less sid sid-build-ia32 http://mirrors.kernel.org/debian/ > I: Retrieving Release > I: Retrieving Packages > I: Validating Packages > I: Resolving dependencies of required packages... > I: Resolving dependencies of base packages... > I: Found additional base dependencies: bzip2 cpp-4.2 debian-archive-keyring g++-4.2 gcc-4.2 gnupg gpgv libbz2-1.0 libgcrypt11 libgdbm3 libgnutls26 libgpg-error0 libldap-2.4-2 libopencdk10 libreadline5 libsasl2-2 libstdc++6-4.2-dev libtasn1-3 libtimedate-perl libusb-0.1-4 linux-libc-dev lzma readline-common > I: Checking component main on http://mirrors.kernel.org/debian... > [snip] > I: Configuring libopencdk10... > I: Configuring libgnutls26... > I: Configuring libldap-2.4-2... > I: Configuring gnupg... > I: Configuring debian-archive-keyring... > I: Configuring apt... > I: Configuring g++-4.2... > I: Configuring g++... > I: Configuring libstdc++6-4.2-dev... > W: Failure while configuring base packages. > W: Failure while configuring base packages. > W: Failure while configuring base packages. > W: Failure while configuring base packages. > W: Failure while configuring base packages. > > Note that if the user is root, rather than a mortal using sudo, the same > commands succeed. This obviously shouldn't be the case. Sudo *is* root, only the environment can differ slightly. I'd need to see your debootstrap.log to make any guesses about what is causing it to fail for you when you use sudo. I do sudo debootstrap frequently without issues, and have just run your command line successfully (though using ftp.us.debian.org; mirrors.kernel.org is distressed) -- see shy jo
Attachment:
signature.asc
Description: Digital signature