-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 20.08.2014 18:36, Jakub Wilk wrote: > * Dariusz Dwornikowski <dariusz.dwornikow...@cs.put.poznan.pl>, > 2014-08-20, 15:39: >>> It's still linking with OpenSSL, via libstrophe, right? This >>> won't work. Also, libstrophe isn't packaged. >> >> It is linking to libstrophe, which is linking to ssl. Lintian >> does not bork about this, since it is not a direct linking. > > <advert> If the copyright file is in the machine-readable format, > and it says that all the files are GPL-ed (which is the case here > AFAICS), then adequate(1) should be able to detect GPL+OpenSSL > license conflict, even when it is caused by indirect linking. > </advert> >
In fact adequate does the job but only after the installation of the package, not while building. Anyways, good to know this tool, and... profanity is violating the license. Back to upstream then :) - -- Dariusz Dwornikowski, Institute of Computing Science, PoznaĆ University of Technology www.cs.put.poznan.pl/ddwornikowski/ room 2.7.2 BTiCW | tel. +48 61 665 29 41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJT9NF+AAoJECEac8aaew/HHSkQANCiJzyn2jdZ2NNmUgNnGY40 pCuY602SA+j5zjKQqP1Tsu8swNe7xJuxy2756ssfCej+/pptaV+ubLeDakmh1b0m 70ANZXkG1wA+33D9b+HjV9v75sJyKbfSd+gK3Ofb6mfBOStcMYgWhb8l5pUnHBYE dR0FUgPo6Sy9iESD0me3es1YrtHxmVoVn0giHUxmnMWnmUBDpbfvYAT2g5NOvULq hyBPwilvsbCglg9D5wHWiz4AIvNNla35dZi0jX1Mj8wv/+gpf1q7s5eRBhC7hCdv 0tFU1ONHdd1zX/xQSQ53kDXcscxTKnP/voE9tXtTMBeWcQAzqeGEYvNug7/qUvd1 TWr+5RXDhRHFcFMVOYjy1yysX16NGOQnmRnTfHKF6ClPOWkd2v0bVECWysNvy+Zm DfiKkWJWwf9Xaw2Nn+TGU/CjWlyAvWkaHkN4/6seZTHz4DdHeLF15S7fvgYdzo5Z feSyl0O0Z5/M/ZKhQjNDGxygly/GeGUdCiQqgBAqT7dGGkjjmuj51NufwZS1Ulv5 NCop+2FGy8yVHG8EGotzhy2weFcIj7aXbyfaNXetiVrXKxTIZ/RtIfsIBf/Bbpcr JJxZHVL+420Ehz/FMp76gSSp5qv4w9bFuD2cSzvMaWz3cNZyvJE/paUIMzplkixF ULmrA3g9SGvkGFpCVoYe =fa7R -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org