On Monday 18 April 2016 17:58:03 Gianfranco Costamagna wrote: > Hi, > > >source-contains-prebuilt-windows-binary storm_dll/storm.dll > >==> Not possible, problem with original upstream tarball > > you can, google for "debian source" repack. > Anyway, since this isn't a license violation, nevermind! Ehm... repacking is ugly! > >debian-watch-may-check-gpg-signature > >==> Not possible, upstream does not provide such feature > > you can ask them to start signing them :) Ok, I can ask, but I doubt that upstream will do that. This is windows project and in windows world is PGP not supported by Visual Studio/MS. (We can be happy that library working fine under linux with gcc :-)) > >hardening-no-bindnow usr/lib/libstorm.so.9.0.0 > >==> How to do that for current debian/rules which uses cmake? > > https://wiki.debian.org/HardeningWalkthrough I already read this and there is written: As a workaround appending CPPFLAGS to CFLAGS and CXXFLAGS should work in most cases. Debhelper (since 0.9.20120417, only with compat=9 and dh_auto* commands!) and cdbs (since 0.4.110) handle this automatically so the workaround is no longer necessary if they are used. As you can see debhelper 9.2015 is in Debian and stormlib has compat=9. So what to do? > >symbols-file-contains-current-version-with-debian-revision on symbol > >AsciiToLowerTable@Base and 215 others ==> What does this mean and > >how to fix it? > > http://lmgtfy.com/?q=symbols-file-contains-current-version-with-debia > n-revision > > :) google is your friend, and lintian too. And this did not helped me too! I read debian lintian description for symbols-file-contains-current-version-with-debian-revision before. File debian/libstorm9.symbols already contains *all* public functions which can be used by other libraries. And all those functions do not have any debian suffix. So I do not understand why it show error message and even how to fix it. -- Pali Rohár pali.rohar@gmail.com
Attachment:
signature.asc
Description: This is a digitally signed message part.