My internet has interference so brew installation procedure may failure sometimes.
==> Downloading https://github.com/openjdk/jdk/commit/f80a6066e45c3d53a61715abfe71abc3b2e162a1.patch?full_index=1
######################################################################## 100.0%
==> Downloading https://github.com/openjdk/jdk/commit/4622a18a72c30c4fc72c166bee7de42903e1d036.patch?full_index=1
curl: (35) LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to github.com:443
Error: Failed to download resource "openjdk--patch"
Download failed: https://github.com/openjdk/jdk/commit/4622a18a72c30c4fc72c166bee7de42903e1d036.patch?full_index=1
I manage to got that file, but I don't known the correct filename for brew.
brew --cache openjdk--patch
Error: No available formula or cask with the name "openjdk--patch".
brew --cache -s openjdk
~/Library/Caches/Homebrew/downloads/336948b1d9a8eba79fadf26569f4af0cb2fe147fde214fc9d9bf6b66f2f927d2--jdk15u-jdk-15.0.1-ga.tar.bz2
So how to got the correct filename for this patch?
I found the tricky, just run
brew install package-name -d
it will print each cache name of resources used by package-name
Related
$ brew install mongodb-community#4.4
It returns:
Error: Failure while executing; `tar --extract --no-same-owner --file /Users/frankline/Library/Caches/Homebrew/downloads/302d48e748531e0994cd7b3caf9bc7069ec6c132b710dc1bb8e33b725495056e--icu4c-69.1.big_sur.bottle.tar.gz --directory /private/tmp/d20210613-34193-g4tpe7` exited with 1. Here's the output:
tar: Error opening archive: Failed to open '/Users/frankline/Library/Caches/Homebrew/downloads/302d48e748531e0994cd7b3caf9bc7069ec6c132b710dc1bb8e33b725495056e--icu4c-69.1.big_sur.bottle.tar.gz're
I got the same problem when I executed brew upgrade. It returns:
==>installing dependencies for python#3.9: gdbm, mpdecimal, openssl#1.1 and xz.
==>Installing python#3.9 dependency: gdbm
==> Pouring gdbm-1.19.big_sur.bottle.tar.gz
tar: Error opening archive: Failed to open '/Users/xxx/Library/Caches/Homebrew/downloads/37cae0aa5a09881f7ab73dab85cc31f096f5dd68aa99e80a4ccac9957292d63d--gdbm-1.19.big_sur.bottle.tar.gz'
Error: Failure while executing; tar --extract --no-same-owner --file /Users/xxx/Library/Caches/Homebrew/downloads/37cae0aa5a09881f7ab73dab85cc31f096f5dd68aa99e80a4ccac9957292d63d--gdbm-1.19.big_sur.bottle.tar.gz --directory /private/tmp/d20210615-1870-15pgco1 exited with 1. Here's the output:
tar: Error opening archive: Failed to open '/Users/lichong/Library/Caches/Homebrew/downloads/37cae0aa5a09881f7ab73dab85cc31f096f5dd68aa99e80a4ccac9957292d63d--gdbm-1.19.big_sur.bottle.tar.gz'
Here is my solution: first install the dependency, i.e., brew install gdbm and then upgrade. Hope this can solve your problem.
brew install "dependency" and brew upgrade worked for me!
The specific dependency in my case was pcre2, not --gdbm as above.
There are the following two packages in conflict. What is the correct way to resolve this conflict?
$ brew cask install rar
==> Downloading https://www.rarlab.com/rar/rarosx-5.9.1.tar.gz
Already downloaded: /Users/pengy/Library/Caches/Homebrew/downloads/fdb2cc1e1fa3b659b0fc92139bc9645b2ec844b68df1b1d25c5f956332af6cd1--rarosx-5.9.1.tar.gz
==> Installing Cask rar
==> Moving Generic Artifact 'default.sfx' to '/usr/local/lib/default.sfx'.
==> Moving Generic Artifact 'rarfiles.lst' to '/usr/local/etc/rarfiles.lst'.
==> Linking Binary 'rar' to '/usr/local/bin/rar'.
==> Unlinking Binary '/usr/local/bin/rar'.
==> Backing Generic Artifact 'rarfiles.lst' up to '/usr/local/Caskroom/rar/5.9.1/rar/rarfiles.lst'.
==> Removing Generic Artifact '/usr/local/etc/rarfiles.lst'.
==> Backing Generic Artifact 'default.sfx' up to '/usr/local/Caskroom/rar/5.9.1/rar/default.sfx'.
==> Removing Generic Artifact '/usr/local/lib/default.sfx'.
==> Purging files for version 5.9.1 of Cask rar
Error: It seems there is already a Binary at '/usr/local/bin/unrar'.
$ brew info unrar
unrar: stable 6.0.2 (bottled)
Extract, view, and test RAR archives
https://www.rarlab.com/
/usr/local/Cellar/unrar/5.9.4 (6 files, 503.5KB) *
Poured from bottle on 2020-09-04 at 23:47:13
From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/unrar.rb
==> Analytics
install: 36,700 (30 days), 60,145 (90 days), 286,295 (365 days)
install-on-request: 28,778 (30 days), 48,112 (90 days), 221,675 (365 days)
build-error: 0 (30 days)
I just had this same problem pop up and a Google search led me here, but there was no answer :(
So I just took a leap of faith and uninstalled unrar:
$ brew uninstall unrar
Uninstalling ... (5 files, 505.8KB)
And then tried the installation of rar again:
$ brew install rar
...
==> Linking Binary 'rar' to '/usr/local/bin/rar'
==> Linking Binary 'unrar' to '/usr/local/bin/unrar'
🍺 rar was successfully installed!
And sure enough, without unrar installed the rar installation succeeded. I was able to verify this by running:
$ which rar
/usr/local/bin/rar
$ which unrar
/usr/local/bin/unrar
[MIRROR] containerd.io-1.2.0-3.el7.x86_64.rpm: Downloading successful, but checksum doesn't match. Calculated: ece851b2b2defa24eb3b817b14d97f31f4043a713d7367972bd2c1ef4f2788b8(sha256) Expected: 7bd1d8da7d896ead55fdea3a42100eac4c4d7800f958d3ae056d40268dec4636(sha256)
(8/21): python3-policycoreutils-2.9-9.el8.noarch.rpm 107 kB/s | 2.2 MB 00:21
[MIRROR] containerd.io-1.2.0-3.el7.x86_64.rpm: Downloading successful, but checksum doesn't match. Calculated: 3928fc6c58817b02602a249e512d7e99b7c3fe06ea5d9ff3ad46e25984ff8141(sha256) Expected: 7bd1d8da7d896ead55fdea3a42100eac4c4d7800f958d3ae056d40268dec4636(sha256)
[MIRROR] docker-ce-18.09.1-3.el7.x86_64.rpm: Downloading successful, but checksum doesn't match. Calculated: 3ddabd445a05b85aeba128da42283d3285ca8055e6a201139ee49b682942ba43(sha256) Expected: 6034f83c3bf3d5d31120ef36b3172dbb28d1ac8ae3699ed8cb33924dcef0d17a(sha256)
[MIRROR] containerd.io-1.2.0-3.el7.x86_64.rpm: Downloading successful, but checksum doesn't match. Calculated: 3914815a5c9756672d6f046929335ddff86607c29ac8a3c3fc12452a69952bf7(sha256) Expected: 7bd1d8da7d896ead55fdea3a42100eac4c4d7800f958d3ae056d40268dec4636(sha256)
[FAILED] containerd.io-1.2.0-3.el7.x86_64.rpm: No more mirrors to try - All mirrors were already tried without success
(10-11/21): docker-ce-18.09.1-3.el7.x86_64.rpm 50% [============================================== ] 1.4 MB/s | 50 MB 00:35 ETA
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'yum clean packages'.
Error: Error downloading packages:
Cannot download Packages/containerd.io-1.2.0-3.el7.x86_64.rpm: All mirrors were tried
Error: Transaction test error: package selinux-policy-targeted-3.14.3-41.el8_2.5.noarch does not verify: Header SHA1 digest: BAD (Expected ab8b3fe6b75faa65c89e64ec34986ee49924f982 != 3716bcc257255e43bc9ace1b9c4aecb6fcba3e61) package python3-policycoreutils-2.9-9.el8.noarch does not verify: Header SHA1 digest: BAD (Expected af32d12b99154706740619e0ac39289c009f1aa9 != faa84ee41c25523f2a05358d172f124370c18f99) package containerd.io-1.2.6-3.3.el7.x86_64 does not verify: no digest
''' Please help me to install docker on centos8 to fix this issue SHA1 digest: BAD '''
Try installing packages containerd manually:
yum clean packages #clean packages from failed install
dnf install https://download.docker.com/linux/centos/7/x86_64/stable/Packages/containerd.io-1.2.6-3.3.el7.x86_64.rpm #install newest containerd manually
sudo yum install docker-ce docker-ce-cli #install Docker daemon and CLI
Links:
Install Docker on CentOS
Docker documentation for installation
on CentOS
Docker CentOS repository
I'm trying to get Docker installed on a machine with Debian 8 (Jessie), but I always seem to run into errors no matter what I try.
Using these instructions: https://docs.docker.com/install/linux/docker-ce/debian
Checking the kernal:
uname -r
3.16.0-4-686-pae
The fateful moment:
sudo apt-get install docker-ce
Setting up docker-ce (18.06.1~ce~3-0~debian) …
Installing new version of config file /etc/bash_completion.d/docker …
Job for docker.service failed. See ‘systemctl status docker.service’ and ‘journalctl -xn’ for details.
invoke-rc.d: initscript docker, action “start” failed.
dpkg: error processing package docker-ce (–configure):
subprocess installed post-installation script returned error exit status 1
Processing triggers for libc-bin (2.19-18+deb8u10) …
Errors were encountered while processing:
docker-ce
E: Sub-process /usr/bin/dpkg returned an error code (1)
I also tried installing directly from a package: https://download.docker.com/linux/debian/dists/jessie/pool/stable/amd64/
(Selecting version 17.03.2)
And after installing the dependencies, things still don't work:
sudo dpkg --install docker-ce_17.03.2_ce-0_debian-jessie_amd64.deb
(Reading database ... 169325 files and directories currently installed.)
Preparing to unpack docker-ce_17.03.2_ce-0_debian-jessie_amd64.deb ...
Unpacking docker-ce (17.03.2~ce-0~debian-jessie) over (17.03.2~ce-0~debian-jessie) ...
Setting up docker-ce (17.03.2~ce-0~debian-jessie) ...
Job for docker.service failed. See 'systemctl status docker.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript docker, action "start" failed.
dpkg: error processing package docker-ce (--install):
subprocess installed post-installation script returned error exit status 1
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for systemd (215-17+deb8u7) ...
Errors were encountered while processing:
docker-ce
I also looked at this article: http://www.boynux.com/docker-jessie/
But I didn't even get past the first step:
curl https://get.docker.com | sh
Either your platform is not easily detectable or is not supported by this
installer script.
Please visit the following URL for more detailed installation instructions:
https://docs.docker.com/engine/installation/
Between every one of these attempts I did a
sudo apt-get remove docker docker-engine docker.io docker-ce
sudo apt-get update
docker-ce isn't available for i686
see OS requirements
Docker CE is supported on both x86_64 (or amd64) and armhf architectures for Jessie and Stretch.
I install ubuntu-14.04.4-server-amd64.iso in my VirtualBox,then I use some way to get its rootfs. after that i can the rootfs to create my docker image.the Dockerfile as following:
FROM scratch
COPY rootfs /
RUN chmod u+s /usr/bin/sudo && chmod u+s /bin/mount && chmod u+s /bin/umount
I start my docker container,then I install some tools,like minicom,wget ...,but error,the following is error msg:
root#20ca319c51e6:~$ apt-get install minicom
Reading package lists... Done
Building dependency tree
Reading state information... Done
minicom is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up libpam-systemd:amd64 (204-5ubuntu20.19) ...
initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
invoke-rc.d: unknown initscript, /etc/init.d/systemd-logind not found.
runlevel:/var/run/utmp: No such file or directory
dpkg: error processing package libpam-systemd:amd64 (--configure):
subprocess installed post-installation script returned error exit status 100
Errors were encountered while processing:
libpam-systemd:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
I also try to "apt-get update；apt-get upgrade",but get same error msg too,
what's should i do.need you help! thanks all :)