| Summary: | virtual/python has be removed but dev-libs/boost still requires it | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Harris Landgarten <harrisl> |
| Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Huh? .../dev-libs/boost %% grep virtual/python * ChangeLog: Depend on dev-lang/python because virtual/python will go away, bug 358849. Hopefully changes will hit the tree soon as
cave resolve world -c
is stuck on the error.
$ sudo cave resolve world -c
Done: 6939 steps
These are the actions I will take, in order:
(nothing to do)
I encountered the following errors:
! virtual/python
Reasons: dev-libs/boost
Unsuitable candidates:
* Found no packages for resolvent virtual/python:(unknown)::(install_to_slash)
Paludis is propably being stupid and doesn't understand dependency changes without revision bumps. It's perfectly valid to change deps without revbumps. I suggest you file an upstream paludis bug for this. (In reply to comment #2) > Hopefully changes will hit the tree soon as > > cave resolve world -c > > is stuck on the error. By my comment in comment #1, I implied that the changes hit the tree on April 5th, 2011. I agree with comment #3, there is nothing to fix in the portage tree and it looks like a paludis bug. |
$ qdepends boost dev-libs/boost-1.41.0-r3: sys-libs/zlib virtual/python !!<=dev-libs/boost-1.35.0-r2 >=app-admin/eselect-boost-0.3 dev-util/boost-build:1.41 >=app-admin/eselect-python-20091230 sudo cave resolve boost Resolving: 1 stepscave@1304004667: [WARNING package_database.ambiguous_name] In thread ID '14034': ... In program cave resolve boost: ... When adding targets from commandline: ... When parsing user package dep spec 'boost': ... When parsing generic package dep spec 'boost': ... When disambiguating package name 'boost': ... Package name 'boost' is ambiguous, assuming you meant 'dev-libs/boost' (candidates were 'cacti-plugins/boost', 'dev-libs/boost') Done: 3260 steps These are the actions I will take, in order: r dev-libs/boost:1.42::gentoo 1.42.0-r2 to ::installed replacing 1.42.0-r2 [cycle 1] -debug -doc eselect -icu -mpi python -static-libs -tools (-test) build_options: -optional_tests symbols=split -trace -preserve_work Reasons: target, !!<=dev-libs/boost-1.35.0-r2 from dev-libs/boost, !<dev-libs/boost-1.34.0 from dev-util/boost-build Self dependent (already met) Total: 1 reinstalls I encountered the following errors: ! virtual/python Reasons: dev-libs/boost Unsuitable candidates: * Found no packages for resolvent virtual/python:(unknown)::(install_to_slash) Reproducible: Always