From: Daniel Goller <morfic@gentoo.org>
To: Norberto Bensa <norberto+gentoo-dev@bensa.ath.cx>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: problem with cascade profiles
Date: Mon, 06 Sep 2004 03:29:25 -0500 [thread overview]
Message-ID: <413C1FE5.2040200@gentoo.org> (raw)
In-Reply-To: <200409052258.48457.norberto+gentoo-dev@bensa.ath.cx>
ok, seems there is a bug in 2.0.50 parsing cascaded profiles, the
make.defaults files are adjusted to this, thanks to jstubbs
please sync 35 mins after reading this mail and test with your portage
2.0.50-r10
thank you
Daniel
Norberto Bensa wrote:
>Jason Stubbs wrote:
>
>
>>portage-2.0.50_pre20 no longer does fetching as root. Make sure that
>>the /usr/portage directory also has write access by the portage group and
>>it should work.
>>
>>
>
>Ermm.... This is a RO-NFS shared distfiles and the file was already fetched.
>
>
>
>>>[Why did I installed a pre version of portage ... ~:( ]
>>>
>>>
>>There may be a couple of hiccups(sp?) but it should be smooth running after
>>working them out.
>>
>>
>
>Thanks. I've reverted to 2.0.50-r10 until those hiccups are fixed ;)
>
>Regards,
>Norberto
>
>--
>gentoo-dev@gentoo.org mailing list
>
>
>
>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-09-06 8:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-05 16:42 [gentoo-dev] problem with cascade profiles Norberto Bensa
2004-09-05 17:36 ` Andrew Gaffney
2004-09-05 17:47 ` Norberto Bensa
2004-09-05 17:54 ` [gentoo-dev] " Sebastian Bergmann
2004-09-05 18:15 ` Norberto Bensa
2004-09-05 19:10 ` Norberto Bensa
2004-09-05 23:23 ` Jason Stubbs
2004-09-06 1:58 ` Norberto Bensa
2004-09-06 7:18 ` Daniel Goller
2004-09-06 8:29 ` Daniel Goller [this message]
2004-09-06 9:02 ` [gentoo-dev] read only distdir and fully fetched files w/ portage 2.0.51_pre20 Brian Harring
2004-09-06 14:44 ` Norberto Bensa
2004-09-06 4:56 ` [gentoo-dev] Re: problem with cascade profiles Sebastian Bergmann
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=413C1FE5.2040200@gentoo.org \
--to=morfic@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=norberto+gentoo-dev@bensa.ath.cx \
/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