From: Harry Putnam <reader@newsguy.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: stumpwm users .. need help with failed emerge
Date: Sun, 16 Nov 2008 14:32:56 -0600 [thread overview]
Message-ID: <87bpwf5s3r.fsf@newsguy.com> (raw)
In-Reply-To: 87iqqo8020.fsf@galiza_ceive.gnu-linux.org
galiza.ceive@gmail.com (Johám-Luís Miguéns Vila) writes:
> Harry Putnam <reader@newsguy.com> writes:
>
>> Attempting to install stumpwm-cvs I run into an emerge failure with on
>> of the dependencies; dev-lisp/cmucl.
>>
>> Below is a snippet from the end of the emerge of
>> dev-lisp/cmucl-l-19d_p2. Can anyone see what might be the problem?
>>
>> [...]
>
> Hi.
>
> First of all, It's not encouraged to use stumpwm-cvs ebuild as it's
> obsolete [1].
Its probably another bug that that fact is not included in the portage
desc statement.
> And regarding cmucl build error, there's a bug report on b.g.o. with a
> patch that seems to fix it [2].
I've downloaded that but not used it yet.
But I seem to recall that when you change an ebuild, you can't just
install it then ... but have to create a new ebuild or some such?
>> Emacs, n.:
>> A slow-moving parody of a text editor.
>> - This message may be digitally signed: GPG KeyID:0x9D2FD6C8 || FNMT SSL
>> cert
>>
>
> Damn!
> Of course, signature statements are not shared by poster... :(
Gack, you were almost caught in print disparaging the `One True Editor'
next prev parent reply other threads:[~2008-11-16 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 16:35 [gentoo-user] stumpwm users .. need help with failed emerge Harry Putnam
2008-11-16 9:58 ` Johám-Luís Miguéns Vila
2008-11-16 10:10 ` Johám-Luís Miguéns Vila
2008-11-16 20:32 ` Harry Putnam [this message]
2008-11-16 22:19 ` [gentoo-user] " Johám-Luís Miguéns Vila
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=87bpwf5s3r.fsf@newsguy.com \
--to=reader@newsguy.com \
--cc=gentoo-user@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