Re: [gentoo-user] emerge --resume says "invalid resume list".

[Fernando Rodriguez]

On 06/22/2016 09:39 AM, Dan Douglas wrote:
> On Tue, Jun 21, 2016 at 10:04 AM, Neil Bothwick  wrote:
>> On Tue, 21 Jun 2016 09:39:42 -0500, Dan Douglas wrote:
>>
>>> Is something misconfigured on my end or is this just a long-standing
>>> bug? I at least need a way to either recover the list of packages
>>> manually or force portage to continue on because any failure prevents
>>> updating a system.
>>
>> Have you tried the --keep-going option? It causes emerge to automatically
>> continue with what it can after a failed build.
> 
> --keep-going is in EMERGE_DEFAULT_OPTS so the problem is only when
> that fails for whatever reason, --resume (with or without
> --skip-first) always fails too. Usually a package that I already know
> is broken and am working on but is already installed wants to be
> rebuilt will trigger this. The problem is portage doesn't seem to care
> whether any packages in the current resume list actually depend on the
> failing package and this can prevent important installations from
> finishing.
> 

I've had the exact same thing happen a couple of times recently and got around 
it
by running the original command but adding the failed package to the --exclude
list. AFAIU (I maybe wrong) the result of both commands should be the same so it
sounds like a bug to me.

Re: [gentoo-user] emerge --resume says "invalid resume list".

[Neil Bothwick]

On Wed, 22 Jun 2016 14:57:50 -0500, Dan Douglas wrote:

> >> --keep-going is in EMERGE_DEFAULT_OPTS so the problem is only when
> >> that fails for whatever reason, --resume (with or without
> >> --skip-first) always fails too.  
> > On 06/22/2016 12:31 PM, Neil Bothwick wrote:
> > That makes sense, --keep-going has already made sure that all updates
> > that are not dependant on the failing one have emerged, so there's
> > nothing left to emerge until you fix the broken package.  
> 
> 
> That's what it should do but it clearly doesn't quite work that way.
> It's easy to prove it's broken by finding any package on the resume list
> that can merge on its own without pulling in a previously failed
> package.
> 
> I've had completely up-to-date systems where no possible failure could
> result in an unsatisfied dependency and portage refuses to resume an
> `emerge -e @world` with hundreds of possible packages on the resume list
> that would work in isolation. That's the problem.

Without specifics it's not possible to say any more.


-- 
Neil Bothwick

"There are two ways of constructing a software design: One way is to make
it so simple that there are obviously no deficiencies, and the other way
is to make it so complicated that there are no obvious deficiencies.
The first method is far more difficult" -C.A.R. Hoare


pgpgBUMGRfNuJ.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] emerge --resume says "invalid resume list".

[Dan Douglas]

On 06/22/2016 12:31 PM, Neil Bothwick wrote:
> On Wed, 22 Jun 2016 08:39:59 -0500, Dan Douglas wrote:
>> --keep-going is in EMERGE_DEFAULT_OPTS so the problem is only when
>> that fails for whatever reason, --resume (with or without
>> --skip-first) always fails too.
> On 06/22/2016 12:31 PM, Neil Bothwick wrote:
> That makes sense, --keep-going has already made sure that all updates
> that are not dependant on the failing one have emerged, so there's
> nothing left to emerge until you fix the broken package.


That's what it should do but it clearly doesn't quite work that way.
It's easy to prove it's broken by finding any package on the resume list
that can merge on its own without pulling in a previously failed package.

I've had completely up-to-date systems where no possible failure could
result in an unsatisfied dependency and portage refuses to resume an
`emerge -e @world` with hundreds of possible packages on the resume list
that would work in isolation. That's the problem.




signature.asc
Description: OpenPGP digital signature

Re: [gentoo-user] emerge --resume says "invalid resume list".

[Neil Bothwick]

On Wed, 22 Jun 2016 08:39:59 -0500, Dan Douglas wrote:

> >> Is something misconfigured on my end or is this just a long-standing
> >> bug? I at least need a way to either recover the list of packages
> >> manually or force portage to continue on because any failure prevents
> >> updating a system.  
> >
> > Have you tried the --keep-going option? It causes emerge to
> > automatically continue with what it can after a failed build.  
> 
> --keep-going is in EMERGE_DEFAULT_OPTS so the problem is only when
> that fails for whatever reason, --resume (with or without
> --skip-first) always fails too.

That makes sense, --keep-going has already made sure that all updates
that are not dependant on the failing one have emerged, so there's
nothing left to emerge until you fix the broken package.


-- 
Neil Bothwick

Feminism: the radical notion that women are people.


pgpRISAMEgB_b.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] emerge --resume says "invalid resume list".

[Dan Douglas]

On Tue, Jun 21, 2016 at 10:04 AM, Neil Bothwick  wrote:
> On Tue, 21 Jun 2016 09:39:42 -0500, Dan Douglas wrote:
>
>> Is something misconfigured on my end or is this just a long-standing
>> bug? I at least need a way to either recover the list of packages
>> manually or force portage to continue on because any failure prevents
>> updating a system.
>
> Have you tried the --keep-going option? It causes emerge to automatically
> continue with what it can after a failed build.

--keep-going is in EMERGE_DEFAULT_OPTS so the problem is only when
that fails for whatever reason, --resume (with or without
--skip-first) always fails too. Usually a package that I already know
is broken and am working on but is already installed wants to be
rebuilt will trigger this. The problem is portage doesn't seem to care
whether any packages in the current resume list actually depend on the
failing package and this can prevent important installations from
finishing.

Re: [gentoo-user] emerge --resume says "invalid resume list".

[Neil Bothwick]

On Tue, 21 Jun 2016 09:39:42 -0500, Dan Douglas wrote:

> Is something misconfigured on my end or is this just a long-standing
> bug? I at least need a way to either recover the list of packages
> manually or force portage to continue on because any failure prevents
> updating a system.

Have you tried the --keep-going option? It causes emerge to automatically
continue with what it can after a failed build.


-- 
Neil Bothwick

Never ask a geek why, just nod your head and slowly back away


pgpD9FHfTWJQl.pgp
Description: OpenPGP digital signature

[gentoo-user] emerge --resume says "invalid resume list".

[Dan Douglas]

Hi. I don't believe I've ever seen portage's --resume --skipfirst
option work correctly without saying "invalid resume list". I know
this is incorrect because I've manually checked that all deps are
satisfied and it even occurs if a custom package I'm working on with
nothing depending upon it fails.

Is something misconfigured on my end or is this just a long-standing
bug? I at least need a way to either recover the list of packages
manually or force portage to continue on because any failure prevents
updating a system. --nodeps isn't an option because this causes
portage to disregard the merge order which can be a problem.

I can't even find where portage stores the resume list. Long ago I
think it was in a python pickle file somewhere but I can't find this
anymore. Any pointers? Thanks.

Most configs here if needed:
https://github.com/ormaaj/dotfiles/tree/master/common/etc/portage
(usually a bit outdated though)

[gentoo-user] emerge --resume finds an old resume rather than the previous one

[felix]

I have a shell script which loops on failure from emerge to use
--skipfirst --resume to continue as much as possible.  Every once in a
while, it gets forgetful and picks up an emerge from several days
previous to try to resume instead of the one that just failed.  This
is pretty annoying.  It started several months ago, sporadically, and
seems to be happening more and more often, but not always, and not in
any pattern I can discern.

This is sys-apps/portage-2.1.6.13 on ~amd64.

-- 
... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
 Felix Finch: scarecrow repairman  rocket surgeon / fe...@crowfix.com
  GPG = E987 4493 C860 246C 3B1E  6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o

Re: [gentoo-user] emerge --resume finds an old resume rather than the previous one

[Willie Wong]

On Thu, Jun 04, 2009 at 09:02:21AM -0700, Penguin Lover fe...@crowfix.com 
squawked:
 I have a shell script which loops on failure from emerge to use
 --skipfirst --resume to continue as much as possible.  

May I suggest using the --keep-going option for emerge to do what you
want to do instead of a shell script?

W
-- 
All of this is on the web, so other people know it too.
~DeathMech, S. Sondhi. P-town PHY 205
Sortir en Pantoufles: up 909 days, 14:55

Re: [gentoo-user] emerge --resume finds an old resume rather than the previous one

[Paul Hartman]

On Thu, Jun 4, 2009 at 11:02 AM,  fe...@crowfix.com wrote:
 I have a shell script which loops on failure from emerge to use
 --skipfirst --resume to continue as much as possible.  Every once in a
 while, it gets forgetful and picks up an emerge from several days
 previous to try to resume instead of the one that just failed.  This
 is pretty annoying.  It started several months ago, sporadically, and
 seems to be happening more and more often, but not always, and not in
 any pattern I can discern.

 This is sys-apps/portage-2.1.6.13 on ~amd64.

It may be easier to use the --keep-going switch instead. It allows
emerge to continue emerging everything else (when possible) and
skipping unresolved dependencies caused by the failed merges.

Re: [gentoo-user] emerge --resume finds an old resume rather than the previous one

[felix]

On Thu, Jun 04, 2009 at 11:08:26AM -0500, Paul Hartman wrote:
 On Thu, Jun 4, 2009 at 11:02 AM,  fe...@crowfix.com wrote:
  I have a shell script which loops on failure from emerge to use
  --skipfirst --resume to continue as much as possible.  Every once in a
  while, it gets forgetful and picks up an emerge from several days
  previous to try to resume instead of the one that just failed.  This
  is pretty annoying.  It started several months ago, sporadically, and
  seems to be happening more and more often, but not always, and not in
  any pattern I can discern.
 
  This is sys-apps/portage-2.1.6.13 on ~amd64.
 
 It may be easier to use the --keep-going switch instead. It allows
 emerge to continue emerging everything else (when possible) and
 skipping unresolved dependencies caused by the failed merges.

Good grief.  That's *zackly* what I have wanted for a long time.  When
did it get added?

I will certainly try that next merge.  Heck, I might try the most
recent one again anyway just to see miracles in action :-)

-- 
... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
 Felix Finch: scarecrow repairman  rocket surgeon / fe...@crowfix.com
  GPG = E987 4493 C860 246C 3B1E  6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o

Re: [gentoo-user] emerge --resume finds an old resume rather than the previous one

[Paul Hartman]

On Thu, Jun 4, 2009 at 11:18 AM,  fe...@crowfix.com wrote:
 Good grief.  That's *zackly* what I have wanted for a long time.  When
 did it get added?

From bug 12768 it looks like it was added by Zac Medico on 2008-06-27 :)

Re: [gentoo-user] emerge --resume finds an old resume rather than the previous one

[felix]

On Thu, Jun 04, 2009 at 09:18:14AM -0700, fe...@crowfix.com wrote:
 On Thu, Jun 04, 2009 at 11:08:26AM -0500, Paul Hartman wrote:
  On Thu, Jun 4, 2009 at 11:02 AM,  fe...@crowfix.com wrote:
   I have a shell script which loops on failure from emerge to use
   --skipfirst --resume to continue as much as possible.  Every once in a
   while, it gets forgetful and picks up an emerge from several days
   previous to try to resume instead of the one that just failed.  This
   is pretty annoying.  It started several months ago, sporadically, and
   seems to be happening more and more often, but not always, and not in
   any pattern I can discern.
  
   This is sys-apps/portage-2.1.6.13 on ~amd64.
  
  It may be easier to use the --keep-going switch instead. It allows
  emerge to continue emerging everything else (when possible) and
  skipping unresolved dependencies caused by the failed merges.
 
 Good grief.  That's *zackly* what I have wanted for a long time.  When
 did it get added?
 
 I will certainly try that next merge.  Heck, I might try the most
 recent one again anyway just to see miracles in action :-)

Unfortunately, it does exactly the same thing.

*** Resuming merge...   


  
Calculating dependencies  ..^H^H... done!   


  
 * One or more packages are either masked or have missing dependencies: 


  
and it picks up the same several day old failed emerge instead of the
one it was running.

-- 
... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
 Felix Finch: scarecrow repairman  rocket surgeon / fe...@crowfix.com
  GPG = E987 4493 C860 246C 3B1E  6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o

Re: [gentoo-user] emerge --resume finds an old resume rather than the previous one

[Dale]

fe...@crowfix.com wrote:
 On Thu, Jun 04, 2009 at 11:08:26AM -0500, Paul Hartman wrote:
   
 On Thu, Jun 4, 2009 at 11:02 AM,  fe...@crowfix.com wrote:
 
 I have a shell script which loops on failure from emerge to use
 --skipfirst --resume to continue as much as possible.  Every once in a
 while, it gets forgetful and picks up an emerge from several days
 previous to try to resume instead of the one that just failed.  This
 is pretty annoying.  It started several months ago, sporadically, and
 seems to be happening more and more often, but not always, and not in
 any pattern I can discern.

 This is sys-apps/portage-2.1.6.13 on ~amd64.
   
 It may be easier to use the --keep-going switch instead. It allows
 emerge to continue emerging everything else (when possible) and
 skipping unresolved dependencies caused by the failed merges.
 

 Good grief.  That's *zackly* what I have wanted for a long time.  When
 did it get added?

 I will certainly try that next merge.  Heck, I might try the most
 recent one again anyway just to see miracles in action :-)

   


You can also add that option to make.conf so it will do it even if you
forget to type it in.  I did that a while back when I found out about it.

Dale

:-)  :-) 

Re: [gentoo-user] emerge --resume finds an old resume rather than the previous one

[Neil Bothwick]

On Thu, 4 Jun 2009 09:55:59 -0700, fe...@crowfix.com wrote:

 and it picks up the same several day old failed emerge instead of the
 one it was running.

Try emaint -f cleanresume


-- 
Neil Bothwick

A computer without Microsoft is like a chocolate cake without mustard.


signature.asc
Description: PGP signature

Re: [gentoo-user] emerge --resume finds an old resume rather than the previous one

[felix]

On Thu, Jun 04, 2009 at 06:30:37PM +0100, Neil Bothwick wrote:
 On Thu, 4 Jun 2009 09:55:59 -0700, fe...@crowfix.com wrote:
 
  and it picks up the same several day old failed emerge instead of the
  one it was running.
 
 Try emaint -f cleanresume

Same result.  emain did something, but the emerge still picks up the
old emerge.

-- 
... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
 Felix Finch: scarecrow repairman  rocket surgeon / fe...@crowfix.com
  GPG = E987 4493 C860 246C 3B1E  6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o

Re: [gentoo-user] emerge --resume

[Neil Bothwick]

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.


signature.asc
Description: PGP signature

Re: [gentoo-user] emerge --resume

[Dale]

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

Re: [gentoo-user] emerge --resume

[Dan]

On Wed, 27 Dec 2006 05:44:09 -0600
Dale [EMAIL PROTECTED] 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

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]

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.


signature.asc
Description: This is a digitally signed message part

[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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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

[gentoo-user] emerge resume list

[evader]

Hi,


When I do an emerge -e world where is the list of files to be merged  
stored? For example if I break an emerge, and want to resume
later from a different position, can I edit the packages to be emerged  
list so I don't have to do emerge --resume --skipfirst constantly?


Thanks,

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

[gentoo-user] emerge --resume question

[Peter Campion-Bye]

Hi,
Trying to do an 'emerge -e world' I come up against the odd package that
doesn't build without some intervention. I know I can do 'emerge --resume
--skipfirst' and carry on, but sometimes the broken package could be built ok
with a little intervention, for example, my build breaks on pilot-link, which
can be simply fixed with 'FEATURES=-sandbox emerge pilot-link'. Problem is,
I can't do a resume after this as the emerge list from the world build has
been blatted when I emerged pilot-link. So, is there any way I can preserve
the state of the world build, so that after building the breaking package I
can do a --resume --skipfirst and carry on with the world build?
Any other suggestions for workarounds?
thanks
-- 
gentoo-user@gentoo.org mailing list

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

[Teresa and Dale]

Peter Campion-Bye wrote:

Hi,
Trying to do an 'emerge -e world' I come up against the odd package that
doesn't build without some intervention. I know I can do 'emerge --resume
--skipfirst' and carry on, but sometimes the broken package could be built ok
with a little intervention, for example, my build breaks on pilot-link, which
can be simply fixed with 'FEATURES=-sandbox emerge pilot-link'. Problem is,
I can't do a resume after this as the emerge list from the world build has
been blatted when I emerged pilot-link. So, is there any way I can preserve
the state of the world build, so that after building the breaking package I
can do a --resume --skipfirst and carry on with the world build?
Any other suggestions for workarounds?
thanks
  


I did this once.  I renamed the emerge.log then did what needed doing
and then put the back-up back to it's original name, erasing the little
that was generated while fixing something.  It may not work in every
case though but it may be worth a try.

Dale
:-)
:-)
-- 
gentoo-user@gentoo.org mailing list

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

[Jason Stubbs]

On Monday 03 April 2006 20:39, Peter Ruskin wrote:
 On Monday 03 April 2006 12:06, Peter Campion-Bye wrote:
  Hi,
  Trying to do an 'emerge -e world' I come up against the odd
  package that doesn't build without some intervention. I know I
  can do 'emerge --resume --skipfirst' and carry on, but sometimes
  the broken package could be built ok with a little intervention,
  for example, my build breaks on pilot-link, which can be simply
  fixed with 'FEATURES=-sandbox emerge pilot-link'. Problem is, I
  can't do a resume after this as the emerge list from the world
  build has been blatted when I emerged pilot-link. So, is there
  any way I can preserve the state of the world build, so that
  after building the breaking package I can do a --resume
  --skipfirst and carry on with the world build? Any other
  suggestions for workarounds?
 
 I'm just experiencing the same thing - with over 800 ebuilds this is 
 an important question.  I'm noting the problem ebuilds in a log 
 file manually, so I can see to them when it's all over.

This is resilient to the single merge between resumes case in 2.1_pre.
For 2.0, you can manually back up and restore /var/cache/edp/mtimedb.

--
Jason Stubbs
-- 
gentoo-user@gentoo.org mailing list

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

[Jason Stubbs]

On Monday 03 April 2006 22:12, Peter Ruskin wrote:
 On Monday 03 April 2006 13:12, Jason Stubbs wrote:
   I'm just experiencing the same thing - with over 800 ebuilds
   this is an important question.  I'm noting the problem ebuilds
   in a log file manually, so I can see to them when it's all
   over.
 
  This is resilient to the single merge between resumes case in
  2.1_pre. For 2.0, you can manually back up and restore
  /var/cache/edp/mtimedb.
 
 Sorry Jason, I don't understand.  How would I backup and 
 restore /var/cache/edp/mtimedb and what would that do?

It does as the opening poster asked:

 So, is there any way I can preserve the state of the world build,
 so that after building the breaking package I can do a --resume
 --skipfirst and carry on with the world build?

The not very aptly named mtimedb file contains the resume list among
other things. Hence, copying it somewhere else before fixing a broken
build and copying it back after will preserve the resume list. Don't
do it for more than single ebuild maintenance though as the file
contains other things too.

--
Jason Stubbs

-- 
gentoo-user@gentoo.org mailing list

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

[Peter Campion-Bye]

 This is resilient to the single merge between resumes case in 2.1_pre.
 For 2.0, you can manually back up and restore /var/cache/edp/mtimedb.

 --
 Jason Stubbs

Thanks Jason, I'll give that a try.
Regarding the original problem with pilot-link, there is AFAIK no way to
specify FEATURES on an individual package basis (ie put
'app-pda/pilot-link -sandbox' into a file named package.features, in the style
of the package.use file) - is that correct?
Thanks
-- 
gentoo-user@gentoo.org mailing list

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

[Neil Bothwick]

On Mon, 3 Apr 2006 16:45:39 +0100 (BST), Peter Campion-Bye wrote:

 Regarding the original problem with pilot-link, there is AFAIK no way to
 specify FEATURES on an individual package basis (ie put
 'app-pda/pilot-link -sandbox' into a file named package.features, in
 the style of the package.use file) - is that correct?

You can use /etc/portage/bashrc to set anything on a per-package basis.

Put this in /etc/portage/bashrc

for MY_ENV in ${PN} ${P} ${PF}; do 
if [ -f /etc/portage/env.d/${CATEGORY}/${MY_ENV} ]; then 
source /etc/portage/env.d/${CATEGORY}/${MY_ENV} 
fi 
done

And put 'FEATURES=-sandbox in /etc/portage/env.d/app-pda/pilot-link


-- 
Neil Bothwick

I understand the answers, the questions throw me.


signature.asc
Description: PGP signature

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

[Peter Campion-Bye]

 Regarding the original problem with pilot-link, there is AFAIK no way to
 specify FEATURES on an individual package basis (ie put
 'app-pda/pilot-link -sandbox' into a file named package.features, in
 the style of the package.use file) - is that correct?

 You can use /etc/portage/bashrc to set anything on a per-package basis.

 Put this in /etc/portage/bashrc

 for MY_ENV in ${PN} ${P} ${PF}; do
   if [ -f /etc/portage/env.d/${CATEGORY}/${MY_ENV} ]; then
   source /etc/portage/env.d/${CATEGORY}/${MY_ENV}
   fi
   done

 And put 'FEATURES=-sandbox in /etc/portage/env.d/app-pda/pilot-link

Very neat solution Neil, thanks.

-- 
gentoo-user@gentoo.org mailing list

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

[Peter Campion-Bye]

 On Monday 03 April 2006 16:45, Peter Campion-Bye wrote:
 Regarding the original problem with pilot-link, there is AFAIK no
 way to specify FEATURES on an individual package basis (ie put
 'app-pda/pilot-link -sandbox' into a file named package.features,
 in the style of the package.use file) - is that correct?

 You can do this from the command line:

 FEATURES=-sandbox emerge app-pda/pilot-link

Thanks, I know that, the question was how to arrange for specific features to
apply only to an individual package in the middle of an 'emerge -e world'.
It would be nice if the package.use functionality could be mirrored with a
package.features file, but I suppose it's needed so rarely that it's not worth
the effort on the part of the portage devs.

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] 'emerge --resume' problem

[Grant]

  Hello, I've been recompiling my system with gcc 3.4 and utilizing
  emerge --resume.  The last time I used emerge --resume it started
  emerging firefox and said 1 of 3.  The next time I checked on it,
  firefox had emerged successfully but the process then stopped.  I ran
  emerge --resume again and it started emerging firefox again and again
  said 1 of 3.  Is this a bug?

 If the emerge process stopped at Firefox instead of continuing with the
 next, the Firefox emerge did not complete successfully. That's why resume
 is starting it again.

 Use emerge --resume --skipfirst to emerge the rest of the outstanding
 packages, then emerge Firefox again with logging enabled - set
 PORT_LOGDIR in make.conf.


 --
 Neil Bothwick

Ok, thanks.  Firefox must have failed.

- Grant

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] 'emerge --resume' problem

[Neil Bothwick]

On Wed, 7 Dec 2005 18:43:57 -0800, Grant wrote:

 Hello, I've been recompiling my system with gcc 3.4 and utilizing
 emerge --resume.  The last time I used emerge --resume it started
 emerging firefox and said 1 of 3.  The next time I checked on it,
 firefox had emerged successfully but the process then stopped.  I ran
 emerge --resume again and it started emerging firefox again and again
 said 1 of 3.  Is this a bug?

If the emerge process stopped at Firefox instead of continuing with the
next, the Firefox emerge did not complete successfully. That's why resume
is starting it again.

Use emerge --resume --skipfirst to emerge the rest of the outstanding
packages, then emerge Firefox again with logging enabled - set
PORT_LOGDIR in make.conf.


-- 
Neil Bothwick

I like you. You remind me of when I was young and stupid.


signature.asc
Description: PGP signature

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
[EMAIL PROTECTED]
Registered Linux User #188143
Remove R777 to email
--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] Emerge --resume

[AJ Spagnoletti]

On 12/7/05, Brett I. Holcomb [EMAIL PROTECTED] wrote:
As long as you don't do another merge between the first one and theresumed 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

[gentoo-user] 'emerge --resume' problem

[Grant]

Hello, I've been recompiling my system with gcc 3.4 and utilizing
emerge --resume.  The last time I used emerge --resume it started
emerging firefox and said 1 of 3.  The next time I checked on it,
firefox had emerged successfully but the process then stopped.  I ran
emerge --resume again and it started emerging firefox again and again
said 1 of 3.  Is this a bug?

- Grant

-- 
gentoo-user@gentoo.org mailing list