Re: [gentoo-user] [SOLVED] emerge --resume

2006-12-26 Thread Bo Ørsted Andresen
On Sunday 24 December 2006 22:03, Daniel Iliev wrote:
 Etaoin Shrdlu wrote:
  On Sunday 24 December 2006 19:59, Daniel Iliev wrote:
  Well, I tried emerge mc and I hit ctrl-c in the middle of the
  process. Then emerge --resume emerged mc. Now emerge --resume
  gives the same strange message again. ;-)
 
  emerge --resume reads the list of packages to emerge from a binary file
  located at /var/cache/edb/mtimedb. In your case, that file is probably
  stale and is likely to contain package names or versions which are not
  available anymore (I don't know why it's there even after a succesful
  emerge though). I think that deleting or renaming it will cause emerge
  to believe that there's nothing to resume.

 Thank you!

 Removing that file did the trick.

The mtimedb contains a lot more than the resume list. The following command 
will show you it's contents:

# python -c 'import portage;print portage.mtimedb'

Removing it seems rather pointless IMO. The resume list gets overwritten if 
you emerge a list of packages rather than just one package. Either way it's 
contents is irrelevant when you don't need to resume a list of packages.

-- 
Bo Andresen


pgpN9pyF54lNl.pgp
Description: PGP signature


Re: [gentoo-user] [SOLVED] emerge --resume

2006-12-26 Thread Daniel Iliev
Bo Ørsted Andresen wrote:
 On Sunday 24 December 2006 22:03, Daniel Iliev wrote:
   
 Etaoin Shrdlu wrote:
 
 On Sunday 24 December 2006 19:59, Daniel Iliev wrote:
   
 Well, I tried emerge mc and I hit ctrl-c in the middle of the
 process. Then emerge --resume emerged mc. Now emerge --resume
 gives the same strange message again. ;-)
 
 emerge --resume reads the list of packages to emerge from a binary file
 located at /var/cache/edb/mtimedb. In your case, that file is probably
 stale and is likely to contain package names or versions which are not
 available anymore (I don't know why it's there even after a succesful
 emerge though). I think that deleting or renaming it will cause emerge
 to believe that there's nothing to resume.
   
 Thank you!

 Removing that file did the trick.
 

 The mtimedb contains a lot more than the resume list. The following command 
 will show you it's contents:

 # python -c 'import portage;print portage.mtimedb'

 Removing it seems rather pointless IMO. The resume list gets overwritten if 
 you emerge a list of packages rather than just one package. Either way it's 
 contents is irrelevant when you don't need to resume a list of packages.

   


Bo, as I said, I tried with only one package. So, you may be right about
the list, but for sure removing /var/cache/edb/mtimedb fixed the
problem: emerge --resume now gives It seems we have nothing to
resume and the strange message disappeared. So, I'm happy. :)

I just hope I haven't erased some important info, but I doubt that - if
something is in the cache it should be possible to be regenerated.
 ;-)))

-- 
Best regards,
Daniel


-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] [SOLVED] emerge --resume

2006-12-24 Thread Daniel Iliev
Etaoin Shrdlu wrote:
 On Sunday 24 December 2006 19:59, Daniel Iliev wrote:

   
 Well, I tried emerge mc and I hit ctrl-c in the middle of the
 process. Then emerge --resume emerged mc. Now emerge --resume
 gives the same strange message again. ;-)
 

 emerge --resume reads the list of packages to emerge from a binary file 
 located at /var/cache/edb/mtimedb. In your case, that file is probably 
 stale and is likely to contain package names or versions which are not 
 available anymore (I don't know why it's there even after a succesful 
 emerge though). I think that deleting or renaming it will cause emerge 
 to believe that there's nothing to resume.
   

Thank you!

Removing that file did the trick.

-- 
Best regards,
Daniel


-- 
gentoo-user@gentoo.org mailing list