Bug#472704: Failure while configuring base packages -- But why?

[Colin Watson <cjwatson@debian.org>]

On Fri, Aug 20, 2010 at 05:19:01PM +0200, Eric Estievenart wrote:
> The issue is likely to be in the functions script :
> 
> resolve_deps () {
>         local m1="${MIRRORS%% *}"
> 
>         # XXX: I can't think how to deal well with dependency
> resolution and
>         #      lots of Packages files. -- aj 2005/06/12
>         c="${COMPONENTS%% *}"
> 
> This only keeps the first component, so if multiple components are used,
> --components=main,contrib
> and a package from contrib is added in the list of required packages,
> its dependencies _will_not_be_fetched_,
> thus resulting in the error.

I couldn't see a bug specifically about this, so I'm replying here.
I've just committed a fix for this, which will be in debootstrap 1.0.30:

  http://git.debian.org/?p=d-i/debootstrap.git;a=commitdiff;h=8ca6fafd9030acfc060bb9f6f83b96cb56b4a9fe;hp=92cf330c441260fa28f6277dc63823f6416e2115

However, this clearly isn't the original problem reported in this bug.
If you look back to the top, you'll see that Peter didn't request
multiple components, and nor did Michael.  James was the first in the
bug log to do so.

Cheers,

-- 
Colin Watson                                       [cjwatson@debian.org]