Hi Ross, On Sat, Oct 12, 2019 at 8:39 PM Ross Vandegrift <rvandegr...@debian.org> wrote: > > I'm seeing a similar false positive:
I do not. The symbols file in the control section of libephysics1_1.21.1-5+b1_amd64.deb contains the following line: $ fgrep -- -5 dir2/symbols _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPcEEvT_S7_St20forward_iterator_tag@Base 1.21.1-5+b1 The symbol shows a Debian revision. Lintian is right. The line furthermore matches Lintian's output: $ frontend/lintian --no-tag-display-limit ../bugs/symbols/libephysics1_1.21.1-5+b1_amd64.deb E: libephysics1: symbols-file-contains-current-version-with-debian-revision on symbol _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPcEEvT_S7_St20forward_iterator_tag@Base N: 1 tag overridden (1 warning) This is not a bug in Lintian (at least not anymore). I will close this bug after writing to Scott, as well. As a side note, I was surprised to find 188 additional Debian revisions: $ fgrep -- -0~eo dir2/symbols | head -5 ephysics_body_angular_movement_enable_get@Base 1.21.1-0~eo ephysics_body_angular_movement_enable_set@Base 1.21.1-0~eo ephysics_body_angular_velocity_get@Base 1.21.1-0~eo ephysics_body_angular_velocity_set@Base 1.21.1-0~eo ephysics_body_back_boundary_add@Base 1.21.1-0~eo $ fgrep -- -0~eo dir2/symbols | wc -l 188 Finally, I am not sure why some symbols were decoded properly using the appropriate pattern [1], while the offender is raw 'c++'. Did you mix C and C++ symbols in the same shared library? Kind regards Felix Lechner [1] https://wiki.debian.org/UsingSymbolsFiles