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

Implicit dependency on some packages removed #181

Closed
yash-nisar opened this Issue Jun 8, 2017 · 4 comments

Comments

2 participants
@yash-nisar
Member

yash-nisar commented Jun 8, 2017

Removal of libasan3, libxslt-tools, python-javapackages, python-pyxb, results in this error.

@yash-nisar

This comment has been minimized.

Show comment
Hide comment
@yash-nisar

yash-nisar Jun 8, 2017

Member

After the prevention of removal of the above packages, we get another error, which is prevented by installing libxml2-devel and libxslt-devel.

See https://stackoverflow.com/questions/33785755/getting-could-not-find-function-xmlcheckversion-in-library-libxml2-is-libxml2

Member

yash-nisar commented Jun 8, 2017

After the prevention of removal of the above packages, we get another error, which is prevented by installing libxml2-devel and libxslt-devel.

See https://stackoverflow.com/questions/33785755/getting-could-not-find-function-xmlcheckversion-in-library-libxml2-is-libxml2

@yash-nisar

This comment has been minimized.

Show comment
Hide comment
@yash-nisar

yash-nisar Jun 8, 2017

Member

After adding libxml2-devel and libxslt-devel, the build is still red with a npm ERR! Cannot find module 'node-fetch-npm' error.

Member

yash-nisar commented Jun 8, 2017

After adding libxml2-devel and libxslt-devel, the build is still red with a npm ERR! Cannot find module 'node-fetch-npm' error.

@yash-nisar

This comment has been minimized.

Show comment
Hide comment
Member

yash-nisar commented Jun 8, 2017

@yash-nisar

This comment has been minimized.

Show comment
Hide comment
@yash-nisar

yash-nisar Jun 8, 2017

Member

Created a separate issue for the NPM error -> #182

Member

yash-nisar commented Jun 8, 2017

Created a separate issue for the NPM error -> #182

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment