I'm running Fedora Workstation 22 on my Notebook. After installing it, I've done
dnf upgrade
to update all packages (was around 700 MB) - and checked the Gnome-Software applications for Updates. Gnome Software hasn't offered any updates. But sometimes, I get a notification from Gnome software to restart my Computer and install the Updates.
I found this procedure - Offline updating for libraries and components which are currently running - in the Wiki. But I don't understand how this works. If I install dnf upgrade, didn't this command update all packages to the most current version in the repos? Is Gnome-Software using different repositories, or how does this mechanism work?
I wanted to update my entire system via command-line. How can I do than? I'm a bit confused, because - for example - on Debian I could simply type
apt-get update && apt-get upgrade
to update my entire system. How is this possible in Fedora?
Its pretty much easy to update your fedora 22.
Use this command and it will simply update your fedora 22 with all available packages.
sudo dnf update
and if you are already root, simply use
dnf update
and will update your fedora.
For any other query related to update, write it in comments.
Related
I am trying to install mysql workbench on a system without network. I downloaded the mysql-workbench-community, mysql-community-{server, client, common, libs} which were noted in the "Installing RPM Packages" section of MySQL Install Manual. It states that these are the standard rpm packages needed for a basic functional install of mysql community. So with that I downloaded all the rpm packages and attempted to manually install each using:
sudo rpm -ivh mysql-community-package-name.rpm
Unfortunately I keep getting dependency errors. I found this link to obtain all the dependencies for a package. So on my second attempt I ran the following:
Repoquery -R --resolve --recursive mysql-community-server | xargs -r yumdownloader
Which gave me about 100 rpm packages. I transferred them onto my machine and unfortunately more dependencies like mysql-connectors-community and mysql-=tools-community came up which were never documented or mentioned as dependencies with the script.
What am i doing wrong? Is there a way to download all the rpms and bundle them together as a custom RPM in the future? I see ubuntu has a apt-offline command mentioned here. Is there a similar method I can apply for redhat?
Update1:
I have an idea to create a container rhel7 instance, mounting /root/tmpkg and running this example. But is there another way I should consider?
First a small situation sketch. We have CentOS 7 and we want to install the opensource version of Oreka (http://oreka.sourceforge.net/). However the software hasn't received updates since 2013.
So we found that in the install script it looks for the rpm package mysql-server. But rpm -q returns package not found since the name is mysql-community-server now. So the question is can we add the alias "mysql-server" somehow to "mysql-community-server" to fool the script. This would be more convenient than rebuilding the install script/package.
You can make your own empty RPM that "Provides" mysql-server and "Requires" mysql-community-server to do this kind of aliasing. You can call it something like mysql-server-compat-myorg.
On my Fedora 19 system, yum update attempts to reinstall a large number packages I have previously removed. This should not happen, as the packages listed are not installed and should not be suggested by yum. How can I make yum work in the expected manner - with updates suggesting only upgrades to preinstalled packages.
Background: I have been trying out new DEs - installing and removing them as I go. Currently, I'm in a DE-less state, booting directly into a tty terminal. My system has no (or a few hidden) xfce or cinnamon packages to "upgrade", yet the package manager is suggesting 300 packages to install, totaling 600M of new install.
Terminal output gist:
https://gist.github.com/Redoubts/29400f0b98cd13120a6a#file-gistfile1-txt
Short answer - It's not possible to disallow installing any packages from the depenency chain. Either you install all of them or drop those who depends on unwanted packages.
In some cases, when the package from a dependency chain is required only during some specific stages of installation (say for execution of a pre- or post-install scripts), it's possible to remove thise package later, after the complete installation. But that's not what you want I suppose.
I just installed Centos 6.4, and installed MySQL using the version that came with the Centos distribution. To my dismay, it is MySQL 5.1.69 versus the current 5.6.12. As stated on http://dev.mysql.com/doc/refman/5.5/en/linux-installation-native.html, "the MySQL version will often be some way behind the currently available release", but I didn't expect that long.
[root#centosBox ~]# rpm -qa | grep mysql
mysql-5.1.69-1.el6_4.x86_64
mysql-devel-5.1.69-1.el6_4.x86_64
mysql-server-5.1.69-1.el6_4.x86_64
mysql-libs-5.1.69-1.el6_4.x86_64
[root#centosBox ~]# whereis mysql
mysql: /usr/bin/mysql /usr/lib64/mysql /usr/include/mysql /usr/share/mysql /usr/share/man/man1/mysql.1.gz
[root#centosBox ~]#
An alternative is to install by RPM packages which is the "recommended way to install MySQL" per http://dev.mysql.com/doc/refman/5.5/en/linux-installation-rpm.html. I have done so and it wasn't overly complicated, however, I am concerned as I've often been told that I should always install by yum when available. Towards the very end of the documentation, it does describe doing so extremely briefly using yum, however, it is so brief that I question whether it is the way to go.
So.... What is the best way for a not guru Linux user to install/upgrade MySQL on a Centos machine?
Just this week (2013-10-28), MySQL announced official yum repositories for MySQL Community Edition. The packages are intended for use with RHEL-compatible Linux (e.g. CentOS).
All the details including how to set up the yum repo on your system, can be found from the announcement:
http://insidemysql.com/announcing-new-yum-repositories-for-mysql/
A bit off-topic but there we go.
It is recommended to install from the repositories because you can later update your software to a newer version with a simple yum upgrade. The repository takes care of that for you, as well as any dependencies the software may entertain with other libraries.
RPM Packages installed manually (even with yum, which then only acts as an installer) will have to be managed manually as well.
Since the MySQL RPM package shows no dependencies (as far as I can tell from the manual), you are safe from this side.
And to answer your question: the best method is to stick with the versions from the repository. If you need a newer version, then you took the right path.
I am no guru myself but I was happy with the result of the RPM method you mentioned since other times I have seen problems with mysql-libs being a dependency for other packages.
(depending on the 5.6 version you want and cpu)
mkdir MySQL
cd MySQL
wget http://dev.mysql.com/get/Downloads/MySQL-5.6/MySQL-5.6.16-1.el6.x86_64.rpm-bundle.tar
tar -xvf MySQL-5.6.16-1.el6.x86_64.rpm-bundle.tar
yum install MySQL*rpm
installs them in the correct order and removes mysql-libs in one step without conflicts.
http://dev.mysql.com/doc/refman/5.6/en/linux-installation-rpm.html
It doesn't surprise me that MySQL is a bit behind. Why would Oracle make it easy for you to not use pay-for Oracle? </rant>
Anyway, you can get the awkwardly named, but otherwise identical MariaDB to run easily by adding a new YUM repository.
You can install MySQL 5.5 (mysql55-server.x86_64) from IUS repository (currently version 5.5.34 available)
When running the transaction check to install mysql i'm getting:
Processing Conflict: mysql55-5.5.29-1.w6.x86_64 conflicts mysql < 5.5
I guess this means i'm attempting to install a package called mysql55-5.5.29-1.w6.x86_64 on to a system with mysql already installed but somehow there is a conflict?
yum says that mysql isn't installed so it was installed without using the repositories. In that case how does yum know there is confict?
it would be good to better under what 'confict' means.
There are many online yum repo available and all are free opensource contribute. So source packages are compiled with different options in each repo. So when we add 2 or more yum repo at a time, it may happen that 2 or more packages are of same version are selected and we get a conflict error.
In your case you added some repo which is providing mysql 5.5 which is already available with some other name in some other repo or already installed but new mysql package is selected by yum for any other package as dependency. Try removing one of the repo or try installing it as yum install mysql-5.5*
You can try this : yum list | grep mysql. It will list mysql in different packages, then you can make a decision to remove one of them and install mysql again.