Skip to content

Name the built .deb after the architecture it was built for - #2

Open
Gjuju wants to merge 1 commit into
moode-player:mainfrom
Gjuju:contrib/plugin-install-arch-portable
Open

Gjuju wants to merge 1 commit into
moode-player:mainfrom
Gjuju:contrib/plugin-install-arch-portable

Conversation

@Gjuju

@Gjuju Gjuju commented Sep 18, 2026

Copy link
Copy Markdown

The three renderer plugins (librespot, shairport-sync, pibuz) clone pkgbuild and run build.sh, which compiles for the machine it runs on — then read back a filename pinned to _arm64.deb.
That's not really a moode related problem but on any other architecture the build will succeeds and the install then fails on a misnamed package.

As dpkg --print-architecture returns arm64 on a Pi, so the resolved filename is unchanged there but can be installed on any other arch.
Checked on arm64, armhf and amd64.

One line per script:

PKG_ARCH=$(dpkg --print-architecture)
PACKAGE_DEB=$PACKAGE"_"$VERSION"_"$PKG_ARCH".deb"

The .zip beside each update/ directory is regenerated to match.

ex: on my 3 nopi boxes

N4000       pibuz_2.4.2~dev.1-1_amd64.deb
Opi 3 LTS   pibuz_2.4.2~dev.1-1_arm64.deb
Opi PC+     pibuz_2.4.2~dev.1-1_armhf.deb

The build step is already architecture-agnostic: it clones pkgbuild and
runs build.sh, which compiles for the running machine. Only the filename
read back afterwards was pinned to arm64, so the install step looks for a
package that was never produced.

dpkg --print-architecture returns arm64 on a Pi, so the resolved filename
is unchanged there.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant