Source strings

108 Strings 100%
Browse Translate
1,670 Words 100%
11,056 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
108 1,670 11,056
All strings Browse Translate Zen
108 1,670 11,056
Read-only strings Browse Translate Zen
4 85 729
Strings with any failing checks Browse Translate Zen
2 62 477
Failing check: Ellipsis Browse Translate Zen
2 23 252
Failing check: Long untranslated Browse Translate Zen

Overview

Project website pagure.io/fedora-docs-l10n/package-maintainers
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/package-maintainers.git
Repository branch master
Last remote commit automatic update of pot/po files 006f285
♪ I'm a bot, bot, bot ♪ authored 3 days ago
Last commit in Weblate Update translation files a10f72b
Weblate authored 3 days ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-package-maintainers/nav/
File mask po/*/master/pages/Using_the_Koji_Build_System.po
Translation file Download pot/master/pages/Using_the_Koji_Build_System.pot
Last change July 4, 2024, 10:52 p.m.
Last author None
4 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 108 1,670 11,056
Translated 100% 108 100% 1,670 100% 11,056
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 108 100% 1,670 100% 11,056
Failing checks 3% 4 5% 85 6% 729
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 0 changes 128 changes 0 changes 0 changes 0 changes 9 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 3 changes 0 changes 0 changes 0 changes 0 changes
Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep

Quick numbers

1,670
Hosted words
108
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/Using_the_Koji_Build_System.pot” file was changed. 3 months ago
User avatar None

String added in the repository
You must pass `--topurl=https://kojipkgs.fedoraproject.org/` to any mock-config command to get a working mock-config from Fedora's koji.
You must pass `--topurl=https://kojipkgs.fedoraproject.org/` to any mock-config command to get a working mock-config from Fedora's koji.
3 months ago
User avatar None

String added in the repository
koji mock-config --tag f{MAJOROSVER}-build --arch=x86_64 --topurl=https://kojipkgs.fedoraproject.org/ f{MAJOROSVER}
koji mock-config --tag f{MAJOROSVER}-build --arch=x86_64 --topurl=https://kojipkgs.fedoraproject.org/ f{MAJOROSVER}
3 months ago
User avatar None

Resource updated
The “pot/master/pages/Using_the_Koji_Build_System.pot” file was changed. 8 months ago
User avatar None

String added in the repository
*Note:* It is possible to do a chained build
directly to the default build target for Rawhide,
but this is no longer recommended or reliable.
Building for the default Rawhide target immediately auto-creates an update,
and some Rawhide updates are now subject to gating tests.
If any package in the chain is subject to gating tests, and one fails,
that package will never reach _stable_
and the rest of the chain will not be able to build.
This is quite likely to happen to chains containing critical path packages.
When using a side tag, no updates will be automatically created,
and each build is immediately available in the side tag's buildroot
without having to pass tests first.
You can manually create the update once all the builds are done,
and the tests will not encounter dependency issues
if you rebuilt all the dependent packages correctly.
*Note:* It is possible to do a chained build
directly to the default build target for Rawhide,
but this is no longer recommended or reliable.
Building for the default Rawhide target immediately auto-creates an update,
and some Rawhide updates are now subject to gating tests.
If any package in the chain is subject to gating tests, and one fails,
that package will never reach _stable_
and the rest of the chain will not be able to build.
This is quite likely to happen to chains containing critical path packages.
When using a side tag, no updates will be automatically created,
and each build is immediately available in the side tag's buildroot
without having to pass tests first.
You can manually create the update once all the builds are done,
and the tests will not encounter dependency issues
if you rebuilt all the dependent packages correctly.
8 months ago
User avatar None

String added in the repository
fedpkg chain-build --target=side-tag-name libwidget libaselib : libgizmo :
fedpkg chain-build --target=side-tag-name libwidget libaselib : libgizmo :
8 months ago
User avatar None

String added in the repository
replacing `side-tag-name` with the actual name of your side tag.
replacing `side-tag-name` with the actual name of your side tag.
8 months ago
User avatar None

String added in the repository
fedpkg chain-build --target=side-tag-name libwidget libgizmo
fedpkg chain-build --target=side-tag-name libwidget libgizmo
8 months ago
User avatar None

String added in the repository
This will print a command you can use to wait for the side tag to be created. Run that command, and when it exits, do:
This will print a command you can use to wait for the side tag to be created. Run that command, and when it exits, do:
8 months ago
User avatar None

String added in the repository
fedpkg request-side-tag
fedpkg request-side-tag
8 months ago
Browse all translation changes