Your message dated Tue, 08 Dec 2020 08:48:56 +0000 with message-id <e1kmyg4-0002ml...@fasolo.debian.org> and subject line Bug#976596: fixed in bpfcc 0.17.0-8 has caused the Debian Bug report #976596, regarding bpfcc FTBFS: symbol differences to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 976596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976596 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: bpfcc Version: 0.17.0-7 Severity: serious Tags: ftbfs This might be due to the LLVM 9 -> 11 transition, or for other reasons. The general problem of shipping symbols files for C++ code is discussed at https://wiki.debian.org/UsingSymbolsFiles https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bpfcc.html ... dh_makeshlibs -a -O--buildsystem=cmake dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libbpfcc/DEBIAN/symbols doesn't match completely debian/libbpfcc.symbols --- debian/libbpfcc.symbols (libbpfcc_0.17.0-7_amd64) +++ dpkg-gensymbolsBsg2p_ 2022-01-07 07:04:25.911746666 -1200 @@ -1,14 +1,38 @@ libbcc.so.0 libbpfcc #MINVER# + MP_BADARG@Base 0.17.0-7 + MP_FALSE@Base 0.17.0-7 + MP_MEMORY@Base 0.17.0-7 + MP_MINERR@Base 0.17.0-7 + MP_NEG@Base 0.17.0-7 + MP_OK@Base 0.17.0-7 + MP_RANGE@Base 0.17.0-7 + MP_TRUE@Base 0.17.0-7 + MP_TRUNC@Base 0.17.0-7 + MP_UNDEF@Base 0.17.0-7 + MP_ZPOS@Base 0.17.0-7 + PollyCategory@Base 0.17.0-7 + PollyDebugPrinting@Base 0.17.0-7 + RejectStatistics@Base 0.17.0-7 + _Z10KnownNamesB5cxx11@Base 0.17.0-7 _Z10ebpfccfreePv@Base 0.14.0 _Z10tmp_str_ccB5cxx11@Base 0.14.0 (subst)_Z11ebpfccalloc{size_t}@Base 0.14.0 (subst)_Z13ebpfccreallocPv{size_t}@Base 0.14.0 + _Z15getMatMulAccRelN3isl12noexceptions3mapEjj@Base 0.17.0-7 + _Z17permuteDimensionsN3isl12noexceptions3mapENS0_3dimEjj@Base 0.17.0-7 + _Z18getPollyPluginInfov@Base 0.17.0-7 + _Z19createExtensionNodeN3isl12noexceptions13schedule_nodeENS0_3mapE@Base 0.17.0-7 _Z20_txnal_cow_string_D1Pv@Base 0.14.0 + _Z21addReferencesFromStmtPKN5polly8ScopStmtEPvb@Base 0.17.0-7 + _Z22getPartialTilePrefixesN3isl12noexceptions3setEi@Base 0.17.0-7 _Z23_txnal_cow_string_c_strPKv@Base 0.14.0 _Z23_txnal_sso_string_c_strPKv@Base 0.14.0 + _Z24isFortranArrayDescriptorPN4llvm5ValueE@Base 0.17.0-7 + _Z24updateLoopCountStatisticN5polly13ScopDetection9LoopStatsENS_4Scop14ScopStatisticsE@Base 0.17.0-7 _Z26_txnal_logic_error_get_msgPv@Base 0.14.0 _Z27_txnal_cow_string_D1_commitPv@Base 0.14.0 _Z28_txnal_runtime_error_get_msgPv@Base 0.14.0 + _Z33getInductionVariablesSubstitutionN3isl12noexceptions13schedule_nodeE19MicroKernelParamsTy19MacroKernelParamsTy@Base 0.17.0-7 _Z35_txnal_cow_string_C1_for_exceptionsPvPKcS_@Base 0.14.0 _ZGTtNKSt11logic_error4whatEv@Base 0.14.0 _ZGTtNKSt13bad_exception4whatEv@Base 0.14.0 @@ -131,6 +155,7 @@ _ZGVZNKSt8__detail11_AnyMatcherINSt7__cxx1112regex_traitsIcEELb0ELb0ELb1EEclEcE5__nul@Base 0.14.0 _ZGVZNKSt8__detail11_AnyMatcherINSt7__cxx1112regex_traitsIcEELb0ELb1ELb0EEclEcE5__nul@Base 0.14.0 _ZGVZNKSt8__detail11_AnyMatcherINSt7__cxx1112regex_traitsIcEELb0ELb1ELb1EEclEcE5__nul@Base 0.14.0 + _ZN10ScopViewer2IDE@Base 0.17.0-7 _ZN10__cxxabiv111__terminateEPFvvE@Base 0.14.0 _ZN10__cxxabiv112__unexpectedEPFvvE@Base 0.14.0 _ZN10__cxxabiv115__forced_unwindD0Ev@Base 0.14.0 ...
--- End Message ---
--- Begin Message ---Source: bpfcc Source-Version: 0.17.0-8 Done: Vasudev Kamath <vasu...@debian.org> We believe that the bug you reported is fixed in the latest version of bpfcc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 976...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Vasudev Kamath <vasu...@debian.org> (supplier of updated bpfcc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Tue, 08 Dec 2020 11:53:12 +0530 Source: bpfcc Architecture: source Version: 0.17.0-8 Distribution: unstable Urgency: medium Maintainer: Ritesh Raj Sarraf <r...@debian.org> Changed-By: Vasudev Kamath <vasu...@debian.org> Closes: 976596 Changes: bpfcc (0.17.0-8) unstable; urgency=medium . * [bb4e5c5] Drop the symbols file for libbpfcc library. Thanks to Adrian Bunk (Closes: #976596) Checksums-Sha1: 0e2359334a3dfff0f62e87a02532c74e4e65445a 2991 bpfcc_0.17.0-8.dsc 392e59e473bb735d82f7dc113aecf62e117fe05e 84388 bpfcc_0.17.0-8.debian.tar.xz fd6a50d292aa8d90a6f9bc57afde25345f84135e 11170 bpfcc_0.17.0-8_amd64.buildinfo Checksums-Sha256: 578e208cf2fbb86a21fadd787aab7171d6a09d93d3f77c5489b63ab2c54d7e79 2991 bpfcc_0.17.0-8.dsc 1b1d5fbc3f7a40418e4d4047643b65dbfa7b860372e17ebe5c5f1da2b9c29d8e 84388 bpfcc_0.17.0-8.debian.tar.xz 1576f51e4971fd13273b9882c8c91a97a76378d513287b77e7d84dc55fadcd1e 11170 bpfcc_0.17.0-8_amd64.buildinfo Files: b64714af3055b8bc7cc2441f09d7c133 2991 misc optional bpfcc_0.17.0-8.dsc 879ff1f1e4111ea034037b3c79499a83 84388 misc optional bpfcc_0.17.0-8.debian.tar.xz 9d1b49eed86c38ac7285fb411aa0ffd6 11170 misc optional bpfcc_0.17.0-8_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEExRfCXeQIdZ2YpMlrbI90rodwC34FAl/POXEACgkQbI90rodw C341LA/+I3YSfd0w88FEu3VyVWd4n+XEN9+qmIuL4thgj6zXB+EyzSfCuyv9fT5p JHdURhlZOC4cIRzoQKrSGnRTHQVsjtN/qeDspd8Y1uwYQovBlO1VfTVvqoMxV1BT AnnclJqqlyHVQe7doBIL2z3SPN1XGq5+9ZF7eLwWG/k1SlmLAPu/FmkfKHE0fDZZ 1sLIlk+evfvvZ15lNr5PLThUV25T2nGvYiqjJ0Jhd6TIAZLdP4SxElzAeZVC1HEj cqzFXexk+v+gEmKCtgUWwz22Xli7mQ3yG4Ir5nksZQ2JOi86qcEEgqD+QYFYx6co Y/UjOD0ZVFOMgWwxxEuQx2zhL6X3XkOYbbhfzAYlhXR0LKqVr0cQ1hceXRt5vazn w03gxBNqTc07jA8ToahgC6nF2FmWl3oIOEEKHg1reSrr47AweQvsiRxOk6RiwAQa 8HwvR63LcgvwZ2ptv1PILeo++tcVxNGGbbTqLA4jBqDyE854gNMQkzfslGCPJz1V ftVAKhlfbg+qejsDnlHJZACesCUExOcEM3LcL34mr3gJX+/bsEq9CiTSdXRjFu6Z zZYac9RCVdvR96pJJDJ0rEXGfZTK25K0VxzxKIV5p1U8SG//TfOXT5GTYzGByGOF 8jMnK/aDsXnf7pFedIQbJwUP2YNZ5HCdNQPyy8odsQHboltrmRY= =mG9e -----END PGP SIGNATURE-----
--- End Message ---
