[gentoo-user] Emerge --resume

[gentoo-user] Emerge --resume

[AJ Spagnoletti]

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

I am in the process of upgrading GCC and currently am doing emerge -e world
I have about 70 packages left to be rebuilt and I got curious. Will emerge
--resume work and pick up with the 70 or so packages left to be rebuilt if
the system is shutdown or will emerge --resume only pick up an emerge if the
system is not shutdown? Thanks in advance for replies.

A.J.

[-- Attachment #2: Type: text/html, Size: 384 bytes --]

Re: [gentoo-user] Emerge --resume

[Michael Sullivan]

On Wed, 2005-12-07 at 20:56 -0500, AJ Spagnoletti wrote:
> I am in the process of upgrading GCC and currently am doing emerge -e
> world I have about 70 packages left to be rebuilt and I got curious.
> Will emerge --resume work and pick up with the 70 or so packages left
> to be rebuilt if the system is shutdown or will emerge --resume only
> pick up an emerge if the system is not shutdown? Thanks in advance for
> replies.
> 
> A.J.

Earlier this afternoon I had to restart a machine that was doing just
what you described.  I was able to emerge --resume successfully.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Emerge --resume

[Brett I. Holcomb]

As long as you don't do another merge between the first one and the 
resumed one it should remember.

On Wed, 7 Dec 2005, Michael Sullivan wrote:

> On Wed, 2005-12-07 at 20:56 -0500, AJ Spagnoletti wrote:
>> I am in the process of upgrading GCC and currently am doing emerge -e
>> world I have about 70 packages left to be rebuilt and I got curious.
>> Will emerge --resume work and pick up with the 70 or so packages left
>> to be rebuilt if the system is shutdown or will emerge --resume only
>> pick up an emerge if the system is not shutdown? Thanks in advance for
>> replies.
>>
>> A.J.
>
> Earlier this afternoon I had to restart a machine that was doing just
> what you described.  I was able to emerge --resume successfully.
>
>

-- 

Brett I. Holcomb
brettholcomb@R777bellsouth.net
Registered Linux User #188143
Remove R777 to email
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Emerge --resume

[AJ Spagnoletti]

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

On 12/7/05, Brett I. Holcomb <brettholcomb@bellsouth.net> wrote:
>
> As long as you don't do another merge between the first one and the
> resumed one it should remember.
>
> > Earlier this afternoon I had to restart a machine that was doing just
> > what you described.  I was able to emerge --resume successfully.


Thanks for the info guys just what I needed to hear :-)

AJ

[-- Attachment #2: Type: text/html, Size: 717 bytes --]

[gentoo-user] emerge --resume

[Daniel Iliev]

Hi, guys!

#emerge --resume gives me:

These are the packages that would be merged, in order:

!!! Error: The resume list contains packages that are no longer
!!!        available to be emerged. Please restart/continue
!!!        the merge operation manually.
#


How could I fix it?

-- 
Best regards,
Daniel


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge --resume

[Stuart Howard]

On 24/12/06, Daniel Iliev <danny@ilievnet.com> wrote:
> Hi, guys!
>
> #emerge --resume gives me:
>
> These are the packages that would be merged, in order:
>
> !!! Error: The resume list contains packages that are no longer
> !!!        available to be emerged. Please restart/continue
> !!!        the merge operation manually.
> #
>
>
> How could I fix it?
>
> --
> Best regards,
> Daniel
>
>
> --
> gentoo-user@gentoo.org mailing list
>
>

Are you doing a large emerge? eg. --emptytree
or have you not --sync lately
or has this emerge been running fora  long... time and prehaps
something has dropped out of the tree in that time?
A bit more information on what you are actually doing may get you a
better response than mine.

Prehaps one of those may explain the issue but for now trying
emerge --resume --skipfirst
may help the situation and get you to the end of the process then you
can go back and discover the offending package.

-- 
"There are 10 types of people in this world: those who understand
binary, those who don't"

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

Re: [gentoo-user] emerge --resume

[Daniel Iliev]

First of all - where did my manners go!?  ;-(

MARRY CHRISTMAS, EVERYONE!
I wish you health, happiness and even more fun with our favorite Gentoo!

;-))))


On the subject: Yes, yesterday I woke up with a broken root FS after a
power failure. I did fix the FS with a boot CD I did "emerge -e system".
Afterwards I booted the system on its own and started "emerge -e world".
During this my cron did "emerge --sync". Unfortunately I lost my network
connection and "emerge -e world" stopped on x11-libs/libxklavier-3.0-r1.
After my connection was restored I had this message from "emerge
--resume". So I started "emerge -e world" again and now it is complete.
Also "emerge -DuN world" gives an empty list therefore I consider my
system to be up-to-date with the current portage. The problem is that
"emerge --resume" still gives this never seen before (by me) output.

Bottom lines: I want to clear "the resume list" in order to get back to
the normal behavior of "emerge --resume"


P.S.

"emerge --resume --skipfirst" doesn't help - it gives the same message.

-- 
Best regards,
Daniel


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge --resume

[Stuart Howard]

On 24/12/06, Daniel Iliev <danny@ilievnet.com> wrote:
>
> First of all - where did my manners go!?  ;-(
>
> MARRY CHRISTMAS, EVERYONE!
> I wish you health, happiness and even more fun with our favorite Gentoo!
>
> ;-))))
>
>
> On the subject: Yes, yesterday I woke up with a broken root FS after a
> power failure. I did fix the FS with a boot CD I did "emerge -e system".
> Afterwards I booted the system on its own and started "emerge -e world".
> During this my cron did "emerge --sync". Unfortunately I lost my network
> connection and "emerge -e world" stopped on x11-libs/libxklavier-3.0-r1.
> After my connection was restored I had this message from "emerge
> --resume". So I started "emerge -e world" again and now it is complete.
> Also "emerge -DuN world" gives an empty list therefore I consider my
> system to be up-to-date with the current portage. The problem is that
> "emerge --resume" still gives this never seen before (by me) output.
>
> Bottom lines: I want to clear "the resume list" in order to get back to
> the normal behavior of "emerge --resume"
>
>
> P.S.
>
> "emerge --resume --skipfirst" doesn't help - it gives the same message.
>
> --
> Best regards,
> Daniel
>
>
> --
> gentoo-user@gentoo.org mailing list
>
>

Ouch! not so merry at this time of yea.

Well my understanding of the emerge command is that resume works only
on the current/last call to emerge and since you have been through the
--emptytree all the way you have nothing to resume.
I confess I dont understand the message but I would assume that if you
emege something else then the "last" emege call will be reset and then
hopefully resume will be working next time you need it, not sure how
you can test to see if resume works unless you try and build a package
that is going to fail then try the resume function.

stu

-- 
"There are 10 types of people in this world: those who understand
binary, those who don't"

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

Re: [gentoo-user] emerge --resume

[Daniel Iliev]

Stuart Howard wrote:
> On 24/12/06, Daniel Iliev <danny@ilievnet.com> wrote:
>>
>> First of all - where did my manners go!?  ;-(
>>
>> MARRY CHRISTMAS, EVERYONE!
>> I wish you health, happiness and even more fun with our favorite Gentoo!
>>
>> ;-))))
>>
>>
>> On the subject: Yes, yesterday I woke up with a broken root FS after a
>> power failure. I did fix the FS with a boot CD I did "emerge -e system".
>> Afterwards I booted the system on its own and started "emerge -e world".
>> During this my cron did "emerge --sync". Unfortunately I lost my network
>> connection and "emerge -e world" stopped on x11-libs/libxklavier-3.0-r1.
>> After my connection was restored I had this message from "emerge
>> --resume". So I started "emerge -e world" again and now it is complete.
>> Also "emerge -DuN world" gives an empty list therefore I consider my
>> system to be up-to-date with the current portage. The problem is that
>> "emerge --resume" still gives this never seen before (by me) output.
>>
>> Bottom lines: I want to clear "the resume list" in order to get back to
>> the normal behavior of "emerge --resume"
>>
>>
>> P.S.
>>
>> "emerge --resume --skipfirst" doesn't help - it gives the same message.
>>
>> -- 
>> Best regards,
>> Daniel
>>
>>
>> -- 
>> gentoo-user@gentoo.org mailing list
>>
>>
>
> Ouch! not so merry at this time of yea.
>
> Well my understanding of the emerge command is that resume works only
> on the current/last call to emerge and since you have been through the
> --emptytree all the way you have nothing to resume.
> I confess I dont understand the message but I would assume that if you
> emege something else then the "last" emege call will be reset and then
> hopefully resume will be working next time you need it, not sure how
> you can test to see if resume works unless you try and build a package
> that is going to fail then try the resume function.
>
> stu
>

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. ;-)

-- 
Best regards,
Daniel


-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge --resume

[Etaoin Shrdlu]

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.
-- 
gentoo-user@gentoo.org mailing list

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

[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

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

[Bo Ørsted Andresen]

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

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

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

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

[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] emerge --resume

[Randy Barlow]

On Sun, 2006-12-24 at 17:55 +0200, Daniel Iliev wrote:
> During this my cron did "emerge --sync".

I would recommend not having cron sync your tree for this very reason...

Randy Barlow
http://www.electronsweatshop.com
Today is a good day for information-gathering. Read someone else's mail
file.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] emerge --resume

[Nicholas Hockey]

[-- Attachment #1.1: Type: text/plain, Size: 854 bytes --]

On Wed, 2006-12-27 at 01:26 -0500, Randy Barlow wrote:

> On Sun, 2006-12-24 at 17:55 +0200, Daniel Iliev wrote:
> > During this my cron did "emerge --sync".
> 
> I would recommend not having cron sync your tree for this very reason...
> 
> Randy Barlow
> http://www.electronsweatshop.com
> Today is a good day for information-gathering. Read someone else's mail
> file.
> 


i agree, i think automagicly syncing the tree is a bad idea..... look at
it this way.... Do you have your windows machines set to automgicly
chack, and install updates ? In an age where system administration is
almost unrequired, there are still some things you should od by hand....
like syncing the tree, and while updating the system, keep an eye out
for messages to indicate potential problems.... yes it's not fun, but
it's the key to a stable system.

[-- Attachment #1.2: Type: text/html, Size: 1383 bytes --]

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 187 bytes --]

Re: [gentoo-user] emerge --resume

[Neil Bothwick]

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

On Wed, 27 Dec 2006 01:32:05 -0500, Nicholas Hockey wrote:

> > > During this my cron did "emerge --sync".  
> > 
> > I would recommend not having cron sync your tree for this very
> > reason...

I have a cron script that syncs each morning, but it checks that emerge
is not running first, to avoid just this sort of problem.

> i agree, i think automagicly syncing the tree is a bad idea..... look at
> it this way.... Do you have your windows machines set to automgicly
> chack, and install updates ?

syncing the tree is not installing anything, all it does is update the
list of what is available. Any comparison with Windows is irrelevant
anyway, Linux is not Windows.


-- 
Neil Bothwick

Daisy Duke shorts would never go out of fashion.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-user] emerge --resume

[Dale]

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

Neil Bothwick wrote:
> On Wed, 27 Dec 2006 01:32:05 -0500, Nicholas Hockey wrote:
> < snip >
>> i agree, i think automagicly syncing the tree is a bad idea..... look at
>> it this way.... Do you have your windows machines set to automgicly
>> chack, and install updates ?
>>     
>
> syncing the tree is not installing anything, all it does is update the
> list of what is available. Any comparison with Windows is irrelevant
> anyway, Linux is not Windows.
>
>
>   

I thought windoze XP was set up to do this now?  I think my Brothers does. 

Dale
:-)  :-)

-- 
www.myspace.com/dalek1967


[-- Attachment #2: Type: text/html, Size: 1160 bytes --]

Re: [gentoo-user] emerge --resume

[Dan]

On Wed, 27 Dec 2006 05:44:09 -0600
Dale <dalek@exceedtech.net> wrote:

> > syncing the tree is not installing anything, all it does is update
> > the list of what is available. Any comparison with Windows is
> > irrelevant anyway, Linux is not Windows.
yeah, in unix you can read files more than once and sane things happen
if you try to change then while they're open (fd still good that is)
> I thought windoze XP was set up to do this now?  I think my Brothers
> does. 
XP's automatic updates are, i think, on by default.  
-- 
gentoo-user@gentoo.org mailing list