From: »Q« <boxcars@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: unmerge boo_boo
Date: Fri, 31 Oct 2008 00:38:44 -0500 [thread overview]
Message-ID: <20081031003844.2de370ba@prezmyra.remarqs.net> (raw)
In-Reply-To: loom.20081031T050157-424@post.gmane.org
In <loom.20081031T050157-424@post.gmane.org>,
James <wireless@tampabay.rr.com> wrote:
> Well,
>
> I've done it now, being in too big of a hurry.
>
> After an emerge --sync, and the blocking packages, I
> got in a hurry, did not think and ran:
>
> emerge --unmerge sys-libs/ss sys-libs/com_err
> sys-fs/e2fsprogs sys-libs/e2fsprogs-libs
>
>
> So now I cannot emerge anything to fix this.
>
> Here I tried (re) emerge wget:
>
> Downloading
> 'ftp://rm.mirror.garr.it/mirrors/gnuftp/gnu/wget/wget-1.11.1.tar.bz2'
> wget: error while loading shared libraries: libcom_err.so.2: cannot
> open shared object file: No such file or directory
>
>
> Can I just copy some file over from another amd64 machine?
>
> If so, which ones exactly?
>
>
> If not, any other ideas to fix this?
It's com_err you need to make wget work again. Using 'emerge -fpv
com_err' should get you a list of URL(s) for the file(s) needed, then
you can use a web browser to download them and put them in your
distfiles/ directory. (Or if you've got them on the other machine,
just copy them from there.)
After you have com_err installed, use 'emerge -fuDN' to to get
everything you need to upgrade before you unmerge the blockers again.
--
»Q«
Kleeneness is next to Gödelness.
next prev parent reply other threads:[~2008-10-31 5:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 5:07 [gentoo-user] unmerge boo_boo James
2008-10-31 5:38 ` »Q« [this message]
2008-10-31 5:47 ` [gentoo-user] " Paul Hartman
2008-10-31 6:32 ` James
2008-10-31 5:39 ` [gentoo-user] " Paul Hartman
2008-10-31 6:48 ` András Csányi
2008-10-31 6:59 ` Dirk Heinrichs
2008-10-31 17:53 ` Joshua Murphy
2008-10-31 18:00 ` Markos Chandras
2008-10-31 21:17 ` [gentoo-user] FIXED: " James
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=20081031003844.2de370ba@prezmyra.remarqs.net \
--to=boxcars@gmx.net \
--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