public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH] NewsManager.getUnreadItems: handle EROFS (490732)
Date: Sun, 9 Nov 2014 23:51:56 -0800	[thread overview]
Message-ID: <20141109235156.08355576.dolsen@gentoo.org> (raw)
In-Reply-To: <1415601050-29668-1-git-send-email-zmedico@gentoo.org>

On Sun,  9 Nov 2014 22:30:50 -0800
Zac Medico <zmedico@gentoo.org> wrote:

> When getUnreadItems tries to lock the news.unread file, it's safe to
> ignore EROFS. This is handled with a ReadOnlyFileSystem exception
> raised from the portage.locks.lockfile function.
> 
> X-Gentoo-Bug: 490732
> X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=490732
> ---
>  pym/portage/exception.py | 1 +
>  pym/portage/locks.py     | 7 ++++++-
>  pym/portage/news.py      | 7 ++++---
>  3 files changed, 11 insertions(+), 4 deletions(-)
> 
>...

>  		unread_lock = None
>  		try:
>  			unread_lock = lockfile(unread_filename,
> wantnewlockfile=1)
> -		except (InvalidLocation, OperationNotPermitted,
> PermissionDenied):
> +		except (InvalidLocation, OperationNotPermitted,
> PermissionDenied.
   typo...........^

 :)

> +			ReadOnlyFileSystem):
>  			pass
>  		try:
>  			try:



-- 
Brian Dolbec <dolsen>



  reply	other threads:[~2014-11-10  7:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10  6:30 [gentoo-portage-dev] [PATCH] NewsManager.getUnreadItems: handle EROFS (490732) Zac Medico
2014-11-10  7:51 ` Brian Dolbec [this message]
2014-11-10  8:14   ` Zac Medico
2014-11-15  4:45 ` [gentoo-portage-dev] [PATCH v2] " Zac Medico
2014-11-17 22:47   ` Brian Dolbec

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=20141109235156.08355576.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