public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] What is the correct version of ncurses on ~amd64 now?
Date: Mon, 31 Aug 2015 14:13:05 -0700	[thread overview]
Message-ID: <20150831141305.0c0c6ee5@a6> (raw)

I ask this strange question because this (badly broken) machine once
again flipped between 6.0 and 6.0-r1 after rsyncing this morning.

First, it emerged 6.0, which turned out to be almost catastrophic
because the qmerge phase of the emerge failed (although it claimed
success afterwards) and deleted the entire /usr/share/terminfo
subdirectory.  That was fun, but I won't bore you with the details.
(The ncurses-6.0 files in /lib64 are dated August 28, BTW.)

Right now emerge tries to install ncurses-6.0-r1 but the 32-bit part of
the build fails because emerge never ran make in the work/cross/progs
directory, and so the 32-bit tools didn't get compiled.

I hacked around this by running make in that directory manually, which
allowed the ebuild install and ebuild package phases to succeed.

Now I have an ncurses-6.0-r1 binary package available but I'm too scared
to install it because I might need to kill myself afterwards :/

Any suggestions before I take the plunge?  Is ncurses-6.0-r1 the right
version as of today, Aug 31?

Thanks.




             reply	other threads:[~2015-08-31 21:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31 21:13 walt [this message]
2015-08-31 22:13 ` [gentoo-user] What is the correct version of ncurses on ~amd64 now? Alan McKinnon
2015-08-31 23:30   ` [gentoo-user] " walt
2015-09-01  0:33   ` [gentoo-user] " Fernando Rodriguez
2015-09-01  2:20     ` [gentoo-user] " walt
2015-09-01  2:55       ` Fernando Rodriguez
2015-09-01  3:24         ` Fernando Rodriguez
2015-09-01 12:34     ` [gentoo-user] " Todd Goodman

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=20150831141305.0c0c6ee5@a6 \
    --to=w41ter@gmail.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