Hi, All I have updated my rebootstrap fork[0], with fix for newt, base-passwd and perl. rebootstrap finishes with report: https://gist.github.com/zhangn1985/790c1ee011b264332ede1aa909b8d3e7
I'm happy to see more Loongson employees join the process of enable Loongarch in Debian upstream, not downstream fork. This is the main purpose of my recent work. With my rebootstrap fork[0], it's easy for Loongson to start, thus I can handover my work to Loongson, and keep silent for a while. Loongson, push the community, not pushed by. BR. Ning. [0] https://salsa.debian.org/zhangn1985/rebootstrap 发件人: Paul Wise 已发送: 2022 年 11 月 4 日 星期五 2:45 收件人: Zhang Ning; debian-devel@lists.debian.org; sangm...@loongson.cn; Santiago Vila 主题: Re: rebootstrap status update for Loongarch On Thu, 2022-11-03 at 18:45 +0800, Zhang Ning wrote: > 7, m4, diffutils: need help, I don't know where is correct > upstream[1][2], the patch[3][4] is for generated files, but Debian > source has these files, thus how can I submit these patch to Debian > source? these two packages don't have VCS. It is best not to patch generated files, instead they should be regenerated from source (and probably removed from the upstream VCS). It is best not to patch embedded code copies, instead they should be removed from the upstream VCS and tarballs and the system version used. In Debian, the dh-autoreconf package is used at build time to automatically regenerate all files generated by autotools. In Debian, the stack-direction.m4 file is provided by gnulib, but I am not sure if that is the canonical place this file is maintained or if it is just yet another copy of this file.. $ apt-file search stack-direction.m4 gnulib: /usr/share/gnulib/m4/stack-direction.m4 For m4, it seems Santiago Vila disabled dh-autoreconf in debian/rules, but there is no indication of the reason for that. So I suggest you test what happens when it is enabled and if the build succeeds and has no warnings in the log, then open a bug asking for it to be enabled. For diffutils, the same issue and solution applies. Another solution would be to ask the upstream m4 and diffutils projects to make new releases with updated configure and stack-direction.m4 files and then file bugs in Debian asking for package updates to the new releases. -- bye, pabs https://wiki.debian.org/PaulWise
