Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/ironthree/fedora-update-feedback
fedora-easy-karma on steroids
https://github.com/ironthree/fedora-update-feedback
Last synced: 3 months ago
JSON representation
fedora-easy-karma on steroids
- Host: GitHub
- URL: https://github.com/ironthree/fedora-update-feedback
- Owner: ironthree
- License: apache-2.0
- Created: 2020-01-09T10:42:16.000Z (about 5 years ago)
- Default Branch: main
- Last Pushed: 2024-04-07T12:47:24.000Z (10 months ago)
- Last Synced: 2024-09-30T05:06:33.597Z (4 months ago)
- Language: Rust
- Size: 288 KB
- Stars: 4
- Watchers: 2
- Forks: 1
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Funding: .github/FUNDING.yml
- License: LICENSE-APACHE
Awesome Lists containing this project
README
# fedora-update-feedback
[](https://crates.io/crates/fedora-update-feedback/)
[](https://crates.io/crates/fedora-update-feedback/)
[](https://crates.io/crates/fedora-update-feedback/)
[](https://docs.rs/fedora-update-feedback/)
This project is inspired by [fedora-easy-karma][f-e-k], but with more features.
[f-e-k]: https://pagure.io/fedora-easy-karma
It allows submitting feedback for bugs and test cases in addition to providing a
comment and karma.
By default, all updates in the `testing` state that the user has not submitted
themselves or has already commented on are presented, sorted by ascending
submission date (so, oldest to most recent update).
### requirements
The program assumes that the `dnf` and `rpm` binaries are present on the system
(which is probably a reasonable assumption for a CLI tool targeted at fedora
users).
It also expects a config file at `~/.config/fedora.toml`, with at least the
following contents:
```toml
[FAS]
username = "USERNAME"
```
If this file is not present, the legacy `~/.fedora.upn` file is used as a
fallback mechanism.
If both files are not present, the username has to be specified with the
`--username USERNAME` CLI switch.
The username is used to authenticate with bodhi, and to filter out updates that
the user themselves has submitted, or has already commented on.
### features
By default, `fedora-update-feedback` queries bodhi for updates for the current
release that are in the `testing` state.
Some additional options can be set either on the command line, or in a
`[fedora-update-feedback]` section in the `~/.config/fedora.toml` configuration
file.
With the `--check-pending` CLI switch or the `check-pending = true`
configuration option, updates in the `pending` state are also queried (for
example, if the user has manually installed builds from koji and wants to give
bodhi feedback for those as well).
Additionally, with the `--check-obsoleted` and `--check-unpushed` flags (or
the `check-obsoleted = true` and `check-unpushed` configuration options),
`fedora-update-feedback` will check if any lingering builds from unpushed
or obsoleted updates are still installed locally.
With the `save-password = true` configuration option, `fedora-update-feedback`
will attempt to securely save the FAS password in the login keyring, so it
does not have to be entered every time. To ignore or overwrite a stored
password, use the `--ignore-keyring` CLI switch.
This information is also printed when running `fedora-update-feedback --help`.
### installation
**RPM packages**:
RPM packages are now available from the official fedora repositories.
**Compiling manually**:
To compile the program, first install `cargo` (the build tool, also pulls in
the Rust compiler) and `openssl-devel` (used by the OpenSSL rust bindings).
To download, build, and install the latest version from ,
just run `cargo install fedora-update-feedback`.
To build from the sources provided on , download the sources
(recommended: tarball of the latest release from GitHub), and easily build
and install the binary for yourself by running `cargo install --path .` in
the source directory.
Either way, `cargo` will install the binary into `~/.cargo/bin` by default.
To make it available in `$PATH`, either copy it into `$HOME/.local/bin`, or add
`~/.cargo/bin` to your `$PATH` (probably by editing `~/.bash_profile`).
### development + debugging
By default, no "structured" log messages from `fedora-update-feedback` or any
of the invoked libraries should be visible when running
`fedora-update-feedback`. For debugging and development purposes, they can be
turned on by setting the `FUF_LOG` environment variable:
```
FUF_LOG=debug cargo run
```
### TODO
- I'd like to improve the "visual quality" of the terminal output and
pretty-printed data, which should be easy.
- It would be great to add additional switches and arguments to the binary (for
example, sorting updates by a different value than submission date).