.deb package available only for amd64 #1331

New Issue

BCMM · 2022-12-02T10:29:52Z

BCMM commented

2022-12-02 10:29:52 +00:00

I would like to install the backend on a Debian armhf server. Is it intentional that the Debian package is only available for amd64?

konrad commented

2022-12-02 15:24:49 +00:00

It's not intentional, it just hasn't been implemented yet. Looks like nfpm does support different architectures but not different binaries for these architectures. If I understand it correctly that means we'd need to template the nfpm config file and run it once for every architecture, adding the previously built binaries for each arch.

Do you want to send a PR?

It's not intentional, it just hasn't been implemented yet. Looks like nfpm does support different architectures but not different binaries for these architectures. If I understand it correctly that means we'd need to template the nfpm config file and run it once for every architecture, adding the previously built binaries for each arch. Do you want to send a PR?

konrad added the

kind/feature

label 2022-12-02 15:24:56 +00:00

BCMM commented

2023-01-25 18:00:58 +00:00

Poster

Do you want to send a PR?

I'm afraid the whole Go ecosystem, including its build tools, is rather unfamiliar to me. I'm still not quite clear which components are involved in building Vikunja and how they interact.

(Sorry for the closing/reopening. I pressed the wrong button.)

> Do you want to send a PR? I'm afraid the whole Go ecosystem, including its build tools, is rather unfamiliar to me. I'm still not quite clear which components are involved in building Vikunja and how they interact. (Sorry for the closing/reopening. I pressed the wrong button.)

BCMM closed this issue

2023-01-25 18:00:58 +00:00

BCMM reopened this issue

2023-01-25 18:01:06 +00:00

konrad commented

2023-01-25 21:18:46 +00:00

Sure, that's fine!

The nfpm config docs show they expand environment variables, maybe that could be used to release packages from different binaries (talking about the ci)

https://nfpm.goreleaser.com/configuration/

Sure, that's fine! The nfpm config docs show they expand environment variables, maybe that could be used to release packages from different binaries (talking about the ci) https://nfpm.goreleaser.com/configuration/

Sign in to join this conversation.