Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Convertor of cli_tool not working #152

Closed
RishabhBhatnagar opened this issue Oct 24, 2020 · 5 comments
Closed

Convertor of cli_tool not working #152

RishabhBhatnagar opened this issue Oct 24, 2020 · 5 comments
Assignees

Comments

@RishabhBhatnagar
Copy link

RishabhBhatnagar commented Oct 24, 2020

This is a follow-up of #148 (comment) .

I've tried running the convertor. But couldn't run it successfully for any of the ways defined in the README.md file.

The following are the ways I tried and the errors they've raised.

convertor --infile file.rdf --outfile output.json raised following error:
Error: Invalid value for '--to' / '-t': invalid choice: undefined. (choose from json, rdf, yaml, xml, tag)
convertor --from rdf file.rdf --to json output.json raised following error:
spdx.parsers.builderexceptions.FileTypeError: INPUT FILETYPE NOT SUPPORTED. (only RDF and TAG format supported)
convertor -f rdf file.rdf -o output.json raised following error:
Error: Invalid value for '--to' / '-t': invalid choice: undefined. (choose from json, rdf, yaml, xml, tag)

If you think I might've made some mistake while running the tool, you can check how I ran it in this google colab file

@TraceyOnim
Copy link

Is there any follow-up on the issue? I'm also facing the same error .

@pombredanne
Copy link
Member

@TraceyOnim not yet... help would be mucho welcomed!

@nicoweidner
Copy link
Collaborator

nicoweidner commented Sep 5, 2022

It looks like the issues reported here were actually fixed in #174; the errors are gone. However, the same PR caused an issue with the first example where both infile and outfile is used. That is caught by this block and just prints the help message.

I think this issue can be used for this followup problem as the title is sufficiently vague ;-)

@meretp
Copy link
Collaborator

meretp commented Oct 12, 2022

I'll have a look.

@nicoweidner
Copy link
Collaborator

Fixed via #235

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants