HI Kotrappa,

 

I can think of two possible causes:

- The extracted license info page does not contain a license reference with
the same ID

- A bug in the tool

 

If you suspect a bug, email me the spreadsheet and I'll try to duplicate/fix
it.

 

Gary

 

 

From: [email protected] [mailto:[email protected]]

Sent: Friday, April 18, 2014 6:06 AM
To: [email protected]; [email protected]
Cc: [email protected]; [email protected]
Subject: [SPDX Tools 1.2.5] Invalid license ID found in the non-standard
lienses: 'LicenseRef-ISCADK'

 

Hello Gary,

 

I was trying to generate .rdf file from  manually generated
libc_so_spdx.xls, I get error as "invalid license id".

Does SpdxTools 1.2.5 support License id can be as follows

 

"LicenseRef-"[idString]

where

[idString] is a unique string containing letters, numbers, ".", "-" or "+"

 

 

 

# java -jar spdx-tools-1.2.5-jar-with-dependencies.jar  SpreadsheetToTag
libc_so_spdx.xls  libc_so_spdx.tag

 

Error translating the Tag file: Invalid license ID found in the non-standard
licenses: 'LicenseRef-ISCADK'

 

If not supported, when it will be available? Because we do have many
licenses which are not registered to spdx license list.

 

Best regards

Kotrappa.

 

From: Gary O'Neall [mailto:[email protected]] 
Sent: Friday, April 18, 2014 12:00 AM
To: Kotrappa DeverShetty (WT01 - Manufacturing & Hi Tech);
[email protected]
Cc: Akanksha Singh (WT01 - Manufacturing & Hi Tech); Ravishankar T.S (WT01 -
Manufacturing & Hi Tech)
Subject: RE: [SPDX Specification] extracted license text in RdfToSpreadsheet
tool

 

Hi Kotrappa,

 

The checksums are all SHA1 checksums which can be generated by various tools
if you have the original file or archive file.  On Linux you can use the
sha1sum command.  Note that the spec requires the SHA1 checksum to be all
lowercase (e.g. 2fd4e1c67a2d28fced849ee1bb76e7391b93eb12).

 

The Verification Code is more complex.  The easiest solution is to use the
GenerateVerificationCode command in the latest SPDX Workgroup Tools
available at http://spdx.org/sites/spdx/files/SPDXTools-v1.2.5.zip.

 

Once you download the and expand the tools archive file, just execute the
following command:

java -jar spdx-tools-jar-with-dependencies.jar GenerateVerificationCode
sourceDirectory [ignoredFilesRegex]

where sourceDirectory is the directory containing the open source files for
the package and the optional ignoredFilesRegex is a regular expression
pattern for any files which should not be included in the verification code
(e.g. '.*\.spdx' will skip all files ending in .spdx).

 

Gary

 

From: [email protected] [mailto:[email protected]]

Sent: Thursday, April 17, 2014 7:51 AM
To: [email protected]; [email protected]
Cc: [email protected]; [email protected]
Subject: RE: [SPDX Specification] extracted license text in RdfToSpreadsheet
tool

 

 

Hi Gary

We have a query as follows.

We have third party/RTOS vendor supplied shared libraries, binaries,
archives for which we dont have source code. But the third party/RTOS vendor
declares license details for each of the binary file.

for e.g.

 

File name                License details                 version info

--

/usr/lib/libc.so            GPL 2.0, BSD            2.5

/usr/bin/pwd               GPL 2.0                      4.0

/usr/lib/libxx.a             GPL 3.0                      6.5

 

we would like to create a .spdx/ or .rdf file for each of above binary.

we will take SPDXSpreadsheetTemplate.xls for each of binary and fill up
mandatary details.

For e.g. for libc.so

 

Sheet - PackageInfo 

PackageName - libc

PackageFileName - libc.zip

Package Version - 2.5

Package Supplier - RTOS vendor

 

- here we dont have information on Package Checksum, and PackageVerfication
code.

How do we generate this information??

 

Sheet - PerFileInfo

FileName  - libc.so

FileType   - BINARY

License info from file - GPL 2.0, BSD

 

How do we generate FileChecksum??

 

Do we need to refer some standard way to generate file check sum? will that
work?

 

Please help.

 

 

regards

Kotrappa

 

The information contained in this electronic message and any attachments to
this message are intended for the exclusive use of the addressee(s) and may
contain proprietary, confidential or privileged information. If you are not
the intended recipient, you should not disseminate, distribute or copy this
e-mail. Please notify the sender immediately and destroy all copies of this
message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should
check this email and any attachments for the presence of viruses. The
company accepts no liability for any damage caused by any virus transmitted
by this email.

www.wipro.com

The information contained in this electronic message and any attachments to
this message are intended for the exclusive use of the addressee(s) and may
contain proprietary, confidential or privileged information. If you are not
the intended recipient, you should not disseminate, distribute or copy this
e-mail. Please notify the sender immediately and destroy all copies of this
message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should
check this email and any attachments for the presence of viruses. The
company accepts no liability for any damage caused by any virus transmitted
by this email.

www.wipro.com

_______________________________________________
Spdx-tech mailing list
[email protected]
https://lists.spdx.org/mailman/listinfo/spdx-tech

Reply via email to