diff options
author | Julian Andres Klode <julian.klode@canonical.com> | 2019-06-17 11:37:57 +0200 |
---|---|---|
committer | Julian Andres Klode <julian.klode@canonical.com> | 2019-06-17 11:37:57 +0200 |
commit | 0cef11a38f14432bf36bf34225ec06c52b2cfb65 (patch) | |
tree | abc4d838422822da23cf69ef3c7df1665c76fac0 /doc/po/es.po | |
parent | d88af368d2a45bf9490fc629edbaa111da8a26cf (diff) |
Release 1.9.0 to experimental1.9.0
Diffstat (limited to 'doc/po/es.po')
-rw-r--r-- | doc/po/es.po | 53 |
1 files changed, 46 insertions, 7 deletions
diff --git a/doc/po/es.po b/doc/po/es.po index 9829f0b27..73deb9069 100644 --- a/doc/po/es.po +++ b/doc/po/es.po @@ -38,7 +38,7 @@ msgid "" msgstr "" "Project-Id-Version: apt-doc 1.0.5\n" "Report-Msgid-Bugs-To: APT Development Team <deity@lists.debian.org>\n" -"POT-Creation-Date: 2019-02-04 15:34+0100\n" +"POT-Creation-Date: 2019-06-17 11:37+0200\n" "PO-Revision-Date: 2014-07-04 01:31+0200\n" "Last-Translator: Omar Campagne <ocampagne@gmail.com>\n" "Language-Team: Debian l10n Spanish <debian-l10n-spanish@lists.debian.org>\n" @@ -860,6 +860,21 @@ msgid "" "command> are also never proposed for automatic removal." msgstr "" +#. type: Content of: <refentry><refsect1><variablelist><varlistentry><listitem><para> +#: apt.8.xml +msgid "" +"<option>satisfy</option> satisfies dependency strings, as used in Build-" +"Depends. It also handles conflicts, by prefixing an argument with <literal>" +"\"Conflicts: \"</literal>." +msgstr "" + +#. type: Content of: <refentry><refsect1><variablelist><varlistentry><listitem><para> +#: apt.8.xml +msgid "" +"Example: <literal>apt satisfy \"foo, bar (>= 1.0)\" \"Conflicts: baz, fuzz" +"\"</literal>" +msgstr "" + #. type: Content of: <refentry><refsect1><variablelist><varlistentry><term> #: apt.8.xml msgid "(&apt-cache;)" @@ -1349,6 +1364,29 @@ msgstr "" #. type: Content of: <refentry><refsect1><variablelist><varlistentry><listitem><para> #: apt-get.8.xml msgid "" +"<literal>satisfy</literal> causes apt-get to satisfy the given dependency " +"strings. The dependency strings may have build profiles and architecture " +"restriction list as in build dependencies. They may optionally be prefixed " +"with <literal>\"Conflicts: \"</literal> to unsatisfy the dependency string. " +"Multiple strings of the same type can be specified." +msgstr "" + +#. type: Content of: <refentry><refsect1><variablelist><varlistentry><listitem><para> +#: apt-get.8.xml +msgid "" +"Example: <literal>apt-get satisfy \"foo\" \"Conflicts: bar\" \"baz (>> " +"1.0) | bar (= 2.0), moo\"</literal>" +msgstr "" + +#. type: Content of: <refentry><refsect1><variablelist><varlistentry><listitem><para> +#: apt-get.8.xml +msgid "" +"The legacy operator '</>' is not supported, use '<=/>=' instead." +msgstr "" + +#. type: Content of: <refentry><refsect1><variablelist><varlistentry><listitem><para> +#: apt-get.8.xml +msgid "" "<literal>check</literal> is a diagnostic tool; it updates the package cache " "and checks for broken dependencies." msgstr "" @@ -2860,10 +2898,11 @@ msgid "" "Note that if usage of <command>apt-key</command> is desired the additional " "installation of the GNU Privacy Guard suite (packaged in <package>gnupg</" "package>) is required. For this reason alone the programmatic usage " -"(especially in package maintainer scripts!) is strongly discouraged. Further " -"more the output format of all commands is undefined and can and does change " -"whenever the underlying commands change. <command>apt-key</command> will try " -"to detect such usage and generates warnings on stderr in these cases." +"(especially in package maintainer scripts!) is strongly discouraged. " +"Further more the output format of all commands is undefined and can and does " +"change whenever the underlying commands change. <command>apt-key</command> " +"will try to detect such usage and generates warnings on stderr in these " +"cases." msgstr "" #. type: Content of: <refentry><refsect1><title> @@ -9991,8 +10030,8 @@ msgid "" "from polluting its cache with (big) .deb files." msgstr "" "Se proporcionan tres opciones de configuración para el control de la caché " -"con proxy cachés conformes an HTTP/1.1. <literal>No-Cache</literal> indica al " -"proxy que nunca utilice la respuesta cacheada. <literal>Max-Age</literal> " +"con proxy cachés conformes an HTTP/1.1. <literal>No-Cache</literal> indica " +"al proxy que nunca utilice la respuesta cacheada. <literal>Max-Age</literal> " "define la máxima antigüedad permitida (en segundos) de un fichero de índice " "en la caché de un proxy. <literal>No-Store</literal> define que el proxy no " "debe almacenar ficheros del archivo en su caché, que se puede utilizar para " |