To build TensorFlow from source I installed bazelisk as recommended. Then when I call ./configure which calls bazelisk I get the following error:
Downloading https://releases.bazel.build/0.29.1/release/bazel-0.29.1-lin
ux-x86_64...
2021/04/07 13:24:54 could not download Bazel: HTTP GET https://releases.bazel.build/0.29.1/r
elease/bazel-0.29.1-linux-x86_64 failed: Get "https://releases.bazel.build/0.29.1/release/ba
zel-0.29.1-linux-x86_64": proxyconnect tcp: net/http: TLS handshake timeout
Bazel is banned in the place I live and I set proxy to Tor to download it (via https://127.0.0.1:8118 through privoxy), but somehow it fails to download it. What's the solution?
As said in the docs bazelisk is just a wrapper that makes sure the version of bazel you are using to build is the best it can be.
Bazelisk does not yet have an offline mode, and appears to always execute an http request or two on invocation.
This model doesn’t appear to work well with your internet settings, so it sounds like you might be better off manually downloading the appropriate release of bazel (check for a .bazelversion file in the project) using their instructions for your platform for the direct binary installation, or if you can use the apt repositories, those appear to be more recommended.
With a direct installation of bazel, you may have to do a couple more things manually, but it won’t be doing those http requests to figure out the right version.
After that, you may find that other dependencies of tensorflow are blocked, and you may have to get bazel itself to use your proxy. Following the instructions for an air gapped environment might be useful for building regularly, but you’ll still need to do the first build. This SO answer appears to be a place to start for your proxy.
As a solution, one can force bazelisk to download bazel from github. To do so you can set the following environment variable before running ./configure
export BAZELISK_BASE_URL="https://github.com/bazelbuild/bazel/releases/download"
Related
When I run the config file for installing GSL library for Windows 10 I get the following error:
error: Something went wrong bootstrapping makefile fragments for
automatic dependency tracking. If GNU make was not used, consider
re-running the configure script with MAKE="gmake" (or whatever is
necessary). You can also try re-running configure with the
'--disable-dependency-tracking' option to at least be able to build
the package (albeit without support for automatic dependency
tracking).
If I run ./config MAKE="gmake" I still get the error. I have searched in StackOverflow and on the web and still haven't found a solution.
I am trying to run npm install in a new Angular app. I am running it behind a corporate firewall, which is obviously the issue.
I am running into errors specifically with the pemrouz/buble package, which is a dependency of a dependency. One of Angular's dependencies is explicitly specifying that buble be downloaded using SSH. Originally, the SSH connection was getting blocked, but I was able to convince the network group to allow the connection.
However, it's still being proxied, which is messing up SSL stuff.
I can git clone the package by specifying that git not use strict SSL, but NPM ignores this setting.
I can also specify that NPM not use strict SSL, which allows HTTPS connections to work properly -- but apparently this also doesn't apply to SSH.
I am not using Docker or Chocolatey (this seems to be the common source of the issue for other people seeing this error).
I have seen the other questions, on StackOverflow and elsewhere, where people have had this issue, but the answer is always "you're running an old version of NPM." However, I am running 6.14.4, which appears to be the latest. Besides, I don't see how that could cause a host key issue?
How can I get NPM to make the SSH connection without using strict SSL? Or otherwise, how can I fix the host key verification issue?
Thanks!
EDIT: I ran ssh git#github.com and it prompted me "do you want to trust this?" and I said yes -- now it's showing the error "Permission denied (publickey)" when I run npm install.
This is not a private repo, it's the public repo at https://github.com/pemrouz/buble.
For testing, I have installed two instances of Ubuntu server 18.04 on VirtualBox. I then installed one with Puppet-server 6.1.0 and one with Puppet-agent 6.1.0, as per the documentation at Puppetlabs for version 6.1. Foreman is not installed.
After registering my agent at the puppetserver and signing the certificate, starting a puppet-run (sudo /opt/puppetlabs/bin/puppet agent --test) fails with the following error:
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Failed when searching for node puppetagent.fritz.box: Exception while executing '/etc/puppetlabs/puppet/node.rb': Cannot run program "/etc/puppetlabs/puppet/node.rb" (in directory "."): error=2, No such file or directory
I was dumbstruck to find that the script /etc/puppetlabs/puppet/node.rb was indeed missing and was also not included in the packages of puppetserver, puppet-agent or facter (sudo dpkg-query -L ...).
Googling for it, I only found a script of the same name that belonged to Foreman.
The file does also not seem to be present in the puppetserver source-code at github.
Is anyone able to shed some light on this?
Your server configuration seems to be set up to specify use of an external node classifier. This is optional: Puppet does not require an ENC and does not provide one by default. That's part of what makes them "external". If you obtained the result you describe straight out of the box then it probably reflects a packaging flaw that you should report.
In the meantime, you should be able to update the configuration to disable use of an ENC by changing the value of the node_terminus setting to plain. Alternatively, you should be able to just delete both node_terminus and external_nodes from your configuration, because the default for the former is plain.
Tagging on to John's answer, your configuration is probably configured to talk to the Foreman. If you didn't write it yourself or copy it from somewhere and you're sure you don't have any Foreman packages installed, then it's definitely a packaging error that you should report.
That said, puppet repos are almost always the right answer rather than distro packages.
I'm using jhbuild to build and run gnome-music.
I'm having a successful build but when I run the command
jhbuild run gnome-music
I get the following error
One of the errors is
1.GstTag was imported without specifying a version first
The rest are in the link above.
I'm not sure how to proceed further,can someone help me out?(I'm using Ubuntu 17.04).
I'm following the steps given on:
https://github.com/GNOME/gnome-music
Gst just warns you against not mentioning a version number. Hence, that's not the error.
The error you are facing is regarding Tracker. As you are on Ubuntu distribution, you should know that Ubuntu disables Tracker by default. Hence jhbuild run gnome-music refuses to start. Tracker is a file-indexing service based on file's metadata.
However, Ubuntu is deciding to enable Tracker by default as many GNOME's core apps relies on it. Read here.
Enable Tracker and jhbuild will pick it up from the host system.
I have found a simulator called ntpdsim for NTP: http://www.eecis.udel.edu/~mills/ntp/html/ntpdsim_new.html
I canot figure out on what OS I can use it. On the page there is no download content. So I thought it is integrated in the NTP package.
I have tried Ubuntu and Opensuse. On both I have installed NTP, but there is no program called ntpdsim.
How can I use this tool?
ntpdsim is indeed part of the ntp source tarball, however apparently not included in the distribution packages you cite.
When compiling from source, you need to run ./configure with --enable-simulator to build/install it. That's at least what ./configure --help says.
Check ./configure --help to see if there's a build option you need to enable.
I think this is what you're looking for : http://doc.ntp.org/4.2.2p1/ntpdsim.html