| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This will fix bug #363137.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add --nousepkg-atoms, --useoldpkg-atoms, and --reinstall-atoms flag
to Portage
reinstall-atoms accepts a space separated list of package names or
slot atoms. Emerge will treat matching packages as if they are not
installed, and reinstall them if necessary.
useoldpkg-atoms accepts a space separated list of package names or
slot atoms. Emerge will prefer matching binary packages over newer
unbuilt packages. This is useful in case you want to request that a
particular package won't be rebuilt from source.
nousepkg-atoms accepts a space separated list of package names or
slot atoms. Emerge will ignore matching binary packages.
Change-Id: I0d73039c6a4cd63695b28ffc80215628e0e05c95
BUG=chromium-os:12507 TEST=Try out the flag
Review URL: http://codereview.chromium.org/6577024
|
|
|
|
| |
This will fix bug #364701.
|
| |
|
|
|
|
| |
This will fix bug #357093.
|
|
|
|
| |
This will fix bug #356555.
|
| |
|
| |
|
|
|
|
| |
This happens if depstring evaluates to nothing.
|
|
|
|
| |
Broken since commit b4f98ec5a1eb2e010a455b19db5bef8d61def241.
|
| |
|
|
|
|
|
| |
This restores some desired logic that was left out of commit
5655b4dcfe5e9dae5e9d6352d791c3d04953baf7.
|
|
|
|
|
| |
Since commit 878f166c5a06b0ab6c5a34dd658c878cc7605fe7, empty implies
deep = True, so these checks are redundant.
|
|
|
|
|
|
| |
Always prefer parents for which the parent atom is unsatisfied by the
child node. This seems to be the intention of the code, though it may
not have behaved correctly due to continuation of the parent loop.
|
|
|
|
| |
This will fix bug #354747.
|
| |
|
|
|
|
|
|
| |
Recursively traversed virtual dependencies, and their direct
dependencies, are considered to have the same depth as direct
dependencies.
|
|
|
|
|
| |
Control over recursion depth hasn't behaved properly since commit
6503980e0e3bcfce9fbaff85c33d87f616e955a9. Now it is fixed and tested.
|
|
|
|
|
|
|
|
| |
Atoms are stored in the graph as (atom, id(atom)) tuples since each
atom is considered to be a unique entity. For example, atoms that
appear identical may behave differently in USE matching, depending on
their unevaluated form. Also, specially generated virtual atoms may
appear identical while having different _orig_atom attributes.
|
| |
|
|
|
|
|
|
|
|
| |
In _add_pkg_dep_string(), _add_pkg() was called with generated
Dependency instances that created fake/distorted edges in the
graph for new-style virtuals (similar to those that were fixed
in commit 5b16e0d800f34dc90cdd8c505172ad16b97f0af4). Now there
won't be any such distorted edges.
|
|
|
|
|
|
|
|
| |
As mentioned in bug #353933, comment #4, special new-style virtual
atoms generated/distorted by _expand_new_virtuals() can prevent
extract_affecting_use() from working properly. This is fixed by
saving the original atoms so that the depgraph can map them back
into place at the appropriate step in dependency evaluation.
|
|
|
|
| |
This will fix bug #354441.
|
|
|
|
| |
This will fix bug #354141.
|
|
|
|
|
|
|
| |
It's essential to feed back autounmask config changes, especially
USE changes, in order to make the last run as successful as possible.
This fixes a regression in the master branch, since commit
2186f87c22e0c4bdb86065855c2034bdbb66fa45.
|
| |
|
|
|
|
|
| |
It's common for downgrades to break dependencies, as in bug #353613, so
automatically trigger complete graph mode when a downgrade is found.
|
|
|
|
|
|
| |
This will fix bug #353613. We remove a hunk of code that was meant
to limit recursion, but is obsolete an buggy. The recursion limiting
is now handled by _add_pkg and the _ignored_deps stack.
|
|
|
|
| |
This will fix bug #353234.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This will fix bug #353443.
|
|
|
|
| |
It can take few seconds to search, so display a status message.
|
| |
|
|
|
|
| |
bug 352208
|
| |
|
|
|
|
| |
Fixes bug 350515.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The fix from bug #351828 broke some of the update avoidance behavior
from bug #275945, and this patch should restore it.
|
|
|
|
| |
This will fix bug #351828. It's fallout from bug #350285.
|