at the end of each week. Over the past few months I’ve noticed the downloads getting awfully large and complex, so I’ve started wondering “How can these all be patches?” However I never got sufficiently curious to follow up until today.
After the latest zypper patch I saw the following notification:
Message from package mariadb:
You just installed MySQL server for the first time.
followed by instructions for setting up my first database.
That sounds more like an “install” than a “patch”.
Hard to say without seeing your list of patches/packages to be installed, but there was a KDE and a GNOME update recently, which contains of many packages of course.
After the latest zypper patch I saw the following notification:
followed by instructions for setting up my first database.
That sounds more like an “install” than a “patch”.
Any thoughts?
This has been mentioned in a different recently.
The mariadb package prints that message if there is no database folder (/var/lib/mysql/) when the package is installed, even if it is just an update.
You probably never started mariadb/mysql as system-wide service.
You can of course ignore that message, or file a bug report to get this fixed/improved.
Hard to say without seeing your list of patches/packages to be installed, but there was a KDE and a GNOME update recently, which contains of many packages of course.
After the latest zypper patch I saw the following notification:
followed by instructions for setting up my first database.
That sounds more like an “install” than a “patch”.
Any thoughts?
This has been mentioned in a different recently: MariaDB, -the first time.. - Install/Boot/Login - openSUSE Forums
The mariadb package prints that message if there is no database folder (/var/lib/mysql/mysql/) when the package is installed, even if it is just an update.
You probably never started mariadb/mysql as system-wide service.
You can choose to ignore that message, or file a bug report to get this fixed/improved.
Was I mistaken in thinking that zypper patch would not upgrade things but only install patches? I’m wondering if some lines might have become blurred here. Am I misinformed?
I am wondering why you posted this in General Chitchat:
A friendly place to converse about your adventures with openSUSE, your weekend, your boss, your new car, and generally stuff that doesn’t fit somewhere else (and we must ask: PLEASE do not post help questions here)
IMHO it is a technical question that would be interesting for your fellow openSUSE users. And not all members here are watching the GeneralChitchat forum because they are using the forums for serious openSUSE questions/problems.
I’ve just done a little follow up and found documentation that appears to confirm my original assumptions.
From zypper --help
Update Management:
update, up Update installed packages with newer versions.
list-updates, lu List available updates.
patch Install needed patches.
list-patches, lp List needed patches.
dist-upgrade, dup Perform a distribution upgrade.
patch-check, pchk Check for patches.
From man zypper
patch
A released patch conflicts with the affected/vulnerable versions of a collection of packages. As long as any of these affected/vulnerable versions are
installed, the conflict triggers and the patch is classified as needed. Selecting the patch, the conflict is resolved by updating all installed and
affected/vulnerable packages to a version providing the fix. When updating the packages zypper always aims for the latest available version.
patch [options]
Install all available needed patches.
If there are patches that affect the package management itself, those will be installed first and you will be asked to run the patch command again.
This command is similar to zypper update -t patch.
update (up) [options] [packagename]…
Update installed packages with newer versions, where possible.
On the other hand last week’s “patch” included the installation of MYSQL where none existed before and none was needed. In the past I’ve seen my entire list of packages from Packman replaced with newer versions. I remain confused.
Are you sure?
KDE’s akonadi framework does require MySQL/MariaDB, so you likely did have it installed before if you have KDE installed.
In the past I’ve seen my entire list of packages from Packman replaced with newer versions.
This only happens if you use “zypper dup”.
“zypper patch” and “zypper up” do not switch packages to versions from other repos, unless you explicitely tell it to.
Sorry I wasn’t more clear. the updates are coming from the original repo, but they are so extensive that the likelihood that they’re all patches is minimal. That’s only one example. One week last month I patched a machine on its usual weekly schedule and saw 218 Mb of multimedia, LibreOffice and Graphics packages get downloaded and installed.
Candidly, this isn’t an issue for me (other than it picqued my curiosity), but I wonder about some poor soul with a slow connection to the Internet. Is that all needed?
You said, that all your Packman packages got switched to the standard versions. And neither “up” nor “patch” do that, unless you force it to, or enable “vendor change” in zypp.conf.
And what do you mean with “coming from the original repo”?
Did additional software from the standard repo get installed? That’s probably because it is recommended by the installation patterns. Remove the patterns that recommend the software that you don’t want, and it shouldn’t get reinstalled again after you uninstalled it. Or set “solver.onlyRequires=true” in /etc/zypp/zypp.conf to prevent the installation of recommended packages altogether.
That’s only one example. One week last month I patched a machine on its usual weekly schedule and saw 218 Mb of multimedia, LibreOffice and Graphics packages get downloaded and installed.
Yes, LibreOffice has been updated to 4.3.6.2. What’s so strange about it?
Other people would be complaining if it wouldn’t be updated…
If you uninstalled it and it got reinstalled, see above.
The rest of the updates (“multimedia”) probably came from Packman. But those do not get installed when running “zypper patch”. They do get installed by “zypper up” though or your desktop’s updater.
Candidly, this isn’t an issue for me (other than it picqued my curiosity), but I wonder about some poor soul with a slow connection to the Internet. Is that all needed?
No. Do not use extra repos, then you won’t have that many updates.
And for the official updates (“patches”) from the update repo, so-called “delta rpms” are used, you only download the differences to the previous versions.
No, I did not say that, though admittedly I was not as clear as I might have been. Nothing has been brought in from any source other than the repo from which the existing file was from. i.e. if the file was from Packman the new file is still from Packman.
And neither “up” nor “patch” do that, unless you force it to, or enable “vendor change” in zypp.conf.
I neither forced anything, nor did I enable any vendor change (or anything else for that matter). I simply ran
:~ # zypper patch
Yes, LibreOffice has been updated to 4.3.6.2. What’s so strange about it?
What’s strange about it is that I did NOT run
:~ # zypper up
I only ran
:~ # zypper patch
No. Do not use extra repos, then you won’t have that many updates.
I wasn’t aware that the basic 5 would be considered “that many”.
In summary, my basic point is that I’m not running Tumbleweed. I’m not obsessed with state of the art. If I wanted to do that I would be using Tumbleweed, but I don’t. I just run plain vanilla OpenSUSE 13.2, and I just want to keep it up to date with needed patches, bugfixes and so on. When I do want to update or upgrade I know how to do that, but it seems that I don’t know how to do just what I want. I thought that was what “zypper patch” was for, but I guess I’m wrong (??)
Then everything is working as expected, no?
If packages in Packman are updated, “zypper up” will install those updates of course.
I neither forced anything, nor did I enable any vendor change (or anything else for that matter). I simply ran
:~ # zypper patch
Yes, and nothing switched the repo.
“zypper patch” will not install updates from Packman either.
But as already mentioned, “zypper up” and your desktop’s updater will.
What’s strange about it is that I did NOT run
:~ # zypper up
I only ran
:~ # zypper patch
The LibreOffice update was reased as official “patch” in the update repo, so it is of course installed by “zypper patch”.
I wasn’t aware that the basic 5 would be considered “that many”.
I didn’t say you shouldn’t have “that many” repos. I said you shouldn’t use any 3rd party repos, then you won’t have “that many” updates.
And Packman is a 3rd party repo. And it contains a lot of stuff that changes frequently.
If you use it, you shouldn’t complain that openSUSE requires so many updates.
Just a few days ago, ffmpeg was updated e.g., this requires a rebuild of basically all packages in the repo.
And you will get a lot of updates then of course.
In summary, my basic point is that I’m not running Tumbleweed. I’m not obsessed with state of the art. If I wanted to do that I would be using Tumbleweed, but I don’t. I just run plain vanilla OpenSUSE 13.2, and I just want to keep it up to date with needed patches, bugfixes and so on. When I do want to update or upgrade I know how to do that, but it seems that I don’t know how to do just what I want. I thought that was what “zypper patch” was for, but I guess I’m wrong (??)
Again, “zypper patch” only installs official updates from the update repo, i.e. all official openSUSE security and bugfixes.
To install all updates from all repos, run “zypper up”.
To switch to a different openSUSE release, run “zypper dup”.
I don’t understand where your confusion still lies…
And I don’t know what you understand with “needed patches, bugfixes and so on”, e.g. does this include Packman or not.
If you are not “obsessed with state of the art”, you probably should run only “zypper patch”, and only call “zypper up” or use your desktop’s updater sporadically. But, OTOH, updates in Packman might be security or important bug fixes as well, for the packages in Packman.
Oh, and that LibreOffice update was a bugfix update…
