From: meino.cramer@gmx.de
To: Gentoo <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Problems after update
Date: Tue, 28 Oct 2014 00:13:25 +0100 [thread overview]
Message-ID: <20141027231325.GB3829@solfire> (raw)
Hi,
I updated via eix/emerge, which does not expose any problems.
After that the sudoers of sudo needs to be updated. For that
tasks I use cf-update.
With cfg-update -u it spits out (and do not stop until CTRL-C:
<< Stage1 >> 0 files in queue for automatic replacing, skipping...
<< Stage2 >> 0 files in queue for automatic 3-way merging, skipping...
<< Stage3 >> vimdiff does not support 3-way merging, skipping...
<< Stage4 >> 1 files in queue for manual 2-way merging, starting...
(1/1) /etc/sudoers *Modified File
* YOU ARE ABOUT TO UPDATE A MODIFIED FILE WHICH PROBABLY CONTAINS
* CUSTOM SETTINGS. YOU ARE FORCED TO UPDATE MANUALLY!
Press [y] - to merge the current file and the ._cfg0000_* file with vimdiff
Press [s] - to skip this update (to investigate first, and try again later)
Press [1] - to use the ._cfg0000_* file
Press [2] - to remove the ._cfg0000_* file
Press [q] - to quit cfg-update immediately
Merge manually with file : /etc/._cfg0000_sudoers ? [y|s|1|2|q] bash: readkey: command not found
* invalid key... try again: bash: readkey: command not found
* invalid key... try again: bash: readkey: command not found
* invalid key... try again: bash: readkey: command not found
* invalid key... try again: bash: readkey: command not found
* invalid key... try again: bash: readkey: command not found
* invalid key... try again: bash: readkey: command not found
* invalid key... try again: bash: readkey: command not found
* invalid key... try again: bash: readkey: command not found
* invalid key... try again: bash: readkey: command not found
and so forth.
Before the update it works fine. This problem remains after reboot.
What went wrong here?
Best regards,
mcc
reply other threads:[~2014-10-27 23:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20141027231325.GB3829@solfire \
--to=meino.cramer@gmx.de \
--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