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

distinguish between network failure and missing tags #39

Open
pravi opened this issue Nov 18, 2016 · 0 comments
Open

distinguish between network failure and missing tags #39

pravi opened this issue Nov 18, 2016 · 0 comments

Comments

@pravi
Copy link
Contributor

pravi commented Nov 18, 2016

I was using mobile internet and internet connection failed during npm2deb run. npm2deb thought tags are missing and created watch file with fakeupstream. It should have thrown an error instead. I'm not sure if uscan gives different error codes for connection failure and no tarball, we may have to ask uscan developers if there is no such option.

Even after creating watch file with fakeupstream, the network was still down, but npm2deb did not print any error message and upstream tarball was not downloaded.

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

1 participant