From: "JosA MarAa Alonso (nimiux)" <nimiux@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo commit in xml/htdocs/proj/es/portage/doc: manually-fixing-portage.xml
Date: Tue, 21 Dec 2010 16:02:25 +0000 (UTC) [thread overview]
Message-ID: <20101221160225.4213120054@flycatcher.gentoo.org> (raw)
nimiux 10/12/21 16:02:25
Modified: manually-fixing-portage.xml
Log:
Update for portage-2.1.9.25 stabilization.
Revision Changes Path
1.4 xml/htdocs/proj/es/portage/doc/manually-fixing-portage.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/es/portage/doc/manually-fixing-portage.xml?rev=1.4&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/es/portage/doc/manually-fixing-portage.xml?rev=1.4&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/proj/es/portage/doc/manually-fixing-portage.xml?r1=1.3&r2=1.4
Index: manually-fixing-portage.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/es/portage/doc/manually-fixing-portage.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- manually-fixing-portage.xml 30 Nov 2010 22:17:14 -0000 1.3
+++ manually-fixing-portage.xml 21 Dec 2010 16:02:25 -0000 1.4
@@ -1,6 +1,8 @@
<?xml version='1.0' encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/es/portage/doc/manually-fixing-portage.xml,v 1.3 2010/11/30 22:17:14 nimiux Exp $ -->
-<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/es/portage/doc/manually-fixing-portage.xml,v 1.4 2010/12/21 16:02:25 nimiux Exp $ -->
+<!DOCTYPE guide SYSTEM "/dtd/guide.dtd" [
+ <!ENTITY stable_version "2.1.9.25">
+]>
<guide link="/proj/es/portage/doc/manually-fixing-portage.xml" lang="es">
@@ -52,9 +54,9 @@
<p>
Lo primero que debe hacer es obtener un tarball de una versión
actualizada de Portage. En este documento usaremos
-<e>portage-2.1.9.24</e> como ejemplo (ya que es la versión estable al
-momento de edición del documento), por favor reemplácelo con una
-versión presente en el árbol Portage en la medida de lo posible.
+<e>portage-&stable_version;</e> como ejemplo (ya que es la versión
+estable al momento de edición del documento), por favor reemplácelo
+con una versión presente en el árbol Portage en la medida de lo posible.
</p>
<table>
@@ -74,8 +76,8 @@
<ti>>= Python 2.6</ti>
<ti>
<uri
- link="http://distfiles.gentoo.org/distfiles/portage-2.1.9.24.tar.bz2">
- portage-2.1.9.24.tar.bz2</uri>
+ link="http://distfiles.gentoo.org/distfiles/portage-&stable_version;.tar.bz2">
+ portage-&stable_version;.tar.bz2</uri>
</ti>
</tr>
</table>
@@ -84,7 +86,7 @@
Si su versión instalada de Python reportada por <c>python -V</c> es
menor que 2.6, entonces debe elegir una versión de Portage compatible
con ésta. Si tienes por lo menos Python 2.6 entonces use
-<e>portage-2.1.9.24.tar.bz2</e>. Si tiene python 2.4 o 2.5 entonces
+<e>portage-&stable_version;.tar.bz2</e>. Si tiene python 2.4 o 2.5 entonces
use <e>portage-2.1.6.tar.bz2</e>.
</warn>
@@ -97,12 +99,12 @@
</p>
<pre caption="Obteniendo el tarball de Portage con wget">
-# <i>wget -P /usr/portage/distfiles http://distfiles.gentoo.org/distfiles/portage-2.1.9.24.tar.bz2</i>
+# <i>wget -P /usr/portage/distfiles http://distfiles.gentoo.org/distfiles/portage-&stable_version;.tar.bz2</i>
</pre>
<p>
Después de ésto el tarball debería estar disponible como
-<path>/usr/portage/distfiles/portage-2.1.9.24.tar.bz2</path>.
+<path>/usr/portage/distfiles/portage-&stable_version;.tar.bz2</path>.
</p>
</body>
@@ -121,7 +123,7 @@
# <i>cd /root</i>
# <i>mkdir portage-recover</i>
# <i>cd portage-recover</i>
-# <i>tar xfj /usr/portage/distfiles/portage-2.1.9.24.tar.bz2</i>
+# <i>tar xfj /usr/portage/distfiles/portage-&stable_version;.tar.bz2</i>
</pre>
<p>
@@ -131,7 +133,7 @@
</p>
<pre caption="Reemplazando los archivos instalados">
-# <i>cd /root/portage-recover/portage-2.1.9.24</i>
+# <i>cd /root/portage-recover/portage-&stable_version;</i>
# <i>rm -rf /usr/lib/portage/*</i>
# <i>cp -R pym bin /usr/lib/portage/</i>
</pre>
next reply other threads:[~2010-12-21 16:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 16:02 JosA MarAa Alonso (nimiux) [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-24 8:27 [gentoo-commits] gentoo commit in xml/htdocs/proj/es/portage/doc: manually-fixing-portage.xml JosA MarAa Alonso (nimiux)
2013-09-10 17:02 JosA MarAa Alonso (nimiux)
2013-06-08 18:55 JosA MarAa Alonso (nimiux)
2013-04-25 18:13 JosA MarAa Alonso (nimiux)
2013-03-20 13:41 JosA MarAa Alonso (nimiux)
2013-03-01 20:56 JosA MarAa Alonso (nimiux)
2013-02-10 19:35 JosA MarAa Alonso (nimiux)
2012-10-28 15:21 Sven Vermeulen (swift)
2012-08-12 19:05 JosA MarAa Alonso (nimiux)
2012-08-12 19:04 JosA MarAa Alonso (nimiux)
2012-03-19 14:00 JosA MarAa Alonso (nimiux)
2012-02-01 22:07 JosA MarAa Alonso (nimiux)
2011-12-29 13:19 JosA MarAa Alonso (nimiux)
2011-08-30 16:35 JosA MarAa Alonso (nimiux)
2011-07-03 21:00 JosA MarAa Alonso (nimiux)
2011-03-17 16:47 JosA MarAa Alonso (nimiux)
2010-11-30 22:17 JosA MarAa Alonso (nimiux)
2010-08-20 1:33 JosA MarAa Alonso (nimiux)
2008-05-18 22:14 John Christian Stoddart (chiguire)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101221160225.4213120054@flycatcher.gentoo.org \
--to=nimiux@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox