On Sun, 2022-02-13 at 18:05 +0800, Bo YU wrote:
I've been using Debian for many years now and have the opportunity to
contribute to it, especially in the RISCV port.
Excellent, thanks for your interest.
The FTBFS(https://udd.debian.org/cgi-bin/ftbfs.cgi?arch=riscv64) I
think it is a good place to start.
Correct.
But some workflow are unknown for me.
The package maintainers guide and developers reference might be useful:
https://mentors.debian.net/intro-maintainers/
https://www.debian.org/doc/manuals/maint-guide/
https://www.debian.org/doc/manuals/developers-reference/
Can I pick one of the packages in FTBFS page, e,g,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997744
This particular bug was filed for amd64, so it likely affects all
architectures, not just riscv64.
then build it with cross-compiling for riscv64?
If you have riscv64 hardware it is often better to build there, since
usually cross-compiling usually means that the build-time tests won't
be run. Using qemu-user-static or qemu-system-riscv64 to emulate a
riscv64 system is an option, but is slower than cross-compiling.
If you are interested in improving cross-compiling in Debian,
please review the following pages.
https://wiki.debian.org/CrossCompiling
https://wiki.debian.org/CrossBuildPackagingGuidelines
https://wiki.debian.org/?action=fullsearch&titlesearch=Titles&value=Cross
https://lists.debian.org/debian-cross/
http://crossqa.debian.net/
If I solve this build issue, what should I do next?
If the issue is Debian specific, send a mail to the bug report with a
patch attached and mark the bug as having a patch using this command as
the very first line of your email (-1 means the current bug):
Control: tags -1 + patch
If the package has Vcs-* headers, then you can often use the pull
request or merge request systems to send the fix, but ensure you also
send a mail to the bug linking to your request and adding the tag.
If the issue also applies to an upstream project on GitHub or
elsewhere, then also send the fix to them too.