fedora-docs-l10n/modularity/master/pages/core-concepts/modular-repository — Spanish @ Fedora Weblate: [mcurlej@localhost final_repo]$ tree . ├── 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-config-35-1.module

Zen

Translation

English type: delimited block -

[mcurlej@localhost final_repo]$ tree
.
├── 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-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* <.>
└── repodata
├── 3f869b4cf0d94c0d1b246d05b2c538259430bc03df65277a6b94b96cd0f5aa2d-other.xml.gz
├── 58a1183d84dc7e319fb365b45c661c6653a530eddf0022a42c5caaf591adb2b8-filelists.sqlite.bz2
├── 686ca60dd902af9d4c49968833b3561fe35fd1b8f8f6f722f1a463dfdf559bdc-filelists.xml.gz
├── afe6147edfe3577fc76ca94d86960e3e008f3edfa7ac5dca497f56a3ac41b22b-primary.sqlite.bz2
├── *b68df50bf8d984cdb05fc08d119e72280f7c998486a1ed74c20e632589c00d25-modules.yaml.gz* <.>
├── d9b1a93ec2353fe6c87795dc59cc7142cf54b89cf762e60bf7f74f7266db75f1-primary.xml.gz
├── ef096d0ee7ba59ef7c73c13e38a18c3ead7fef5f21abd115b367e2d9d3c1c39b-other.sqlite.bz2
└── repomd.xml

Spanish

[mcurlej@localhost final_repo]$ tree
.
├── 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-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* <.>
└── repodata
    ├── 3f869b4cf0d94c0d1b246d05b2c538259430bc03df65277a6b94b96cd0f5aa2d-other.xml.gz
    ├── 58a1183d84dc7e319fb365b45c661c6653a530eddf0022a42c5caaf591adb2b8-filelists.sqlite.bz2
    ├── 686ca60dd902af9d4c49968833b3561fe35fd1b8f8f6f722f1a463dfdf559bdc-filelists.xml.gz
    ├── afe6147edfe3577fc76ca94d86960e3e008f3edfa7ac5dca497f56a3ac41b22b-primary.sqlite.bz2
    ├── *b68df50bf8d984cdb05fc08d119e72280f7c998486a1ed74c20e632589c00d25-modules.yaml.gz* <.>
    ├── d9b1a93ec2353fe6c87795dc59cc7142cf54b89cf762e60bf7f74f7266db75f1-primary.xml.gz
    ├── ef096d0ee7ba59ef7c73c13e38a18c3ead7fef5f21abd115b367e2d9d3c1c39b-other.sqlite.bz2
    └── repomd.xml

Needs editing

Skip

	English	Spanish	Actions
	Modular repository	Repositorio Modular
	A standard non-modular RPM repository contains RPM binary files and the repodata directory which is generated by the `createrepo_c` tool. In a non-modular repository the metadata information is stored inside the RPM binary files themselves. So when running `createrepo_c` command on a directory with RPM files present, the metadata is extracted from each of the headers of the RPM files and bundled together in the repodata directory.	Un repositorio RPM estándar no modular contiene archivos binarios RPM y el directorio repodata que es generado por la herramienta `createrepo_c`. En un repositorio no modular los metadatos de información se almacenan dentro de los archivos binarios RPM mismos. De modo que cuando ejecuta el comando `createrepo_c` sobre un directorio con archivos RPM presentes, los metadatos son extraídos de las cabeceras de los archivos RPM y se agrupan en el directorio repodata.
	Modular repository is a standard RPM repository which is extended with modular metadata and modular binary RPM files. A modular repository can consist of non-modular binary RPMs, modular binary RPMs and their corresponding modular metadata. Modular metadata defines a new entity inside a modular repository which is called a module stream. The simplest explanation of a module stream is that a module stream is a group of binary RPM artifacts bound together with extra modular metadata inside a YAML file. + +	El repositorio modular es un repositorio RPM estándar que se extiende con los metadatos modulares y los archivos binarios modulares RPM. Un repositorio modular puede constar de binarios RPMs no modulares, binarios RPMs modulares y sus correspondientes metadatos modulares. Los metadatos modulares definen una nueva entidad dentro de un repositorio modular que es llamado flujo de módulo. La explicación más sencilla de un flujo de módulo es que un flujo de módulo es un grupo de artefactos RPM unidos con metadatos modulares adicionales dentro de un archivo YAML. + +
	Basic modular repository	Repositorio modular básico
	of a Modular repository with one module stream.	de un repositorio Modular con un flujo de módulo.
	[mcurlej@localhost final_repo]$ tree . ├── 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-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 <.> └── repodata ├── 3f869b4cf0d94c0d1b246d05b2c538259430bc03df65277a6b94b96cd0f5aa2d-other.xml.gz ├── 58a1183d84dc7e319fb365b45c661c6653a530eddf0022a42c5caaf591adb2b8-filelists.sqlite.bz2 ├── 686ca60dd902af9d4c49968833b3561fe35fd1b8f8f6f722f1a463dfdf559bdc-filelists.xml.gz ├── afe6147edfe3577fc76ca94d86960e3e008f3edfa7ac5dca497f56a3ac41b22b-primary.sqlite.bz2 ├── b68df50bf8d984cdb05fc08d119e72280f7c998486a1ed74c20e632589c00d25-modules.yaml.gz <.> ├── d9b1a93ec2353fe6c87795dc59cc7142cf54b89cf762e60bf7f74f7266db75f1-primary.xml.gz ├── ef096d0ee7ba59ef7c73c13e38a18c3ead7fef5f21abd115b367e2d9d3c1c39b-other.sqlite.bz2 └── repomd.xml	[mcurlej@localhost final_repo]$ tree . ├── 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-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 <.> └── repodata ├── 3f869b4cf0d94c0d1b246d05b2c538259430bc03df65277a6b94b96cd0f5aa2d-other.xml.gz ├── 58a1183d84dc7e319fb365b45c661c6653a530eddf0022a42c5caaf591adb2b8-filelists.sqlite.bz2 ├── 686ca60dd902af9d4c49968833b3561fe35fd1b8f8f6f722f1a463dfdf559bdc-filelists.xml.gz ├── afe6147edfe3577fc76ca94d86960e3e008f3edfa7ac5dca497f56a3ac41b22b-primary.sqlite.bz2 ├── b68df50bf8d984cdb05fc08d119e72280f7c998486a1ed74c20e632589c00d25-modules.yaml.gz <.> ├── d9b1a93ec2353fe6c87795dc59cc7142cf54b89cf762e60bf7f74f7266db75f1-primary.xml.gz ├── ef096d0ee7ba59ef7c73c13e38a18c3ead7fef5f21abd115b367e2d9d3c1c39b-other.sqlite.bz2 └── repomd.xml
	1 directory, 13 files [mcurlej@localhost final_repo]$	1 directorio, 13 archivos [mcurlej@localhost final_repo]$
	<.> modulemd YAML file which holds information about one module stream <.> modules.yaml.gz file which holds information about all the module streams in the repository	<.> archivo modulemd YAML que contiene información sobre un flujo de módulo <.> archivo modules.yaml.gz que contiene información sobre todos los flujos de módulo en el repositorio
	In the first example we have a simple tree view of a modular repository. The repository contains the RPM packages `flatpak-rpm-macros` and `flatpak-runtime-config` both of those are the components of the module stream which is defined in the `flatpak-runtime:devel:20220211094818:1234:x86_64.modulemd` YAML file. The binary RPM files are also defined in the YAML metadata as the artifacts of the module stream.
	A shorthand expression for modular metadata is modulemd
	Running `createrepo_c` on such a directory will generate a repodata directory but with one extra file. The file is `\-modules.yaml.gz` and holds the YAML modulemd from all the present module stream YAML modulemd files in the directory. The `-modules.yaml.gz` describes to DNF how many module streams are present in the modular repository, how they can be installed and which module streams cover which RPM packages. More on module streams can be found xref:core-concepts/module-stream.adoc[here].
	Modular binary RPM files can NOT be installed without the corresponding metadata. A module stream inside a repository HAS to always consist of a modulemd YAML file and the modular binary RPM files.
	Mixed modular repository
	of a modular repository with multipe module streams and non-modular packages
	[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]$
	<.> modulemd YAML file of module stream `flatpak-runtime:common` <.> modulemd YAML file of module stream `flatpak-runtime:devel` <.> non-modular package `module-build`
	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.
	The non-modular package `module-build` in our modular repository behaves like it would in a non-modular repository. More about how you can enable and install module streams can be found in the section xref:using-modules.adoc[Using modules].
	RPMs inside a modular repository are still standard source and binary RPM files. They are still using the NEVRA (name-epoch-version-release-architecture) naming convention. As you can see in our example the RPM files have the same name and version. The unique identifier here is the release (or distag) of the filename. The modular RPM files in the example were built by the tool link:https://github.com/mcurlej/module-build[module-build]. The release part is defined by the tool or distribution pipeline you are using to build the RPM files.

Loading…

vareli

Translation added

English

Spanish 1029 characters edited Current translation Translated

6 months ago

None

String updated in the repository

English

Spanish 0 characters edited Empty

10 months ago

Browse all string changes

Things to check

Unchanged translation

Source and translation are identical

Reset

Glossary

English	Spanish
No related strings found in the glossary.

16773029 String information

Source string description

type: delimited block -

Flags

no-wrap

Source string location

./pages/core-concepts/modular-repository.adoc:35

String age

10 months ago

Last updated

6 months ago

Source string age

2 years ago

Translation file

po/es/master/pages/core-concepts/modular-repository.po, string 6

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.