Summary: | sys-apps/portage-2.1.6.11: skipfirst makes other packages to be skipped but it's really hard to know who are they | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Pacho Ramos <pacho> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Pacho Ramos
![]() You might want to try --keep-going since that should list all of the skipped packages. The --skipfirst option is considered to be sort of a "legacy" option now that --keep-going is available. Also, note that --skip-first has specially issues (bug #247106) when using --jobs for parallel builds. With --keep-going I hit other problem: bug 264806 But thanks for the tip Pacho, is this bug still relevant with recent portage versions? If not, please close it. Thanks It's nice now :D # emerge --skipfirst These are the packages that would be merged, in order: Calculating dependencies... done! !!! One or more packages have been dropped due to !!! masking or unsatisfied dependencies: (dev-python/chaco-4.5.0:0/0::gentoo, ebuild scheduled for merge) requires >=dev-python/enable-4.4.0[python_targets_python2_7(-),-python_single_target_python2_7(-)], >=dev-python/enable-4.4.0[python_targets_python2_7(-),-python_single_target_python2_7(-)] emerge: It seems we have nothing to resume... Thanks |