/[gentoo]/xml/htdocs/proj/en/portage/doc/manually-fixing-portage.xml
Gentoo

Diff of /xml/htdocs/proj/en/portage/doc/manually-fixing-portage.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.7 Revision 1.8
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/portage/doc/manually-fixing-portage.xml,v 1.7 2007/05/30 23:54:07 genone Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/portage/doc/manually-fixing-portage.xml,v 1.8 2007/09/19 23:19:31 zmedico Exp $ -->
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4 4
5<guide link="/proj/en/portage/doc/manually-fixing-portage.xml"> 5<guide link="/proj/en/portage/doc/manually-fixing-portage.xml">
6 6
7<title>Manually fixing broken portage installations</title> 7<title>Manually fixing broken portage installations</title>
8 8
9<author> 9<author>
10 <mail link="genone@gentoo.org">Marius Mauch</mail> 10 <mail link="genone@gentoo.org">Marius Mauch</mail>
11</author> 11</author>
12 12
13<abstract> 13<abstract>
14This document attempts to help people to manually fix a broken sys-apps/portage 14This document attempts to help people to manually fix a broken sys-apps/portage
15installation. 15installation.
16</abstract> 16</abstract>
17 17
87files of your existing installation with the ones from the tarball (in most 87files of your existing installation with the ones from the tarball (in most
88cases anyway). To do so please run: 88cases anyway). To do so please run:
89</p> 89</p>
90 90
91<pre caption="Replacing installed files"> 91<pre caption="Replacing installed files">
92# <i>cd /root/portage-recover/portage-2.1.1</i> 92# <i>cd /root/portage-recover/portage-2.1.1</i>
93# <i>cp -R pym bin /usr/lib/portage/</i> 93# <i>cp -R pym bin /usr/lib/portage/</i>
94</pre> 94</pre>
95 95
96<note> 96<note>
97If you accidently unmerged portage before or lost 97If you accidently unmerged portage before or lost
98<path>/etc/make.globals</path> for other reasons you should also copy 98<path>/etc/make.globals</path> for other reasons you should also copy
99<path>cnf/make.globals</path> back into <path>/etc</path>, otherwise 99<path>cnf/make.globals</path> back into <path>/etc</path>, otherwise
100portage might behave in strange ways. 100portage might behave in strange ways.
101</note> 101</note>
102<note>
103If the previous version of portage was less than 2.1 then you should now run
104<c>emerge --metadata</c> before continuing to the next step. This is necessary
105in order to convert the ebuild metadata to the new format that is used by
106portage 2.1 and above. It is okay to run this command even if you are not sure
107what the previous version of portage was.
108</note>
102 109
103<p> 110<p>
104Now you should have a working portage install again. To ensure a consistent 111Now you should have a working portage install again. To ensure a consistent
105system state however you should now run <c>emerge sys-apps/portage</c> again 112system state however you should now run <c>emerge sys-apps/portage</c> again
106immediately. 113immediately.
107</p> 114</p>
108 115
109<p> 116<p>
110If you get a <e>command not found</e> error message when you try to run 117If you get a <e>command not found</e> error message when you try to run
111<c>emerge</c> you have to recreate the symlink: 118<c>emerge</c> you have to recreate the symlink:
112</p> 119</p>
113 120
114<pre caption="Recreating the emerge symlink"> 121<pre caption="Recreating the emerge symlink">
115# <i>ln -s ../lib/portage/bin/emerge /usr/bin/emerge</i> 122# <i>ln -s ../lib/portage/bin/emerge /usr/bin/emerge</i>
116</pre> 123</pre>

Legend:
Removed from v.1.7  
changed lines
  Added in v.1.8

  ViewVC Help
Powered by ViewVC 1.1.20