| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
disable warnings about "missing repo_name entries" for the stable
branch.
|
|
|
|
| |
instead of just GPL-2.
|
|
|
|
|
| |
atomc reading and writing of whole pickles. This should be the least
error-prone approach, given the non-blocking nature of the streams.
|
|
|
|
| |
depgraph._show_unsatisfied_dep() calls it.
|
|
|
|
|
|
|
|
|
| |
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().
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
packages, and use it for evaluating conditional USE deps in atoms
passed via IPC to helpers like has_version and best_version.
Since the pickled object that contains the IPC command will no longer
contain USE, it should solve cases that have been reported in which
large USE strings trigger poor handling of non-blocking read in
pickle.load():
Traceback (most recent call last):
File "/usr/bin/emerge", line 43, in <module>
retval = emerge_main()
File "/usr/lib64/portage/pym/_emerge/main.py", line 1649, in emerge_main
myopts, myaction, myfiles, spinner)
File "/usr/lib64/portage/pym/_emerge/actions.py", line 437, in action_build
retval = mergetask.merge()
File "/usr/lib64/portage/pym/_emerge/Scheduler.py", line 1033, in merge
rval = self._merge()
File "/usr/lib64/portage/pym/_emerge/Scheduler.py", line 1349, in _merge
self._main_loop()
File "/usr/lib64/portage/pym/_emerge/Scheduler.py", line 1498, in _main_loop
self._poll_loop()
File "/usr/lib64/portage/pym/_emerge/PollScheduler.py", line 139, in _poll_loop
handler(f, event)
File "/usr/lib64/portage/pym/_emerge/EbuildIpcDaemon.py", line 36, in _input_handler
obj = pickle.load(self._files.pipe_in)
File "/usr/lib64/python2.6/pickle.py", line 1370, in load
return Unpickler(file).load()
File "/usr/lib64/python2.6/pickle.py", line 858, in load
dispatch[key](self)
File "/usr/lib64/python2.6/pickle.py", line 1195, in load_setitem
value = stack.pop()
IndexError: pop from empty list
|
|
|
|
| |
error handling to portage.util.ensure_dirs().
|
| |
|
|
|
|
| |
exists when EISDIR is raised, since this is abnormal behavior.
|
|
|
|
| |
for it are given.
|
| |
|
|
|
|
| |
'manifest' and 'digest' that don't require a temp dir.
|
|
|
|
| |
on FreeBSD (see bug #187518).
|
|
|
|
|
| |
set for nonatoms so that we don't trigger 'TypeError: can only
concatenate list (not "set") to list'.
|
|
|
|
| |
to the front of the merge list when it is reinstalled.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If multiple ebuild processes create the same directory, portage should not
exit with an error message. Instead we should just be okay with the fact
that another process created the directory.
This is only necessary for fast build because we eliminate the giant lock that
surrounds package merges.
TEST=Create fresh chroot and do full build from source start to finish
BUG=none
Review URL: http://codereview.chromium.org/2998002
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Portage should use the ensure_dirs function instead of os.makedirs to create
directories, because this function ensures atomicity. It prevents failures
when more than one process tries to create the same directory.
This fixes a crash bug reported by msb:
[...]
File "/usr/lib64/portage/pym/portage/dbapi/vartree.py", line 3258, in _merge
self.vartree.dbapi._bump_mtime(self.mycpv)
File "/usr/lib64/portage/pym/portage/dbapi/vartree.py", line 152, in _bump_mtime
os.makedirs(catdir)
File "/usr/lib64/portage/pym/portage/__init__.py", line 210, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
File "/usr/lib64/python2.6/os.py", line 157, in makedirs
mkdir(name, mode)
OSError: [Errno 17] File exists: '/home/msb/trunk/src/build/images/x86-generic/0.8.63.2010_08_03_1844-a1/rootfs//var/db/pkg/x11-proto'
BUG=chromium-os:5366
TEST=build_packages && build_image
Review URL: http://codereview.chromium.org/3113014
|
| |
|
| |
|
| |
|
|
|
|
| |
'_eroot'" in vartree.get_provide().
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
correctly.
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
enabled by default now, but it may be in the future, depending on feedback
from unknown-features-warn.
|
|
|
|
|
| |
that it shows warnings for unknown FEATURES settings from package.env,
and keep a record of shown warnings in config._unknown_features.
|
|
|
|
| |
and warnings advising use of revdep-rebuild.
|
|
|
|
| |
world_sets file in WorldSelectedSet.
|
|
|
|
|
| |
a default hardcoded set configuration that will be used by the
upcoming 2.1.9 branch.
|
|
|
|
| |
instantiation of vardbapi._plib_registry and vardbapi._linkmap.
|
|
|
|
| |
minimize the diff between branches.
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
portage.util._dyn_libs.PreservedLibsRegistry module.
|
| |
|