Describe the bug
The deb recipe builds the loong64 package with an incorrect copy destination. Other architectures copy the binary to usr/local/bin/g, but the loong64 branch copies it into usr.
This can produce a loong64 .deb package without the expected /usr/local/bin/g executable.
To Reproduce
- Build release artifacts including deb packages:
- Inspect the loong64 package contents.
- The binary path differs from other architectures.
Screenshots
Not applicable.
Info (please complete the following information):
- OS: release packaging
- Version: v0.31.2
Additional context
Relevant line in justfile:
cp build/g-linux-loong64 build/g_{{latest}}_loong64/usr
It likely should mirror the other architectures and copy to:
build/g_{{latest}}_loong64/usr/local/bin/g
Describe the bug
The
debrecipe builds the loong64 package with an incorrect copy destination. Other architectures copy the binary tousr/local/bin/g, but the loong64 branch copies it intousr.This can produce a loong64
.debpackage without the expected/usr/local/bin/gexecutable.To Reproduce
Screenshots
Not applicable.
Info (please complete the following information):
Additional context
Relevant line in
justfile:cp build/g-linux-loong64 build/g_{{latest}}_loong64/usrIt likely should mirror the other architectures and copy to:
build/g_{{latest}}_loong64/usr/local/bin/g