[gentoo-user] Portage: Complaining about multiple incidents at once

[gentoo-user] Portage: Complaining about multiple incidents at once

[Gerion Entrup]

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

Hi,

does Portage have a "don't stop" mode?

With that I mean the following:
I'm doing updates with
emerge -auND world --keep-going --quiet-build --verbose-conflicts

Portage then often stops, saying a dependency keyword is missing or a
useflag etc. However, this always happens incident after incident, so I
need to run portage multiple times.

Is there a way to instruct portage to just say: "Ok, here is a
configuration fix necessary, maybe a use flag must be added, but let's
assume, the user does this and the use flag is set now. What do I need
to do next."

Without checking it, this behaviour seems to be more the case in prior
portage version (complaining about multiple incidents at once).

Best,
Gerion

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

Re: [gentoo-user] Portage: Complaining about multiple incidents at once

[Ashley Dixon]

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

On Sun, Apr 19, 2020 at 01:03:55PM +0200, Gerion Entrup wrote:
> Portage then often stops, saying a dependency keyword is missing or a
> useflag etc. However, this always happens incident after incident, so I
> need to run portage multiple times.
> 
> Is there a way to instruct portage to just say: "Ok, here is a
> configuration fix necessary, maybe a use flag must be added, but let's
> assume, the user does this and the use flag is set now. What do I need
> to do next."

Have you seen the --skipfirst option, to be used in  conjunction  with  --resume
(-r) ? Taking directly from the man page of emerge:

        --skipfirst
                This option is only valid when used with --resume.   It  removes
                the  first  package  in  the  resume  list.   Dependencies   are
                recalculated  for  remaining  packages   and   any   that   have
                unsatisfied dependencies or are  masked  will  be  automatically
                dropped.    Also   see   the   related   --keep-going    option.

        --resume, -r
                Resumes the most recent merge list that has been aborted due  to
                an error.  This re-uses the  arguments  and  options  that  were
                given with the original command that's being  resumed,  and  the
                user  may  also  provide   additional   options   when   calling
                --resume.  It is an error to provide atoms or sets as  arguments
                to --resume, since the arguments from the  resumed  command  are
                used instead.  Please note that this operation will only  return
                an error on failure.  If there is nothing  for  portage  to  do,
                then portage will exit with a message and a  success  condition.
                A resume list will  persist  until  it  has  been  completed  in
                entirety or until another aborted merge list replaces  it.   The
                resume history is capable of storing two merge lists.  After one
                resume list completes, it is possible to  invoke  --resume  once
                again in order to resume an older list.  The  resume  lists  are
                stored  in  /var/cache/edb/mtimedb,  and   may   be   explicitly
                discarded by running `emaint --fix cleanresume` (see emaint(1)).

Sorry  if  I've   misunderstood   your   intentions;   the   wording   of   your
question was a  little  difficult  for  me  to  comprehend,  but  I  think  this
is what you want ;-)

-- 

Ashley Dixon
suugaku.co.uk

2A9A 4117
DA96 D18A
8A7B B0D2
A30E BF25
F290 A8AA


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

Re: [gentoo-user] Portage: Complaining about multiple incidents at once

[Mickaël Bucas]

Le dim. 19 avr. 2020 à 13:03, Gerion Entrup <gerion.entrup@flump.de> a écrit :
>
> Hi,
>
> does Portage have a "don't stop" mode?
>
> With that I mean the following:
> I'm doing updates with
> emerge -auND world --keep-going --quiet-build --verbose-conflicts
>
> Portage then often stops, saying a dependency keyword is missing or a
> useflag etc. However, this always happens incident after incident, so I
> need to run portage multiple times.
>
> Is there a way to instruct portage to just say: "Ok, here is a
> configuration fix necessary, maybe a use flag must be added, but let's
> assume, the user does this and the use flag is set now. What do I need
> to do next."
>
> Without checking it, this behaviour seems to be more the case in prior
> portage version (complaining about multiple incidents at once).
>
> Best,
> Gerion

Hi Gerion

I believe that what you are looking for are the options starting with
--autounmask, which affect the initial analysis of the build tree,
which is the source of the complaints about missing keywords or USE
flags.
The --keep-going option does a great job at continuing to build other
packages when one build fails.

There are a bunch of them so I don't know how much you'd like to use
but it seems tailored to go forward in almost any situation !
They are well described in "man emerge"
--autounmask [ y | n ]
--autounmask-backtrack < y | n >
--autounmask-continue [ y | n ]
--autounmask-only [ y | n ]
--autounmask-unrestricted-atoms [ y | n ]
--autounmask-keep-keywords [ y | n ]
--autounmask-keep-masks [ y | n ]
--autounmask-license < y | n >
--autounmask-use < y | n >
--autounmask-write [ y | n ]

Adding --backtrack=COUNT with COUNT > 10 (the default value) may push
Portage to look forward a bit more.

However, as I don't use them, I don't know what stability you could
expect from your system after activating any or all of them.

Best regards
Mickaël Bucas