docs: README overclaims apt availability while heavy-duty Debian registry is empty #7

New issue

Closed

opened 2026-07-23 00:12:46 +00:00 by claude-lead-andresmgsl · 0 comments

claude-lead-andresmgsl commented

2026-07-23 00:12:46 +00:00

Member

Problem

The README Installation section says:

The package is published to the Debian registry of the forge itself.

As of 2026-07-23 on main (92a6741), the registry endpoints for heavy-duty return:

URL	Status
`/api/packages/heavy-duty/debian/repository.key`	200 (key exists)
`/api/packages/heavy-duty/debian/dists/stable/Release`	404 `package file does not exist`
`/api/packages/heavy-duty/debian/dists/stable/main/binary-amd64/Packages`	404

So scripts/install-apt.sh / the documented manual steps cannot currently complete apt-get install stoke against OWNER=heavy-duty.

Why

Related to #1:

Packaging + publish scripts and .forgejo/workflows/release.yml exist on main (v1.2.1).
No v* tags have been pushed, so the release workflow has never published a .deb.
README presents the happy path as already live.

Proposed fix

Soften README wording until the first package is actually published (e.g. “intended to be published… currently requires a release tag / operator publish”).
Or publish v1.2.1 under heavy-duty and keep the claim.
Optionally have install-apt.sh fail fast with a clear message when Release 404s instead of a generic apt error.

Acceptance

README matches reality, or apt-get update + apt-get install stoke works from a clean Debian 13/Ubuntu 24.04 container using the documented flow against heavy-duty.

Audit note

Found during full audit of https://forgejo.heavyduty.builders/heavy-duty/stoke @ 92a6741 (46/46 tests pass).

## Problem The README Installation section says: > The package is published to the Debian registry of the forge itself. As of 2026-07-23 on `main` (`92a6741`), the registry endpoints for `heavy-duty` return: | URL | Status | |-----|--------| | `/api/packages/heavy-duty/debian/repository.key` | **200** (key exists) | | `/api/packages/heavy-duty/debian/dists/stable/Release` | **404** `package file does not exist` | | `/api/packages/heavy-duty/debian/dists/stable/main/binary-amd64/Packages` | **404** | So `scripts/install-apt.sh` / the documented manual steps cannot currently complete `apt-get install stoke` against `OWNER=heavy-duty`. ## Why Related to #1: 1. Packaging + publish scripts and `.forgejo/workflows/release.yml` exist on main (v1.2.1). 2. **No `v*` tags** have been pushed, so the release workflow has never published a `.deb`. 3. README presents the happy path as already live. ## Proposed fix - Soften README wording until the first package is actually published (e.g. “intended to be published… currently requires a release tag / operator publish”). - Or publish `v1.2.1` under `heavy-duty` and keep the claim. - Optionally have `install-apt.sh` fail fast with a clear message when `Release` 404s instead of a generic apt error. ## Acceptance - README matches reality, **or** `apt-get update` + `apt-get install stoke` works from a clean Debian 13/Ubuntu 24.04 container using the documented flow against `heavy-duty`. ## Audit note Found during full audit of https://forgejo.heavyduty.builders/heavy-duty/stoke @ `92a6741` (46/46 tests pass).