Facing an issue with go-openapi/analysis library using glide - go

I was trying to install the go-openapi/analysis using the glide. Using the glide up -v command for installing. Glide version v0.13.2 and go version 1.11
glide.yaml
package: abc
import:
- package: github.com/go-openapi/analysis
version: 0.16.0
Got this error during the installation process.
Keeping github.com/go-openapi/analysis 0.16.0 [INFO]
--> Setting version for github.com/mailru/easyjson to 2f5df55504ebc322e4d52d34df6a1f5b503bf26d.
[ERROR] Error scanning path/filepath: cannot find package "." in:
.glide/cache/src/https-path-filepath

Related

pip --no-dependencies flag appears to be ignored

Executing pip install --no-dependencies pyarrow==4.0.1,
I see
Looking in indexes: ...
Collecting pyarrow==4.0.1
Using cached ...
Installing build dependencies ...
Why is it still "Installing build dependencies"? Installing the numpy dependency (somehow it started compiling it) failed shortly afterwards, so I'd like to skip that step.

Failure to build any conda package on MAC OS

When building any conda recipie on my macOS (High Sierra, version 10.13.6), I get the following error:
OSError: dlopen(/anaconda3/bin/../lib/libarchive.dylib, 6): Library not loaded: #rpath/libxml2.2.dylib Referenced from: /anaconda3/lib/libarchive.13.dylib
Reason: Incompatible library version: libarchive.dylib requires version 12.0.0 or later, but libxml2.2.dylib provides version 10.0.0
I have done the following:
Downloaded and installed https://repo.anaconda.com/archive/Anaconda3-2019.03-MacOSX-x86_64.pkg.
updated conda: conda update conda
installed conda-build: conda install conda-build
then tried building conda recipe: conda install .
I get this error when building any recipe, for the sake of example, here is the one i am trying:
package:
name: cmake
version: 3.2.3
source:
fn: cmake-3.2.3.tar.gz [not win]
url: http://www.cmake.org/files/v3.2/cmake-3.2.3.tar.gz [not win]
build:
number: 0
requirements:
build:
run:
about:
home: http://www.cmake.org
license: BSD 3-clause
build.sh contains:
#!/bin/bash
./bootstrap --prefix=$PREFIX
make
make install

How to Setting PDO PHP 7.0 on AWS Server EC2

I have trouble on setting PDO on AWS Server. Like this :
[root#ip-172-31-31-52 /]# sudo yum install php-pdo
Loaded plugins: priorities, update-motd, upgrade-helper
amzn-main | 2.1 kB 00:00
amzn-updates | 2.5 kB 00:00
Resolving Dependencies
--> Running transaction check
---> Package php-pdo.x86_64 0:5.3.29-1.8.amzn1 will be installed
--> Processing Dependency: php-common(x86-64) = 5.3.29-1.8.amzn1 for package: php-pdo-5.3.29-1.8.amzn1.x86_64
--> Running transaction check
---> Package php-common.x86_64 0:5.3.29-1.8.amzn1 will be installed
--> Processing Conflict: php70-common-7.0.33-1.32.amzn1.x86_64 conflicts php-common < 5.5.22-1.98
--> Finished Dependency Resolution
Error: php70-common conflicts with php-common-5.3.29-1.8.amzn1.x86_64
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
How to solve this. I need PDO settings. Please help me
Step 1:
Take snapshot of your server
Step 2:
Check your php version and install the php packages corresponding to php version.
Additional info:
Laravel 5.4 requires PHP >= 5.6.4
Make sure you install php 5.6.4 or greater.
Specifically call out the exact package for php version.
Example:
For PHP 5.6 support, the package is php56-mysqlnd.
For PHP 7.0 support, the package is php70-mysqlnd.
For PHP 7.1 support, the package is php71-mysqlnd.
These package will install pdo support.
Advice, Install latest stable version of php and laravel.
Happy coding!

Error in Puppet agent 3.8 installation on cent OS 7.5 without internet

I am installing puppet agent 3.8.7 on cent OS 7.5. The OS was installed on a new VM and it is not connected to internet. I have created a yum repo which points to pulp repository. Below are the contents of my yum repo for puppet -
[root#server --- ~]# cat /etc/yum.repos.d/puppetlabs.repo
[puppetlabs-products]
name=Puppet Labs Products El 7 - $basearch
baseurl=http://136.243.83.142/pulp/repos/puppetlabs-products-el6
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppetlabs
file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppet
enabled=1
gpgcheck=1
[puppetlabs-deps]
name=Puppet Labs Dependencies El 7 - $basearch
baseurl=http://136.243.83.142/pulp/repos/puppetlabs-deps-el6/
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppetlabs
file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppet
enabled=1
gpgcheck=1
when I run 'yum install puppet', I get below error. I have ruby 2.0 installed but the puppet packages reuquire ruby 1.8. When I checked the puppetlabs site, they mention puppet supports ruby 2.0. So, how do I proceed now, given the fact that my server is in internal domain and not connected to internet.
Below is the error I get on executing 'yum install puppet' -
[root#server --- ~]# yum install puppet
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
epel | 2.5 kB 00:00:00
puppetlabs-deps | 1.8 kB 00:00:00
puppetlabs-products | 1.8 kB 00:00:00
Resolving Dependencies
--> Running transaction check
---> Package puppet.noarch 0:3.8.7-1.el6 will be installed
--> Processing Dependency: hiera >= 1.0.0 for package: puppet-3.8.7-1.el6.noarch
--> Processing Dependency: facter >= 1:1.7.0 for package: puppet-3.8.7-1.el6.noarch
--> Processing Dependency: ruby(selinux) for package: puppet-3.8.7-1.el6.noarch
--> Processing Dependency: ruby-augeas for package: puppet-3.8.7-1.el6.noarch
--> Processing Dependency: ruby-shadow for package: puppet-3.8.7-1.el6.noarch
--> Running transaction check
---> Package facter.x86_64 1:2.4.6-1.el6 will be installed
---> Package hiera.noarch 0:1.3.4-1.el6 will be installed
---> Package puppet.noarch 0:3.8.7-1.el6 will be installed
--> Processing Dependency: ruby(selinux) for package: puppet-3.8.7-1.el6.noarch
---> Package ruby-augeas.x86_64 0:0.4.1-3.el6 will be installed
--> Processing Dependency: ruby(abi) = 1.8 for package: ruby-augeas-0.4.1-3.el6.x86_64
--> Processing Dependency: libruby.so.1.8()(64bit) for package: ruby-augeas-0.4.1-3.el6.x86_64
---> Package ruby-shadow.x86_64 1:2.2.0-2.el6 will be installed
--> Processing Dependency: libruby.so.1.8()(64bit) for package: 1:ruby-shadow-2.2.0-2.el6.x86_64
--> Finished Dependency Resolution
Error: Package: puppet-3.8.7-1.el6.noarch (puppetlabs-products)
Requires: ruby(selinux)
Error: Package: ruby-augeas-0.4.1-3.el6.x86_64 (puppetlabs-deps)
Requires: libruby.so.1.8()(64bit)
Error: Package: 1:ruby-shadow-2.2.0-2.el6.x86_64 (puppetlabs-deps)
Requires: libruby.so.1.8()(64bit)
Error: Package: ruby-augeas-0.4.1-3.el6.x86_64 (puppetlabs-deps)
Requires: ruby(abi) = 1.8
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

pipenv cannot find module 'runpy' when installing dependancies

C:\Users\danie01\fox\test\robotframework>pipenv install
Installing dependencies from Pipfile.lock (49d163)...
An error occurred while installing robotframework-seleniumlibrary==3.1.0! Will try again.
An error occurred while installing selenium==3.9.0! Will try again.
An error occurred while installing robotframework==3.0.2! Will try again.
An error occurred while installing psutil==5.4.3! Will try again.
================================ 4/4 - 00:00:00
Installing initially failed dependencies...
-------------------------------- 0/4 - 00:00:00
Could not import runpy module
ImportError: No module named 'runpy'
================================ 0/4 - 00:00:00
I recently reinstalled Python for all users, and now I am having this problem when attempting to run pipenv install. Why might this be?
Python 3.5 is in path. Running immediately after the prior command:
C:\Users\danie01\fox\test\robotframework>echo %PATH%
C:\Program Files\Python 3.5\;C:\Program Files\Python 3.5\Scripts\;blahblah
C:\Users\danie01\fox\test\robotframework>pipenv run python --version
Python 3.5.0
I had the same issue recently when moving from 3.5 to 3.7.3:
I removed 3.5, installed 3.7.3
remove older versions of python from path
updated pipfile to point to newer version of python
restarted terminal
reinstall pip: https://www.liquidweb.com/kb/install-pip-windows/
reinstall pip install pipenv
Then you should be good to run pipenv install.

Resources