Hi Eriberto, > 1. Update d/copyright. The current copyright for Troy is 2003-2013.
Oh yes, I missed that. > 2. I found: > > # This product includes software developed by the OpenSSL Project for use in > # the OpenSSL Toolkit. (http://www.openssl.org/) > # This product includes cryptographic software written by Eric Young > # (e...@cryptsoft.com) > # This product includes software written by Tim Hudson (t...@cryptsoft.com) > > If you used external codes in your program, you must to put it in > d/copypyright too. The d/copyright must relate all licenses and > copyrights found in upstream code. See this 'drastic' example: > http://sources.debian.net/src/sleuthkit/4.1.3-4/debian/copyright. I don't include any openssl code, but do use it. My original paranoid interpretation of the licence requirements was that if I was using it, I had to put the above in a readme somewhere. I am no longer certain that this is the case. Either way, there is no direct openssl code included in the tar. > 3. Is normal this issue? > > ./08-ssl-connect-no-auth.py python/08-ssl-connect-no-auth.test > Traceback (most recent call last): > File "python/08-ssl-connect-no-auth.test", line 36, in <module> > mosq.loop() > File "/sponsor/mosquitto2/mosquitto-1.3.4/lib/python/mosquitto.py", > line 725, in loop > ./08-ssl-connect-cert-auth.py python/08-ssl-connect-cert-auth.test > Traceback (most recent call last): > File "python/08-ssl-connect-cert-auth.test", line 35, in <module> > mosq.loop() > File "/sponsor/mosquitto2/mosquitto-1.3.4/lib/python/mosquitto.py", > line 725, in loop No it isn't, all tests should pass fine. Is it repeatable? Could you have had multiple sets of the tests running at once? That would have a good chance of causing failures. Cheers, Roger -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cah7zdyfj2fwgcdjhnotocm7nmnj9j_qhchmje35+5blvwn1...@mail.gmail.com
