--components argument does not resolve dependencies properly

Bug #378547 reported by Julien on 2009-05-20
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
debootstrap (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: debootstrap

I created custom repositories with my own component names, but that should not be necessary to duplicate this problem. Take for example --components=main,restricted, it will only look for dependencies on packages for one of the two repos, yet will install "Required" and "Important" packages from both.

When --components is specified, dependencies for packages in all but one of the specified components are ignored. The component picked for resolving dependencies seems to depend on line 1004 of functions 'c="${COMPONENTS%% *}"'.

The expected behavior is for the resolve_deps() function to resolve dependencies in all components.

I have been unable to find any patches related to this problem. I am using 1.0.8 on Hardy.

I have attached my hack to fix this.

Julien (julien-rhodes) wrote :

I forgot to remove my debugging code: "echo "$c:\n$PKGS">>/tmp.cpkgs"
Also, the tr ' ' '\n' is probably not necessary, but made debugging easier to read.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in debootstrap (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers