Source strings

112 Strings 100%
Browse Translate
2,887 Words 100%
19,808 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
112 2,887 19,808
All strings Browse Translate Zen
112 2,887 19,808
Read-only strings Browse Translate Zen
1 1 8
Strings with any failing checks Browse Translate Zen
1 1 8
Failing check: Multiple failing checks Browse Translate Zen

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 a233f9785
♪ I'm a bot, bot, bot ♪ authored 6 days ago
Last commit in Weblate Translated using Weblate (Spanish) 76319285b
User avatar vareli authored 4 days ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-packaging-guidelines/nav/
File mask po/*/master/pages/Versioning.po
Translation file Download pot/master/pages/Versioning.pot
Last change June 9, 2023, 10:07 p.m.
Last author None
4 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 112 2,887 19,808
Translated 100% 112 100% 2,887 100% 19,808
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 112 100% 2,887 100% 19,808
Failing checks 1% 1 1% 1 1% 8
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 0% 0 0% 0 0% 0
Last 12 months Previous

Activity in last 12 months

0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 1 change 0 changes 1 change 0 changes 2 changes 0 changes 0 changes 0 changes 26 changes 0 changes 2 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes
Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep

Quick numbers

2,887
Hosted words
112
Hosted strings
100%
Translated
0
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
—
Contributors
—
User avatar None

Resource updated
The “pot/master/pages/Versioning.pot” file was changed. a year ago
User avatar None

String updated in the repository
The method described in this section is deprecated, but **may** be used. As mentioned in the xref:_handling_non_sorting_versions_with_tilde_dot_and_caret[Handling non-sorting versions with tilde, dot, and caret] section above, this method is recommended for packages with complex versioning when supporting RHEL7 and other systems with old rpm versions.
The method described in this section is deprecated, but **may** be used. As mentioned in the xref:_handling_non_sorting_versions_with_tilde_dot_and_caret[Handling non-sorting versions with tilde, dot, and caret] section above, this method is recommended for packages with complex versioning when supporting RHEL7 and other systems with old rpm versions.
a year ago
User avatar None

Resource updated
The “pot/master/pages/Versioning.pot” file was changed. a year ago
User avatar None

String updated in the repository
In the situation described in <<Only an old branch needs a change>>, you **may** adjust the `+Release+` by appending a number *after* the dist tag, creating a E-V-R for F{CURRENTVER} that still compares lower than the one in F{NEXTVER}. Set `+<minorbump>+` to an in integer beginning with '1' and increase it by one for each minor bump you need to do. Remove `+<minorbump>+` once you are able to increase the package release normally without introducing ordering issues.
In the situation described in <<Only an old branch needs a change>>, you **may** adjust the `+Release+` by appending a number *after* the dist tag, creating a E-V-R for F{CURRENTVER} that still compares lower than the one in F{NEXTVER}. Set `+<minorbump>+` to an in integer beginning with '1' and increase it by one for each minor bump you need to do. Remove `+<minorbump>+` once you are able to increase the package release normally without introducing ordering issues.
a year ago
User avatar None

String updated in the repository
Rebuilds in older branches using `<minorbump>`
Rebuilds in older branches using `<minorbump>`
a year ago
User avatar None

String updated in the repository
Note that the dist tag is supplied by other portions of the system and may in some circumstances contain additional structure, including tildes. As this is not under the control of the packager, that structure is not covered here. The packager **must** simply include `+%{?dist}+` verbatim as indicated above.
Note that the dist tag is supplied by other portions of the system and may in some circumstances contain additional structure, including tildes. As this is not under the control of the packager, that structure is not covered here. The packager **must** simply include `+%{?dist}+` verbatim as indicated above.
a year ago
User avatar None

String updated in the repository
In this method, `+%autorelease+` is not used, and the `Release` field must be managed manually.
In this method, `+%autorelease+` is not used, and the `Release` field must be managed manually.
a year ago
User avatar None

String updated in the repository
Traditional versioning with part of the upstream version information in the Release field
Traditional versioning with part of the upstream version information in the Release field
a year ago
User avatar None

String updated in the repository
In this case the full N-V-R could be e.g. `pkg-1.0.1.security1^20210301gabc0202-1.fc{CURRENTVER}`.
In this case the full N-V-R could be e.g. `pkg-1.0.1.security1^20210301gabc0202-1.fc{CURRENTVER}`.
a year ago
User avatar None

String updated in the repository
|Upstream version | Version | Notes

| 1.0.0-rc1 | `+1.0.0~rc1+` | First prerelease

| 1.0.0-rc2 | `+1.0.0~rc2+` | Second prerelease

| git commit `f00fabd` | `+1.0.0~rc2^20210101gf00fabd+` | Post-prerelease snapshot

| 1.0.0 | `+1.0.0+` | A release

| 1.0.1 | `+1.0.1+` | A bugfix release

| git commit `bbbccc0` | `+1.0.1^20210203gbbbccc0+` or `+pkg-1.0.1^1.gbbbccc0+` | A snapshot

| 1.0.1-security1 | `+1.0.1.security1+` | A security bufix release. From past history we know that the bugfix releases will have sortable versions. If not, we could use '`+<date>.security1+`' instead.

| git commit `abc0202` | `+1.0.1.security1^20210301gabc0202+` or `+pkg-1.0.1.security1^1.gabc0202+` | Another snapshot
|Upstream version | Version | Notes

| 1.0.0-rc1 | `+1.0.0~rc1+` | First prerelease

| 1.0.0-rc2 | `+1.0.0~rc2+` | Second prerelease

| git commit `f00fabd` | `+1.0.0~rc2^20210101gf00fabd+` | Post-prerelease snapshot

| 1.0.0 | `+1.0.0+` | A release

| 1.0.1 | `+1.0.1+` | A bugfix release

| git commit `bbbccc0` | `+1.0.1^20210203gbbbccc0+` or `+pkg-1.0.1^1.gbbbccc0+` | A snapshot

| 1.0.1-security1 | `+1.0.1.security1+` | A security bufix release. From past history we know that the bugfix releases will have sortable versions. If not, we could use '`+<date>.security1+`' instead.

| git commit `abc0202` | `+1.0.1.security1^20210301gabc0202+` or `+pkg-1.0.1.security1^1.gabc0202+` | Another snapshot
a year ago
Browse all translation changes