0
I would like to install cpp-ethereum
following the documentation
Powershell is running in admin mode, but if I try to run the install command (choco install cpp-ethereum
), I get this error:
PS C:\WINDOWS\system32> choco install cpp-ethereum
Chocolatey v0.10.8
Installing the following packages:
cpp-ethereum
By installing you accept licenses for the packages.
cpp-ethereum not installed. The package was not found with the source(s) listed.
If you specified a particular version and are receiving this message, it is possible that the package name exists but t
he version does not.
Version: ""
Source(s): "https://chocolatey.org/api/v2/"
Chocolatey installed 0/1 packages. 1 packages failed.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
Failures
- cpp-ethereum - cpp-ethereum not installed. The package was not found with the source(s) listed.
If you specified a particular version and are receiving this message, it is possible that the package name exists but t
he version does not.
Version: ""
Source(s): "https://chocolatey.org/api/v2/"
The same error message can be found in the log. What does this error message mean and how is it possible to fix it?
As a clarification point - the package was not removed by the moderators/community, it never existed. You could go directly to the package page at https://chocolatey.org/packages/cpp-ethereum and see a hidden package if it existed. There isn't one.
– ferventcoder – 2017-10-02T15:48:30.140@ferventcoder - I am not sure it really matters. It doesn't exist today. So an alternative must be used if the author wants to use Chocolatey to install a similar package. – Ramhound – 2017-10-02T15:50:01.837
I just wanted to be clear on that one point. I read the link, and I don't know if the group ever maintained a Chocolatey package on the community repository. If they did, it certainly wasn't under the name
cpp-ethereum
. One by that name never existed - one namedethereum
was submitted by a community member but it never made it past moderation. So I'm not really sure what they meant by "though we have done so in the past." – ferventcoder – 2017-10-02T16:18:26.487@ferventcoder - Understood. Adding the clarification it never existed just isn't a huge priority when it does not really make a difference to my actual answer. – Ramhound – 2017-10-02T16:21:11.633
I did provide an edit - the edit also points out that the OP can create and maintain an internal package and that they can also make a package available on the community package repository if they would like to do that as well - two additional options for fixing the issue. – ferventcoder – 2017-10-02T16:25:13.783