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