From: "Arttu V." <arttuv69@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] python-updater broken
Date: Thu, 23 Oct 2008 03:53:47 +0300 [thread overview]
Message-ID: <fecdbac60810221753v3a8de7f4i6b09f03a7b6f579d@mail.gmail.com> (raw)
In-Reply-To: <loom.20081022T231832-259@post.gmane.org>
On 10/23/08, James <wireless@tampabay.rr.com> wrote:
> Hello,
>
> One of my systems in an old Pentium III (Coppermine).
> python-updater will not complete. It echoes one
> line and then sits indefinately (for a day or more).
...
> Here's what else happens:
>
> # eselect python list
> !!! Error: Can't load module python
>
>
> thoughts and ideas are most welcome.
Some thoughts, not really informed, but trying to lure some better
experts and ideas out:
- Maybe you should run python-updater with several "-v" options? Maybe
it will become more talkative? (See man page and/or the script itself)
- Maybe the disks or filesystems have some problems or bit-rot after
having possibly been powered on 24/7 for a long time? Has there been
power outages? Voluntary fsck time!
- Has something happened to your scanelf? emerge -1 pax-utils might
fix some issues
- I'd guess eselect python complaining like above is probably just
normal, unless you're supposed to have eselect-python package
installed (many systems probably don't and you say your system is sort
of minimal anyway?)
- Does anything unusual appear in /var/log/messages or other logs?
--
Arttu V.
next prev parent reply other threads:[~2008-10-23 0:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 23:23 [gentoo-user] python-updater broken James
2008-10-23 0:53 ` Arttu V. [this message]
2008-10-23 18:29 ` [gentoo-user] " James
2008-10-23 1:06 ` [gentoo-user] " Albert Hopkins
2008-10-24 20:38 ` [gentoo-user] " James
2008-10-24 20:51 ` Paul Hartman
2008-10-25 22:57 ` James
2008-10-24 20:54 ` Albert Hopkins
2008-10-27 18:14 ` 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=fecdbac60810221753v3a8de7f4i6b09f03a7b6f579d@mail.gmail.com \
--to=arttuv69@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