| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Display upstream maintainers and bugtrackers along with Gentoo
maintainers when emerging a package.
|
| |
|
|
|
|
| |
This will fix bug #289486.
|
|
|
|
| |
This will fix bug #348864.
|
| |
|
| |
|
| |
|
|
|
|
| |
This will fix bug #349757.
|
| |
|
|
|
|
| |
This will fix bug #53607.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Broken since refactoring in commit
48c8cec7c079cb07a4f421a36cdc46a7fdbc7811.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Thanks to Christian Ruppert <idl0r@gentoo.org> for the suggestion.
|
| |
|
|
|
|
|
|
|
|
|
| |
Since commit 75d3130fc8293fff68389b8fed44b8d47a0abe80, doebuild()
for the 'setup' phase triggers the actionmap_deps code path in order
to call the 'pretend' phase as a dependency. This path previously
assumed a portdbapi instance, which may not hold for some api consumers
such as entropy. Therefore, fix the code path to work with other dbapi
types.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This should succeed even in some cases in which a normal write might
fail due to file permission settings on some operating systems such as
HP-UX.
|
|
|
|
|
| |
It should be faster to use the bash builtin, and also allows us to
avoid issues with touch breakage (like in bug #348640).
|
| |
|
| |
|
|
|
|
|
|
|
| |
The depgraph sometimes uses paren_enclose to temporarily convert parts
of use_reduce output to a plain string. In these cases, we want to
preserve atom USE conditionals, since these sometimes make a difference
for IUSE checks during package matching (as in bug #348389).
|
|
|
|
|
| |
In python-2.x, KeyError.__str__ produces unicode literals that we
don't want users to see.
|
|
|
|
| |
This should have been done as part of bug #338190.
|
|
|
|
|
|
|
| |
Use local import since https typically isn't needed, and this way we
can usually avoid triggering the global scope http.client ImportError
handler (like during stage1 -> stage2 builds where USE=ssl is disabled
for python).
|
|
|
|
|
|
|
|
| |
This fixes a broken assumption about USE dep matching behavior,
since commit 766988aa56bb1bbd2796f96946e62ed78cdf259 introduced
stricter IUSE matching by using Atom.unevaluated_atom for IUSE
checks (thus changing behavior in cases where conditional USE
dependencies disappear upon evaluation).
|
|
|
|
|
| |
Atom.unevaluated_atom.use is used for IUSE checks when matching
packages, so it must not propagate to Atom.without_use.
|
|
|
|
| |
A test case is included, which triggers the previously broken case.
|
|
|
|
|
| |
Fix bug #348790, make sure that CONTENTS entries keep their EPREFIX, by
using ROOT, instead of EROOT.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will fix the following error, reported in bug #339670:
_ebuild_exit
_post_phase_userpriv_perms(settings)
File "/usr/lib64/portage/pym/portage/package/ebuild/doebuild.py", line 1207,
in _post_phase_userpriv_perms
filemode=0o60, filemask=0)
File "/usr/lib64/portage/pym/portage/util/__init__.py", line 1018, in
apply_recursive_permissions
uid=uid, gid=gid, mode=filemode, mask=filemask)
File "/usr/lib64/portage/pym/portage/util/__init__.py", line 1043, in
apply_secpass_permissions
stat_cached = os.stat(filename)
File "/usr/lib64/portage/pym/portage/__init__.py", line 226, in __call__
rval = self._func(*wrapped_args, **wrapped_kwargs)
OSError: [Errno 40] Too many levels of symbolic links:
'/var/tmp/portage/dev-vcs/mercurial-1.7.2/temp/tests-2.7/child0/test-mq-symlinks.t/linka'
|
|
|
|
|
| |
We need to break out of the loop after the first match here, since
the first package comes from the highest priority repo.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
The previous code created hardlinks rather aggressively, which was
helpful as a workaround for lack of hardlinks in tarballs created
by quickpkg due to bug #185305. Since bug #338509, quickpkg tarballs
preserve hardlinks, so there's no need for aggressive hardlink
creation. Therefore, simply preserve existing hardlinks during merge,
by comparison of st_dev and st_ino from the source files.
|
|
|
|
|
| |
For some reason, bug #185305 no longer seems to be an issue, and the
fix/workaround seems to cause bug 338509.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|