-
-
Notifications
You must be signed in to change notification settings - Fork 562
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
Do not report absolute location for NPM package "metafile" #782
Labels
Comments
pombredanne
added a commit
that referenced
this issue
Oct 2, 2017
* do not map the legacy "url" to anything #755 * allow to build a Package from data and not only from a file * do not return full location for the metafile but only filename #782 * ensure only one download_urls is created #779 * improve the mapping of "parties" * other misc code improvement and TODOs * add new tests for #755 and other samples Signed-off-by: Philippe Ombredanne <[email protected]>
pombredanne
added a commit
that referenced
this issue
Oct 3, 2017
* do not map the legacy "url" to anything #755 * allow to build a Package from data and not only from a file * do not return full location for the metafile but only filename #782 * ensure only one download_urls is created #779 * improve the mapping of "parties" * other misc code improvement and TODOs * add new tests for #755 and other samples Signed-off-by: Philippe Ombredanne <[email protected]>
pombredanne
added a commit
that referenced
this issue
Oct 4, 2017
* do not map the legacy "url" to anything #775 * allow to build a Package from data and not only from a file * do not return full location for the metafile but only filename #782 * ensure only one download_urls is created #779 * improve the mapping of "parties" * other misc code improvement and TODOs * add new tests for #775 and other samples Signed-off-by: Philippe Ombredanne <[email protected]>
Fixed in develop |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This should be only a filename
The text was updated successfully, but these errors were encountered: