Package: depthcharge-tools (0.6.1-1)
Tools for ChromeOS firmware/bootloader integration
Package information
- Homepage
- [https://github.com/alpernebbi/depthcharge-tools]
- License
- Unknown: not reported in the indexed source
- Downstream package maintainer
- Debian Python Teamteam+python@tracker.debian.org
- Software project
- [depthcharge-tools]
Versions and downloads for depthcharge-tools
| Version / release | Architecture / repository | Package size | Installed size | Files | Publisher repository artifact |
|---|---|---|---|---|---|
| 0.6.1-1bookworm / main | allDebian 12 · main · amd64 | 82 KiB | 400 KiB | list of files | depthcharge-tools_0.6.1-1_all.deb |
| 0.6.1-1bookworm / main | allDebian 12 · main · arm64 | 82 KiB | 400 KiB | list of files | depthcharge-tools_0.6.1-1_all.deb |
About these downloads
Each row is recorded package-index metadata for one version, architecture, suite, and repository. Names, URLs, and sizes are source-reported; a link is a potentially mutable retrieval location, not an OpenFactory redistribution claim or proof that OpenFactory retained the artifact bytes.
Dependencies and recommendations for depthcharge-tools
View 14 package relationships
pre: [init-system-helpers] (>= 1.54~)
helper tools for all init systems
dep: [python3-pkg-resources]
Package Discovery and Resource Access using pkg_resources
dep: [python3] (>= 3.7~) [any]
interactive high-level object-oriented language (default python3 version)
dep: [linux-base]
Linux image base package
dep: [u-boot-tools]
companion tools for Das U-Boot bootloader
dep: [device-tree-compiler]
Device Tree Compiler for Flat Device Trees
dep: [vboot-utils]
Chrome OS verified u-boot utilities
dep: [vboot-kernel-utils]
Chrome OS verified boot utils required to sign kernels
dep: [cgpt]
GPT manipulation tool with support for Chromium OS extensions
dep: [lz4]
Fast LZ compression algorithm library - tool
dep: [xz-utils]
XZ-format compression utilities
Package file paths (0)
Paths come from the repository package-file index for the observed builds. They describe archive/package associations, not every file that will exist on a running system after maintainer scripts, alternatives, generated state, diversions, or installation choices.
No package-associated file paths were observed for the displayed build metadata.
Field source: Debian 12 (Bookworm) main amd64
