From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: Track down a failure involving shr
Date: Sat, 20 Dec 2014 18:19:55 -0500 [thread overview]
Message-ID: <873889gb8k.fsf@reader.local.lan> (raw)
In-Reply-To: <87oaqyc4sh.fsf@cougar.home.aneadesign.com>
Clemens Schüller <cs.mlists+gnus@mailbox.org> writes:
> Hello!
>
> On 20. Dez. 2014 at 23:45 Steinar Bang wrote:
>>>>>>> Harry Putnam <reader@newsguy.com>:
>
>
>>> Setup: Gentoo linux (new install)
>>> emacs-25
>>> gentoo pkg emacs-vcs which installs from the bzr trunk
>>
>> I thought emacs had moved from bzr to git?
>
>
> Thats true. And in case of gentoo there exists a new ebuild file for
> emacs-vcs.
>
> Please make a emerge --sync and then a
> emerge -av "=app-editors/emacs-vcs-25.0.9999-r1"
> to install the git (and not the bzr) repo.
I was wrong about it being bzr. It was git.
OK, but I'm getting some fluff from emerge I don't really understand.
------- ------- ---=--- ------- -------
[ebuild U *] app-editors/emacs-vcs-25.0.9999-r1:25
[25.0.50_pre20141130:25] USE="X Xaw3d athena gif gpm gtk gtk3
imagemagick inotify jpeg png svg tiff xpm zlib -acl -alsa (-aqua)
-dbus -games -gconf -gfile -gnutls -gsettings -gzip-el -hesiod
-kerberos -libxml2 -livecd -m17n-lib -motif -pax_kernel (-selinux)
-sound -source -toolkit-scroll-bars -wide-int -xft" 0 KiB
Total: 1 package (1 upgrade), Size of downloads: 0 KiB
The following keyword changes are necessary to proceed: (see
"package.accept_keywords" in the portage(5) man page for more
details) # required by =app-editors/emacs-vcs-25.0.9999-r1 (argument)
=app-editors/emacs-vcs-25.0.9999-r1 **
/
NOTE: The --autounmask-keep-masks option will prevent emerge
from creating package.unmask or ** keyword changes.
------- ------- ---=--- ------- -------
I'm not really sure what that means, but I guess it means to lierally
create the `packag.accept_keywords' file containing:
=app-editors/emacs-vcs-25.0.9999-r1 **
At any rate, that is what I did and it seems to have smoothed things out
Now I need to get some of those USE flags set differently.
Any advice what to do with the libxml2?
It was turned off on the last go around so is it posible it needs to
be ON to make that related error I posted go away?
Any way, I will now close all emacs including this one and fiddle with
thing until I can see a clean install
More later...
next prev parent reply other threads:[~2014-12-20 23:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-20 21:16 Harry Putnam
2014-12-20 21:57 ` Adam Sjøgren
2014-12-20 22:45 ` Steinar Bang
2014-12-20 22:52 ` Clemens Schüller
2014-12-20 23:19 ` Harry Putnam [this message]
2014-12-21 6:35 ` Adam Sjøgren
2014-12-21 12:27 ` Clemens Schüller
2014-12-21 11:51 ` Harry Putnam
2014-12-20 22:54 ` Harry Putnam
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=873889gb8k.fsf@reader.local.lan \
--to=reader@newsguy.com \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).