From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH] Manifest._apply_max_mtime: handle EPERM from utime (bug 582388)
Date: Sun, 8 May 2016 16:15:01 -0700 [thread overview]
Message-ID: <20160508161501.23145ecb.dolsen@gentoo.org> (raw)
In-Reply-To: <1462744656-16090-1-git-send-email-zmedico@gentoo.org>
On Sun, 8 May 2016 14:57:36 -0700
Zac Medico <zmedico@gentoo.org> wrote:
> Only warn if utime fails due to the Manifest parent directory
> being owned by a different user, since it's not a problem
> unless the repo is being prepared for distribution via rsync.
>
> X-Gentoo-bug: 582388
> X-Gentoo-bug-url: https://bugs.gentoo.org/show_bug.cgi?id=582388
> ---
> pym/portage/manifest.py | 17 ++++++++++++++---
> 1 file changed, 14 insertions(+), 3 deletions(-)
>
> diff --git a/pym/portage/manifest.py b/pym/portage/manifest.py
> index f696f84..fe4166c 100644
> --- a/pym/portage/manifest.py
> +++ b/pym/portage/manifest.py
> @@ -1,10 +1,11 @@
> -# Copyright 1999-2014 Gentoo Foundation
> +# Copyright 1999-2016 Gentoo Foundation
> # Distributed under the terms of the GNU General Public License v2
>
> from __future__ import unicode_literals
>
> import errno
> import io
> +import logging
> import re
> import stat
> import sys
> @@ -15,7 +16,7 @@ portage.proxy.lazyimport.lazyimport(globals(),
> 'portage.checksum:hashfunc_map,perform_multiple_checksums,'
> + \ 'verify_all,_apply_hash_filter,_filter_unaccelarated_hashes',
> 'portage.repository.config:_find_invalid_path_char',
> - 'portage.util:write_atomic',
> + 'portage.util:write_atomic,writemsg_level',
> )
>
> from portage import os
> @@ -387,7 +388,17 @@ class Manifest(object):
>
> if max_mtime is not None:
> for path in preserved_stats:
> - os.utime(path, (max_mtime,
> max_mtime))
> + try:
> + os.utime(path, (max_mtime,
> max_mtime))
> + except OSError as e:
> + # Even though we have write
> permission, utime fails
> + # with EPERM if path is
> owned by a different user.
> + # Only warn in this case,
> since it's not a problem
> + # unless this repo is being
> prepared for distribution
> + # via rsync.
> + writemsg_level('!!!
> utime(\'%s\', (%s, %s)): %s\n' %
> + (path, max_mtime,
> max_mtime, e),
> +
> level=logging.WARNING, noiselevel=-1)
> def sign(self):
> """ Sign the Manifest """
Looks fine :)
--
Brian Dolbec <dolsen>
prev parent reply other threads:[~2016-05-08 23:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-08 21:57 [gentoo-portage-dev] [PATCH] Manifest._apply_max_mtime: handle EPERM from utime (bug 582388) Zac Medico
2016-05-08 23:15 ` Brian Dolbec [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160508161501.23145ecb.dolsen@gentoo.org \
--to=dolsen@gentoo.org \
--cc=gentoo-portage-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox