| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
stdout, so that app-portage/autounmask continues to work. Note that
depgraph.display_problems() temporarily overrides the stdout stream
to point to stderr, so mask messages shown there continue to go
to stderr. Maybe the emerge --autounmask will eventually make
app-portage/autounmask obsolete, but for now we should support both
approaches since emerge --autounmask is relatively experimental.
|
|
|
|
| |
EbuildPhase._env_extractor_exit().
|
|
|
|
| |
to the front of the merge list when it is reinstalled.
|
| |
|
|
|
|
|
|
|
|
|
| |
git.eclass or has 9999 in its version, trigger the 'use copy of current
sources for install, then restart portage' routine. This is required
since with the live git portage-9999 ebuild we can't use the version
to detect incompatible changes to ebuild.sh. This issue was noticed
due to recent versions of ebuild.sh expecting PORTAGE_BZIP2_COMMAND to
be set, causing incompatibility with installed portage-9999 instances.
|
|
|
|
| |
in case it triggers mysterious unpack() issues or something.
|
|
|
|
|
|
| |
PORTAGE_BUNZIP2_COMMAND settings in make.conf. This only adds support
for binary packages, since that's where pbzip2 can provide the most
benefit in common cases.
|
|
|
|
| |
and warnings advising use of revdep-rebuild.
|
|
|
|
| |
for logging via named pipe (fifo) for sesandbox.
|
| |
|
|\ |
|
| |
| |
| |
| | |
assignment".
|
| | |
|
|/ |
|
|
|
|
|
| |
in the upcoming 2.1.9 branch which will not have sets support but will
still have the code in private and disabled form.
|
|
|
|
|
|
| |
None before trying to use them. This will be useful in the upcoming
2.1.9 branch which will not have preserve-libs support but will
still have the code in private and disabled form.
|
|
|
|
|
|
| |
trying to minimize the diff between the master branch and upcoming
2.1.9 branch which will not have preserve-libs support but will
still have the code in private and disabled form.
|
|
|
|
|
|
| |
trying to minimize the diff between the master branch and upcoming
2.1.9 branch which will not have preserve-libs support but will
still have the code in private and disabled form.
|
| |
|
| |
|
|
|
|
| |
for solving bug #279623.
|
|
|
|
| |
_is_work_scheduled() method.
|
|
|
|
| |
of uninstall nodes since those aren't dependencies in the usual sense.
|
|
|
|
|
|
| |
doesn't have a message, eliminate root nodes before calling
digraph.debug_print(). If --debug is enabled then do this even if
circular_dependency_handler has a message.
|
|
|
|
| |
Atom.violated_conditionals() raises InvalidAtom.
|
| |
|
|
|
|
| |
portage.exception.InvalidDependString.
|
|
|
|
|
| |
PROVIDE, and RESTRICT, and generate IUSE.missing errors for repoman
when appropriate.
|
| |
|
| |
|
|
|
|
|
|
| |
conditional which references a flag that is not listed in IUSE.
Also split out a Package._metadata_exception() method to handle
IUSE.missing for *DEPEND and SRC_URI.
|
|
|
|
|
|
|
|
|
|
| |
in cases when it's irrelevant (should re-evaluate these when new EAPIs
are deployed):
* EAPI.incompatible IUSE defaults
* EAPI.incompatible *DEPEND
* *DEPEND conditionals missing from IUSE
* SRC_URI.syntax
|
|
|
|
|
|
| |
about masked installed packages, customize the InvalidDependString
display to show the path of the *DEPEND file that contains the
invalid dependency.
|
| |
|
|
|
|
| |
packages, no that it accounts for invalid metadata.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
InvalidAtom exceptions, make use_reduce() raise InvalidDependString
exceptions that encapsulate InvalidAtom exceptions, and make
Package._validate_deps() use the InvalidAtom categories when
recording the invalid metadata for use by repoman. Also, remove
the EAPI.incompatible code from repoman that's no longer used.
|
| |
|
|
|
|
|
| |
Atom.unevaluated_atom.violated_conditionals() since in this case
the parent_use argument is required.
|
|
|
|
|
|
| |
Atom.violated_conditionals since the USE conditionals should have been
evaluated in dep_check() and we don't want to accidentally pass a
DependencyArg instance into _pkg_use_enabled().
|
|
|
|
|
| |
don't pass parent_use to Atom.violated_conditionals() since these atoms
already have already been through use_reduce() with the parent's USE.
|
|
|
|
|
| |
so that it only passes Package instances (not DependencyArg instances) into
_pkg_use_enabled().
|
| |
|
| |
|
|
|
|
| |
EAPI that does not support it.
|
|
|
|
| |
REQUIRED_USE.
|
|
|
|
|
| |
the package is not installed and it should have been validated and masked
already if necessary.
|
|
|
|
|
|
|
| |
with invalid metadata, and remove show_invalid_depstring_notice()
calls for installed packages since depgraph.display_problems() will
now show the invalid metadata masking reasons when it displays installed
packages that are masked.
|
|
|
|
|
|
| |
to avoid invalid or masked installed packages when necessary. This is
especially important for invalid packages since they need be replaced
so that their dependencies can be parsed for --depclean operations.
|