Installed packages to be REMOVED
-
From time to time I manually run:
pkg update; pkg upgrade
just to o see if there any packages to update
[root@pfSense~]$ pkg update; pkg upgrade Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... Fetching meta.txz: 100% 944 B 0.9kB/s 00:01 Fetching packagesite.txz: 100% 138 KiB 140.9kB/s 00:01 Processing entries: 100% pfSense repository update completed. 518 packages processed. All repositories are up to date. Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. Updating database digests format: 100% Checking for upgrades (9 candidates): 100% Processing candidates (9 candidates): 100% The following 3 package(s) will be affected (of 0 checked): Installed packages to be REMOVED: pfSense-2.4.4_3 bind-tools-9.12.2P1 Installed packages to be UPGRADED: pfSense-Status_Monitoring: 1.7.10 -> 1.7.11 [pfSense] Number of packages to be removed: 2 Number of packages to be upgraded: 1 The operation will free 39 MiB. 17 KiB to be downloaded. Proceed with this action? [y/N]: n
but this one looks like a system killer, right?
No extra repos, just pfSense. -
No idea what it's doing there, but I usually check via System - Package Manager. That way you not only get to see new packages at a glance, but there are links to release notes etc that you should ALWAYS read before blindly applying. Some users have asked for a dashboard widget that alerts on installed package updates but I don't think anything has been done there.
-
@Bismarck said in Installed packages to be REMOVED:
pfSense-2.4.4_3
Any idea, how I can check what is triggering pkg to remove it?
pkg update; pkg upgrade was always way more stable and safe installing updates as System - Package Manager, at least for me but this one scares me.
-
@KOM said in Installed packages to be REMOVED:
Some users have asked for a dashboard widget that alerts on installed package updates but I don't think anything has been done there
Not right now, but this (a dashboard widget ?! ) does show me when an update is available.
True : no mail notification.@KOM said in Installed packages to be REMOVED:
you should ALWAYS read before
Except for those who love to deal with new ( unknown ) bugs instead of the old ones.
@Bismarck said in Installed packages to be REMOVED:
Installed packages to be REMOVED:
pfSense-2.4.4_3I agree. That's ... strange.
Btw : I just ran the same commands :
[2.4.4-RELEASE][admin@pfsense.brit-hotel-fumel.net]/root: pkg upgrade Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. Checking for upgrades (1 candidates): 100% Processing candidates (1 candidates): 100% The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense-Status_Monitoring: 1.7.7 -> 1.7.11 [pfSense] Number of packages to be upgraded: 1 17 KiB to be downloaded. Proceed with this action? [y/N]: Y [1/1] Fetching pfSense-Status_Monitoring-1.7.11.txz: 100% 17 KiB 17.3kB/s 00:01 Checking integrity... done (0 conflicting) [1/1] Upgrading pfSense-Status_Monitoring from 1.7.7 to 1.7.11... [1/1] Extracting pfSense-Status_Monitoring-1.7.11: 100%
-
Yes but that monstrosity takes up wayyyy too much screen space. Just an alert or something would be enough, or perhaps have that widget have a collapse mode where it just shows you a summary: "7 packages installed, 2 have updates" or something, then you click it and it expands to show you the list with updates highlighted.
-
Just updating pfSense-Status_Monitoring, looks safe
[root@pfSense~]$ pkg install pfSense-Status_Monitoring Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. The following 1 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense-Status_Monitoring: 1.7.10 -> 1.7.11 [pfSense] Number of packages to be upgraded: 1 17 KiB to be downloaded. Proceed with this action? [y/N]: y [1/1] Fetching pfSense-Status_Monitoring-1.7.11.txz: 100% 17 KiB 17.3kB/s 00:01 Checking integrity... done (0 conflicting) [1/1] Upgrading pfSense-Status_Monitoring from 1.7.7 to 1.7.11... [1/1] Extracting pfSense-Status_Monitoring-1.7.11: 100%
and now pkg update ; pkg upgrade again too
[root@pfSense~]$ pkg update ; pkg upgrade Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. Updating database digests format: 100% Checking for upgrades (8 candidates): 100% Processing candidates (8 candidates): 100% Checking integrity... done (0 conflicting) Your packages are up to date.
-
If it's trying to remove the
pfSense
package then the pkg solver must believe something your installed packages or the pending upgrade has a conflict.You might do
pkg upgrade -f pfSense
to reinstall the meta package and then see what happens. -
@jimp said in Installed packages to be REMOVED:
pkg upgrade -f pfSense
Hi jimp, how safe is it to run this on a productive machine? At the moment all looks fine, maybe pkg had just a little hiccup.
Thanks.
-
That's just the meta-pkg, it doesn't do much on its own. It pulls in the other packages as dependencies.
This is all it contains:
[2.4.4-RELEASE][root@rose.lab.jimp.pw]/root: pkg info -l pfSense pfSense-2.4.4_3: /etc/version.patch /usr/local/share/licenses/pfSense-2.4.4_3/APACHE20 /usr/local/share/licenses/pfSense-2.4.4_3/LICENSE /usr/local/share/licenses/pfSense-2.4.4_3/catalog.mk
-
uhm 1.7.11 was my doing, a trivial patch to permit uppercase name for the tabs on status monitoring
https://github.com/pfsense/FreeBSD-ports/pull/662
idk but i don't think it can't be that
I just ran the same commands on my 2.4.4-p3 and i had same results of @Gertjan. so all fine here