Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English CC-BY-SA-3.0 0 0 0 0 0 0 0
Chinese (Simplified) CC-BY-SA-3.0 0% 59 1,784 11,362 59 0 0 0
Finnish CC-BY-SA-3.0 1% 58 1,783 11,353 58 0 0 0
French CC-BY-SA-3.0 0% 59 1,784 11,362 59 0 1 0
Japanese CC-BY-SA-3.0 0% 59 1,784 11,362 59 0 1 0
Portuguese (Brazil) CC-BY-SA-3.0 0% 59 1,784 11,362 59 0 1 0
Spanish CC-BY-SA-3.0 0% 59 1,784 11,362 59 0 1 0
Please sign in to see the alerts.

Overview

Project website pagure.io/fedora-docs-l10n/packaging-guidelines
Instructions for translators

Mailing list for translators: <<trans@lists.fedoraproject.org>
Translation license Creative Commons Attribution Share Alike 3.0 Unported
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository ssh://pagure.io/fedora-docs-l10n/packaging-guidelines.git
Repository branch master
Last remote commit automatic update of pot/po files 355fc8915
♪ I'm a bot, bot, bot ♪ authored 17 hours ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-packaging-guidelines/nav/
File mask po/*/master/pages/Conflicts.po
8 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 413 12,488 79,534
Source 59 1,784 11,362
Translated 14% 60 14% 1,785 14% 11,371
Needs editing 0% 0 0% 0 0% 0
Read-only 14% 59 14% 1,784 14% 11,362
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 1% 4 1% 4 1% 36
Untranslated strings 85% 353 85% 10,703 85% 68,163
Last 12 months Previous

Activity in last 12 months

3 changes 6 changes 61 changes 1 change 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 3 changes 0 changes 0 changes 0 changes 0 changes 62 changes 0 changes 0 changes 3 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

Quick numbers

12,488
Hosted words
413
Hosted strings
14%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+14%
—
Contributors
—
User avatar mt:weblate-translation-memory

Suggestion added

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Conflicts
  3. Spanish
Conflicts
Conflictos
5 months ago
User avatar None

Resource updated

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Conflicts
  3. Spanish
File po/es/master/pages/Conflicts.po was added. 5 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Conflicts
  3. Spanish
If you find yourself in a situation where you feel that your package has to conflict with another package (either explicitly or implicitly), but does not fit the documented accepted cases above, then you need to make your case to the https://pagure.io/packaging-committee[Fedora Packaging Committee]. If they agree, then, and only then can you use `+Conflicts:+` in a Fedora package. Remember, whenever you use `+Conflicts:+`, you are also required to include the reasoning in a comment next to the `+Conflicts:+` entry, so that it will be abundantly clear why it needed to exist.
 
5 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Conflicts
  3. Spanish
Other Uses of Conflicts:
 
5 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Conflicts
  3. Spanish
Renaming packages and replacing them with others can be difficult if it has to occur at a later time (for instance, upgrade paths can become complex in these situations) so it is even more important to be aware of potential conflicts here than it is with filenames.
 
5 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Conflicts
  3. Spanish
Just as files can conflict, package names can as well. Conflicting package names *MUST* be resolved. Package names which differ only in case are still considered to be conflicting. You should follow the same basic steps outlined in xref:#_approaching_upstream[Approaching Upstream].
 
5 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Conflicts
  3. Spanish
Conflicting Package Names
 
5 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Conflicts
  3. Spanish
Common names are allowed for standard commands since those will be the only commands to implement them. Standard commands include things provided for in published and widely implemented standards like POSIX and de facto standards such as a program that has traditionally been shipped with a certain filename as part of a large number of Unix variants. If in doubt, send a message to fedora-devel-list[at]redhat.com with details of what standards the command appears in, how long it's been available on what Unix systems, and whether you've found any conflicting programs that implement a substantially different command with the same filename.
 
5 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Conflicts
  3. Spanish
Standard Commands
 
5 months ago
User avatar None

String updated in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/Conflicts
  3. Spanish
In the second case, where there is no known package to conflict with at this time, it is up to the packager to make a decision. Note that it is encouraged that you at least speak to upstream about the potential for conflicts. However, we can hope that any later projects that attempt to use that name can be persuaded to rename based on this project being around longer.
 
5 months ago
Browse all component changes