822102 – emerge --keep-going should skip rebuilding packages brought into the dependency tree by a failed update

Bug 822102 - emerge --keep-going should skip rebuilding packages brought into the dependency tree by a failed update

Summary: emerge --keep-going should skip rebuilding packages brought into the dependen...

Status:	RESOLVED DUPLICATE of bug 629952

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Core (show other bugs)
Hardware:	AMD64 Linux

Importance:	Normal enhancement (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:	373807
	Show dependency tree

Reported:	2021-11-06 12:15 UTC by Progenyx
Modified:	2022-03-05 07:37 UTC (History)
CC List:	3 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Progenyx 2021-11-06 12:15:52 UTC

Upon resuming merge the dependency tree still contains a package which was supposed to be rebuild only after the update of another. 

I started an update last night with the following excerpt:


...
[ebuild  r  U  ] dev-libs/libgit2-1.3.0 [1.1.1]
...
[ebuild  rR   ~] dev-util/cargo-ebuild-0.4.0
...

The following packages are causing rebuilds:

  (dev-libs/libgit2-1.3.0:0/1.3::local, ebuild scheduled for merge) causes rebuilds for:
    (dev-util/cargo-ebuild-0.4.0:0/0::local, ebuild scheduled for merge)


What I noticed the next morning was that libgit2 had failed yet carbo-ebuild was still rebuilt.

I realize this is a very small, barely noticeable inconvenience but this could happen with packages that bring in many large programs, e.g. poppler or re2 come to mind.

Reproducible: Always

Comment 1 Sam James archtester

2022-03-05 07:37:01 UTC


*** This bug has been marked as a duplicate of bug 629952 ***