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/policies/packaging-guidelines — Spanish	If the module includes one or more profile definition, xref:building-modules/fedora/managing-defaults.adoc[module defaults] **SHOULD** also be defined.
	fedora-docs-l10n/modularity/master/pages/building-modules/copr/building-modules-in-copr — Spanish	The package version resolution was straightforward in the pre-modularity era. If multiple repositories provided the same package, the one with the highest version was preferred. It is https://dnf.readthedocs.io/en/latest/modularity.html#package-filtering[more complicated now]. If there is a module stream enabled within the system and this stream provides a package, it is preferred over its non-modular variant regardless of its version.
	fedora-docs-l10n/modularity/master/pages/requirements — French	_Requirement_: Build-time only dependencies for an alternative version may be excluded from the installable output artifacts. These excluded artifacts may be preserved by the build-system for other purposes.
	fedora-docs-l10n/modularity/master/pages/building-modules/copr/building-modules-in-copr — French	To suppress this behavior, `module_hotfixes` repositories were invented. For them, DNF upgrades to a higher version of a package regardless of where it comes from. Enable them in Copr by going to project settings and turning on this checkbox.
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	List all source SRPM packages this module should include, referenced them by their dist-git repo name + branch name.
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/updating-modules — French	`NAME` — name of the module
	fedora-docs-l10n/modularity/master/pages/policies/packaging-guidelines — French	In the case of RPM content, the profile package lists reference binary RPM package names.
	fedora-docs-l10n/modularity/master/pages/core-concepts/dnf-behavior — French	Other
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	Namely:
	fedora-docs-l10n/modularity/master/pages/using-modules — French	__group__
	fedora-docs-l10n/modularity/master/pages/core-concepts/upgrade-paths — French	Next day a new update appears:
	fedora-docs-l10n/modularity/master/pages/requirements — Spanish	_Requirement_: Build-time only dependencies for an alternative version may be excluded from the installable output artifacts. These excluded artifacts may be preserved by the build-system for other purposes.
	fedora-docs-l10n/modularity/master/pages/core-concepts/dnf-behavior — Spanish	Other
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/updating-modules — Spanish	`NAME` — name of the module
	fedora-docs-l10n/modularity/master/pages/using-modules — Spanish	__group__
	fedora-docs-l10n/modularity/master/pages/core-concepts/upgrade-paths — Spanish	Next day a new update appears:
	fedora-docs-l10n/modularity/master/pages/policies/packaging-guidelines — Spanish	In the case of RPM content, the profile package lists reference binary RPM package names.
	fedora-docs-l10n/modularity/master/pages/building-modules/copr/building-modules-in-copr — Spanish	To suppress this behavior, `module_hotfixes` repositories were invented. For them, DNF upgrades to a higher version of a package regardless of where it comes from. Enable them in Copr by going to project settings and turning on this checkbox.
	fedora-docs-l10n/modularity/master/pages/requirements — French	_Requirement_: All sources used for generating alternative versions, regardless of final visibility, must be available to the community for purposes of modification and reproducibility.
	fedora-docs-l10n/modularity/master/pages/building-modules/copr/building-modules-in-copr — French	[ ] This repository contains module hotfixes This will make packages from this project available on along with packages from the active module streams.
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	components: rpms: first-package: <1> rationale: Provides the core functionality. <2> ref: 3.0 <3> second-package: rationale: Web UI for the first-package. ref: latest ... <4>
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/updating-modules — French	`BRANCH` — name of the stream branch of the module
	fedora-docs-l10n/modularity/master/pages/policies/packaging-guidelines — French	API
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	`N`
	fedora-docs-l10n/modularity/master/pages/core-concepts/dnf-behavior — French	Any package in an enabled module takes priority over any nonmodular RPM with the same package name, regardless of which repositories those modules and packages may be in.
	fedora-docs-l10n/modularity/master/pages/using-modules — French	__dependency__
	fedora-docs-l10n/modularity/master/pages/core-concepts/upgrade-paths — French	Package From a module Requires a module Unlisted package ──────────────────────────────────────────────────────────── bar:1:2024:a loo:1 ╮ empty bar:1:2024:a foo ╯ modules
	fedora-docs-l10n/modularity/master/pages/requirements — Spanish	_Requirement_: All sources used for generating alternative versions, regardless of final visibility, must be available to the community for purposes of modification and reproducibility.
	fedora-docs-l10n/modularity/master/pages/core-concepts/dnf-behavior — Spanish	Any package in an enabled module takes priority over any nonmodular RPM with the same package name, regardless of which repositories those modules and packages may be in.
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/updating-modules — Spanish	`BRANCH` — name of the stream branch of the module
	fedora-docs-l10n/modularity/master/pages/using-modules — Spanish	__dependency__
	fedora-docs-l10n/modularity/master/pages/core-concepts/upgrade-paths — Spanish	Package From a module Requires a module Unlisted package ──────────────────────────────────────────────────────────── bar:1:2024:a loo:1 ╮ empty bar:1:2024:a foo ╯ modules
	fedora-docs-l10n/modularity/master/pages/policies/packaging-guidelines — Spanish	API
	fedora-docs-l10n/modularity/master/pages/building-modules/copr/building-modules-in-copr — Spanish	[ ] This repository contains module hotfixes This will make packages from this project available on along with packages from the active module streams.
	fedora-docs-l10n/modularity/master/pages/requirements — French	Defining the public API
	fedora-docs-l10n/modularity/master/pages/building-modules/copr/building-modules-in-copr — French	Or in a command line
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	Name of the package — maps to a DistGit repository name.
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/updating-modules — French	Module Build
	fedora-docs-l10n/modularity/master/pages/policies/packaging-guidelines — French	Module API are components, symbols, files or abstract features the module explicitly declares to be its supported interface. Everything else is considered an internal detail and shouldn't be relied on by any other module.
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	`N::A`
	fedora-docs-l10n/modularity/master/pages/core-concepts/dnf-behavior — French	If there's a nonmodular or modular RPM with a higher NVR than the hotfix one, the nonmodular or modular one wins. This is to ensure new proper updates override the temporary hotfix RPMs.
	fedora-docs-l10n/modularity/master/pages/using-modules — French	Because modules use the __group__ reason, which is weaker than __user__ used by the `dnf install` command, the package stays on the system after running the `dnf module remove` command. "Downgrading" it to __group__, however, makes the `dnf module remove` remove it as well.
	fedora-docs-l10n/modularity/master/pages/core-concepts/upgrade-paths — French	`dnf upgrade foo` command will not upgrade anything, reporting `foo-3` is already latest and installed.
	fedora-docs-l10n/modularity/master/pages/requirements — Spanish	Defining the public API
	fedora-docs-l10n/modularity/master/pages/core-concepts/dnf-behavior — Spanish	If there's a nonmodular or modular RPM with a higher NVR than the hotfix one, the nonmodular or modular one wins. This is to ensure new proper updates override the temporary hotfix RPMs.
	fedora-docs-l10n/modularity/master/pages/using-modules — Spanish	Because modules use the __group__ reason, which is weaker than __user__ used by the `dnf install` command, the package stays on the system after running the `dnf module remove` command. "Downgrading" it to __group__, however, makes the `dnf module remove` remove it as well.
	fedora-docs-l10n/modularity/master/pages/core-concepts/upgrade-paths — Spanish	`dnf upgrade foo` command will not upgrade anything, reporting `foo-3` is already latest and installed.
	fedora-docs-l10n/modularity/master/pages/policies/packaging-guidelines — Spanish	Module API are components, symbols, files or abstract features the module explicitly declares to be its supported interface. Everything else is considered an internal detail and shouldn't be relied on by any other module.
	fedora-docs-l10n/modularity/master/pages/building-modules/copr/building-modules-in-copr — Spanish	Or in a command line
	fedora-docs-l10n/modularity/master/pages/requirements — French	Similarly, there are times when an application the packager cares about depends on another package that is required at runtime, but sufficiently complex that the packager would not want to maintain it for general use. (For example, an application that links to a complicated library but only uses a few functions.)
	fedora-docs-l10n/modularity/master/pages/building-modules/copr/building-modules-in-copr — French	copr-cli modify frostyx/foo --module-hotfixes on
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	The reason why is this package here. Mostly for humans.
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/updating-modules — French	NOTE: With Modularity, you no longer build individual packages. Instead, you need to submit a module build.
	fedora-docs-l10n/modularity/master/pages/policies/packaging-guidelines — French	Every module **SHOULD** define its public API.
	fedora-docs-l10n/modularity/master/pages/core-concepts/dnf-behavior — French	References
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	`N:S`
	fedora-docs-l10n/modularity/master/pages/using-modules — French	Modular filtering and conflicts
	fedora-docs-l10n/modularity/master/pages/core-concepts/upgrade-paths — French	A reasoning is that the pile of available packages contains `foo-1`, `foo-2`, and `foo-3` and `foo-3` is already installed.
	fedora-docs-l10n/modularity/master/pages/requirements — Spanish	Similarly, there are times when an application the packager cares about depends on another package that is required at runtime, but sufficiently complex that the packager would not want to maintain it for general use. (For example, an application that links to a complicated library but only uses a few functions.)
	fedora-docs-l10n/modularity/master/pages/core-concepts/dnf-behavior — Spanish	References
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/updating-modules — Spanish	NOTE: With Modularity, you no longer build individual packages. Instead, you need to submit a module build.
	fedora-docs-l10n/modularity/master/pages/using-modules — Spanish	Modular filtering and conflicts
	fedora-docs-l10n/modularity/master/pages/core-concepts/upgrade-paths — Spanish	A reasoning is that the pile of available packages contains `foo-1`, `foo-2`, and `foo-3` and `foo-3` is already installed.
	fedora-docs-l10n/modularity/master/pages/policies/packaging-guidelines — Spanish	Every module **SHOULD** define its public API.
	fedora-docs-l10n/modularity/master/pages/building-modules/copr/building-modules-in-copr — Spanish	copr-cli modify frostyx/foo --module-hotfixes on
	fedora-docs-l10n/modularity/master/pages/requirements — French	In this case, we want there to be a standard mechanism for the packager to be able to indicate that some of the output artifacts are not supported for use outside this module. If they are needed by others, they should package it themselves and/or help maintain it in a shared place.
	fedora-docs-l10n/modularity/master/pages/building-modules/copr/building-modules-in-copr — French	Examples
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	DistGit branch, tag, or a commit — so the right version of the package gets included.
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/updating-modules — French	Submitting module builds is done using `fedpkg` and is covered in the xref:building-modules/fedora/building-modules.adoc[Building modules] section.
	fedora-docs-l10n/modularity/master/pages/policies/packaging-guidelines — French	Filters
	fedora-docs-l10n/modularity/master/pages/core-concepts/dnf-behavior — French	[[[mmd-spec-v2]]] https://github.com/fedora-modularity/libmodulemd/blob/master/spec.v2.yaml
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	`N:S::A`
	fedora-docs-l10n/modularity/master/pages/using-modules — French	When consuming module streams a lot of operations are being executed. A module stream contains alternative modular RPM packages which can have the same name as already existing non-modular RPM packages, a lot of conflicts can arise. In the next few examples we will show you some of the conflicts.
	fedora-docs-l10n/modularity/master/pages/core-concepts/upgrade-paths — French	Please observe that `foo-1` package became available because `foo` is unlisted name now. However, unlisting that name does not disappear the modular packages `foo-2` and `foo-3`. Modular and and nonmodular `foo` packages are now handled equally.
	fedora-docs-l10n/modularity/master/pages/requirements — Spanish	In this case, we want there to be a standard mechanism for the packager to be able to indicate that some of the output artifacts are not supported for use outside this module. If they are needed by others, they should package it themselves and/or help maintain it in a shared place.
	fedora-docs-l10n/modularity/master/pages/core-concepts/dnf-behavior — Spanish	[[[mmd-spec-v2]]] https://github.com/fedora-modularity/libmodulemd/blob/master/spec.v2.yaml
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/updating-modules — Spanish	Submitting module builds is done using `fedpkg` and is covered in the xref:building-modules/fedora/building-modules.adoc[Building modules] section.
	fedora-docs-l10n/modularity/master/pages/using-modules — Spanish	When consuming module streams a lot of operations are being executed. A module stream contains alternative modular RPM packages which can have the same name as already existing non-modular RPM packages, a lot of conflicts can arise. In the next few examples we will show you some of the conflicts.
	fedora-docs-l10n/modularity/master/pages/core-concepts/upgrade-paths — Spanish	Please observe that `foo-1` package became available because `foo` is unlisted name now. However, unlisting that name does not disappear the modular packages `foo-2` and `foo-3`. Modular and and nonmodular `foo` packages are now handled equally.
	fedora-docs-l10n/modularity/master/pages/policies/packaging-guidelines — Spanish	Filters
	fedora-docs-l10n/modularity/master/pages/requirements — French	_Requirement_: Packagers must be able to encode whether their output artifacts are intended for use by other projects or if they are effectively private to the alternative version. Packagers must also have a way of finding this information out so they understand what they can and cannot rely on as a dependency.
	fedora-docs-l10n/modularity/master/pages/building-modules/copr/building-modules-in-copr — French	Build a module from a modulemd yaml file hosted online:
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	List as many packages as you need.
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/updating-modules — French	Publishing the Module
	fedora-docs-l10n/modularity/master/pages/policies/packaging-guidelines — French	Module filters define lists of components or other content that should not be part of the resulting, composed module deliverable. They can be used to only ship a limited subset of generated RPM packages, for instance.
	fedora-docs-l10n/modularity/master/pages/core-concepts/dnf-behavior — French	[[[fedora-module-defaults-repo]]] https://pagure.io/releng/fedora-module-defaults
	fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French	`N:S:V`
	fedora-docs-l10n/modularity/master/pages/using-modules — French	Switching a module stream without removing the RPM packages from the old module stream
	fedora-docs-l10n/modularity/master/pages/core-concepts/upgrade-paths — French	Example 3
	fedora-docs-l10n/modularity/master/pages/requirements — Spanish	_Requirement_: Packagers must be able to encode whether their output artifacts are intended for use by other projects or if they are effectively private to the alternative version. Packagers must also have a way of finding this information out so they understand what they can and cannot rely on as a dependency.
	fedora-docs-l10n/modularity/master/pages/core-concepts/dnf-behavior — Spanish	[[[fedora-module-defaults-repo]]] https://pagure.io/releng/fedora-module-defaults
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/updating-modules — Spanish	Publishing the Module
	fedora-docs-l10n/modularity/master/pages/using-modules — Spanish	Switching a module stream without removing the RPM packages from the old module stream
	fedora-docs-l10n/modularity/master/pages/core-concepts/upgrade-paths — Spanish	Example 3
	fedora-docs-l10n/modularity/master/pages/policies/packaging-guidelines — Spanish	Module filters define lists of components or other content that should not be part of the resulting, composed module deliverable. They can be used to only ship a limited subset of generated RPM packages, for instance.
	fedora-docs-l10n/modularity/master/pages/building-modules/copr/building-modules-in-copr — Spanish	Build a module from a modulemd yaml file hosted online:
	fedora-docs-l10n/modularity/master/pages/requirements — French	Use-case-based installation
	fedora-docs-l10n/modularity/master/pages/building-modules/copr/building-modules-in-copr — French	copr-cli create testproject1 --chroot fedora-rawhide-x86_64 copr-cli build-module testproject1 \ --url https://src.fedoraproject.org/modules/httpd/raw/2.4/f/httpd.yaml
	fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French	Advanced definitions
	fedora-docs-l10n/modularity/master/pages/policies/packaging-guidelines — French	filter: rpms: - mypackage-plugins

• 21 / 24
  / 24