This fixes _dep_check_composite_db to mask packages that aren't the
highest visible match, but only if an update is desirable. This causes
desirable updates to get pulled in for cases like bug #526160. The
included unit test simulates the virtual/pypy update that triggered
the bug.
X-Gentoo-Bug:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
LGTM, Zac. Go ahead and push.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Sure. Go ahead and push, Zac.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 27/10/14 08:33, Zac Medico wrote:
+ if not
self._depgraph._virt_deps_visible( +
new_child,
ignore_use=True): +
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 27/10/14 09:22, Alexander Berntsen wrote:
On 27/10/14 08:33, Zac Medico wrote:
+if not
self._depgraph._virt_deps_visible( +
new_child,
ignore_use=True): +
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I give up. You'll figure it out.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
On 10/27/2014 01:22 AM, Alexander Berntsen wrote:
On 27/10/14 08:33, Zac Medico wrote:
+if not
self._depgraph._virt_deps_visible( +
new_child,
ignore_use=True): +
On 27/10/14 07:05, Zac Medico wrote:
On 10/26/2014 12:31 PM, Michael Palimaka wrote:
On 26/10/14 07:57, Zac Medico wrote:
On 10/25/2014 01:32 PM, Zac Medico wrote:
On 10/25/2014 01:26 PM, Michał Górny wrote:
Dnia 2014-10-25, o godz. 12:53:15
Zac Medico zmed...@gentoo.org napisał(a):
These
On 10/27/2014 06:15 AM, Michael Palimaka wrote:
On 27/10/14 07:05, Zac Medico wrote:
On 10/26/2014 12:31 PM, Michael Palimaka wrote:
I've sent updated patches based on the last feedback. Should I send a
new one with the aliases, and if so, should the portage checks use the
alias or real
Users may not want some symlinks to get clobbered, so protect them
with CONFIG_PROTECT. Changes were required in the dblink.mergeme method
and the new_protect_filename function.
The changes to dblink.mergeme do 3 things:
* Move the bulk of config protection logic from dblink.mergeme to a
new
This fixes a case with --onlydeps were dep_zapdeps would pull in an
avoidable direct circular dependency on an onlydeps node. The logic
changes only apply to --onlydeps, so there's no chance of regressions
for cases when --onlydeps is not enabled.
X-Gentoo-Bug: 524916
X-Gentoo-Bug-URL:
This includes numerous logic adjustments that are needed to support
protected symlinks. The show_diff function now supports arbitrary
file types. For example, a diff between two symlinks looks like this:
-SYM: /foo/bar - baz
+SYM: /foo/bar - blah
X-Gentoo-Bug: 485598
X-Gentoo-Bug-URL:
This includes numerous logic adjustments that are needed to support
protected symlinks. The new diff_mixed function is used for diffs
between arbitrary file types. For example, a diff between two symlinks
looks like this:
-SYM: /foo/bar - baz
+SYM: /foo/bar - blah
X-Gentoo-Bug: 485598
13 matches
Mail list logo
