From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH] emerge: check for writable /var/db/pkg (490732)
Date: Tue, 18 Nov 2014 08:42:13 -0800 [thread overview]
Message-ID: <546B76E5.3010902@gentoo.org> (raw)
In-Reply-To: <20141118025743.45199dce.dolsen@gentoo.org>
On 11/18/2014 02:57 AM, Brian Dolbec wrote:
> On Tue, 18 Nov 2014 01:19:01 -0800
> Zac Medico <zmedico@gentoo.org> wrote:
>
>> If there are packages to be merged or unmerge, then bail out early if
>> /var/db/pkg is not writable.
>>
> ...
>
>> diff --git a/pym/portage/dbapi/vartree.py
>> b/pym/portage/dbapi/vartree.py index 0fd1bd9..64b0ff6 100644
>> --- a/pym/portage/dbapi/vartree.py
>> +++ b/pym/portage/dbapi/vartree.py
>> @@ -33,6 +33,7 @@ portage.proxy.lazyimport.lazyimport(globals(),
>> 'portage.util.env_update:env_update',
>> 'portage.util.listdir:dircache,listdir',
>> 'portage.util.movefile:movefile',
>> + 'portage.util.path:first_existing',
>> 'portage.util.writeable_check:get_ro_checker',
>
> ^^^^^^^^^^^^^^^^^^^^^^^^
> That's what this was suppose to fix I thought
The writeable_check module is designed to check write access for the
files to be merged, and it's only used just prior to merge, when the
list of files is known.
The vardbapi.writable check that I have implemented provides a much
earlier warning, before anything has even been built.
--
Thanks,
Zac
next prev parent reply other threads:[~2014-11-18 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 9:19 [gentoo-portage-dev] [PATCH] emerge: check for writable /var/db/pkg (490732) Zac Medico
2014-11-18 10:57 ` Brian Dolbec
2014-11-18 16:42 ` Zac Medico [this message]
2014-11-19 4:48 ` [gentoo-portage-dev] [PATCH v2] " Zac Medico
2014-11-19 15:49 ` [gentoo-portage-dev] [PATCH v3] " Zac Medico
2014-11-19 19:12 ` 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=546B76E5.3010902@gentoo.org \
--to=zmedico@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