license confusion

[pymnh]

Hi,

I am working on getting this package into debian. Little problem is that the packaging policy requires naming copyright and license explicitly per file (or regex on multiple files), like here

The license file of this project says that ISC licensed code from Googles BoringSSL is included, but I have trouble finding the respective files. At least there seems to be no files with according headers. Is the respective code still present in this package? If yes, can you maybe point them out to me?

[dadrian]

I believe that code is now gone, it was in some cipher implementations that have since been added to the Golang stdlib.

That being said, what does it mean to add a library-only Go project to Debian?

[pymnh]

I believe that code is now gone, it was in some cipher implementations that have since been added to the Golang stdlib.

perfect, than there should be nothing in the way for packaging this :)

That being said, what does it mean to add a library-only Go project to Debian?

ultimately the goal is to get zmap/zlint and zmap/zcertificate into debian. the build servers do not have network access hence all build dependency need to be packaged for debian archives to be available at build time.