| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix the following AttributeError error:
# ebuild /var/db/pkg/sys-apps/portage-2.3.71/portage-2.3.71.ebuild clean pretend clean
Traceback (most recent call last):
File "/usr/lib/python-exec/python3.6/ebuild", line 318, in <module>
type_name=pkg_type)
File "/usr/lib64/python3.6/site-packages/_emerge/Package.py", line 72, in __init__
db = self.cpv._db
AttributeError: 'str' object has no attribute '_db'
Bug: https://bugs.gentoo.org/532674
Fixes: bfe7892202b8 ("_pkg_str: add _db attribute (bug 640318)")
Signed-off-by: Zac Medico <zmedico@gentoo.org>
|
|
|
|
|
|
|
|
| |
Respect PORTAGE_NICENESS variable.
Closes: https://github.com/gentoo/portage/pull/441
Signed-off-by: Felix Neumärker <xdch47@posteo.de>
Signed-off-by: Zac Medico <zmedico@gentoo.org>
|
|
|
|
| |
Reported-by: M. J. Everitt <m.j.everitt@iee.org>
|
| |
|
|
|
|
| |
Closes: https://github.com/gentoo/portage/pull/343
|
|
|
|
|
|
|
| |
The default asyncio event loop triggers a resource warning if it
is not explicitly closed, therefore close it when appropriate.
Bug: https://bugs.gentoo.org/654390
|
|
|
|
|
| |
In order to avoid swallowing an unexpected KeyError, selectively
handle PortageKeyerror from doebuild.
|
|
|
|
|
|
|
|
|
|
|
| |
In order to ensure that any unintentionally inherited file descriptors
will not be inherited by child processes, set the inheritable flag to
False on startup, except for those corresponding to stdin, stdout, and
stderr. This mitigates potential problems that might result from
making the portage.process.spawn close_fds parameter default to False
for versions of python with PEP 446 support.
Bug: https://bugs.gentoo.org/648432
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
dev-python/pycparser-2.18+ exposes a design flaw in dev-python/ply that
makes it unable to work with -OO code. Given that Gentoo compiles its
Python packages with -OO and both -O and -OO use the same files for
Python < 3.5, using -O in Portage implicitly means -OO for those
implementations.
Remove the optimizations from Portage shebangs to prevent triggering the
issue until we find a proper solution for it.
Bug: https://bugs.gentoo.org/628386
Reviewed-by: Zac Medico <zmedico@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Ensure that config adjustments are applied to all relevant
config instances, in order to prevent inconsistencies like
the one that triggered bug 601466. Move the "Forcing test"
message from config to bin/ebuild, in order to avoid
duplicate messages.
X-Gentoo-Bug: 601466
X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=601466
Acked-by: Brian Dolbec <dolsen@gentoo.org>
|
|
|
|
|
|
| |
This reverts commit 9e104c424ef08d543546eb4ae54724af97d11c0e. This was
unreviewed and the PORTAGE_REPOSITORIES design is at least
controversial.
|
|
|
|
|
|
| |
This reverts commit fb4d1f4ff710c7d7c848cf5ed4a7232bc1dd1e19. The revert
is necessary to make it possible to sanely revert 9e104c4 ("ebuild: Set
PORTAGE_REPOSITORIES instead of deprecated PORTDIR_OVERLAY.")
|
|
|
|
|
|
| |
Reverts: e7d95cb ("Support location with trailing whitespace [...]")
Reverts: 7853950 ("Delete support for PORTDIR and PORTDIR_OVERLAY [...]")
Reverts: 31923f4 ("Skip some warnings for Portage Python [...]")
|
|
|
|
|
|
| |
whitespace by using quoting.
configparser.ConfigParser strips initial and trailing whitespace.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Since we don't support python 2.6 anymore, there's no need to wrap
argparse, so switch all the users to the standard library for it.
|
|
|
|
|
|
|
|
|
|
| |
When the NOCOLOR variable is overridden in portage.settings, it's
necessary to call the config.backup_changes method in order for the
change to persist through config.reset calls.
X-Gentoo-Bug: 531690
X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=531690
Acked-by: Brian Dolbec <dolsen@gentoo.org>
|
|
|
|
|
|
|
|
|
|
|
| |
It makes sense to run pkg_config by itself, but special phases like
"clean", "digest", and "manifest" can be useful. For example, if the
developer modifies the ebuild, then it's useful to regenerate the
manifest and use "clean" to discard the stale environment.
Fixes: bfa98d7a5b7a ("fixed ebuild so")
Reported-by: Vlastimil Babka <caster@gentoo.org>
Reviewed-by: Alexander Berntsen <bernalex@gentoo.org>
|
|
|
|
|
| |
Modules of installed instance of Portage are now placed in standard location,
which is included in default sys.path.
|
|
|
|
| |
(-bb can trigger errors, depending on Python version and environment.)
|
| |
|
| |
|
|
|
|
| |
Shouldn't be any functional changes here.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
A bunch of the messages are written to stdout instead of stderr, and
lack any sort of general context.
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
|
|
|
|
|
|
| |
This avoids weird issues that are triggered when the module is
reloaded (like having classes redefined while instances from the old
classes are still around, triggering TypeError confusion).
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This is especially necessary when running in prefix mode, since
sys.path may contain the path for a different version of portage.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
It makes more sense to use EROOT instead of ROOT for keys in mappings
like portage.db, since it allows for multiple prefixes to exist
simultaneously within the same map without having a key collision.
This affects all portageq commands which take a <root> parameter, since
that parameter now corresponds to EROOT instead of ROOT. None of this
makes any difference for non-prefix users, since EROOT and ROOT are
identical when EPREFIX is empty.
|
|
|
|
| |
This removes the last reference to PORTAGE_CALLER.
|
|
|
|
|
|
|
|
|
|
| |
Specifically, the cache can use any portage supported checksum method,
or use the standard mtime approach. In addition, support controlling
whether or not paths are stored, and generally try to restore some
of the centralization/encapsulation that was in place originally.
(cherry picked from commit bc1aed614fb588f0ade5bcb5d1265a8db0f8d247)
Change-Id: Ic38057e7dbb15063c64a93c99e66e113a7d4c70e
|
| |
|
|
|
|
|
| |
There's no need to query os.environ here, because portage.settings
will inherit the value automatically.
|
| |
|
|
|
|
|
|
|
|
| |
This code should be unnecessary, as long as the repo is correctly
identified for all calls to portdbapi methods like aux_get and
findname. Notably, config.setcpv() must be called with a Package
instance in order to ensure that it gets the metadata from the correct
repository.
|
|
|
|
|
|
| |
When overriding PORTDIR_OVERLAY, we can avoid "Location not set for
repository" messages if we include the original PORTDIR_OVERLAY paths
in the overridden setting.
|
|
|
|
|
| |
This enables controling the behaviour (creation and validation) per
repo, and while mildly ugly, refactors in the right direction.
|
| |
|
| |
|
| |
|