build-reborn: SRC path ($PROJECT_DIR/Syplheed-Reborn) doesn't exist in this container #26

New Issue

sylph-decoder · 2026-09-12T13:28:58Z

sylph-decoder commented

2026-09-12 13:28:58 +00:00

/usr/local/bin/build-reborn (the Decoder's own wrapper for
cargo build|test --workspace with SYLPHEED_DISC/CARGO_BUILD_JOBS
wired up) hardcodes:

SRC="${PROJECT_DIR:-/work}/Syplheed-Reborn"
cd "$SRC"

That path doesn't exist anywhere in this container (checked: not under
/work, not found by find / -iname '*Syplheed*' -o -iname '*Sylpheed-Reborn*') — the repo is mounted directly at $PROJECT_DIR
(/work), which is where Cargo.toml and everything else actually lives.
Running build-reborn test fails immediately on the cd under
set -euo pipefail, before touching cargo at all.

Not new breakage from today — docs/re/REFUTED.md and
docs/re/test-suite-runtime.md (2026-08-29) both cite a real, completed
build-reborn test run, so the tool worked at some point. Either the
container's layout changed since (repo un-nested from a
Sylpheed-Reborn/Syplheed-Reborn subdirectory to living at /work
directly) or this container's layout was always different from whatever
the script assumed — I don't have visibility into the Port's container to
tell which.

Worked around this iteration by exporting SYLPHEED_RES3D/
CARGO_BUILD_JOBS and running cargo test --workspace directly from
/work — same effective invocation, minus the broken cd. Not filing a
fix myself: I don't know whether /usr/local/bin/build-reborn is
container-image tooling shared with the Port's container (where the old
path might still be correct) or something safe for me to edit directly.

Pass: either the cd's target fixed to match this container's actual
layout, or confirmation this container's layout is the outlier and the
workaround above is the intended answer going forward.

Low urgency — cheap workaround exists — but real: this is exactly the
"build-reborn test wires up SYLPHEED_DISC... prefer it over a raw
cargo test --release" guidance in every Decoder loop prompt, and as
written it can't be followed literally in this container.

`/usr/local/bin/build-reborn` (the Decoder's own wrapper for `cargo build|test --workspace` with `SYLPHEED_DISC`/`CARGO_BUILD_JOBS` wired up) hardcodes: ```sh SRC="${PROJECT_DIR:-/work}/Syplheed-Reborn" cd "$SRC" ``` That path doesn't exist anywhere in this container (checked: not under `/work`, not found by `find / -iname '*Syplheed*' -o -iname '*Sylpheed-Reborn*'`) — the repo is mounted directly at `$PROJECT_DIR` (`/work`), which is where `Cargo.toml` and everything else actually lives. Running `build-reborn test` fails immediately on the `cd` under `set -euo pipefail`, before touching cargo at all. **Not new breakage from today** — `docs/re/REFUTED.md` and `docs/re/test-suite-runtime.md` (2026-08-29) both cite a real, completed `build-reborn test` run, so the tool worked at some point. Either the container's layout changed since (repo un-nested from a `Sylpheed-Reborn`/`Syplheed-Reborn` subdirectory to living at `/work` directly) or this container's layout was always different from whatever the script assumed — I don't have visibility into the Port's container to tell which. **Worked around this iteration** by exporting `SYLPHEED_RES3D`/ `CARGO_BUILD_JOBS` and running `cargo test --workspace` directly from `/work` — same effective invocation, minus the broken `cd`. Not filing a fix myself: I don't know whether `/usr/local/bin/build-reborn` is container-image tooling shared with the Port's container (where the old path might still be correct) or something safe for me to edit directly. **Pass:** either the `cd`'s target fixed to match this container's actual layout, or confirmation this container's layout is the outlier and the workaround above is the intended answer going forward. Low urgency — cheap workaround exists — but real: this is exactly the "`build-reborn test` wires up `SYLPHEED_DISC`... prefer it over a raw `cargo test --release`" guidance in every Decoder loop prompt, and as written it can't be followed literally in this container.

sylph-decoder added the kind/defect state/proposed labels 2026-09-12 13:29:03 +00:00

fabi commented

2026-09-17 19:02:13 +00:00

Still literally true: docker/decoder/sylph-decoder and docker/port/bin/build-reference-cli on main still name Syplheed-Reborn, which has been archived read-only since the consolidation (docs/agents/CONSOLIDATION.md), and nothing mounts that path any more.

Closing as obsolete rather than fixing it. The agent and container tooling is parked for a from-scratch redo, so these wrappers get rewritten, not patched — a path fix now would only make a dead script look alive. If the redo revives a build-reborn equivalent, re-file against the new script.

Still literally true: `docker/decoder/sylph-decoder` and `docker/port/bin/build-reference-cli` on `main` still name `Syplheed-Reborn`, which has been archived read-only since the consolidation (`docs/agents/CONSOLIDATION.md`), and nothing mounts that path any more. **Closing as obsolete rather than fixing it.** The agent and container tooling is parked for a from-scratch redo, so these wrappers get rewritten, not patched — a path fix now would only make a dead script look alive. If the redo revives a `build-reborn` equivalent, re-file against the new script.

fabi closed this issue

2026-09-17 19:02:14 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: fabi/Sylpheed#26

build-reborn: SRC path ($PROJECT_DIR/Syplheed-Reborn) doesn't exist in this container #26

build-reborn: SRC path (`$PROJECT_DIR/Syplheed-Reborn`) doesn't exist in this container #26