2. fedora-docs-l10n/modularity
3. Search

Filters

• Untranslated strings • state:empty
• Unfinished strings • state:<translated
• Translated strings • state:>=translated
• Strings marked for edit • state:needs-editing
• Strings with suggestions • has:suggestion
• Strings with variants • has:variant
• Strings with screenshots • has:screenshot
• Strings with labels • has:label
• Strings with context • has:context
• Unfinished strings without suggestions • state:<translated AND NOT has:suggestion
• Strings with comments • has:comment
• Strings with any failing checks • has:check
• Approved strings • state:approved
• Strings waiting for review • state:translated

state:empty

Position and priority

• Position and priority
• Position
• Priority
• Labels
• Source string
• Target string
• String age
• Last updated
• Number of words
• Number of comments
• Number of failing checks
• Key
• String location

	Translation	Source string	Target string
	fedora-docs-l10n/modularity/master/pages/requirements — Spanish	_Requirement_: For alternative versions whose lifecycle will continue through at least part of the next Fedora release, it must be possible to upgrade from one release to the next and remain with the fully-compatible version.
	fedora-docs-l10n/modularity/master/pages/using-modules — Spanish	[root@bdaeaab947e6 /]# dnf module enable perl:5.30 Fedora 35 - x86_64 6.8 MB/s | 79 MB 00:11 Fedora 35 openh264 (From Cisco) - x86_64 3.1 kB/s | 2.5 kB 00:00 Fedora Modular 35 - x86_64 2.8 MB/s | 3.3 MB 00:01 Fedora 35 - x86_64 - Updates 7.3 MB/s | 27 MB 00:03 Fedora Modular 35 - x86_64 - Updates 2.3 MB/s | 2.8 MB 00:01 Dependencies resolved. =========================================================================================================================================================================== Package Architecture Version Repository Size =========================================================================================================================================================================== Enabling module streams: perl 5.30
	fedora-docs-l10n/modularity/master/pages/requirements — French	Third-party additions
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	A number of the build group.
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	Allowed Characters
	fedora-docs-l10n/modularity/master/pages/using-modules — French	Transaction Summary ===========================================================================================================================================================================
	fedora-docs-l10n/modularity/master/pages/requirements — Spanish	Third-party additions
	fedora-docs-l10n/modularity/master/pages/using-modules — Spanish	Transaction Summary ===========================================================================================================================================================================
	fedora-docs-l10n/modularity/master/pages/requirements — French	Some third-party add-on repositories (particularly EPEL) have been limited in the past by relying on the system copies of packages in the base distribution of the release. In the particular case of EPEL, little can be done to upgrade these system copies. In order to be able to package much of the available FOSS software out there, it may be necessary to override some of the content shipped in the base system with packages known to work properly.
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	**N** - Name
	fedora-docs-l10n/modularity/master/pages/using-modules — French	Is this ok [y/N]: y Complete! [root@bdaeaab947e6 /]# dnf install perl-Tie-RefHash Last metadata expiration check: 0:00:22 ago on Thu Mar 3 09:41:23 2022. Error: Problem: package perl-Tie-RefHash-1.40-478.fc35.noarch requires perl(:MODULE_COMPAT_5.34.0), but none of the providers can be installed - conflicting requests - package perl-libs-4:5.34.0-481.fc35.i686 is filtered out by modular filtering - package perl-libs-4:5.34.0-481.fc35.x86_64 is filtered out by modular filtering - package perl-libs-4:5.34.0-482.fc35.i686 is filtered out by modular filtering - package perl-libs-4:5.34.0-482.fc35.x86_64 is filtered out by modular filtering (try to add '--skip-broken' to skip uninstallable packages) [root@bdaeaab947e6 /]#
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	For even more complex scenarios, please study the https://github.com/fedora-modularity/libmodulemd/blob/main/yaml_specs/modulemd_packager_v3.yaml[modulemd-packager specification].
	fedora-docs-l10n/modularity/master/pages/requirements — Spanish	Some third-party add-on repositories (particularly EPEL) have been limited in the past by relying on the system copies of packages in the base distribution of the release. In the particular case of EPEL, little can be done to upgrade these system copies. In order to be able to package much of the available FOSS software out there, it may be necessary to override some of the content shipped in the base system with packages known to work properly.
	fedora-docs-l10n/modularity/master/pages/using-modules — Spanish	Is this ok [y/N]: y Complete! [root@bdaeaab947e6 /]# dnf install perl-Tie-RefHash Last metadata expiration check: 0:00:22 ago on Thu Mar 3 09:41:23 2022. Error: Problem: package perl-Tie-RefHash-1.40-478.fc35.noarch requires perl(:MODULE_COMPAT_5.34.0), but none of the providers can be installed - conflicting requests - package perl-libs-4:5.34.0-481.fc35.i686 is filtered out by modular filtering - package perl-libs-4:5.34.0-481.fc35.x86_64 is filtered out by modular filtering - package perl-libs-4:5.34.0-482.fc35.i686 is filtered out by modular filtering - package perl-libs-4:5.34.0-482.fc35.x86_64 is filtered out by modular filtering (try to add '--skip-broken' to skip uninstallable packages) [root@bdaeaab947e6 /]#
	fedora-docs-l10n/modularity/master/pages/requirements — French	_Requirement_: It must be possible for third party repositories to create alternative versions that override base distribution content at the user’s explicit choice.
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	a-z A-Z 0-9 . - _ +
	fedora-docs-l10n/modularity/master/pages/using-modules — French	The example describes a situation when you try to install a RPM package which is not provided from the enabled `perl:5.30` module stream. We first enable the `perl:5.30` module stream. After that we are trying to install the package `perl-Tie-RefHash`. The DNF package manager is trying to tell you that the `perl-Tie-RefHash` cannot be installed because it is not provided by any of the enabled module streams. Modular filtering will automatically filter out all the RPM packages which are not provided by the actual enabled module streams.
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	RPM macros (optional)
	fedora-docs-l10n/modularity/master/pages/requirements — Spanish	_Requirement_: It must be possible for third party repositories to create alternative versions that override base distribution content at the user’s explicit choice.
	fedora-docs-l10n/modularity/master/pages/using-modules — Spanish	The example describes a situation when you try to install a RPM package which is not provided from the enabled `perl:5.30` module stream. We first enable the `perl:5.30` module stream. After that we are trying to install the package `perl-Tie-RefHash`. The DNF package manager is trying to tell you that the `perl-Tie-RefHash` cannot be installed because it is not provided by any of the enabled module streams. Modular filtering will automatically filter out all the RPM packages which are not provided by the actual enabled module streams.
	fedora-docs-l10n/modularity/master/pages/requirements — French	_Requirement_: It must be possible for third party repositories to create alternative versions of software that exist in the base distribution.
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	**S** - Stream
	fedora-docs-l10n/modularity/master/pages/using-modules — French	To fix this conflict you have to enable the correct module stream. In our case it is the `perl:5.32` module stream.
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	RPM packages while being built as part of a module have the following RPM macros available:
	fedora-docs-l10n/modularity/master/pages/requirements — Spanish	_Requirement_: It must be possible for third party repositories to create alternative versions of software that exist in the base distribution.
	fedora-docs-l10n/modularity/master/pages/using-modules — Spanish	To fix this conflict you have to enable the correct module stream. In our case it is the `perl:5.32` module stream.
	fedora-docs-l10n/modularity/master/pages/requirements — French	Reduce duplication in packaging work
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	**V** - Version
	fedora-docs-l10n/modularity/master/pages/using-modules — French	Installing a RPM package without enabling the module stream which provides it.
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	%dist .scrmod+f37+14301+76d220e4 <.> %modularitylabel perl-Module-Install:master:3720220414092112:dd3c6e0e <.> %_module_build 1 <.> %_module_name perl-Module-Install <.> %_module_stream master <.> %_module_version 3720220414092112 <.> %_module_context dd3c6e0e <.>
	fedora-docs-l10n/modularity/master/pages/requirements — Spanish	Reduce duplication in packaging work
	fedora-docs-l10n/modularity/master/pages/using-modules — Spanish	Installing a RPM package without enabling the module stream which provides it.
	fedora-docs-l10n/modularity/master/pages/requirements — French	There is plenty of software out in the wild that maintains compatibility over time and is therefore useful to carry in multiple releases of Fedora. With traditional packaging, this means carrying and building separate branches of the packages for each release of Fedora. In the case of software “stacks” which are tightly bound, this means also manually building each of its dependencies in each release of Fedora.
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	0-9
	fedora-docs-l10n/modularity/master/pages/using-modules — French	of a installation conflict when installing a package without enabling the correct module stream
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	<.> A `%dist` macro of a unique value used in `Release` RPM specification tags. <.> An RPM tag stored into binary RPM packages. DNF uses it to distinguish modular packages from nonmodular ones. <.> A macro denoting that a modular package is being built. <.> A name of the module being built. <.> A stream of the module being built. <.> A version of the module being built. <.> A context of the module being built.
	fedora-docs-l10n/modularity/master/pages/requirements — Spanish	There is plenty of software out in the wild that maintains compatibility over time and is therefore useful to carry in multiple releases of Fedora. With traditional packaging, this means carrying and building separate branches of the packages for each release of Fedora. In the case of software “stacks” which are tightly bound, this means also manually building each of its dependencies in each release of Fedora.
	fedora-docs-l10n/modularity/master/pages/using-modules — Spanish	of a installation conflict when installing a package without enabling the correct module stream
	fedora-docs-l10n/modularity/master/pages/requirements — French	_Requirement_: It must be possible to build multiple component software packages in the same build process.
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	**C** - Context
	fedora-docs-l10n/modularity/master/pages/using-modules — French	[root@bdaeaab947e6 /]# dnf install perl-DBI Last metadata expiration check: 3:13:30 ago on Thu Mar 3 09:41:23 2022. Error: Problem: package perl-DBI-1.643-10.fc35.x86_64 requires libperl.so.5.34()(64bit), but none of the providers can be installed - conflicting requests - package perl-libs-4:5.34.0-481.fc35.x86_64 is filtered out by modular filtering - package perl-libs-4:5.34.0-482.fc35.x86_64 is filtered out by modular filtering (try to add '--skip-broken' to skip uninstallable packages) [root@bdaeaab947e6 /]# dnf module enable perl-DBI Last metadata expiration check: 3:14:38 ago on Thu Mar 3 09:41:23 2022. Dependencies resolved. =========================================================================================================================================================================== Package Architecture Version Repository Size =========================================================================================================================================================================== Enabling module streams: perl-DBI 1.643
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	You can use these macros in RPM specification files of your RPM components to modify building of the packages.
	fedora-docs-l10n/modularity/master/pages/requirements — Spanish	_Requirement_: It must be possible to build multiple component software packages in the same build process.
	fedora-docs-l10n/modularity/master/pages/using-modules — Spanish	[root@bdaeaab947e6 /]# dnf install perl-DBI Last metadata expiration check: 3:13:30 ago on Thu Mar 3 09:41:23 2022. Error: Problem: package perl-DBI-1.643-10.fc35.x86_64 requires libperl.so.5.34()(64bit), but none of the providers can be installed - conflicting requests - package perl-libs-4:5.34.0-481.fc35.x86_64 is filtered out by modular filtering - package perl-libs-4:5.34.0-482.fc35.x86_64 is filtered out by modular filtering (try to add '--skip-broken' to skip uninstallable packages) [root@bdaeaab947e6 /]# dnf module enable perl-DBI Last metadata expiration check: 3:14:38 ago on Thu Mar 3 09:41:23 2022. Dependencies resolved. =========================================================================================================================================================================== Package Architecture Version Repository Size =========================================================================================================================================================================== Enabling module streams: perl-DBI 1.643
	fedora-docs-l10n/modularity/master/pages/requirements — French	_Requirement_: It must be possible for the packager to specify the order in which packages must be built (and to indicate which ones can be built in parallel).
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	0-9 a-f
	fedora-docs-l10n/modularity/master/pages/using-modules — French	Is this ok [y/N]: y Complete! [root@bdaeaab947e6 /]# dnf install perl-DBI Last metadata expiration check: 3:14:46 ago on Thu Mar 3 09:41:23 2022. Dependencies resolved. =========================================================================================================================================================================== Package Architecture Version Repository Size =========================================================================================================================================================================== Installing: perl-DBI x86_64 1.643-7.module_f35+12493+425c54a8 fedora-modular 700 k
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	If you need additional RPM macros, you can define them in a `buildopts` section of your modulemd file:
	fedora-docs-l10n/modularity/master/pages/requirements — Spanish	_Requirement_: It must be possible for the packager to specify the order in which packages must be built (and to indicate which ones can be built in parallel).
	fedora-docs-l10n/modularity/master/pages/using-modules — Spanish	Is this ok [y/N]: y Complete! [root@bdaeaab947e6 /]# dnf install perl-DBI Last metadata expiration check: 3:14:46 ago on Thu Mar 3 09:41:23 2022. Dependencies resolved. =========================================================================================================================================================================== Package Architecture Version Repository Size =========================================================================================================================================================================== Installing: perl-DBI x86_64 1.643-7.module_f35+12493+425c54a8 fedora-modular 700 k
	fedora-docs-l10n/modularity/master/pages/requirements — French	_Requirement_: It must be possible to be build for all supported platforms using the same specification and with a single build command.
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	**A** - Arch
	fedora-docs-l10n/modularity/master/pages/using-modules — French	Transaction Summary =========================================================================================================================================================================== Install 1 Package
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	buildopts: rpms: macros: | %perl_bootstrap 1
	fedora-docs-l10n/modularity/master/pages/requirements — Spanish	_Requirement_: It must be possible to be build for all supported platforms using the same specification and with a single build command.
	fedora-docs-l10n/modularity/master/pages/using-modules — Spanish	Transaction Summary =========================================================================================================================================================================== Install 1 Package
	fedora-docs-l10n/modularity/master/pages/requirements — French	Non-Goals
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	**P** - Profile
	fedora-docs-l10n/modularity/master/pages/using-modules — French	Total download size: 700 k Installed size: 1.9 M Is this ok [y/N]:
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	This section belongs into an item of `configurations` list in case of v3 modulemd format. In case of v2 format it belongs directly into `data` section.
	fedora-docs-l10n/modularity/master/pages/requirements — Spanish	Non-Goals
	fedora-docs-l10n/modularity/master/pages/using-modules — Spanish	Total download size: 700 k Installed size: 1.9 M Is this ok [y/N]:
	fedora-docs-l10n/modularity/master/pages/requirements — French	Parallel installability
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	Filtered Packages (optional, defaults to no filters)
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	All fields **MUST** start and end with an alphanumeric character: a-z A-Z 0-9
	fedora-docs-l10n/modularity/master/pages/using-modules — French	In this example we are trying to install the `perl-DBI` package. On our system we have previously enabled and installed the `perl:5.32` module stream. The conflict tells us that we are trying to install non-modular `perl-DBI` which depends on the non-modular `perl` but the non-modular `perl` package is not available due to modular filtering. The only RPM packages which are available for dependency resolution are the RPM packages from the `5.32` stream.
	fedora-docs-l10n/modularity/master/pages/requirements — Spanish	Parallel installability
	fedora-docs-l10n/modularity/master/pages/using-modules — Spanish	In this example we are trying to install the `perl-DBI` package. On our system we have previously enabled and installed the `perl:5.32` module stream. The conflict tells us that we are trying to install non-modular `perl-DBI` which depends on the non-modular `perl` but the non-modular `perl` package is not available due to modular filtering. The only RPM packages which are available for dependency resolution are the RPM packages from the `5.32` stream.
	fedora-docs-l10n/modularity/master/pages/requirements — French	As mentioned in the Background section, the goals of Modularity are specifically to *not* implement parallel-installability. We recommend instead that users should rely on other mechanisms such as virtualization or containerization to accomplish this. If parallel-installation is unavoidable, then Modularity is not the correct tool for this job.
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	The build process of a RPM packages can result in a subpackages which complement the build of the package (docs, additional build requires etc.). One source RPM package might produce multiple binary RPM packages. Those subpackages are not always desired to be shipped with the Module. Modules enable you to filter out those undesirable packages with the `filter` build option. After the build is finished the filtered packages will be not included in the `artifacts` property in the result modulemd yaml file. The `artifacts` property is added by the build system post build. For an example please refer to the https://github.com/fedora-modularity/libmodulemd/tree/main/yaml_specs[modulemd spec files].
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	Forbidden Characters
	fedora-docs-l10n/modularity/master/pages/using-modules — French	Non-modular RPM packages can not depend on modular content. If your non-modular package needs a modular dependency please modularize your content.
	fedora-docs-l10n/modularity/master/pages/requirements — Spanish	As mentioned in the Background section, the goals of Modularity are specifically to *not* implement parallel-installability. We recommend instead that users should rely on other mechanisms such as virtualization or containerization to accomplish this. If parallel-installation is unavoidable, then Modularity is not the correct tool for this job.
	fedora-docs-l10n/modularity/master/pages/using-modules — Spanish	Non-modular RPM packages can not depend on modular content. If your non-modular package needs a modular dependency please modularize your content.
	fedora-docs-l10n/modularity/master/pages/requirements — French	Arbitrary stream switching
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	Filtered RPMs are still available to use as build dependencies in subsequent stages of the module build, but are not included in the composed repository for users.
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	This paragraph serves as a design decision for future changes.
	fedora-docs-l10n/modularity/master/pages/using-modules — French	To fix this we need to enable the `perl-DBI:1.643` module stream. When enabling the `perl-DBI:1.643` we are satisfying the modular dependency for the `perl` module. The non-modular `perl-DBI` RPM package is now filtered by modular filtering and it is not considered in dependency resolution and content set creation.
	fedora-docs-l10n/modularity/master/pages/requirements — Spanish	Arbitrary stream switching
	fedora-docs-l10n/modularity/master/pages/using-modules — Spanish	To fix this we need to enable the `perl-DBI:1.643` module stream. When enabling the `perl-DBI:1.643` we are satisfying the modular dependency for the `perl` module. The non-modular `perl-DBI` RPM package is now filtered by modular filtering and it is not considered in dependency resolution and content set creation.
	fedora-docs-l10n/modularity/master/pages/requirements — French	Module streams are intended to be compatible update streams. That means they must follow the same rules regarding RPM package-level updates within the stream. By definition, two streams of the same module exist because upgrades (or downgrades or cross-grades…) are not capable of being done in a safe, automated fashion.
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	filter: rpms: - first-package-debuginfo - second-package-nope
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	Following characters **MUST NOT** be part of any field:
	fedora-docs-l10n/modularity/master/pages/requirements — Spanish	Module streams are intended to be compatible update streams. That means they must follow the same rules regarding RPM package-level updates within the stream. By definition, two streams of the same module exist because upgrades (or downgrades or cross-grades…) are not capable of being done in a safe, automated fashion.
	fedora-docs-l10n/modularity/master/pages/requirements — French	That does not mean that stream switching should be impossible, but it does mean that we will not build any tools intended to handle such switching in a generic manner. Stream switches should be handled on a module-by-module basis and detailed instructions and/or tools written for each such case.
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	`:` (colon) - separator
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	[[demodularized]]Demodularized packages (optional, defaults to none)
	fedora-docs-l10n/modularity/master/pages/requirements — Spanish	That does not mean that stream switching should be impossible, but it does mean that we will not build any tools intended to handle such switching in a generic manner. Stream switches should be handled on a module-by-module basis and detailed instructions and/or tools written for each such case.
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	If you decide to remove a binary package from your module stream, you will probably stop building it, or you will filter it out with a `filter` option. But that's not enough if you want to move the package back to nonmodular packages: Because the package remains listed among artifacts in the previous version of the stream and a package manager could see both the updated and the historical version. (The previous version can be available in GA and updates repositories, while your updated module will first appear in an updates-testing repository.)
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	`/` (forward slash) - profile separator
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	To return the package back to nonmodular package set, you need to write it on a list of demodularized packages. A package manager checks the demodularized list of the very latest version of the module stream over all repositories and if it only sees a package name there, it will stop hiding the same-named nonmodular packages while the stream is enabled.
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	`\` (backslash) - comon control character
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	The list of demodularized packages is defined in `demodularized` field:
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	`*` (asterisk) - common wildcard
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	demodularized: rpms: - first-removed-package - second-removed-package
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	`?` (question mark) - common wildcard
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	With this explicit mechanism, called demodularization, a package can be demoted from a module. If you ever revert your decision and make the package modular again, the only thing necessary is remove it from the demodularized list.
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	`@` (at) - grpspec in YUM and DNF
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	Creating build-only components (optional)
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	` ` (space) - common separator

• 23 / 24
  / 24