public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rudmer van Dijk <rudmer.van.dijk@casema.nl>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Damaged file in portage cache
Date: Thu, 14 Jun 2007 11:00:47 +0200	[thread overview]
Message-ID: <200706141100.47328.rudmer.van.dijk@casema.nl> (raw)
In-Reply-To: <eaa71e3e0706140142u61fbdfa7i8b150fb269cfe6aa@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2195 bytes --]

On Thursday 14 June 2007, Jean-Baptiste Mestelan wrote:
> Many thanks for your kind answers.
>
> I have tried to emerge --metadata, too, and the result is just the same.
>
> localhost ~ # emerge --metadata
>
> >>> Updating Portage cache:      Traceback (most recent call last):
>
>   File "/usr/bin/emerge", line 5530, in ?
>     retval = emerge_main()
>   File "/usr/bin/emerge", line 5489, in emerge_main
>     action_metadata(settings, portdb, myopts)
>   File "/usr/bin/emerge", line 4300, in action_metadata
>     eclass_cache=ec, verbose_instance=noise_maker)
>   File "/usr/lib/portage/pym/cache/util.py", line 22, in mirror_cache
>     dead_nodes = dict.fromkeys(trg_cache.keys())
>   File "/usr/lib/portage/pym/cache/template.py", line 95, in keys
>     return tuple(self.iterkeys())
>   File "/usr/lib/portage/pym/cache/flat_hash.py", line 122, in iterkeys
>     st = os.lstat(p)
> OSError: [Errno 2] No such file or directory:
> '/var/cache/edb/dep/usr/portage/net-misc/vmpsd-1.3-r\x12'
> 
> I have manually deleted a lot of files from  /var/cache/edb/dep, but
> the offending ones can  neither be removed nor renamed. (Was I all
> right, in manually butchering /var/cache/edb/dep ?) The fact that the
> remaining files contain strange characters is puzzling, indeed.
> 
> I thought some wise list member might correct me in the way I use
> portage, but I am getting to think that the problem is with the file
> system, more than with portage ?

hmm, then it really looks like your filesystem is screwed...

what filesystem are you using?
and have you tried to do a fsck on it?


> I'll report a bug (Gentoo bug ?) , if this is more appropriate.

I don't think it is useful, the problem is clearly not in portage but on your 
filesystem. on the other hand if your filesystem is damaged through use of 
portage...


> Here is my emerge --info, anyhow :
<snip>
> gentoo-user@gentoo.org mailing list
>
> éí¢‹¬z¸\x1ežÚ(¢¸&j)bž	b²

hmm, this is not suppost to be there...


you really should be backing up your valuable data and checking your 
haddrive/filesystem for errors.


	Rudmer
--
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-06-14  9:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-14  0:49 [gentoo-user] Damaged file in portage cache Jean-Baptiste Mestelan
2007-06-14  4:59 ` Philip Webb
2007-06-14  7:19   ` Kent Fredric
2007-06-14  5:59 ` Rudmer van Dijk
2007-06-14  8:42   ` Jean-Baptiste Mestelan
2007-06-14  9:00     ` Rudmer van Dijk [this message]
2007-06-14 12:27       ` Jean-Baptiste Mestelan
2007-06-14 13:28         ` Rudmer van Dijk
2007-06-14 13:10     ` Alex Schuster
2007-06-14 13:59       ` Jean-Baptiste Mestelan

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=200706141100.47328.rudmer.van.dijk@casema.nl \
    --to=rudmer.van.dijk@casema.nl \
    --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