Source strings

13 Strings 100%
Browse Translate
530 Words 100%
3,303 Characters 100%
This translation is being used as source strings within this component.

Strings status

Strings Words Characters
13 530 3,303
All strings Browse Translate Zen
13 530 3,303
Read-only strings Browse Translate Zen

Overview

Project website pagure.io/fedora-docs-l10n/modularity
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/modularity.git
Repository branch master
Last remote commit automatic update of pot/po files d453d4ba
♪ I'm a bot, bot, bot ♪ authored 10 months ago
Weblate repository https://translate.fedoraproject.org/git/fedora-docs-l10n-modularity/nav/
File mask po/*/master/pages/core-concepts/module-artifacts.po
Translation file Download pot/master/pages/core-concepts/module-artifacts.pot
Last change March 8, 2022, 10:04 p.m.
Last author None
4 weeks ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 13 530 3,303
Translated 100% 13 100% 530 100% 3,303
Needs editing 0% 0 0% 0 0% 0
Read-only 100% 13 100% 530 100% 3,303
Failing checks 0% 0 0% 0 0% 0
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 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 changes 0 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

530
Hosted words
13
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
File “pot/master/pages/core-concepts/module-artifacts.pot” was added. 2 years ago
User avatar None

String updated in the repository
We strongly discourage you to create module streams out of non-modular binary RPM as this can cause wrong dependency resolution of your installation transaction and break your system. Alway build your module streams through a distribution pipeline or local cli tools.
We strongly discourage you to create module streams out of non-modular binary RPM as this can cause wrong dependency resolution of your installation transaction and break your system. Alway build your module streams through a distribution pipeline or local cli tools.
2 years ago
User avatar None

String updated in the repository
As we already established earlier, module streams are only bundles of RPM packages which are installed together. This means that existing non-modular RPM packages can be bundled into a module stream just with adding the correct modulemd YAML file to the repodata.
As we already established earlier, module streams are only bundles of RPM packages which are installed together. This means that existing non-modular RPM packages can be bundled into a module stream just with adding the correct modulemd YAML file to the repodata.
2 years ago
User avatar None

String updated in the repository
Compatibility
Compatibility
2 years ago
User avatar None

String updated in the repository
The `modularitylabel` flag is an important feature of modularity. Module RPM artifacts can not be installed by themselves. If a `modularitylabel` flag is detected in the header of a RPM file the installation will be rejected. This is also called a `failsafe`. Module streams need to be enabled first by DNF and then the RPM packages within a module stream will be available for installation. The `failsafe` guarantees that the correct RPM packages are visible and available for installation and all necessary modular dependencies are satisfied before the DNF transaction can proceed. All this information is stored in the modulemd YAML file. Without this file DNF does not know which RPM package should be installed and what is their relation with the rest of the RPM repository.
The `modularitylabel` flag is an important feature of modularity. Module RPM artifacts can not be installed by themselves. If a `modularitylabel` flag is detected in the header of a RPM file the installation will be rejected. This is also called a `failsafe`. Module streams need to be enabled first by DNF and then the RPM packages within a module stream will be available for installation. The `failsafe` guarantees that the correct RPM packages are visible and available for installation and all necessary modular dependencies are satisfied before the DNF transaction can proceed. All this information is stored in the modulemd YAML file. Without this file DNF does not know which RPM package should be installed and what is their relation with the rest of the RPM repository.
2 years ago
User avatar None

String updated in the repository
We also refer to RPM artifacts built within a modules stream as module (or modular) RPMs.
We also refer to RPM artifacts built within a modules stream as module (or modular) RPMs.
2 years ago
User avatar None

String updated in the repository
Artifacts which are the result of a module stream build are ordinary source and binary RPM files. There is one difference. Each binary RPM package built within a module stream contains a `modularitylabel` flag inside its file header. This flag is set during the build process of a RPM package. We need this to be able to distinguish between the binary RPM files built within a module stream and RPM files built the non-modular way.
Artifacts which are the result of a module stream build are ordinary source and binary RPM files. There is one difference. Each binary RPM package built within a module stream contains a `modularitylabel` flag inside its file header. This flag is set during the build process of a RPM package. We need this to be able to distinguish between the binary RPM files built within a module stream and RPM files built the non-modular way.
2 years ago
User avatar None

String updated in the repository
Failsafe
Failsafe
2 years ago
User avatar None

String updated in the repository
Module streams are delivered as an RPM repository that will work on top of existing releases. The modular repository will also be available in the Fedora container base image, enabling users to build containers with multiple versions of software.
Module streams are delivered as an RPM repository that will work on top of existing releases. The modular repository will also be available in the Fedora container base image, enabling users to build containers with multiple versions of software.
2 years ago
User avatar None

String updated in the repository
*Binary packages* are produced by building source packages in a build environment called a buildroot. Different buildroots produce different binary packages. This means that a source package without a context is not a complete definition of a resulting binary package.
*Binary packages* are produced by building source packages in a build environment called a buildroot. Different buildroots produce different binary packages. This means that a source package without a context is not a complete definition of a resulting binary package.
2 years ago
Browse all translation changes