From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] Can't create livecd-stage1: error during configuration of gaim
Date: Sun, 07 May 2006 10:54:07 -0400 [thread overview]
Message-ID: <1147013647.25179.7.camel@vertigo.twi-31o2.org> (raw)
In-Reply-To: <445E054C.7040800@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
On Sun, 2006-05-07 at 16:33 +0200, Alex wrote:
> > First, an error emerging gaim is not catalyst's fault. It's up to you to
> > determine why it won't build and fix it.
> Yes, _that_ isn't catalyst's fault, but catalyst's fault is maybe the
> other one.
>
> How you can see in the error-message, catalyst isn't able to unmount dev.
>
> > Second, you should really be using catalyst-2.0_pre45 as 1.x is no
> > longer supported.
> Oh, I didn't know. So it seems I've to try it with the unstable version.
Not unstable... testing. Gentoo doesn't have anything "unstable" in the
tree that isn't under package.mask.
It is definitely stable. More so than the "stable" version. The only
reason it is not marked stable is I wish to wait until 2.0 final is
released before marking it stable. I am currently waiting on a couple
fixes to go in so I can roll 2.0_rc46, then I plan on rebadging rc46 as
2.0 final, if no new bugs are found.
--
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-05-07 14:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-06 15:22 [gentoo-catalyst] Can't create livecd-stage1: error during configuration of gaim Alex
2006-05-06 20:37 ` Andrew Gaffney
2006-05-07 14:33 ` Alex
2006-05-07 14:54 ` Chris Gianelloni [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=1147013647.25179.7.camel@vertigo.twi-31o2.org \
--to=wolf31o2@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