Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 487000 - emerge --noreplace doesn't update world file if some ebuild fails from a list of (dependent) builds.
Summary: emerge --noreplace doesn't update world file if some ebuild fails from a li...
Status: RESOLVED WONTFIX
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core - Interface (emerge) (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-05 10:59 UTC by Nico Baggus
Modified: 2018-01-07 22:17 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nico Baggus 2013-10-05 10:59:21 UTC
During a rebuild of a laptop, starting with a stage3 running
emerge --noreplace -DN $( cat /home/originalworld )

some ebuilds failed (they are separate [ dependency ] issues ). 
The world file (/var/lib/portage/world ) isn't updated.

Only when emerge completes succesfully the world file gets updated.

Reproducible: Always

Steps to Reproduce:
1.starting with a stage3 + world file from another laptop.
2.emerge --noreplace -DN $( cat /home/originalworld )
3.
Actual Results:  
world file only updated on total success.

Expected Results:  
all successful merged items mentioned in the world file.
Comment 1 Nico Baggus 2018-01-07 18:12:34 UTC
obviously something that isn't being taken care of or cared about
Closing to prevent polution.
Comment 2 Zac Medico gentoo-dev 2018-01-07 22:17:10 UTC
Normally, packages are added to the world file in the EbuildMerge._merge_exit method, immediately after the package is installed. It calls the create_world_atom function, which skips packages that are in the system set.