On Mon, 7 Feb 2022 at 05:55, Alessandro Baggi
Hi,
I'm using AlmaLinux 8.5 on my workstation. Today running dnf update I noticed that it is trying to install new packages, This is the list of available upgrade:
cockpit cockpit-bridge cockpit-system cockpit-ws cryptsetup cryptsetup-libs dnf-plugins-core gnome-control-center gnome-control-center-filesystem google-chrome-stable java-1.8.0-openjdk-headless libipa_hbac libsmbclient libsss_autofs libsss_certmap libsss_idmap libsss_nss_idmap libsss_sudo libvirt-bash-completion libvirt-client libvirt-daemon libvirt-daemon-config-network libvirt-daemon-driver-interface libvirt-daemon-driver-network libvirt-daemon-driver-nodedev libvirt-daemon-driver-nwfilter libvirt-daemon-driver-qemu libvirt-daemon-driver-secret libvirt-daemon-driver-storage libvirt-daemon-driver-storage-core libvirt-daemon-driver-storage-disk libvirt-daemon-driver-storage-gluster libvirt-daemon-driver-storage-iscsi libvirt-daemon-driver-storage-iscsi-direct libvirt-daemon-driver-storage-logical libvirt-daemon-driver-storage-mpath libvirt-daemon-driver-storage-rbd libvirt-daemon-driver-storage-scsi libvirt-daemon-kvm libvirt-libs libwbclient ostree ostree-libs python3-dnf-plugins-core python3-rpm python3-sssdconfig rpm rpm-build rpm-build-libs rpm-libs rpm-plugin-selinux rpm-plugin-systemd-inhibit rpm-sign samba samba-client-libs samba-common samba-common-libs samba-common-tools samba-libs sos sssd sssd-ad sssd-client sssd-common sssd-common-pac sssd-ipa sssd-kcm sssd-krb5 sssd-krb5-common sssd-ldap sssd-nfs-idmap sssd-proxy tcpdump teamviewer tigervnc-license tigervnc-server-minimal vim-common vim-enhanced vim-filesystem vim-minimal vulkan-loader
This is followed by "Dependency Installation":
clevis jose jq libjose libluksmeta luksmeta python3-lxml python3-ptyprocess python3-webencodings tpm2-tools tracer-common
I checked if clevis and other packages are installed but I can't find them. So why it is trying to install new deps and packages?
That is weird. Do you have cockpit-storaged installed on the system? It looks like it suggests clevis-luks and that is what is causing it to get pulled into the system as upstream EL8 is supposed to treat suggests/recommends etc as depends. Why it is doing it now versus earlier updates I don't know. ``` # dnf repoquery --whatdepends clevis-luks Last metadata expiration check: 1:55:05 ago on Mon 07 Feb 2022 10:36:59 GMT. clevis-systemd-0:15-1.el8.x86_64 clevis-systemd-0:15-1.el8_5.1.x86_64 clevis-udisks2-0:15-1.el8.x86_64 clevis-udisks2-0:15-1.el8_5.1.x86_64 cockpit-storaged-0:251.1-1.el8.noarch stratisd-0:2.4.2-2.el8.x86_64 [root@xanadu ~]# rpm -qa | grep cockpit cockpit-ws-251.3-1.el8_5.x86_64 cockpit-251.3-1.el8_5.x86_64 cockpit-packagekit-251.1-1.el8.noarch cockpit-storaged-251.1-1.el8.noarch cockpit-system-251.3-1.el8_5.noarch cockpit-podman-39-1.module_el8.5.0+2613+1b78b731.noarch cockpit-bridge-251.3-1.el8_5.x86_64 ```
Thank you in advance.
_______________________________________________ AlmaLinux Users mailing list -- users@lists.almalinux.org To unsubscribe send an email to users-leave@lists.almalinux.org
-- Stephen J Smoogen. Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren