* [gentoo-user] emerge --resume says "invalid resume list".
@ 2016-06-21 14:39 Dan Douglas
2016-06-21 15:04 ` Neil Bothwick
0 siblings, 1 reply; 8+ messages in thread
From: Dan Douglas @ 2016-06-21 14:39 UTC (permalink / raw
To: gentoo-user
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)
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] emerge --resume says "invalid resume list".
2016-06-21 14:39 [gentoo-user] emerge --resume says "invalid resume list" Dan Douglas
@ 2016-06-21 15:04 ` Neil Bothwick
2016-06-22 13:39 ` Dan Douglas
0 siblings, 1 reply; 8+ messages in thread
From: Neil Bothwick @ 2016-06-21 15:04 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 509 bytes --]
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] emerge --resume says "invalid resume list".
2016-06-21 15:04 ` Neil Bothwick
@ 2016-06-22 13:39 ` Dan Douglas
2016-06-22 17:31 ` Neil Bothwick
2016-07-09 15:28 ` Fernando Rodriguez
0 siblings, 2 replies; 8+ messages in thread
From: Dan Douglas @ 2016-06-22 13:39 UTC (permalink / raw
To: gentoo-user
On Tue, Jun 21, 2016 at 10:04 AM, Neil Bothwick <neil@digimed.co.uk> 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.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] emerge --resume says "invalid resume list".
2016-06-22 13:39 ` Dan Douglas
@ 2016-06-22 17:31 ` Neil Bothwick
2016-06-22 19:57 ` Dan Douglas
2016-07-09 15:28 ` Fernando Rodriguez
1 sibling, 1 reply; 8+ messages in thread
From: Neil Bothwick @ 2016-06-22 17:31 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
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.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] emerge --resume says "invalid resume list".
2016-06-22 17:31 ` Neil Bothwick
@ 2016-06-22 19:57 ` Dan Douglas
2016-06-23 19:13 ` [gentoo-user] " Jonathan Callen
2016-06-23 19:55 ` [gentoo-user] " Neil Bothwick
0 siblings, 2 replies; 8+ messages in thread
From: Dan Douglas @ 2016-06-22 19:57 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1.1: Type: text/plain, Size: 1020 bytes --]
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.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* [gentoo-user] Re: emerge --resume says "invalid resume list".
2016-06-22 19:57 ` Dan Douglas
@ 2016-06-23 19:13 ` Jonathan Callen
2016-06-23 19:55 ` [gentoo-user] " Neil Bothwick
1 sibling, 0 replies; 8+ messages in thread
From: Jonathan Callen @ 2016-06-23 19:13 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1.1: Type: text/plain, Size: 1862 bytes --]
On 06/22/2016 03:57 PM, Dan Douglas wrote:
> 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.
>
>
Often, the issue in these cases is that there is some broken dependency
already present on the system (for some value of "broken"). This may be
a package that is not required by anything (so --depclean would remove
it) is now broken because it requires something that isn't installed.
It may also be a package that is only required as a build dependency of
something, if you do not have '--with-bdeps=y' in your
EMERGE_DEFAULT_OPTS. Unfortunately, it is difficult to get portage to
explain what it thinks is broken in these cases. If trying to do a
`emerge -pvte @world` shows packages that would be updated, newly
installed, or rebuilt, when your normal @world update would show
nothing, this may be part of the problem.
--
Jonathan Callen
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 847 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] emerge --resume says "invalid resume list".
2016-06-22 19:57 ` Dan Douglas
2016-06-23 19:13 ` [gentoo-user] " Jonathan Callen
@ 2016-06-23 19:55 ` Neil Bothwick
1 sibling, 0 replies; 8+ messages in thread
From: Neil Bothwick @ 2016-06-23 19:55 UTC (permalink / raw
To: gentoo-user
[-- Attachment #1: Type: text/plain, Size: 1367 bytes --]
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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [gentoo-user] emerge --resume says "invalid resume list".
2016-06-22 13:39 ` Dan Douglas
2016-06-22 17:31 ` Neil Bothwick
@ 2016-07-09 15:28 ` Fernando Rodriguez
1 sibling, 0 replies; 8+ messages in thread
From: Fernando Rodriguez @ 2016-07-09 15:28 UTC (permalink / raw
To: gentoo-user
On 06/22/2016 09:39 AM, Dan Douglas wrote:
> On Tue, Jun 21, 2016 at 10:04 AM, Neil Bothwick <neil@digimed.co.uk> 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.
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2016-07-09 15:28 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-06-21 14:39 [gentoo-user] emerge --resume says "invalid resume list" Dan Douglas
2016-06-21 15:04 ` Neil Bothwick
2016-06-22 13:39 ` Dan Douglas
2016-06-22 17:31 ` Neil Bothwick
2016-06-22 19:57 ` Dan Douglas
2016-06-23 19:13 ` [gentoo-user] " Jonathan Callen
2016-06-23 19:55 ` [gentoo-user] " Neil Bothwick
2016-07-09 15:28 ` Fernando Rodriguez
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox