Re: [gentoo-portage-dev] [PATCH] Manifest._apply_max_mtime: account for removals and renames (bug 567920)

On Tue, 15 Dec 2015 08:50:10 -0800 Zac Medico wrote: > On 12/15/2015 12:43 AM, Michał Górny wrote: > > On Tue, 15 Dec 2015 00:10:03 -0800 > > Zac Medico wrote: > > > >> Include directory mtimes in the max mtime calculation, in order > >> to account for

Re: [gentoo-portage-dev] [PATCH] Manifest._apply_max_mtime: account for removals and renames (bug 567920)

On 12/15/2015 12:43 AM, Michał Górny wrote: > On Tue, 15 Dec 2015 00:10:03 -0800 > Zac Medico wrote: > >> Include directory mtimes in the max mtime calculation, in order >> to account for removals and renames. > > Mildly irrelevant but I think this reached the point when we

Re: [gentoo-portage-dev] [PATCH] Add .git dir to excluded dirs in default PORTAGE_RSYNC_OPTS

On Mon, 14 Dec 2015 08:54:27 -0800 Brian Dolbec wrote: > On Mon, 14 Dec 2015 10:52:50 -0500 > NP-Hardass wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA256 > > > > My apologies for the ambiguity. I didn't realize there was a bug on > >

[gentoo-portage-dev] [PATCH] Manifest._apply_max_mtime: account for removals and renames (bug 567920)

Include directory mtimes in the max mtime calculation, in order to account for removals and renames. Fixes: 6dacd0ed9f6d ("Manifest.write: stable/predictable Manifest mtime for rsync (bug 557962)") X-Gentoo-Bug: 567920 X-Gentoo-Bug-url: https://bugs.gentoo.org/show_bug.cgi?id=567920 ---

[gentoo-portage-dev] [PATCH] depgraph._resolve: consider unresolved @system atoms fatal (bug 568354)

Since @system atoms are presumably chosen by someone who knows what they are doing (usually a gentoo developer), it makes sense to consider resolution failures for these atoms as fatal errors. X-Gentoo-Bug: 568354 X-Gentoo-Bug-url: https://bugs.gentoo.org/show_bug.cgi?id=568354 ---

[gentoo-portage-dev] [PATCH] egencache: add --stable-mtime option

Disable Manifest "stable mtime" behavior by default, and add a corresponding egencache option. Suggested-by: Michał Górny --- bin/egencache | 6 +- man/egencache.1| 3 +++

[gentoo-portage-dev] Re: [PATCH] depgraph._resolve: consider unresolved @system atoms fatal (bug 568354)

On 12/15/2015 12:46 PM, Zac Medico wrote: > Since @system atoms are presumably chosen by someone who knows what > they are doing (usually a gentoo developer), it makes sense to consider > resolution failures for these atoms as fatal errors. > > X-Gentoo-Bug: 568354 > X-Gentoo-Bug-url:

[gentoo-portage-dev] [PATCH] repoman: use metadata.dtd from rsync tree if available (bug 567746)

Search for metadata.dtd in current repository and masters, and if that fails then fetch is as usual. X-Gentoo-Bug: 567746 X-Gentoo-Bug-url: https://bugs.gentoo.org/show_bug.cgi?id=567746 --- pym/repoman/_xml.py | 9 + pym/repoman/checks/ebuilds/pkgmetadata.py | 6