fedora-docs-l10n/packaging-guidelines

master/pages/Conflicts

	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

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 process	Translations can be made directly. Translation suggestions can be made. Any authenticated user can contribute. The translation uses bilingual files.
Translation license	Creative Commons Attribution Share Alike 3.0 Unported
Source code repository	`ssh://pagure.io/fedora-docs-l10n/packaging-guidelines.git`
Repository branch	master
Last remote commit	Update translation files `5835af862` Weblate authored an hour ago
Weblate repository	`https://translate.fedoraproject.org/git/fedora-docs-l10n-packaging-guidelines/nav/`
File mask	`po/*/master/pages/Conflicts.po`

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		354		10,704		68,172
Source		59		1,784		11,362
Translated	16%	60	16%	1,785	16%	11,371
Needs editing	0%	0	0%	0	0%	0
Read-only	16%	59	16%	1,784	16%	11,362
Failing checks	0%	0	0%	0	0%	0
Strings with suggestions	1%	3	1%	3	1%	27
Untranslated strings	83%	294	83%	8,919	83%	56,801

Last 12 months Previous

Activity in last 12 months


Jul	Aug	Sep	Oct	Nov	Dec	Jan	Feb	Mar	Apr	May	Jun

Quick numbers

10,704

Hosted words

354

Hosted strings

16%

Translated

0

Contributors

and previous 30 days

Trends of last 30 days

—

Hosted words

+16%

—

Hosted strings

+16%

—

Translated

−3%

—

Contributors

—

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>=2022-05-31 AND NOT changed_by:anonymous`	Add
Translated strings	`state:>=translated`	Add
Strings with comments	`has:comment`	Add
Strings with any failing checks	`has:check`	Add
Strings with suggestions from others	`has:suggestion AND NOT suggestion_author:anonymous`	Add
Approved strings with suggestions	`state:approved AND has:suggestion`	Add
All untranslated strings added the past month	`added:>=2022-05-31 AND state:<=needs-editing`	Add
Translated strings in a certain language	`is:translated AND language:en`	Add

None New strings to translate fedora-docs-l10n/packaging-guidelines / master/pages/Conflicts — Chinese (Simplified)	59 new strings to translate appeared to the translation. a month ago
None Resource update fedora-docs-l10n/packaging-guidelines / master/pages/Conflicts — Chinese (Simplified)	File `po/zh_Hans/master/pages/Conflicts.po` was added. a month ago
None String updated in the repository fedora-docs-l10n/packaging-guidelines / master/pages/Conflicts — Chinese (Simplified)	English 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. Chinese (Simplified) a month ago
None String updated in the repository fedora-docs-l10n/packaging-guidelines / master/pages/Conflicts — Chinese (Simplified)	English Other Uses of Conflicts: Chinese (Simplified) a month ago
None String updated in the repository fedora-docs-l10n/packaging-guidelines / master/pages/Conflicts — Chinese (Simplified)	English 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. Chinese (Simplified) a month ago
None String updated in the repository fedora-docs-l10n/packaging-guidelines / master/pages/Conflicts — Chinese (Simplified)	English 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]. Chinese (Simplified) a month ago
None String updated in the repository fedora-docs-l10n/packaging-guidelines / master/pages/Conflicts — Chinese (Simplified)	English Conflicting Package Names Chinese (Simplified) a month ago
None String updated in the repository fedora-docs-l10n/packaging-guidelines / master/pages/Conflicts — Chinese (Simplified)	English 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. Chinese (Simplified) a month ago
None String updated in the repository fedora-docs-l10n/packaging-guidelines / master/pages/Conflicts — Chinese (Simplified)	English Standard Commands Chinese (Simplified) a month ago
None String updated in the repository fedora-docs-l10n/packaging-guidelines / master/pages/Conflicts — Chinese (Simplified)	English 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. Chinese (Simplified) a month ago

Browse all component changes