Translation Source string Target string
fedora-docs-l10n/modularity/master/pages/building-modules/fedora/updating-modules — French
In the past there was https://raw.githubusercontent.com/fedora-modularity/libmodulemd/main/yaml_specs/modulemd_stream_v2.yaml[modulemd, version 2,] format used for building modules. That format featured stream expansion and dynamic contexts. However, these features were proved impossible to be handled correctly by DNF and thus a new format, https://raw.githubusercontent.com/fedora-modularity/libmodulemd/main/yaml_specs/modulemd_packager_v3.yaml[modulemd-packager, version 3,] was https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/KG7L5WE5IYC5CQMS6XOVTPYBJ57AFMF3/#UWQSMM5JANB7MS6XJBLJRGA7N4KIAEIH[introduced] which features a static context.
 
fedora-docs-l10n/modularity/master/pages/core-concepts/upgrade-paths — French
DNF will create two lineages `1` and `2`, and will upgrade to `foo:stream:2:A`. This is because `foo:stream:2:A` has the highest version in a lineage whose modules require `bar:x` as the already installed `foo:stream:0:Z`.
 
fedora-docs-l10n/modularity/nav — Spanish
xref:building-modules/fedora/inspecting-build-failures.adoc[Inspecting Build Failures]
 
fedora-docs-l10n/modularity/master/pages/community — Spanish
Petr Písař mailto:ppisar@redhat.com[ppisar@redhat.com] — Developer and libmodulemd maintainer
 
fedora-docs-l10n/modularity/master/pages/policies/index — Spanish
Packages provided at runtime by the default stream of a module *MUST* depend only on packages provided by packages from default module streams or the non-modular package set. By extension, default streams of a module *MUST NOT* have a dependency on any non-default stream.footnote:[It is highly recommended that default streams have no module dependencies besides the platform to avoid potential future conflicts during upgrades.]
 
fedora-docs-l10n/modularity/master/pages/history — Spanish
Perhaps unsurprisingly, the overwhelming majority of respondents were thrilled to have supported versions of software beyond what had shipped with the base operating system. What the survey team did come away with that was an epiphany was that the respondents generally did not care about the parallel installability of the SCLs. For the most part, they maintained individual userspaces (using bare metal, traditional virtualization or containers) for each of the applications they cared about.
 
fedora-docs-l10n/modularity/master/pages/core-concepts/module-stream — Spanish
The example has four context configurations. This means that this definition file will produce four different module stream builds for each context. Each context defines how, where and for what purpose a module stream is built. You can find more information on contexts in the xref:core-concepts/module-context.adoc[Module context section].
 
fedora-docs-l10n/modularity/master/pages/building-modules/fedora/adding-new-modules — Spanish
`NAME` — name of the package and the module
 
fedora-docs-l10n/modularity/master/pages/building-modules/fedora/building-modules — Spanish
http://localhost:12345/?code=7c35ded4-054b-4df0-9151-7ef12c7fb838_xe3JWkvf_sL1UyLOzftHJZ3uIlfOo00N
 
fedora-docs-l10n/modularity/master/pages/building-modules/local/building-modules-locally — Spanish
where MODULE is "module-NAME-STREAM-VERSION", so for example "module-testmodule-master-20180612122805".
 
fedora-docs-l10n/modularity/master/pages/building-modules/fedora/managing-defaults — Spanish
Please note that if the module stream masks part of the Traditional RPM repos (e.g it replaces an existing RPM or it introduces a non-trivial set of conflicts) it may not be made a default stream without the express permission of FESCo. Release Engineering will be responsible for escalating any PR that is questionable on this point to FESCo for a final decision.
 
fedora-docs-l10n/modularity/master/pages/requirements — Spanish
As Linux containers grow more popular, the number of disreputable images on container registries has also been rising. Delivering trustworthy binaries to users is something that traditional distributions have always done well. They provide assurance (in the form of signatures, Secure Boot and other trusted delivery paths) that the software you’re running is the software you think it is.
 
fedora-docs-l10n/modularity/master/pages/building-modules/fedora/module-obsoletes — Spanish
document: modulemd-obsoletes
version: 1
data:
modified: 2018-05-23T14:25Z
module: nodejs
stream: "11"
message: "Module stream nodejs:11 is no longer supported. Please switch to nodejs:12"
obsoleted_by:
module: nodejs
stream: "12"
 
fedora-docs-l10n/modularity/master/pages/core-concepts/consuming — Spanish
Modularity brings parallel availability, not parallel installability. Only one stream of a given module can be enabled on a system — so it is always clear which version gets installed. Installing and running multiple versions of software can be achieved by using existing technologies, such as containers.
 
fedora-docs-l10n/modularity/master/pages/core-concepts/module-context — Spanish
---
 
fedora-docs-l10n/modularity/master/pages/core-concepts/dnf-behavior — Spanish
If the module "arch" is not specified, the system's base architecture will be used.
 
fedora-docs-l10n/modularity/master/pages/building-modules/fedora/updating-modules — Spanish
In the past there was https://raw.githubusercontent.com/fedora-modularity/libmodulemd/main/yaml_specs/modulemd_stream_v2.yaml[modulemd, version 2,] format used for building modules. That format featured stream expansion and dynamic contexts. However, these features were proved impossible to be handled correctly by DNF and thus a new format, https://raw.githubusercontent.com/fedora-modularity/libmodulemd/main/yaml_specs/modulemd_packager_v3.yaml[modulemd-packager, version 3,] was https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/KG7L5WE5IYC5CQMS6XOVTPYBJ57AFMF3/#UWQSMM5JANB7MS6XJBLJRGA7N4KIAEIH[introduced] which features a static context.
 
fedora-docs-l10n/modularity/master/pages/policies/naming-guidelines — Spanish
Option 3: Rolling and unstable streams
 
fedora-docs-l10n/modularity/master/pages/using-modules — Spanish
To **enable a module stream** and make its packages available for installation, run the following command:
 
fedora-docs-l10n/modularity/master/pages/core-concepts/upgrade-paths — Spanish
DNF will create two lineages `1` and `2`, and will upgrade to `foo:stream:2:A`. This is because `foo:stream:2:A` has the highest version in a lineage whose modules require `bar:x` as the already installed `foo:stream:0:Z`.
 
fedora-docs-l10n/modularity/master/pages/faq — Spanish
We are developing the technology such as the build pipeline and client tooling to enable contributors to build multiple versions. We envision longer life cycles of stacks mainly for server, and devel/rolling releases of some stacks for developers. However, contributors to the Fedora project will be the deciders and maintainers of any versions that are available.
 
fedora-docs-l10n/modularity/master/pages/core-concepts/modular-repository — Spanish
[mcurlej@localhost final_repo]$ tree
.
├── flatpak-rpm-macros-35-4.module_fc35+common+1234.src.rpm
├── flatpak-rpm-macros-35-4.module_fc35+common+1234.x86_64.rpm
├── flatpak-rpm-macros-35-4.module_fc35+devel+1234.src.rpm
├── flatpak-rpm-macros-35-4.module_fc35+devel+1234.x86_64.rpm
├── *flatpak-runtime:common:20220211094818:1234:x86_64.modulemd.yaml* <.>
├── flatpak-runtime-config-35-1.module_fc35+common+1234.src.rpm
├── flatpak-runtime-config-35-1.module_fc35+common+1234.x86_64.rpm
├── flatpak-runtime-config-35-1.module_fc35+devel+1234.src.rpm
├── flatpak-runtime-config-35-1.module_fc35+devel+1234.x86_64.rpm
├── *flatpak-runtime:devel:20220211094818:1234:x86_64.modulemd.yaml* <.>
├── *module-build-0.1.0-1.fc35.noarch.rpm* <.>
├── module-build-0.1.0-1.fc35.src.rpm
└── repodata
⋮
1 directory, 20 files
[mcurlej@localhost final_repo]$
 
fedora-docs-l10n/modularity/master/pages/policies/packaging-guidelines — Spanish
Packager **MUST NOT** specify `name`, name is taken from name of dist-git repository
 
fedora-docs-l10n/modularity/master/pages/index — Spanish
You need/want to provide additional major versions of your existing RPM packages i. e. postgresql 10, postgresql 11 within one Fedora release or a custom RPM repository.
 
fedora-docs-l10n/modularity/master/pages/building-modules/copr/building-modules-in-copr — Spanish
dnf install copr-cli
 
fedora-docs-l10n/modularity/master/pages/core-concepts/building — Spanish
The above example produces three different binaries, one for each release. In case there are multiple architectures, three binaries will be produced (one each).
 
fedora-docs-l10n/modularity/master/pages/history — French
The most common problem reported for Software Collections was that using them required changes to the applications they wanted to run. SCLs install to a separate filesystem location from more traditional RPMs and applications that rely on them need to know where to look for them. (In SCL parlance, this is called “activating” the collection.)
 
fedora-docs-l10n/modularity/master/pages/requirements — French
_Requirement_: It must be possible for users to construct container images based on Fedora content matching the software version they need for their applications.
 
fedora-docs-l10n/modularity/master/pages/faq — French
I can just ‘dnf downgrade’ to get an older version.. Why do we need modularity?
 
fedora-docs-l10n/modularity/nav — French
xref:building-modules/copr/building-modules-in-copr.adoc[COPR]
 
fedora-docs-l10n/modularity/master/pages/building-modules/copr/building-modules-in-copr — French
And make sure that an https://copr.fedorainfracloud.org/api/[API token is properly configured].
 
fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French
Every modulemd starts with these three lines:
 
fedora-docs-l10n/modularity/master/pages/building-modules/fedora/adding-new-modules — French
`BRANCH` — name of the stream branch of the package and the module
 
fedora-docs-l10n/modularity/master/pages/policies/packaging-guidelines — French
Packager **MUST NOT** specify `stream`, stream is taken from branch of dist-git repository
 
fedora-docs-l10n/modularity/master/pages/policies/naming-guidelines — French
For streams that don't guarantee an API/ABI stability over time and just roll forward, we suggest packagers use one of the following stream names.
 
fedora-docs-l10n/modularity/master/pages/glossary — French
Module Artifact
 
fedora-docs-l10n/modularity/master/pages/building-modules/local/building-modules-locally — French
Build your module with other SCM
 
fedora-docs-l10n/modularity/master/pages/policies/index — French
Packages provided from default streams *MAY* depend on content from other default streams. If they do so, this dependency *MUST* be encoded in the module metadata.footnote:[This is so that if the maintainers of either module wishes to change its default stream, it is easy to see what other modules would be impacted and coordinate it.]
 
fedora-docs-l10n/modularity/master/pages/building-modules/fedora/module-obsoletes — French
Theses are perhaps the most common scanarios, but check the specification for other workflows:
 
fedora-docs-l10n/modularity/master/pages/core-concepts/building — French
Building multiple versions
 
fedora-docs-l10n/modularity/master/pages/core-concepts/module-stream — French
At the time of writing a standard Perl module stream needs to build around 180 RPM packages. Those RPM packages build around 400 source and binary RPM files. So when building four context configurations you get to around 1600 source and binary RPM files.
 
fedora-docs-l10n/modularity/master/pages/core-concepts/dnf-behavior — French
Specifying a non-existent "module" name should fail.
 
fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French
Version
 
fedora-docs-l10n/modularity/master/pages/core-concepts/module-context — French
document: modulemd
version: 2
data:
name: perl
stream: "5.32"
version: 3520210922083143
context: ab7e7bfe
static_context: true
arch: x86_64
summary: Practical Extraction and Report Language
description: >
Perl is a high-level programming language with roots in C, sed, awk and shell
scripting. Perl is good at handling processes and files, and is especially good
at handling text. Perl's hallmarks are practicality and efficiency. While it is
used to do a lot of different things, Perl's most common applications are system
administration utilities and web programming.
license:
module:
- MIT
content:
- (Copyright only) and (Artistic or GPL+)
- (GPL+ or Artistic) and (GPLv2+ or Artistic) and MIT
- (GPL+ or Artistic) and Artistic 2.0 and UCD
⋮
xmd: {}
dependencies:
- buildrequires:
perl-bootstrap: [5.32]
platform: [f35]
requires:
platform: [f35]
⋮
 
fedora-docs-l10n/modularity/master/pages/core-concepts/consuming — French
Installing a module
 
fedora-docs-l10n/modularity/master/pages/core-concepts/module-dependency-resolution — French
green-legend {
 
fedora-docs-l10n/modularity/master/pages/community — French
Marek Kulik mailto:mkulik@redhat.com[mkulik@redhat.com] — Developer and infrastructure
 
fedora-docs-l10n/modularity/master/pages/building-modules/fedora/building-modules — French
At this point `fedpkg` waits on port 12345 of your system for an incoming connection from your web browser. While `fedpkg` waits for an incoming OIDC answer from your browser, imitate the answer with `curl` tool in a parallel terminal using the very same URL:
 
fedora-docs-l10n/modularity/master/pages/using-modules — French
$ dnf module enable NAME:STREAM
 
fedora-docs-l10n/modularity/master/pages/building-modules/fedora/updating-modules — French
Modules built from modulemd-packager format are supported since Fedora 34 and RHEL 9.
 
fedora-docs-l10n/modularity/master/pages/core-concepts/upgrade-paths — French
Observe that with the dynamic context a module maintainer cannot express that `foo:stream:0:Z` or `foo:stream:1:B` should upgrade to `foo:stream:2:C` if the maintainer decided to change a dependency from `bar:x` to `bar:y` and were unable to build `foo:stream:2:A` (e.g. an upstream rewrote the application from Ruby 2.4 to Ruby 2.6).
 
fedora-docs-l10n/modularity/master/pages/core-concepts/modular-repository — French
<.> modulemd YAML file of module stream `flatpak-runtime:common` <.> modulemd YAML file of module stream `flatpak-runtime:devel` <.> non-modular package `module-build`
 
fedora-docs-l10n/modularity/nav — Spanish
xref:building-modules/copr/building-modules-in-copr.adoc[COPR]
 
fedora-docs-l10n/modularity/master/pages/community — Spanish
Marek Kulik mailto:mkulik@redhat.com[mkulik@redhat.com] — Developer and infrastructure
 
fedora-docs-l10n/modularity/master/pages/policies/index — Spanish
Packages provided from default streams *MAY* depend on content from other default streams. If they do so, this dependency *MUST* be encoded in the module metadata.footnote:[This is so that if the maintainers of either module wishes to change its default stream, it is easy to see what other modules would be impacted and coordinate it.]
 
fedora-docs-l10n/modularity/master/pages/history — Spanish
The most common problem reported for Software Collections was that using them required changes to the applications they wanted to run. SCLs install to a separate filesystem location from more traditional RPMs and applications that rely on them need to know where to look for them. (In SCL parlance, this is called “activating” the collection.)
 
fedora-docs-l10n/modularity/master/pages/core-concepts/module-stream — Spanish
At the time of writing a standard Perl module stream needs to build around 180 RPM packages. Those RPM packages build around 400 source and binary RPM files. So when building four context configurations you get to around 1600 source and binary RPM files.
 
fedora-docs-l10n/modularity/master/pages/building-modules/fedora/adding-new-modules — Spanish
`BRANCH` — name of the stream branch of the package and the module
 
fedora-docs-l10n/modularity/master/pages/building-modules/fedora/building-modules — Spanish
At this point `fedpkg` waits on port 12345 of your system for an incoming connection from your web browser. While `fedpkg` waits for an incoming OIDC answer from your browser, imitate the answer with `curl` tool in a parallel terminal using the very same URL:
 
fedora-docs-l10n/modularity/master/pages/building-modules/local/building-modules-locally — Spanish
Build your module with other SCM
 
fedora-docs-l10n/modularity/master/pages/requirements — Spanish
_Requirement_: It must be possible for users to construct container images based on Fedora content matching the software version they need for their applications.
 
fedora-docs-l10n/modularity/master/pages/building-modules/fedora/module-obsoletes — Spanish
Theses are perhaps the most common scanarios, but check the specification for other workflows:
 
fedora-docs-l10n/modularity/master/pages/core-concepts/consuming — Spanish
Installing a module
 
fedora-docs-l10n/modularity/master/pages/core-concepts/module-context — Spanish
document: modulemd
version: 2
data:
name: perl
stream: "5.32"
version: 3520210922083143
context: ab7e7bfe
static_context: true
arch: x86_64
summary: Practical Extraction and Report Language
description: >
Perl is a high-level programming language with roots in C, sed, awk and shell
scripting. Perl is good at handling processes and files, and is especially good
at handling text. Perl's hallmarks are practicality and efficiency. While it is
used to do a lot of different things, Perl's most common applications are system
administration utilities and web programming.
license:
module:
- MIT
content:
- (Copyright only) and (Artistic or GPL+)
- (GPL+ or Artistic) and (GPLv2+ or Artistic) and MIT
- (GPL+ or Artistic) and Artistic 2.0 and UCD
⋮
xmd: {}
dependencies:
- buildrequires:
perl-bootstrap: [5.32]
platform: [f35]
requires:
platform: [f35]
⋮
 
fedora-docs-l10n/modularity/master/pages/core-concepts/dnf-behavior — Spanish
Specifying a non-existent "module" name should fail.
 
fedora-docs-l10n/modularity/master/pages/building-modules/fedora/updating-modules — Spanish
Modules built from modulemd-packager format are supported since Fedora 34 and RHEL 9.
 
fedora-docs-l10n/modularity/master/pages/policies/naming-guidelines — Spanish
For streams that don't guarantee an API/ABI stability over time and just roll forward, we suggest packagers use one of the following stream names.
 
fedora-docs-l10n/modularity/master/pages/using-modules — Spanish
$ dnf module enable NAME:STREAM
 
fedora-docs-l10n/modularity/master/pages/core-concepts/upgrade-paths — Spanish
Observe that with the dynamic context a module maintainer cannot express that `foo:stream:0:Z` or `foo:stream:1:B` should upgrade to `foo:stream:2:C` if the maintainer decided to change a dependency from `bar:x` to `bar:y` and were unable to build `foo:stream:2:A` (e.g. an upstream rewrote the application from Ruby 2.4 to Ruby 2.6).
 
fedora-docs-l10n/modularity/master/pages/faq — Spanish
I can just ‘dnf downgrade’ to get an older version.. Why do we need modularity?
 
fedora-docs-l10n/modularity/master/pages/core-concepts/modular-repository — Spanish
<.> modulemd YAML file of module stream `flatpak-runtime:common` <.> modulemd YAML file of module stream `flatpak-runtime:devel` <.> non-modular package `module-build`
 
fedora-docs-l10n/modularity/master/pages/policies/packaging-guidelines — Spanish
Packager **MUST NOT** specify `stream`, stream is taken from branch of dist-git repository
 
fedora-docs-l10n/modularity/master/pages/index — Spanish
You need/want to provide additional custom flavours of your existing RPM packages i. e. custom build RPM packages with a variety of features.
 
fedora-docs-l10n/modularity/master/pages/building-modules/copr/building-modules-in-copr — Spanish
And make sure that an https://copr.fedorainfracloud.org/api/[API token is properly configured].
 
fedora-docs-l10n/modularity/master/pages/core-concepts/building — Spanish
Building multiple versions
 
fedora-docs-l10n/modularity/master/pages/history — French
The consequence of this relocation on disk is that users were unable to take existing applications (either FOSS or proprietary) and simply use them. Instead, they had to modify the projects to first activate the collections. This was a consistent pain point.
 
fedora-docs-l10n/modularity/master/pages/requirements — French
Don’t break the app!
 
fedora-docs-l10n/modularity/master/pages/faq — French
Using an older version that is no longer maintained can be dangerous, mostly because of the lack of security updates. Modules, on the other hand, represent a major version that is still being actively maintained by the upstream and therefore should receive updates.
 
fedora-docs-l10n/modularity/nav — French
xref:building-modules/local/building-modules-locally.adoc[Localhost]
 
fedora-docs-l10n/modularity/master/pages/building-modules/copr/building-modules-in-copr — French
To submit a build from locally stored modulemd yaml file, use:
 
fedora-docs-l10n/modularity/master/pages/policies/packaging-guidelines — French
Packager **MUST NOT** specify `version`, it is automatically generated by buildsystem
 
fedora-docs-l10n/modularity/master/pages/policies/naming-guidelines — French
"rolling" for user-focused content meant for general use
 
fedora-docs-l10n/modularity/master/pages/glossary — French
<<Module Metadata (modulemd),Module Metadata>> + built RPMs identified by <<NSVCA,N:S:V:C:A>>.
 
fedora-docs-l10n/modularity/master/pages/building-modules/local/building-modules-locally — French
This feature is experimental use it at own risk. If you can use distgit for building your packages.
 
fedora-docs-l10n/modularity/master/pages/policies/index — French
All packages provided at runtime by the default stream of a module *MUST* provide all the same functionality that a downstream consumer would expect from a package in the non-modular package set.footnote:[If a package is not filtered out from the default module stream, it is going to be part of the default-available content and therefore must be treated (and supported) just like a non-modular package.]
 
fedora-docs-l10n/modularity/master/pages/building-modules/fedora/module-obsoletes — French
Resetting a previously EOLed/obsoleted stream.
 
fedora-docs-l10n/modularity/master/pages/core-concepts/building — French
mod-doc-build-more-versions.png
 
fedora-docs-l10n/modularity/master/pages/core-concepts/module-stream — French
When the input `modulemd-packager` file is processed by the build system it is split into output `modulemd` files which are copies of the `modulemd-packager`, but are updated with the context configuration of each context and the build process of the build system. In our example this would equal to four output `modulemd` yaml files.
 
fedora-docs-l10n/modularity/master/pages/core-concepts/dnf-behavior — French
Specifying a non-existent "stream" (for a valid "module") should fail.
 
fedora-docs-l10n/modularity/master/pages/core-concepts/modular-repository — French
In the second example we have a modular repository with multiple module streams and a non-modular package. The module streams are always present in the repository but are not xref:core-concepts/module-dependency-resolution.adoc#_enabling_a_module_stream[enabled] by default. Module streams need to be enabled by the user before installation. If a module is not enabled by the user the binary RPM artifacts are not included in the dependency resolution and content set creation transactions which are done by DNF. In our example our modular repository contains the `flatpak-runtime` module which has the module streams `flatpak-runtime:common` and `flatpak-runtime:devel`. Each module stream consists of its modulemd YAML file and corresponding binary RPM files whose filenames are listed in the `artifacts` section of the modulemd YAML file.
 
fedora-docs-l10n/modularity/master/pages/core-concepts/nsvca — French
Versions are just updates of a given stream. Technically, version is a number generated by the build system. Higher number always wins. This means that version does not identify a major/minor version of the software but the update/commit to a particular stream.
 
fedora-docs-l10n/modularity/master/pages/core-concepts/module-context — French
Modular dependencies
 
fedora-docs-l10n/modularity/master/pages/core-concepts/consuming — French
To make installation easy, some modules can be also installed as a unit, without the need of enabling them first and then installing individual packages. Installing a module doesn’t necessarily mean installing all of its packages. Modules can define something called an "installation profile" to help users with the installation.
 
fedora-docs-l10n/modularity/master/pages/core-concepts/module-dependency-resolution — French
background-color: green;
width: 50px;
align: center;
}
 
fedora-docs-l10n/modularity/master/pages/building-modules/fedora/adding-new-modules — French
`SERVICE_LEVEL:YYYY-MM-DD`[[SLA]] — expected end of life (e.g. `bug_fixes:2020-12-01`). The date must end with either `12-01` or `06-01`. There are various service levels like `bug_fixes`, `security_fixes`, and `rawhide`. Right now, this is used for locking the branch from pushing new commits there. You can change the date later with a https://pagure.io/releng/new_issue?template=module_eol[releng ticket]. Current dates are stored in https://pdc.fedoraproject.org/rest_api/v1/component-branch-slas/?branch_type=rpm[Product Definition Center]. Other option is to choose a date far in the future so you're not affected. (https://tree.taiga.io/project/modularity-wg/epic/3[Work to fix this is in progress].)
 
fedora-docs-l10n/modularity/master/pages/community — French
Jaroslav Mráček mailto:jmracek@redhat.com[jmracek@redhat.com] — Modularity in DNF
 
fedora-docs-l10n/modularity/master/pages/building-modules/fedora/building-modules — French
$ curl 'http://localhost:12345/?code=7c35ded4-054b-4df0-9151-7ef12c7fb838_xe3JWkvf_sL1UyLOzftHJZ3uIlfOo00N'
 
fedora-docs-l10n/modularity/master/pages/using-modules — French
For example, to make Node.js 8 packages available for installation, run:
 
fedora-docs-l10n/modularity/master/pages/building-modules/fedora/defining-modules — French
document: modulemd-packager
version: 3
data:
... <1>
 
fedora-docs-l10n/modularity/master/pages/building-modules/fedora/updating-modules — French
Changes in the format include: