Pi:admin pupextract: Difference between revisions
via /pi-wiki-publish |
No edit summary |
||
| Line 5: | Line 5: | ||
== Prerequisits == | == Prerequisits == | ||
* NextPi Version: 1. | * NextPi Version: 1.91D | ||
== Backend == | == Backend == | ||
Latest revision as of 14:58, 5 May 2026
Abstract
`nextpi-admin_pupextract` validates a Pi Update Patch (`.PUP`) file's header and extracts its payload archive ready for a subsequent update step.
Prerequisits
- NextPi Version: 1.91D
Backend
- Binary: Proprietory
Options
-h display usage information
-vl verbose logging (writes to /tmp/puphelper.log)
-c check the patch's version requirement against the running system without extracting
A single positional argument names the .PUP file to inspect.
Behaviour
The first 512 bytes of the file are read as a PUP header. The header is rejected unless its signature reads PUP, its secondary signature byte is 254, and its version field is 1. If the header's strict flag is set, the header's piMajor and piMinor must match the running NextPi's major and minor version; otherwise the patch is refused.
On success, the payload that follows the header is copied to /ram/update.tbz in 1 MiB chunks, ready for a subsequent step in the update pipeline.
Errors
- File of 512 bytes or fewer — too small to contain a header.
- Header signature mismatch — not a PUP, or unsupported version.
- Strict-mode version mismatch — the running NextPi does not satisfy the patch's version requirement.