public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Hinnerk van Bruinehsen <h.v.bruinehsen@fu-berlin.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  glibc-2.17 fails and warning: setlocale: LC_ALL error
Date: Tue, 15 Jul 2014 10:40:54 +0200	[thread overview]
Message-ID: <20140715084054.GC10473@TranscendTheRubicon.zedat.fu-berlin.de> (raw)
In-Reply-To: <20140715081526.GB10473@TranscendTheRubicon.zedat.fu-berlin.de>

[-- Attachment #1: Type: text/plain, Size: 498 bytes --]

On a side note:

You can also boot into a chroot, move your /etc and /var directories elsewhere
(e.g. etc_old and var_old) (do the same for other directories where you
yourself made changes), extract a stage 3 tarball on top of your normal
/ directory (overwriting potentially broken stuff), move etc_old and var_old
back to their old locations/names, chroot into it (like during install) and
emerge @system @world -evDNa (to rebuild everything from the known-good start
that the stage3 provides).

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2014-07-15  8:41 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15  1:50 [gentoo-user] glibc-2.17 fails and warning: setlocale: LC_ALL error Dale
2014-07-15  2:02 ` Hinnerk van Bruinehsen
2014-07-15  2:19   ` Dale
2014-07-15  2:35     ` Hinnerk van Bruinehsen
2014-07-15  3:44       ` Dale
2014-07-15  5:33 ` Dale
2014-07-15  7:04   ` Hinnerk van Bruinehsen
2014-07-15  7:40     ` Dale
2014-07-15  8:15       ` Hinnerk van Bruinehsen
2014-07-15  8:40         ` Hinnerk van Bruinehsen [this message]
2014-07-15  9:25           ` Dale
2014-07-15 18:52             ` Douglas J Hunley
2014-07-15 19:18               ` Dale
2014-07-16  7:32             ` Dale
2014-07-16  7:46               ` Helmut Jarausch
2014-07-16  8:43                 ` Dale
2014-07-16  9:19                   ` Dale
2014-07-16 10:33                     ` J. Roeleveld
2014-07-16 15:44                       ` Dark Templar
2014-07-16 17:26                         ` Dale
2014-07-16 21:09                           ` Mick
2014-07-16 21:34                             ` Dale
2014-07-17  4:52                           ` J. Roeleveld
2014-07-17  7:19                             ` J. Roeleveld
2014-07-17  9:03                               ` Dale
2014-07-17  9:19                                 ` J. Roeleveld
2014-07-17 10:45                                   ` J. Roeleveld
2014-07-18  9:18                                     ` Dale
2014-07-18  9:38                                       ` J. Roeleveld
2014-07-18 12:44                                       ` Jc García
2014-07-17  9:20                                 ` Peter Humphrey
2014-07-17 13:24                                   ` Peter Humphrey
2014-07-16 17:21                       ` Dale
2014-07-17  0:39                         ` [gentoo-user] " walt
2014-07-17  1:01                           ` Dale
2014-07-17 21:41 ` [gentoo-user] SNIP " Dale
2014-07-17 22:08   ` Mick
2014-07-18  3:55     ` Dale
2014-07-18  4:32       ` Jc García
2014-07-17 22:48   ` Peter Humphrey
2014-07-18  5:54     ` Mick
2014-07-18  8:12       ` Peter Humphrey

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=20140715084054.GC10473@TranscendTheRubicon.zedat.fu-berlin.de \
    --to=h.v.bruinehsen@fu-berlin.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