Re: Bug#1012798: libecap: diff for NMU version 1.0.1-3.3 fix FTBFS on riscv arch

[xiao sheng wen(肖盛文) <atzlinux@sina.com>]

Hi Luigi,

在 2022/6/16 06:40, Luigi Gangitano 写道:

Hi Xiao,

Thanks a lot for taking care of this bug. libecap is currently undeveloped upstream, so these fixes are the only ones expected from time to time.

    I'm glad to see your reply.

If I understand correctly the post you referred to, step 3 is still needed to check if everything is ok for other architectures. This means uploading a new version, triggering buildds and then feeding back the errors to pkgkde-symbolshelper.

    Yes. I'd do it in this NMU, the next is to triggering buildds to
    verify.

It looks like this is what Matthias did back in 2016.

Shall we do that in experimental?

    I also find some MISSING infos in the build log:

+#MISSING: 1.0.1-3.3# (optional=templinst|arch=!powerpc !riscv64)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag@Base 1.0.1
+#MISSING: 1.0.1-3.3# (optional=templinst|arch=!powerpc !riscv64)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPcEEvT_S7_St20forward_iterator_tag@Base 1.0.1

As they are optional, so they don't bread the build.

From man deb-src-symbols (5), section "Standard symbol tags" "optional",

It say "such a symbol needs to be removed from the symbol file".

The libecap package is builded several years ago in buildds, there are many things changed in buildds,

so I'm not very sure what will happen for symbols in the next build.

Anyway, cancel this NMU, upload to sid, not use experimental, it is also a way to fix this bug.

Thanks!

    Best,
-- 
肖盛文 xiao sheng wen Faris Xiao 
微信(wechat)：atzlinux
《铜豌豆 Linux》https://www.atzlinux.com
基于 Debian 的 Linux 中文 桌面 操作系统
Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com
GnuPG Public Key: 0x00186602339240CB

Attachment: OpenPGP_signature
Description: OpenPGP digital signature