Difference between revisions of "News:Portage Git Sync Fix"
Jump to navigation
Jump to search
(test edit) |
|||
| Line 14: | Line 14: | ||
# emerge --oneshot --update portage | # emerge --oneshot --update portage | ||
}} | }} | ||
<code>git pull</code> only needed once, so that portage tree getting all objects and fixed portage ebuild. After updating portage, updating of portage tree should be good by <code>emerge --sync</code> as we all used to do. | <code>git pull</code> only needed once, so that portage tree getting all objects and fixed portage ebuild. After updating portage, updating of portage tree should be good by <code>emerge --sync</code> as we all used to do. | ||
[1] https://bugs.gentoo.org/show_bug.cgi?id=552814 | [1] https://bugs.gentoo.org/show_bug.cgi?id=552814 | ||
Latest revision as of 20:54, November 19, 2016
Portage Git Sync Fix
- upstream experimental changes in
git.pymodule which added into portage and in portage ebuilds caused a regression, which result in missing objects in portage tree or other artifacts. We reverted this to older stable behavior. [1] Update steps are:
root # cd /usr/portage root # git pull root # emerge --oneshot --update portage
git pull only needed once, so that portage tree getting all objects and fixed portage ebuild. After updating portage, updating of portage tree should be good by emerge --sync as we all used to do.
[1] https://bugs.gentoo.org/show_bug.cgi?id=552814