From: Brian Dolbec <dolsen@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] another stopper with catalyst, this time /etc/portage problem
Date: Sun, 12 Jan 2014 17:46:46 -0800 [thread overview]
Message-ID: <1389577606.7103.166.camel@big_daddy.dol-sen.ca> (raw)
In-Reply-To: <CACU8XWk=vyBNvjU4e28ydn0UtU3jaLG__pB_1Tq2-2-VjKDTfQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1813 bytes --]
On Sun, 2014-01-12 at 17:04 -0600, lin pro wrote:
> Hi,
> I really try hard to get the idea of what catalyst is all about.
> Yopu are my witness that I have been trying for the past 3 months.
> Not even once I managed to ge to the end of stage1,2,3,4 build process.
> Theere is always some kond of a probelm which is not easy to resolve.
>
> This time it os about this message:
> http://bpaste.net/show/167389/
>
> Namely:
> Configuring /etc/portage...
> ***** cmd(); args = ['/bin/bash', '-c', 'rsync -a
> /var/tmp/catalyst/portage/gentoostudio/
> /var/tmp/catalyst/tmp/default/stage3-core2-2014.1//etc/portage']
> rsync: mkdir "/var/tmp/catalyst/tmp/default/stage3-core2-2014.1//etc/portage"
> failed: No such file or directory (2)
> rsync error: error in file IO (code 11) at main.c(587) [Receiver=3.0.9]
> rsync: connection unexpectedly closed (9 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at
> io.c(605) [sender=3.0.9]
>
> !!! catalyst: cmd() NON-zero return value from: Error copying /etc/portage
>
> --- Exeption running action sequence:setup_confdir
> !!! catalyst: Error encountered during run of target stage3
> Catalyst aborting....
>
>
>
> Previous stages have no problem, building. I didn't change in the
> config anything.
> Here is the outcome of grep on my spec files.
> http://bpaste.net/show/167392/
>
>
> Thank for any help
> Ben
First thank you trying the 3.0 code. But I haven't done any testing
using the portage_confdir option. And it looks like it is broken.
Please use 2.0.16 which I just released today. It is stable catalyst.
I will try to get the problem in 3.0 fixed as soon as possible. Also
what do you have in portage_confdir?
--
Brian Dolbec <dolsen@gentoo.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 620 bytes --]
prev parent reply other threads:[~2014-01-13 1:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-12 23:04 [gentoo-catalyst] another stopper with catalyst, this time /etc/portage problem lin pro
2014-01-13 1:46 ` 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=1389577606.7103.166.camel@big_daddy.dol-sen.ca \
--to=dolsen@gentoo.org \
--cc=gentoo-catalyst@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