# Pkg Update

> Update an Arch Linux package to a new upstream version. Use when a package version has changed, nvchecker reports a delta, oldver.json is stale, the user asks to update/sync/upgrade a package, or a version bump is needed — even if the user doesn't explicitly mention "PKGBUILD" or "sync-package.sh."

- Skill: `pngdeity/pkg-update` (Agent Skill)
- Install (CLI): `npx skillmds@latest add pngdeity/pkg-update`
- Raw SKILL.md: https://api.skillmd.com/api/skills/pngdeity/pkg-update/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: pngdeity (https://skillmd.com/u/pngdeity)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/pngdeity/pkg-update

---


## Package Update Workflow

When updating a package to a new upstream version:

1. Run the sync script:
   ```bash
   bash scripts/sync-package.sh <pkgname> <version>
   ```
   This performs the hybrid merge with upstream, applies `update.sh`, and updates hashes.

2. Lint the result:
   ```bash
   namcap PKGBUILD
   ```
   Fix any issues before proceeding.

3. Regenerate metadata:
   ```bash
   makepkg --printsrcinfo > .SRCINFO
   ```

4. Build in a clean chroot:
   ```bash
   pkgctl build
   ```
   This verifies the package compiles and passes `check()` in an isolated environment.

5. Sanity check the payload:
   ```bash
   pkgctl diff --list
   ```
   Verify the primary binary, license file, and directory structure are intact. A payload size deviation of >10% or disappearance of `/usr/bin/` targets must be investigated.

6. Acknowledge the update:
   ```bash
   nvtake <pkgname>
   ```
   Refer to the [Debian nvtake manual](https://manpages.debian.org/testing/python3-nvchecker/nvtake.1) for flags. Do not hallucinate options.

7. Commit `PKGBUILD` and `.SRCINFO` together in a single commit. Use the format `<pkgname>: update to <version>`.

## Gotchas

- `pkgctl build` may require a pre-configured chroot. If missing, set up with `mkarchroot`.
- If `updpkgsums` fails due to a re-rolled upstream tarball, verify the file content before accepting new hashes.
- If the `sync-package.sh` merge produces conflicts, manual intervention is required. Hybrid merge conflict recovery is not yet automated (see `docs/TODO.md`).