Source: forgejo-cli Version: 0.3.0-4 Severity: serious Tags: FTBFS, patch User: debian-ri...@lists.debian.org Usertags: riscv64
Dear forgejo-cli maintainer,
The package forgejo-cli build failed on riscv64.The crucial buildd log
below:
```
dh_auto_test -- test --all
debian cargo wrapper: options = ['parallel=4'], profiles = [],
parallel = ['-j4'], lto =
debian cargo wrapper: rust_type = riscv64gc-unknown-linux-gnu,
gnu_type = riscv64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
'/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose',
'--verbose', '-j4', '--target', 'riscv64gc-unknown-linux-gnu',
'--all'],) {}
error: no matching package found
searched package name: `hex`
perhaps you meant: aes, h2, h3, ...
location searched: directory source
`/build/reproducible-path/forgejo-cli-0.3.0/debian/cargo_registry`
(which is replacing registry `crates-io`)
required by package `sha256 v1.6.0`
... which satisfies dependency `sha256 = "^1.6.0"` of package
`forgejo-cli v0.3.0 (/build/reproducible-path/forgejo-cli-0.3.0)`
dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned
exit code 101
make[1]: *** [debian/rules:7: override_dh_auto_test] Error 25
make[1]: Leaving directory '/build/reproducible-path/forgejo-cli-0.3.0'
make: *** [debian/rules:4: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned
exit status 2
```
The full buildd log is here:
https://buildd.debian.org/status/fetch.php?pkg=forgejo-cli&arch=riscv64&ver=0.3.0-4&stamp=1747478309&raw=0
My solution to this issue:
The issue was caused by the failure to properly install all required
dependencies
on the RISC-V architecture. It can be resolved by explicitly adding
the necessary
dependencies to the debian/control file.I have tested that locally, and it
works well.The debdiff patch is in the attachment.Please let me know
whether this solution can be accepted.
Gui-Yue
Best Regards
fix_forgejo-cli_missing_package_on_riscv.patch
Description: Binary data
