[Bug 378547] Re: --components argument does not resolve dependencies properly

Ken Sharp 378547 at bugs.launchpad.net
Mon Jan 22 03:12:51 UTC 2024


Does this still occur on a supported Ubuntu release?

** Tags added: hardy

** Changed in: debootstrap (Ubuntu)
       Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debootstrap in Ubuntu.
https://bugs.launchpad.net/bugs/378547

Title:
  --components argument does not resolve dependencies properly

Status in debootstrap package in Ubuntu:
  Incomplete

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/378547/+subscriptions




More information about the foundations-bugs mailing list