Errors during install on Xenial, missing ppa package
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 65
- Forks
- 218
- PR merge metrics
- No merged PRs in 30d
Description
Hi, I am trying to follow this guide in order to install and test the module on a ficus.1 devstack but I am encountering some errors.
First of all during the install-sys-requirements I get:
W: http://packages.elasticsearch.org/elasticsearch/0.90/debian/dists/stable/Release.gpg: Signature by key 46095ACC8548582C1A2699A9D27D666CD88E42B4 uses weak digest algorithm (SHA1)
W: http://downloads-distro.mongodb.org/repo/ubuntu-upstart/dists/dist/Release.gpg: Signature by key 492EAFE8CD016A07919F1D2B9ECBEC467F0CEB10 uses weak digest algorithm (SHA1)
sudo xargs -a apt-packages.txt apt-get install -qq --fix-missing
E: Unable to locate package libblas3gf
E: Unable to locate package liblapack3gf
and it seems [1] [2] that those packages do not exist in Xenial.
Anyway trying to comment them out from the apt-packages.txt I still get problems during the install because it is trying to fetch node.js from this repo:
http://ppa.launchpad.net/chris-lea/node.js/ubuntu/dists/xenial/main/binary-amd64/Packages
which does not exist.
Am I missing something?
Thanks
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the install-sys-requirements entry point and inspect apt-packages.txt plus the configuration that adds the chris-lea/node.js PPA. Reproduce the Xenial installation and verify which listed packages and repositories are unavailable. Done means the documented installation proceeds without the reported missing-package or invalid-PPA errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, python, ubuntu
- Domain
- build-system, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100