No description
15d604f32e
If you pass --key to download-build and signed packages aren't available, Koji will skip the unsigned package, or error out. This adds a modified behavior controlled by the new --fallback-unsigned arg. If this is passed with --key, unsigned copies will be downloaded for packages for which no signed copy can be found. This is primarily intended to work with a proposed Bodhi feature: https://github.com/fedora-infra/bodhi/pull/5859 . That would make Bodhi's `bodhi updates download` command automatically try to download signed copies, but I think it would be best if it falls back to getting unsigned copies if that doesn't work. Just failing out entirely seems wrong for that case. Implementing the fallback in Bodhi itself is more awkward and messy than adding it in Koji, and it may be useful for others in Koji I guess. Note there are two distinct 'no signed copies' cases. In the simple one, queryRPMSigs tells us Koji has no record of the package ever being signed with the key in question. In this case we don't bother trying to download a signed copy. In the other case, queryRPMSigs tells us the package *has* been signed with the key, but it turns out that signed copy has been garbage- collected and we can no longer download it. In this case we have to catch the failure on the download attempt and retry the download with sigkey set to None. Signed-off-by: Adam Williamson <awilliam@redhat.com> |
||
|---|---|---|
| builder | ||
| cli | ||
| devtools | ||
| docs | ||
| koji | ||
| kojihub | ||
| plugins | ||
| schemas | ||
| tests | ||
| util | ||
| vm | ||
| www | ||
| .coveragerc | ||
| .coveragerc3 | ||
| .editorconfig | ||
| .flake8 | ||
| .gitignore | ||
| Authors | ||
| COPYING | ||
| koji.next.md | ||
| koji.spec | ||
| LGPL | ||
| Makefile | ||
| README.md | ||
| requirements.txt | ||
| runtests | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
koji - RPM building and tracking system
Koji is an RPM-based build system. The Fedora Project uses Koji for their build system, as do several other projects.
Koji's goal is to provide a flexible, secure, and reproducible way to build software.
Key features:
- New buildroot for each build
- Robust XML-RPC APIs for easy integration with other tools
- Web interface with SSL and Kerberos authentication
- Thin, portable command line client
- Users can create local buildroots
- Buildroot contents are tracked in the database
- Versioned data
Communicate
- Comments, questions, bugs, feedback, ideas, help requests? We'd love to hear from you.
- Mailing lists:
- Development: koji-devel AT lists.fedorahosted.org
- User discussion and Fedora-specific topics: buildsys AT lists.fedoraproject.org
- IRC chat: #koji on libera.chat
Bugs/RFEs
If you have found a bug or would like to request a new feature, please report an issue in Pagure.
Download
The koji source code can be downloaded with git via:
git clone https://pagure.io/koji.git
You may browse code at https://pagure.io/koji
Archived releases can be found at https://pagure.io/koji/releases
Documentation
See: https://docs.pagure.org/koji/