misoctl
Upload Debian builds to Koji as a content generator.
Example
Here’s an example of building a package, uploading the artifacts to Koji, and tagging the resulting build:
# Clone a Debian package (ceph-ansible) from Git: SCM_URL=git://example.com/ceph-ansible git clone $SCM_URL cd mypackage # Build the package: gbp buildpackage ... # Upload the source and .deb artifacts into Koji: cd .. misoctl upload \ --scm-url=$SCM_URL \ --owner=kdreyer \ --tag=ceph-3.2-xenial-candidate \ ceph-ansible/
To run this utility, you must authenticate to Koji as a user account that has permission to upload to the “debian” content generator.
Koji server configuration
You must configure your Koji instance to accept debian builds.
As a Koji administrator:
Allow “debian” content-generator access to a system account. In this case ours is named “rcm/debbuild”:
koji grant-cg-access rcm/debbuild debian
Add the debian build type to Koji:
koji call addBType debian
Add the debian archive types (needs the new addArchiveType RPC <https://pagure.io/koji/pull-request/1149> on the Koji hub):
koji call addArchiveType deb "Debian packages" deb koji call addArchiveType dsc "Debian source contro files" dsc
Now you can run misoctl upload as the rcm/debbuild system user.
About the Name
This tool is similar to chacractl, and Koji is an ingredient in Miso.
Metadata
Release files for misoctl 0.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| misoctl-0.0.2.tar.gz | 7.6 kB | Without provenance | Details |
Release files / misoctl-0.0.2.tar.gz
| Download URL | misoctl-0.0.2.tar.gz |
|---|---|
| Size | 7.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
408b5b57f74500e73e0adb41e66f46d25fe4e6e285413bb254597ee0741fcd92
|
|
BLAKE2b-256 checksum How to use checksums |
a688e16207e19e4d74f995a2d3b11d89815288bf8b3f98f00ed53b422c554962
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.10.0 pkginfo/1.4.2 requests/2.20.0 setuptools/40.4.3 requests-toolbelt/0.8.0 tqdm/4.19.6 CPython/3.7.1
|
Security for misoctl 0.0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.