Easier Gentoo system maintenance
This is a set of commands to simplify maintaining a Gentoo system.
Installation
Poetry
poetry add upkeep
Pip
pip install upkeep
emerges
This command will do the following:
- Update Portage
- Update
@worldwith options--with-bdeps=y,--update,--deep,--newuse - Update live installations of packages (
@live-rebuild) - Run
emerge @preserved-rebuild - Run
systemctl daemon-reexec(if applicable) - Update the kernel
There are flags to disable most parts of this functionality, such as
--no-upgrade-kernel. Pass --help to see all the options.
Automatic kernel update process
Older versions of this tool supported various ways to update the kernel to boot from. However this
is better left to the configuration and hooks of kernelinstall which is invoked by make install.
The automatic kernel update will only work if there are 2 kernels displayed
with the command eselect --brief kernel list. The first one in the list must
be the active kernel. The second one is the one to upgrade to. After switching
to the new kernel, a .config must exist in /usr/src/linux or the command
will not run make. If the configuration exists at /proc/config.gz it will
be used.
If emerges fails to build the kernel because of the state of
eselect kernel list, you can fix it and re-run the update by running
upgrade-kernel.
The old kernel data in /boot will be stored in /root/.upkeep/old-kernels.
If you want to only rebuild the kernel, run rebuild-kernel.
ecleans
This command will run the following commands (or equivalents):
emerge --depcleanemerge @preserved-rebuildrevdep-rebuildeclean-dist --deeprm -fR /var/tmp/portage/*
Metadata
Release files for upkeep 1.7.1
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 | Actions |
|---|---|---|---|---|
| upkeep-1.7.1.tar.gz | 16.5 kB | With provenance | Details for upkeep-1.7.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| upkeep-1.7.1-py3-none-any.whl | Python 3 | none | any | Details for upkeep-1.7.1-py3-none-any.whl |
Total release size: 30.2 kB
Release files / upkeep-1.7.1.tar.gz
| Download URL | upkeep-1.7.1.tar.gz |
|---|---|
| Size | 16.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c47f97cd5f69b3a8043bd44317fef77e12f3de34566890d9e2a65804cdc7efb6
|
|
BLAKE2b-256 checksum How to use checksums |
55f92d1f6a8f69344e4e9124fca170cb25ff3b6cbad6fe4ad03b3aadcf7c26ba
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 3, 2026.
Transparency logRelease files / upkeep-1.7.1-py3-none-any.whl
| Download URL | upkeep-1.7.1-py3-none-any.whl |
|---|---|
| Size | 13.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7146b2aca1af39ced13af3b67f79af5a4d3ee6f5b06602cca1eb4c0f3166e6c8
|
|
BLAKE2b-256 checksum How to use checksums |
8458fb16f63d0bee02961a31f3a840b1e4e535f40bee2e4d18e3a5fdcd1a290d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 3, 2026.
Transparency logSecurity for upkeep 1.7.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for upkeep-1.7.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 3, 2026.
Transparency logA 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.