I'm unable to install the specific sub version 5.7.23 on mac, however I'm able to install just MySQL 5.7, which is something i don't want. Any ideas? I'm using macOS10.15.4
brew install mysql#5.7.23
Error: No available formula with the name "mysql#5.7.23"
==> Searching for a previously deleted formula (in the last month)...
Error: No previously deleted formula found.
==> Searching for similarly named formulae...
Error: No similarly named formulae found.
==> Searching taps...
==> Searching taps on GitHub...
Error: No formulae found in taps.
Due to homebrew-core versioned formulae support policy:
Versioned formulae should differ in major/minor (not patch) versions from the current stable release. This is because patch versions indicate bug or security updates, and we want to ensure you apply security updates.
The latest mysql#5.7 points to mysql#5.7 5.7.31. GitHub PR reference
You should be able to use the latest 5.7.x series with brew install mysql#5.7 or brew upgrade mysql#5.7 (if you already installed it).
Related
The current installed MySQL version on my server (ubuntu 18.04) is 5.7, I need to update it to 8th version .. I'm following this instruction.
I'm at /home/martin# path and I executed apt-get update and apt-get upgrade as well. I've also executed this wget https://dev.mysql.com/get/mysql-apt-config_0.8.22-1_all.deb and the installation file downloaded correctly.
Now, when I run this dpkg -i mysql-apt-config_0.8.22-1_all.deb, I get a prompt with old version:
See? it's still mysql-5.7. Why?
The expected result (based on the instruction) should be mysql-8.0.
Well it says "currently selected: mysql-5.7", but what happens when you actually select that item? As this is the Package configuration step it may well be that this is actually what's going to do the actual configuration replacement, so replacing 5.7 with the more recent install
I am downloading chromedriver through a brew cask install (see related issue ) and when I try to download it I get the following error (pasted full output from command entry):
(env) MacBook:project_dir owner$ brew cask install chromedriver
Updating Homebrew...
==> Auto-updated Homebrew!
Updated 1 tap (homebrew/core).
==> Updated Formulae
dnstwist grpc pdns uftp
firebase-cli lf pdnsrec wildfly-as
glslviewer libxlsxwriter tile38 zabbix
==> Satisfying dependencies
==> Downloading https://chromedriver.storage.googleapis.com/2.41/chromedriver_ma
######################################################################## 100.0%
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/utils/quarantine.swift:29:30: error: 'quarantinePropertiesKey' is only available on OS X 10.10 or newer
forKey: URLResourceKey.quarantinePropertiesKey
^
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/utils/quarantine.swift:29:30: note: add 'if #available' version check
forKey: URLResourceKey.quarantinePropertiesKey
^
Error: Failed to quarantine /Users/user/Library/Caches/Homebrew/downloads/42621d77ecaa889fa8ca73ac4b2a2228e3c1d11f20d84c6898e7645397d00f1d--chromedriver_mac64.zip. Here's the reason:
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/utils/quarantine.swift:29:30: error: 'quarantinePropertiesKey' is only available on OS X 10.10 or newer
forKey: URLResourceKey.quarantinePropertiesKey
^
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/utils/quarantine.swift:29:30: note: add 'if #available' version check
forKey: URLResourceKey.quarantinePropertiesKey
My current macbook specs are as follows:
Has anyone ran into this issue before? Any help would be appreciated. I am trying to set up a headless chrome driver and failing.
UPDATE_EDIT: I've since moved on from Chrome and had more luck using Firefox headless instead, but this is still no solution to the issue above.
https://github.com/Homebrew/homebrew-cask/issues/51554#issuecomment-418215466
try below.
$ brew cask install --no-quarantine chromedriver
This is due to a current bug in Homebrew, and a fix has been merged
Per issue #4809:
Hi, PR #4656 appears to break brew cask install on 10.11. I get an error on 10.11, but not on 10.12. As a workaround, re-running with the --no-quarantine flag is successful. I'm not sure why this swift feature isn't available, my OS is up to date.
(snip)
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/utils/quarantine.swift:29:30: error: 'quarantinePropertiesKey' is only available on OS X 10.10 or newer
forKey: URLResourceKey.quarantinePropertiesKey
(etc)
(snip and etc mine)
This is the same issue you are facing.
There is a PR (#4796) that addresses this, which has been merged into master as of a day ago (2018-09-06):
The Gatekeeper API I've written relies on an up-to-date CLT (or Xcode) install, and xattr's -r flag for native recursion. There are cases where Swift is too old or is set to a deployment target earlier than MacOS 10.10, and thus cannot use the URLResourceKey.quarantinePropertiesKey constant. And in the current Mojave beta, xattr does not have Apple's -r extension for doing native filesystem traversal.
This pull request inserts an additional check in the Swift script, the Quarantine.available? function and brew cask doctor, and changes propagate to use xargs for recursion.
I just ran a brew update and it tells me I am running 1.7.3 running at commit 5d894, which was committed today (2018-09-07) and is the latest version of homebrew-core at time of writing.
I'm trying to install Atom from the official RPM provided. libXss.so.1 is a dependency and tries to install the 32-bit version of glibc when I already have the 64-bit version. It then conflicts with the 2.23.1-7 older version of glibc that I already have.
So where do I go from here? I'm guessing that there is a bugfix somewhere in libXss. libXss tries to install i686 arch for all it's dependencies.
I'm using Fedora 24 x86_64
Terminal Output
sudo rpm -ivh atom.x86_64.rpm
error: Failed dependencies:
libXss.so.1 is needed by atom-1.13.0-0.1.x86_64
sudo dnf install libXss.so.1
Error: Transaction check error:
file /usr/share/doc/glibc/NEWS from install of glibc-2.23.1-11.fc24.i686 conflicts with file from package glibc-2.23.1-7.fc24.x86_64
sudo dnf install glibc-2.23.1-11.fc.24.x86_64
Package glibc-2.23.1-11.fc24.x86_64 is already installed, skipping.
Dependencies resolved.
Nothing to do.
Complete!
Secondary/Unimportant Question
Do I need glibc-2.23.1-7.fc24.x86_64 when I already have glibc-2.23.1-11.fc24.x86_64? I see that I have both installed yet I have no conflict problems.
edit
I gave up and decided to install from the copr repo
sudo dnf copr enable mosquito/atom
sudo dnf install atom
Error: Transaction check error:
file /usr/lib64/libkadm5clnt_mit.so.10.0 from install of libkadm5-1.14.4-4.fc24.x86_64 conflicts with file from package krb5-libs-1.14.1-6.fc24.x86_64
file /usr/lib64/libkadm5srv_mit.so.10.0 from install of libkadm5-1.14.4-4.fc24.x86_64 conflicts with file from package krb5-libs-1.14.1-6.fc24.x86_64
What is going on?
Can I bypass installing glibc.i686 as a dependency when I already have the x86_64 version?
Not if you need to install 32-bit software — you'll need the 32-bit libs for that. 64-bit libraries aren't supersets of the 32-bit ones.
I'm trying to install Atom from the official RPM provided. libXss.so.1 is a dependency and tries to install the 32-bit version of glibc when I already have the 64-bit version. It then conflicts with the 2.23.1-7 older version of glibc that I already have.
This is a frequent problem. Installing 32-bit versions of packages without updating to the latest versions of the main 64-bit packages is not supported. Upgrade first, then install.
Do I need glibc-2.23.1-7.fc24.x86_64 when I already have glibc-2.23.1-11.fc24.x86_64? I see that I have both installed yet I have no conflict problems.
This can happen if there's an interrupted upgrade transaction. You should be able to dnf remove glibc-2.23.1-7.fc24.x86_64 safely. If that gives you errors, time to stop and make sure nothing else is wrong. Or, you can really just ignore it — next time a new glibc update comes out, it should replace both.
I gave up and decided to install from the copr repo
The errors you see here are actually the same root problem as trying to install 32-bit packages without updating first. RPMs can share files, as long as they are completely identical. That's true in matched versions of the various kerberos packages, but not true if there's a mismatch, and the dependency information doesn't handle this. So, again upgrade to latest packages before installing new ones.
This question has been asked before here (404 error when using brew to install mysql), but unfortunately the fix doesn't work for me. I have already ran brew update, so I'm up to date.
I'm on the latest version of MacOS 10.12 and I am running Xcode 8 if that matters.
brew install mysql
Warning: You are using OS X 10.12.
We do not provide support for this pre-release version.
You may encounter build failures or other breakages.
==> Downloading https://cdn.mysql.com/Downloads/MySQL-5.7/mysql-boost-5.7.11.tar.gz
curl: (22) The requested URL returned error: 404 Not Found Error:
Failed to download resource "mysql" Download failed:
https://cdn.mysql.com/Downloads/MySQL-5.7/mysql-boost-5.7.11.tar.gz
I know it says this is a pre-release version, but is there any hope here?
Thanks
The 5.7.11 mysql download you reference no longer exists (it certainly is 404).
Looking at the homebrew formula for mysql, it has been updated to point to the latest mysql version.
So it seems that you are not in fact up to date. Try running brew update twice, then brew doctor and fix any warnings.
There have been some big changes in homebrew over the last 9 months, if you have an old install it might be easier to uninstall totally. There are also several ownership and directory location changes that need to be straightened out with the upgrade to homebrew 1.0
I followed the steps laid out here: Brew Update not working after mac 10.9
In case that's not visible anymore, here's that answer:
cd `brew --prefix`
git fetch origin
git reset --hard origin/master
After that, you should be able to brew update and then brew install mysql
For those who are still struggling to resolve this.
Please try:
brew update-reset
brew update
I found this gem here.
P.S.: If you have a shallow clone, after brew update-reset command, run the following command to unshallow:
git -C /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core fetch --unshallow
I am trying to install a software which required MySQL-server, MySQL-client installed on the server so now I want to install MySQL-server and MySQL-client using rpm files "MySQL-server-5.5.17-1.rhel5.x86_64.rpm" and "MySQL-client-5.5.17-1.rhel5.x86_64.rpm".
I have installed MySQL-client but when I try to run mysql-server
*rpm -i MySQL-server-5.5.17-1.rhel5.x86_64.rpm*
it's showing error:
*error: Failed dependencies:
MySQL conflict with mysql-5.0.77-4.el5_6.6.x86_64
MySQL conflict with mysql-5.0.77-4.el5_6.6.i386
MySQL conflict with mysql-server-5.0.77-4.el5_6.6.x86_64*
So how can i solve this problem?
the error given by you *error: Failed dependencies:
MySQL conflict with mysql-5.0.77-4.el5_6.6.x86_64
MySQL conflict with mysql-5.0.77-4.el5_6.6.i386
MySQL conflict with mysql-server-5.0.77-4.el5_6.6.x86_64*
It clear show that the machine you are going to install mysql 5.5 rpm have mysql 5.0.77 installed .
to resolve this problem .
1. you take backup of datadir and my.cnf (if you are using mysql 5.0 db server earlier).
2. remove all mysql 5.0 server packages , to remove these package you should knew what are the packages already installed on machine
to view all mysql package already installed use rpm -qa | grep -i "mysql*" this command show what package is already installed on machine
now you have to remove all package which name shows in above command.
to remove a package/rpm use rpm -e mysql-5.0.** if show error then use
rpm -e --nodeps mysql-5.0.**
we have to remove all packages one by one by using rpm -e .
after successful remove all older version of mysql , now start installation of mysql-5.5*** packages by using rpm -ivh mysql-5.5***.rpm.
First question - is the version of MySQL already installed actually in use or was it simply there as a result of a fresh CentOS install? If the former, try upgrading rather than installing. If the latter, uninstall the old version (possibly using the --no-deps option on rpm) and then install the newer version
Next, are you trying to replace MySQL or install another version alongside it?
If the former, again try upgrading rather than installing. If that's not possible, you're going to have to remove the older version and then install the new version
If the latter, and if it is possible, look at the --prefix and --relocate options in RPM.as they may help.
If you do to mange to get it installed side by side with an older, you'll have fun and games ensuring that the relevant versions are pointing to the correct libraries and that you don't get any corruption between them. Also, you will need to run them so that they listen on separate ports with separate database folders, PID and socket files etc.
Whatever you need to do, do it out of business hours with as many backups as you can do