Zen

Source string Source string

94/10000 · 94

The string is read only.

English Actions
To submit a build from locally stored modulemd yaml file, use:
copr-cli build-module --yaml /some/path/testmodule.yaml <COPR project name>
If the modulemd yaml file is available on a URL accessible for public, use following:
copr-cli build-module --url https://example/some/path/testmodule.yaml <COPR project name>
To specify a different project owner (e.g. when building into a group project), use:
copr-cli build-module --yaml /some/path/testmodule.yaml @mygroup/testmodule
For more information, see `copr-cli build-module --help` or `man copr-cli`.
Generate modulemd from a Copr project
This method aims to provide modularity features with the lowest entry barrier possible. It doesn't demand a user to know either how to write modulemd yaml file nor using the command line. The only prerequisite is to have a Copr project with some package successfully built in it.
Open your project, click on `Modules`, then click to `New Module`. The input page looks like this.
copr-build-new-module.png
It provides a list of all successfully built packages in the project. By default, they are all selected to become part of the module. Uncheck those that are not wanted. Optionally specify https://pagure.io/modulemd/blob/ade28f3f3b39fcddcb626ca915df1a6ce35c14fd/f/spec.yaml#_137[a module API] or its https://pagure.io/modulemd/blob/ade28f3f3b39fcddcb626ca915df1a6ce35c14fd/f/spec.yaml#_90[profiles].
Modules with Copr packages
It is trivial to achieve when generating modulemd from Copr project. This section describes a special case of how to add a Copr package into an existing custom modulemd yaml file.
Update `components.rpms` section and add a new package definition.
hello:
rationale: Showing how to use a package from Copr
ref: ...
repository: ...
The `...` placeholders need to be replaced with real values. Open a web browser and navigate to a build detail whose results should be used by the module. The build needs to be finished successfully. Scroll down to the `Results` section.
copr-build-result.png
Use the hash value from the `Dist Git Source` column as a `ref` in the modulemd.
Follow the link of the `Dist Git Source` value to a Copr distgit instance. Use the URL as a `repository` in modulemd - with some small adjustments.
Trim everything after `.git`
Replace `/cgit/` with `/git/`
copr-disgit.png
To avoid confusion, here are some example values.
hello:
rationale: Showing how to use a package from Copr
ref: 9d1ced1
repository: http://copr-dist-git.fedorainfracloud.org/git/frostyx/hello/hello.git
Modules in Copr as dependencies
At this moment, Copr doesn't properly parse module dependencies from modulemd yaml file. They need to be explicitly enabled in the project settings - more precisely chroot settings within a project.
When the dependency comes from Fedora repositories, simply edit `Enable module` field and append the module in `name:stream` format.
If the dependency was built in Copr, it is necessary to edit also the `Repos` field and provide a repository URL from which the module can be installed. See the <<Installing modules from Copr>> section to learn how to find a repofile for a module (in this case the module that is used as a dependency). Use it's `baseurl` as the value for `Repos` field.
Installing modules from Copr
Currently `dnf copr` plugin does not support enabling module repositories and therefore it needs to be done manually. Navigate to a Copr project in a web browser, see the `Modules` page, and open detail of a module that is to be installed. If the build is still running, wait until it finishes. For successfully built modules, a "How to use" section is displayed. Follow its instructions. After that, standard DNF commands for manipulation with modules can be used.

Loading…

User avatar None

Source string added
hello:
rationale: Showing how to use a package from Copr
ref: ...
repository: ...
4 years ago
Browse all string changes

Things to check

Ellipsis

The string uses three dots (...) instead of an ellipsis character (…)

Reset

Glossary

English English
No related strings found in the glossary.

String information

Source string description
type: delimited block -
Flags
no-wrap, read-only
Source string location
./pages/building-modules/copr/building-modules-in-copr.adoc:100
String age
4 years ago
Last updated
a year ago
Source string age
4 years ago
Translation file
pot/master/pages/building-modules/copr/building-modules-in-copr.pot, string 32