|
42.
|
|
|
Couldn't initizalize rpm database at %s
|
|
|
|
Couldn't initialise rpm database at %s
|
|
Translated and reviewed by
Dave Walker
|
In upstream: |
|
Couldn't initizalize rpm database at %s
|
|
|
Suggested by
Rehan Khan
|
|
|
|
Located in
smart/backends/rpm/base.py:70
|
|
43.
|
|
|
Initialized new rpm database at %s
|
|
|
|
Initialised new rpm database at %s
|
|
Translated and reviewed by
Dave Walker
|
In upstream: |
|
Initialized new rpm database at %s
|
|
|
Suggested by
Rehan Khan
|
|
|
|
Located in
smart/backends/rpm/base.py:73
|
|
167.
|
|
|
Remote repository with slackware packages.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
Remote repository with slackware packages.
|
|
Translated and reviewed by
Robert Readman
|
In upstream: |
|
Remote repository with Slackware packages.
|
|
|
Suggested by
Rehan Khan
|
|
|
|
Located in
smart/channels/slack_site_info.py:28
|
|
172.
|
|
|
Installed packages in a slackware system.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
Installed packages in a slackware system.
|
|
Translated and reviewed by
Robert Readman
|
In upstream: |
|
Installed packages in a Slackware system.
|
|
|
Suggested by
Rehan Khan
|
|
|
|
Located in
smart/channels/slack_sys_info.py:28
|
|
190.
|
|
|
argument is an alias and one or more key=value pairs defining a channel, or a filename/url pointing to a channel description in the same format used by --show, or a directory path where autodetection will be tried
|
|
|
|
argument is an alias and one or more key=value pairs defining a channel, or a filename/url pointing to a channel description in the same format used by --show, or a directory path where autodetection will be tried
|
|
Translated and reviewed by
Robert Readman
|
In upstream: |
|
argument is an alias and one or more key=value pairs defining a channel or a filename/url pointing to a channel description in the same format used by --show or a directory path where autodetection will be tried
|
|
|
Suggested by
Rehan Khan
|
|
|
|
Located in
smart/commands/channel.py:103
|
|
191.
|
|
|
argument is an alias, and one or more key=value pairs modifying a channel
|
|
|
|
argument is an alias, and one or more key=value pairs modifying a channel
|
|
Translated and reviewed by
Robert Readman
|
In upstream: |
|
argument is an alias and one or more key=value pairs modifying a channel
|
|
|
Suggested by
Rehan Khan
|
|
|
|
Located in
smart/commands/channel.py:110
|
|
194.
|
|
|
show channels with given aliases, or all channels if no arguments were given
|
|
|
|
show channels with given aliases, or all channels if no arguments were given
|
|
Translated and reviewed by
Robert Readman
|
In upstream: |
|
show channels with given aliases or all channels if no arguments were given
|
|
|
Suggested by
Rehan Khan
|
|
|
|
Located in
smart/commands/channel.py:119
|
|
264.
|
|
|
Argument is not a file nor url: %s
|
|
|
|
Argument is not a file nor url: %s
|
|
Translated and reviewed by
Robert Readman
|
In upstream: |
|
Argument is not a file nor an url: %s
|
|
|
Suggested by
Rehan Khan
|
|
|
|
Located in
smart/commands/download.py:173
|
|
273.
|
|
|
include additional information about changes,when possible
|
|
|
|
include additional information about changes,when possible
|
|
Translated and reviewed by
Robert Readman
|
In upstream: |
|
include additional information about changes when possible
|
|
|
Suggested by
Rehan Khan
|
|
|
|
Located in
smart/commands/fix.py:60 smart/commands/install.py:62
smart/commands/reinstall.py:58 smart/commands/remove.py:57
smart/commands/upgrade.py:75
|
|
313.
|
|
|
This command allows one to manipulate mirrors. Mirrors are URLs
that supposedly provide the same contents as are available in
other URLs, named origins in this help text. There is no internal
restriction on the kind of information which is mirrored. Once
an origin URL is provided, and one or more mirror URLs are
provided, these mirrors will be considered for any file which
is going to be fetched from an URL starting with the origin URL.
Whether the mirror will be chosen or not will depend on the
history of downloads from this mirror and from other mirrors for
the same URL, since mirrors are automatically balanced so that
the fastest mirror and with less errors is chosen. When errors
occur, the next mirror is tried.
For instance, if a mirror "http://mirror.url/path/" is provided
for the origin "ftp://origin.url/other/path/", and a file in
"ftp://origin.url/other/path/subpath/somefile" is going to be
fetched, the mirror will be considered for being used, and the
URL "http://mirror.url/path/subpath/somefile" will be used if
the mirror is chosen. Notice that strings are compared and
replaced without any pre-processing, so that it's possible to
use URLs ending in prefixes of directory entries.
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
This command allows one to manipulate mirrors. Mirrors are URLs
that supposedly provide the same contents as are available in
other URLs, named origins in this help text. There is no internal
restriction on the kind of information which is mirrored. Once
an origin URL is provided, and one or more mirror URLs are
provided, these mirrors will be considered for any file which
is going to be fetched from an URL starting with the origin URL.
Whether the mirror will be chosen or not will depend on the
history of downloads from this mirror and from other mirrors for
the same URL, since mirrors are automatically balanced so that
the fastest mirror and with less errors is chosen. When errors
occur, the next mirror is tried.
For instance, if a mirror "http://mirror.url/path/" is provided
for the origin "ftp://origin.url/other/path/", and a file in
"ftp://origin.url/other/path/subpath/somefile" is going to be
fetched, the mirror will be considered for being used, and the
URL "http://mirror.url/path/subpath/somefile" will be used if
the mirror is chosen. Notice that strings are compared and
replaced without any pre-processing, so that it's possible to
use URLs ending in prefixes of directory entries.
|
|
Translated and reviewed by
Robert Readman
|
In upstream: |
|
This command allows one to manipulate mirrors. Mirrors are URLs
that supposedly provide the same contents as are available in
other URLs, named origins in this help text. There is no internal
restriction on the kind of information which is mirrored. Once
an origin URL is provided, and one or more mirror URLs are
provided, these mirrors will be considered for any file which
is going to be fetched from an URL starting with the origin URL.
Whether the mirror will be chosen or not will depend on the
history of downloads from this mirror and from other mirrors for
the same URL, since mirrors are automatically balanced so that
the fastest mirror and with least errors is chosen. When errors
occur, the next mirror is tried.
For instance, if a mirror "http://mirror.url/path/" is provided
for the origin "ftp://origin.url/other/path/", and a file in
"ftp://origin.url/other/path/subpath/somefile" is going to be
fetched, the mirror will be considered for being used, and the
URL "http://mirror.url/path/subpath/somefile" will be used if
the mirror is chosen. Notice that strings are compared and
replaced without any pre-processing, so that it's possible to
use URLs ending in prefixes of directory entries.
|
|
|
Suggested by
Rehan Khan
|
|
|
|
Located in
smart/commands/mirror.py:32
|