Sample Header Ad - 728x90

Unix & Linux Stack Exchange

Q&A for users of Linux, FreeBSD and other Unix-like operating systems

Latest Questions

0 votes
1 answers
2535 views
upgrade to php 8.* version on centos 7.9
I have a Centos 7.9 with PHP 7.4.33 pre installed. followed this command steps for upgrading the php version to 8.1: sudo yum install -y https://rpms.remirepo.net/enterprise/remi-release-7.rpm sudo yum install -y yum-utils sudo yum-config-manager --enable remi-php81 sudo yum-config-manager --disable...
I have a Centos 7.9 with PHP 7.4.33 pre installed. followed this command steps for upgrading the php version to 8.1: sudo yum install -y https://rpms.remirepo.net/enterprise/remi-release-7.rpm sudo yum install -y yum-utils sudo yum-config-manager --enable remi-php81 sudo yum-config-manager --disable remi-php74 sudo yum install -y php php-common php-opcache php-mcrypt php-cli php-gd php-curl php-mysqlnd but at the end it returns: No package php available. No package php-common available. No package php-opcache available. No package php-mcrypt available. No package php-cli available. No package php-gd available. No package php-curl available. No package php-mysqlnd available. Error: Nothing to do retried with this: yum --disablerepo="*" --enablerepo="remi-php81" list available got same return. also tried: sudo yum clean all sudo yum update and: sudo yum install -y php81 php81-common php81-opcache php81-cli php81-gd php81-curl php81-mysqlnd Same... . what should i do? --------- Update: I have a Cpanel WHM on this server. in php version manager, i was able to change the version to 8. But what I want is 8.1 and it is not among the options.
Pooya Behravesh (101 rep)
Apr 3, 2023, 02:54 PM • Last activity: Aug 3, 2025, 04:08 AM
1 votes
1 answers
2230 views
Upgrading Linux Mint 17.3 KDE edition to 18.2 KDE in situ
Officially, upgrading the KDE version of Linux Mint 17.3 to 18 is [not supported][1], because "Linux Mint 18 KDE will use a new and different desktop called Plasma". I presume this means that the KDE4 to KDE5 upgrade process is not trivial. The official way to upgrade is to do a clean reinstall. I u...
Officially, upgrading the KDE version of Linux Mint 17.3 to 18 is not supported , because "Linux Mint 18 KDE will use a new and different desktop called Plasma". I presume this means that the KDE4 to KDE5 upgrade process is not trivial. The official way to upgrade is to do a clean reinstall. I use Linux Mint on my main (scientific computing) workstation, and would much rather not do a clean reinstall: following advice, my /home/ is not on a separate partition, I have several different (non-physical!) users installed, and the official installers just want to wipe everything and start again. I'd really much rather not. What I'd like to do is update all of the apt sources to point at the right place, do an apt-get update && apt-get dist-upgrade and go home for the evening. As it stands at the moment, quite a few things randomly break every time I do an apt-get update (at the last one, nvidia drivers, cuda, and xfce due to a change in dbus!). I _like_ the look of Plasma, and the live usb of 18.2 runs great on my computer. I _want to upgrade_ *without* wiping _everything_. This is far from an unreasonable request. I have't heard of anyone else doing this _successfully_ for KDE Mint 17.3, and I'd like to know if it's possible. mintupgrade certainly thinks not. I'd like to try. What happens if you just do something stupid, like sed -i 's/trusty/rosa/' /etc/apt/sources.list?
Landak (374 rep)
Jun 22, 2017, 02:33 PM • Last activity: Jul 31, 2025, 01:03 AM
0 votes
1 answers
26 views
Can't update CachyOS: failed to commit transaction (conflicting files) with linux-firmware-nvidia
Whenever I try to update my system for the past few months, I get the following errors: [![CachyOS Hello Update System][1]][1] ``` error: failed to commit transaction (conflicting files) linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad103 exists in filesystem linux-firmware-nvidia: /usr/lib/firmwa...
Whenever I try to update my system for the past few months, I get the following errors: ![CachyOS Hello Update System ][1]
error: failed to commit transaction (conflicting files)
linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad103 exists in filesystem
linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad104 exists in filesystem
linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad106 exists in filesystem
linux-firmware-nvidia: /usr/lib/firmware/nvidia/ad107 exists in filesystem
Errors occurred, no packages were upgraded.
--- I found some other answers suggesting that I need to overwrite it. So I tried the following:
sudo pacman -Syu --overwrite=/usr/lib/firmware/nvidia/*
But that didn't work. It said something about not finding the path event though the path seems like it's 100% correct? --- How can I fix this and actually update my system?
Shaun Roselt (237 rep)
Jul 30, 2025, 07:53 AM
3 votes
2 answers
2117 views
Can't change update settings on elementary OS
I can't update elementary OS, when I try to change the settings 'Install updates from', none of the check boxes will check, it stays like the following image. What should I do? ![enter image description here][1] [1]: https://i.sstatic.net/KM203.png
I can't update elementary OS, when I try to change the settings 'Install updates from', none of the check boxes will check, it stays like the following image. What should I do? enter image description here
Aaron (31 rep)
Oct 5, 2014, 04:24 AM • Last activity: Jul 25, 2025, 10:08 PM
0 votes
2 answers
4544 views
Centos 7 offline update
I want to upgrade my Centos version 7.8 to 7.9 or 8. But my system is not connected to the internet. And I can reach remotely with ssh and sftp to the this server. Is there a way to do this update remotely from cli? I will be glad if you help.
I want to upgrade my Centos version 7.8 to 7.9 or 8. But my system is not connected to the internet. And I can reach remotely with ssh and sftp to the this server. Is there a way to do this update remotely from cli? I will be glad if you help.
Can Atila (1 rep)
Jan 16, 2023, 06:50 PM • Last activity: Jul 25, 2025, 02:07 PM
2 votes
1 answers
3122 views
Upgrading Berkeley DB rpm in a Centos OS
I have a software which needs Berkeley DB 4.5 or above. But in my CentOS 5.11 x86_64 Server I have: * Package db4-4.3.29-10.el5_5.2.x86_64 already installed and latest version * Package db4-4.3.29-10.el5_5.2.i386 already installed and latest version How can I upgrade these rpm to a newer version? I...
I have a software which needs Berkeley DB 4.5 or above. But in my CentOS 5.11 x86_64 Server I have: * Package db4-4.3.29-10.el5_5.2.x86_64 already installed and latest version * Package db4-4.3.29-10.el5_5.2.i386 already installed and latest version How can I upgrade these rpm to a newer version? I tried to upgrade using Centos 6.6 rpm in this way: rpm -Uvh ftp://195.220.108.108/linux/centos/6.6/os/x86_64/Packages/db4-4.7.25-18.el6_4.i686.rpm but I receive this error: Retrieving ftp://195.220.108.108/linux/centos/6.6/os/x86_64/Packages/db4-4.7.25-18.el6_4.i686.rpm warning: /var/tmp/rpm-xfer.IKWqHE: Header V3 RSA/SHA1 signature: NOKEY, key ID c105b9de error: Failed dependencies: rpmlib(FileDigests) = 4.4.0 conflicts with pam-0.99.6.2-12.el5.i386 db4 >= 4.4.0 conflicts with pam-0.99.6.2-12.el5.x86_64 libdb-4.3.so is needed by (installed) subversion-1.6.11-12.el5_10.i386 libdb-4.3.so is needed by (installed) pam_ccreds-3-5.i386 libdb-4.3.so is needed by (installed) apr-util-1.2.7-11.el5_5.2.i386 libdb-4.3.so is needed by (installed) db4-devel-4.3.29-10.el5_5.2.i386 libdb_cxx-4.3.so is needed by (installed) db4-devel-4.3.29-10.el5_5.2.i386 I also tried to compile from source db-4.5.20.tar.gz. I compiled it with no problem, however my software is still seeing the Berkley DB preinstalled in rpm package db4-4.3.29. Any help please ?
gr68 (334 rep)
Jan 28, 2015, 04:01 PM • Last activity: Jul 24, 2025, 04:00 PM
2 votes
2 answers
499 views
how to update my kernel to Linux 6.6.12 in LinuxMint to make MT7902 work?
i did a search on google for "what version of linux uses theMediaTek 7902." The answer came back as: > The MediaTek Wi-Fi 6E MT7902 wireless network adapter is not natively > supported by the Linux kernel. However, the driver for the MT7902 was > added in the Linux 6.6.12 kernel series, and you can...
i did a search on google for "what version of linux uses theMediaTek 7902." The answer came back as: > The MediaTek Wi-Fi 6E MT7902 wireless network adapter is not natively > supported by the Linux kernel. However, the driver for the MT7902 was > added in the Linux 6.6.12 kernel series, and you can install these > recent kernels to enable support. Ubuntu recommends using its mainline > builds for this purpose. OK I installed LinuxMint 22.3 here as a dual boot. My Windows works with the mediatek but I have no idea how to add the Linux 6.6.12 kernel series. Any simple answers for a newbie?
Douglas Southcott (21 rep)
Jun 12, 2025, 09:07 AM • Last activity: Jul 23, 2025, 08:30 PM
4 votes
1 answers
185 views
After upgrading my Debian 11 system, Cinnamon freezes or shows lines on screen
Some weeks ago, I updated and upgraded my Debian 11 system. My desktop environment is Cinnamon. Now, very often, the entire desktop freezes or displays strange graphical artifacts (like lines or glitches), and the system feels extremely laggy. I have to restart to fix it. What can I do to solve this...
Some weeks ago, I updated and upgraded my Debian 11 system. My desktop environment is Cinnamon. Now, very often, the entire desktop freezes or displays strange graphical artifacts (like lines or glitches), and the system feels extremely laggy. I have to restart to fix it. What can I do to solve this problem?
Gin (43 rep)
Jul 19, 2025, 02:58 PM • Last activity: Jul 20, 2025, 02:01 PM
2 votes
2 answers
2069 views
Getting conflict errors when running yum update
I'm truing to run yum update, and keep getting errors about conflicts. I must have accidentally interrupted an update at some point, but I don't know when and how. I've tried —skip-broken, but it doesn't really help me, because I want to update the parts that now refuse to update. Also, I've tried "...
I'm truing to run yum update, and keep getting errors about conflicts. I must have accidentally interrupted an update at some point, but I don't know when and how. I've tried —skip-broken, but it doesn't really help me, because I want to update the parts that now refuse to update. Also, I've tried "yum remove util-linux", but then when I tried to re-install it, it didn't let me. Due to conflict errors much like what I'm getting now. (So I reverted to a backup volume, hence back on square 1). Any ideas of how I can solve this? yum update Loaded plugins: priorities, update-motd, upgrade-helper amzn-main/latest | 2.1 kB 00:00 amzn-updates/latest | 2.3 kB 00:00 Resolving Dependencies --> Running transaction check ---> Package aws-amitools-ec2.noarch 0:1.5.2-0.0.amzn1 will be updated ---> Package aws-amitools-ec2.noarch 0:1.5.3-0.0.amzn1 will be an update ---> Package aws-apitools-as.noarch 0:1.0.61.4-1.0.amzn1 will be updated ---> Package aws-apitools-as.noarch 0:1.0.61.5-1.0.amzn1 will be an update ---> Package aws-apitools-ec2.noarch 0:1.6.13.0-1.1.amzn1 will be updated ---> Package aws-apitools-ec2.noarch 0:1.7.1.0-1.2.amzn1 will be an update ---> Package aws-apitools-elb.noarch 0:1.0.34.0-1.0.amzn1 will be updated ---> Package aws-apitools-elb.noarch 0:1.0.35.0-1.0.amzn1 will be an update ---> Package aws-cli.noarch 0:1.3.6-1.0.amzn1 will be updated ---> Package aws-cli.noarch 0:1.3.24-1.0.amzn1 will be an update ---> Package cloud-init.noarch 0:0.5.15-77.amzn1 will be updated ---> Package cloud-init.noarch 0:0.7.2-7.20.amzn1 will be updated ---> Package cloud-init.noarch 0:0.7.2-7.27.amzn1 will be an update ---> Package curl.x86_64 0:7.35.0-2.42.amzn1 will be updated ---> Package curl.x86_64 0:7.36.0-2.44.amzn1 will be updated ---> Package curl.x86_64 0:7.36.0-2.45.amzn1 will be an update ---> Package cyrus-sasl.x86_64 0:2.1.23-13.13.amzn1 will be updated ---> Package cyrus-sasl.x86_64 0:2.1.23-13.15.amzn1 will be an update ---> Package cyrus-sasl-lib.x86_64 0:2.1.23-13.10.amzn1 will be updated ---> Package cyrus-sasl-lib.x86_64 0:2.1.23-13.13.amzn1 will be updated ---> Package cyrus-sasl-lib.x86_64 0:2.1.23-13.15.amzn1 will be an update ---> Package cyrus-sasl-plain.x86_64 0:2.1.23-13.10.amzn1 will be updated ---> Package cyrus-sasl-plain.x86_64 0:2.1.23-13.13.amzn1 will be updated ---> Package cyrus-sasl-plain.x86_64 0:2.1.23-13.15.amzn1 will be an update ---> Package ec2-net-utils.noarch 0:0.4-1.20.amzn1 will be updated ---> Package ec2-net-utils.noarch 0:0.4-1.22.amzn1 will be an update ---> Package ec2-utils.noarch 0:0.4-1.20.amzn1 will be updated ---> Package ec2-utils.noarch 0:0.4-1.22.amzn1 will be an update ---> Package elfutils-libelf.x86_64 0:0.152-1.12.amzn1 will be updated ---> Package elfutils-libelf.x86_64 0:0.157-2.14.amzn1 will be updated ---> Package elfutils-libelf.x86_64 0:0.158-3.16.amzn1 will be an update ---> Package file.x86_64 0:5.11-13.14.amzn1 will be updated ---> Package file.x86_64 0:5.11-13.16.amzn1 will be updated ---> Package file.x86_64 0:5.19-1.18.amzn1 will be an update ---> Package file-libs.x86_64 0:5.11-13.14.amzn1 will be updated ---> Package file-libs.x86_64 0:5.11-13.16.amzn1 will be updated ---> Package file-libs.x86_64 0:5.19-1.18.amzn1 will be an update ---> Package glibc.x86_64 0:2.12-1.132.45.amzn1 will be updated ---> Package glibc.x86_64 0:2.17-36.81.amzn1 will be updated ---> Package glibc.x86_64 0:2.17-55.84.amzn1 will be an update ---> Package glibc-common.x86_64 0:2.12-1.132.45.amzn1 will be updated ---> Package glibc-common.x86_64 0:2.17-36.81.amzn1 will be updated ---> Package glibc-common.x86_64 0:2.17-55.84.amzn1 will be an update ---> Package glibc-devel.x86_64 0:2.17-36.81.amzn1 will be updated ---> Package glibc-devel.x86_64 0:2.17-55.84.amzn1 will be an update ---> Package glibc-headers.x86_64 0:2.17-36.81.amzn1 will be updated ---> Package glibc-headers.x86_64 0:2.17-55.84.amzn1 will be an update ---> Package gnupg2.x86_64 0:2.0.22-1.24.amzn1 will be updated ---> Package gnupg2.x86_64 0:2.0.24-1.25.amzn1 will be an update ---> Package httpd.x86_64 0:2.2.27-1.2.amzn1 will be updated ---> Package httpd.x86_64 0:2.2.27-1.3.amzn1 will be an update ---> Package httpd-tools.x86_64 0:2.2.27-1.2.amzn1 will be updated ---> Package httpd-tools.x86_64 0:2.2.27-1.3.amzn1 will be an update ---> Package java-1.6.0-openjdk.x86_64 1:1.6.0.0-66.1.13.1.62.amzn1 will be updated ---> Package java-1.6.0-openjdk.x86_64 1:1.6.0.0-66.1.13.1.63.amzn1 will be updated ---> Package java-1.6.0-openjdk.x86_64 1:1.6.0.0-67.1.13.4.65.amzn1 will be an update ---> Package kernel.x86_64 0:3.10.48-55.140.amzn1 will be installed ---> Package kernel-headers.x86_64 0:3.10.35-43.137.amzn1 will be updated ---> Package kernel-headers.x86_64 0:3.10.48-55.140.amzn1 will be an update ---> Package libblkid.x86_64 0:2.17.2-13.17.amzn1 will be updated ---> Package libblkid.x86_64 0:2.23.2-6.21.amzn1 will be updated ---> Package libblkid.x86_64 0:2.23.2-16.22.amzn1 will be an update ---> Package libcurl.x86_64 0:7.35.0-2.42.amzn1 will be updated ---> Package libcurl.x86_64 0:7.36.0-2.44.amzn1 will be updated ---> Package libcurl.x86_64 0:7.36.0-2.45.amzn1 will be an update ---> Package libmount.x86_64 0:2.23.2-6.21.amzn1 will be updated ---> Package libmount.x86_64 0:2.23.2-16.22.amzn1 will be an update ---> Package libpwquality.x86_64 0:1.2.3-1.2.amzn1 will be updated ---> Package libpwquality.x86_64 0:1.2.3-1.5.amzn1 will be an update ---> Package libtasn1.x86_64 0:2.3-3.4.amzn1 will be updated ---> Package libtasn1.x86_64 0:2.3-6.6.amzn1 will be an update ---> Package libuuid.x86_64 0:2.17.2-13.17.amzn1 will be updated ---> Package libuuid.x86_64 0:2.23.2-6.21.amzn1 will be updated ---> Package libuuid.x86_64 0:2.23.2-16.22.amzn1 will be an update ---> Package libxml2.x86_64 0:2.9.1-1.1.28.amzn1 will be updated ---> Package libxml2.x86_64 0:2.9.1-1.1.29.amzn1 will be updated ---> Package libxml2.x86_64 0:2.9.1-1.1.31.amzn1 will be an update ---> Package mod_ssl.x86_64 1:2.2.27-1.2.amzn1 will be updated ---> Package mod_ssl.x86_64 1:2.2.27-1.3.amzn1 will be an update ---> Package mysql55.x86_64 0:5.5.34-1.40.amzn1 will be updated ---> Package mysql55.x86_64 0:5.5.36-1.44.amzn1 will be updated ---> Package mysql55.x86_64 0:5.5.38-1.0.amzn1 will be an update ---> Package mysql55-common.x86_64 0:5.5.34-1.40.amzn1 will be updated ---> Package mysql55-common.x86_64 0:5.5.36-1.44.amzn1 will be updated ---> Package mysql55-common.x86_64 0:5.5.38-1.0.amzn1 will be an update ---> Package mysql55-libs.x86_64 0:5.5.34-1.40.amzn1 will be updated ---> Package mysql55-libs.x86_64 0:5.5.36-1.44.amzn1 will be updated ---> Package mysql55-libs.x86_64 0:5.5.38-1.0.amzn1 will be an update ---> Package mysql55-server.x86_64 0:5.5.34-1.40.amzn1 will be updated ---> Package mysql55-server.x86_64 0:5.5.36-1.44.amzn1 will be updated ---> Package mysql55-server.x86_64 0:5.5.38-1.0.amzn1 will be an update ---> Package nspr.x86_64 0:4.10.2-1.19.amzn1 will be updated ---> Package nspr.x86_64 0:4.10.4-1.22.amzn1 will be an update ---> Package nss.x86_64 0:3.15.3-3.32.amzn1 will be updated ---> Package nss.x86_64 0:3.16.0-1.36.amzn1 will be an update ---> Package nss-softokn.x86_64 0:3.14.3-9.15.amzn1 will be updated ---> Package nss-softokn.x86_64 0:3.16.0-1.19.amzn1 will be an update ---> Package nss-softokn-freebl.x86_64 0:3.14.3-9.15.amzn1 will be updated ---> Package nss-softokn-freebl.x86_64 0:3.16.0-1.19.amzn1 will be an update ---> Package nss-sysinit.x86_64 0:3.15.3-3.32.amzn1 will be updated ---> Package nss-sysinit.x86_64 0:3.16.0-1.36.amzn1 will be an update ---> Package nss-tools.x86_64 0:3.15.3-3.32.amzn1 will be updated ---> Package nss-tools.x86_64 0:3.16.0-1.36.amzn1 will be an update ---> Package nss-util.x86_64 0:3.15.3-1.18.amzn1 will be updated ---> Package nss-util.x86_64 0:3.15.3-1.19.amzn1 will be updated ---> Package nss-util.x86_64 0:3.16.0-1.22.amzn1 will be an update ---> Package openssh.x86_64 0:6.2p2-7.40.amzn1 will be updated ---> Package openssh.x86_64 0:6.2p2-8.41.amzn1 will be an update ---> Package openssh-clients.x86_64 0:6.2p2-7.40.amzn1 will be updated ---> Package openssh-clients.x86_64 0:6.2p2-8.41.amzn1 will be an update ---> Package openssh-server.x86_64 0:6.2p2-7.40.amzn1 will be updated ---> Package openssh-server.x86_64 0:6.2p2-8.41.amzn1 will be an update ---> Package openssl.x86_64 1:1.0.1e-4.55.amzn1 will be updated ---> Package openssl.x86_64 1:1.0.1g-1.69.amzn1 will be updated ---> Package openssl.x86_64 1:1.0.1i-1.78.amzn1 will be an update ---> Package pam.x86_64 0:1.1.1-13.20.amzn1 will be updated ---> Package pam.x86_64 0:1.1.8-1.25.amzn1 will be updated ---> Package pam.x86_64 0:1.1.8-9.29.amzn1 will be an update ---> Package python-boto.noarch 0:2.27.0-1.0.amzn1 will be updated ---> Package python-boto.noarch 0:2.32.0-1.0.amzn1 will be an update ---> Package python-botocore.noarch 0:0.40.0-1.0.amzn1 will be updated ---> Package python-botocore.noarch 0:0.58.0-1.0.amzn1 will be an update ---> Package python-jmespath.noarch 0:0.3.1-1.0.amzn1 will be updated ---> Package python-jmespath.noarch 0:0.4.1-1.0.amzn1 will be an update ---> Package python-simplejson.x86_64 0:3.3.0-1.5.amzn1 will be updated ---> Package python-simplejson.x86_64 0:3.5.3-1.7.amzn1 will be an update ---> Package readline.x86_64 0:6.0-4.12.amzn1 will be updated ---> Package readline.x86_64 0:6.2-6.13.amzn1 will be updated ---> Package readline.x86_64 0:6.2-9.14.amzn1 will be an update ---> Package util-linux.x86_64 0:2.23.2-6.21.amzn1 will be updated ---> Package util-linux.x86_64 0:2.23.2-16.22.amzn1 will be obsoleting ---> Package util-linux-ng.x86_64 0:2.17.2-13.17.amzn1 will be obsoleted --> Processing Conflict: glibc-2.17-55.84.amzn1.x86_64 conflicts audit Processing Conflict: util-linux-2.23.2-16.22.amzn1.x86_64 conflicts coreutils Processing Conflict: util-linux-2.23.2-16.22.amzn1.x86_64 conflicts sysvinit Processing Conflict: util-linux-2.23.2-16.22.amzn1.x86_64 conflicts sysvinit Finished Dependency Resolution --> Running transaction check ---> Package glibc.x86_64 0:2.17-36.81.amzn1 will be updated ---> Package glibc.x86_64 0:2.17-36.81.amzn1 will be updated ---> Package kernel.x86_64 0:3.4.76-65.111.amzn1 will be erased --> Processing Conflict: glibc-2.17-55.84.amzn1.x86_64 conflicts audit Processing Conflict: util-linux-2.23.2-16.22.amzn1.x86_64 conflicts coreutils Processing Conflict: util-linux-2.23.2-16.22.amzn1.x86_64 conflicts sysvinit Processing Conflict: util-linux-2.23.2-16.22.amzn1.x86_64 conflicts sysvinit Finished Dependency Resolution Error: util-linux conflicts with coreutils-8.4-31.20.amzn1.x86_64 Error: util-linux conflicts with sysvinit-2.87-4.dsf.10.amzn1.x86_64 Error: util-linux conflicts with upstart-0.6.5-12.10.amzn1.x86_64 Error: glibc conflicts with audit-2.2-2.17.amzn1.x86_64 You could try using --skip-broken to work around the problem ** Found 113 pre-existing rpmdb problem(s), 'yum check' output follows: apr-1.5.0-2.11.amzn1.x86_64 is a duplicate with apr-1.4.6-1.10.amzn1.x86_64 audit-2.3.2-3.19.amzn1.x86_64 is a duplicate with audit-2.2-2.17.amzn1.x86_64 audit-libs-2.3.2-3.19.amzn1.x86_64 is a duplicate with audit-libs-2.2-2.17.amzn1.x86_64 ca-certificates-2013.1.94-65.0.9.amzn1.noarch is a duplicate with ca-certificates-2012.1.95-3.12.amzn1.noarch cloud-init-0.7.2-7.20.amzn1.noarch is a duplicate with cloud-init-0.5.15-77.amzn1.noarch coreutils-8.21-13.31.amzn1.x86_64 is a duplicate with coreutils-8.4-31.20.amzn1.x86_64 cronie-anacron-1.4.4-7.5.amzn1.x86_64 has missing requires of cronie = ('0', '1.4.4', '7.5.amzn1') cronie-anacron-1.4.4-12.6.amzn1.x86_64 is a duplicate with cronie-anacron-1.4.4-7.5.amzn1.x86_64 cryptsetup-1.6.2-2.11.amzn1.x86_64 is a duplicate with cryptsetup-1.5.1-1.3.amzn1.x86_64 cryptsetup-libs-1.6.2-2.11.amzn1.x86_64 is a duplicate with cryptsetup-libs-1.5.1-1.3.amzn1.x86_64 curl-7.36.0-2.44.amzn1.x86_64 is a duplicate with curl-7.35.0-2.42.amzn1.x86_64 cyrus-sasl-lib-2.1.23-13.13.amzn1.x86_64 is a duplicate with cyrus-sasl-lib-2.1.23-13.10.amzn1.x86_64 cyrus-sasl-plain-2.1.23-13.13.amzn1.x86_64 is a duplicate with cyrus-sasl-plain-2.1.23-13.10.amzn1.x86_64 db4-4.7.25-18.11.amzn1.x86_64 is a duplicate with db4-4.7.25-17.10.amzn1.x86_64 db4-utils-4.7.25-18.11.amzn1.x86_64 is a duplicate with db4-utils-4.7.25-17.10.amzn1.x86_64 1:dbus-1.6.12-5.25.amzn1.x86_64 is a duplicate with 1:dbus-1.2.24-7.16.amzn1.x86_64 1:dbus-libs-1.6.12-5.25.amzn1.x86_64 is a duplicate with 1:dbus-libs-1.2.24-7.16.amzn1.x86_64 dejavu-fonts-common-2.33-5.8.amzn1.noarch is a duplicate with dejavu-fonts-common-2.30-2.4.amzn1.noarch dejavu-sans-fonts-2.33-5.8.amzn1.noarch is a duplicate with dejavu-sans-fonts-2.30-2.4.amzn1.noarch dejavu-serif-fonts-2.33-5.8.amzn1.noarch is a duplicate with dejavu-serif-fonts-2.30-2.4.amzn1.noarch 12:dhclient-4.1.1-38.P1.19.amzn1.x86_64 is a duplicate with 12:dhclient-4.1.1-34.P1.18.amzn1.x86_64 12:dhcp-common-4.1.1-38.P1.19.amzn1.x86_64 is a duplicate with 12:dhcp-common-4.1.1-34.P1.18.amzn1.x86_64 e2fsprogs-libs-1.42.8-2.29.amzn1.x86_64 is a duplicate with e2fsprogs-libs-1.42.3-3.17.amzn1.x86_64 elfutils-libelf-0.157-2.14.amzn1.x86_64 is a duplicate with elfutils-libelf-0.152-1.12.amzn1.x86_64 file-5.11-13.16.amzn1.x86_64 is a duplicate with file-5.11-13.14.amzn1.x86_64 file-libs-5.11-13.16.amzn1.x86_64 is a duplicate with file-libs-5.11-13.14.amzn1.x86_64 glib2-2.36.3-2.14.amzn1.x86_64 is a duplicate with glib2-2.22.5-7.11.amzn1.x86_64 glibc-2.17-36.81.amzn1.x86_64 has installed conflicts audit < ('0', '2.3.0', None): audit-2.2-2.17.amzn1.x86_64 glibc-2.17-36.81.amzn1.x86_64 is a duplicate with glibc-2.12-1.132.45.amzn1.x86_64 glibc-common-2.17-36.81.amzn1.x86_64 is a duplicate with glibc-common-2.12-1.132.45.amzn1.x86_64 groff-1.22.2-6.10.amzn1.x86_64 is a duplicate with groff-1.18.1.4-21.7.amzn1.x86_64 groff-base-1.22.2-6.10.amzn1.x86_64 has installed conflicts groff < ('0', '1.22.2', None): groff-1.18.1.4-21.7.amzn1.x86_64 grubby-7.0.15-5.7.amzn1.x86_64 is a duplicate with grubby-7.0.15-3.6.amzn1.x86_64 gzip-1.5-4.16.amzn1.x86_64 is a duplicate with gzip-1.3.12-19.9.amzn1.x86_64 hwdata-0.233-9.1.16.amzn1.noarch is a duplicate with hwdata-0.233-7.9.14.amzn1.noarch info-5.1-1.9.amzn1.x86_64 is a duplicate with info-4.13a-8.8.amzn1.x86_64 initscripts-9.03.40-2.29.amzn1.x86_64 has installed conflicts util-linux-ng < ('0', '2.23', None): util-linux-ng-2.17.2-13.17.amzn1.x86_64 initscripts-9.03.40-2.29.amzn1.x86_64 has installed conflicts util-linux < ('0', '2.23', None): util-linux-ng-2.17.2-13.17.amzn1.x86_64 initscripts-9.03.40-2.29.amzn1.x86_64 is a duplicate with initscripts-9.03.38-1.22.amzn1.x86_64 1:java-1.6.0-openjdk-1.6.0.0-66.1.13.1.63.amzn1.x86_64 is a duplicate with 1:java-1.6.0-openjdk-1.6.0.0-66.1.13.1.62.amzn1.x86_64 kpartx-0.4.9-72.7.amzn1.x86_64 is a duplicate with kpartx-0.4.9-64.6.amzn1.x86_64 ksh-20120801-10.12.amzn1.x86_64 is a duplicate with ksh-20100621-19.11.amzn1.x86_64 libblkid-2.23.2-6.21.amzn1.x86_64 is a duplicate with libblkid-2.17.2-13.17.amzn1.x86_64 libcom_err-1.42.8-2.29.amzn1.x86_64 is a duplicate with libcom_err-1.42.3-3.17.amzn1.x86_64 libcurl-7.36.0-2.44.amzn1.x86_64 is a duplicate with libcurl-7.35.0-2.42.amzn1.x86_64 libgcrypt-1.5.3-1.14.amzn1.x86_64 is a duplicate with libgcrypt-1.4.5-9.12.amzn1.x86_64 14:libpcap-1.4.0-1.20130826git2dbcaa1.10.amzn1.x86_64 is a duplicate with 14:libpcap-1.0.0-6.20091201git117cb5.9.amzn1.x86_64 libss-1.42.8-2.29.amzn1.x86_64 is a duplicate with libss-1.42.3-3.17.amzn1.x86_64 libtool-ltdl-2.4.2-18.4.8.2.21.amzn1.x86_64 is a duplicate with libtool-ltdl-2.2.10-4.6.3.14.amzn1.x86_64 libudev-173-4.13.amzn1.x86_64 is a duplicate with libudev-173-4.12.amzn1.x86_64 libuuid-2.23.2-6.21.amzn1.x86_64 is a duplicate with libuuid-2.17.2-13.17.amzn1.x86_64 libxml2-2.9.1-1.1.29.amzn1.x86_64 is a duplicate with libxml2-2.9.1-1.1.28.amzn1.x86_64 libxslt-1.1.28-3.8.amzn1.x86_64 is a duplicate with libxslt-1.1.26-2.7.amzn1.x86_64 libyaml-0.1.6-1.6.amzn1.x86_64 is a duplicate with libyaml-0.1.4-6.5.amzn1.x86_64 mdadm-3.2.6-7.29.amzn1.x86_64 is a duplicate with mdadm-3.2.5-4.23.amzn1.x86_64 mysql-5.5-1.6.amzn1.noarch is a duplicate with mysql-5.5-1.3.amzn1.noarch mysql-server-5.5-1.6.amzn1.noarch is a duplicate with mysql-server-5.5-1.3.amzn1.noarch mysql55-5.5.36-1.44.amzn1.x86_64 is a duplicate with mysql55-5.5.34-1.40.amzn1.x86_64 mysql55-common-5.5.36-1.44.amzn1.x86_64 is a duplicate with mysql55-common-5.5.34-1.40.amzn1.x86_64 mysql55-libs-5.5.36-1.44.amzn1.x86_64 is a duplicate with mysql55-libs-5.5.34-1.40.amzn1.x86_64 mysql55-server-5.5.36-1.44.amzn1.x86_64 is a duplicate with mysql55-server-5.5.34-1.40.amzn1.x86_64 nss-util-3.15.3-1.19.amzn1.x86_64 is a duplicate with nss-util-3.15.3-1.18.amzn1.x86_64 numactl-2.0.7-8.11.amzn1.x86_64 is a duplicate with numactl-2.0.7-6.10.amzn1.x86_64 1:openssl-1.0.1g-1.69.amzn1.x86_64 is a duplicate with 1:openssl-1.0.1e-4.55.amzn1.x86_64 pam-1.1.8-1.25.amzn1.x86_64 is a duplicate with pam-1.1.1-13.20.amzn1.x86_64 4:perl-5.16.3-280.36.amzn1.x86_64 is a duplicate with 4:perl-5.10.1-136.21.amzn1.x86_64 perl-DBD-MySQL-4.023-2.16.amzn1.x86_64 is a duplicate with perl-DBD-MySQL-4.020-2.8.amzn1.x86_64 perl-DBI-1.627-1.7.amzn1.x86_64 is a duplicate with perl-DBI-1.609-4.4.amzn1.x86_64 1:perl-Digest-SHA-5.85-1.4.amzn1.x86_64 is a duplicate with 1:perl-Digest-SHA-5.47-136.21.amzn1.x86_64 perl-Digest-SHA1-2.13-7.6.amzn1.x86_64 is a duplicate with perl-Digest-SHA1-2.12-2.4.amzn1.x86_64 perl-Encode-Locale-1.03-4.7.amzn1.noarch is a duplicate with perl-Encode-Locale-1.02-3.1.amzn1.noarch perl-HTML-Tagset-3.20-14.6.amzn1.noarch is a duplicate with perl-HTML-Tagset-3.20-4.4.amzn1.noarch perl-LWP-MediaTypes-6.02-1.8.amzn1.noarch is a duplicate with perl-LWP-MediaTypes-6.01-3.3.amzn1.noarch 1:perl-Module-Pluggable-4.8-1.2.amzn1.noarch is a duplicate with 1:perl-Module-Pluggable-3.90-136.21.amzn1.x86_64 perl-Net-LibIDN-0.12-13.5.amzn1.x86_64 is a duplicate with perl-Net-LibIDN-0.12-3.2.amzn1.x86_64 1:perl-Pod-Escapes-1.04-280.36.amzn1.noarch is a duplicate with 1:perl-Pod-Escapes-1.04-136.21.amzn1.x86_64 1:perl-Pod-Simple-3.28-3.5.amzn1.noarch is a duplicate with 1:perl-Pod-Simple-3.13-136.21.amzn1.x86_64 1:perl-TimeDate-2.30-1.6.amzn1.noarch is a duplicate with 1:perl-TimeDate-1.16-11.1.4.amzn1.noarch perl-URI-1.60-8.7.amzn1.noarch is a duplicate with perl-URI-1.40-2.5.amzn1.noarch perl-XML-NamespaceSupport-1.11-9.7.amzn1.noarch is a duplicate with perl-XML-NamespaceSupport-1.10-3.5.amzn1.noarch 4:perl-libs-5.16.3-280.36.amzn1.x86_64 is a duplicate with 4:perl-libs-5.10.1-136.21.amzn1.x86_64 perl-podlators-2.5.1-2.7.amzn1.noarch has installed conflicts perl < ('4', '5.16.1', '234'): 4:perl-5.10.1-136.21.amzn1.x86_64 3:perl-version-0.99.02-2.5.amzn1.x86_64 is a duplicate with 3:perl-version-0.77-136.21.amzn1.x86_64 psmisc-22.20-6.11.amzn1.x86_64 is a duplicate with psmisc-22.6-15.8.amzn1.x86_64 pyliblzma-0.5.3-3.6.amzn1.x86_64 is a duplicate with pyliblzma-0.5.3-3.4.amzn1.x86_64 python26-2.6.9-1.46.amzn1.x86_64 is a duplicate with python26-2.6.9-1.43.amzn1.x86_64 python26-libs-2.6.9-1.46.amzn1.x86_64 is a duplicate with python26-libs-2.6.9-1.43.amzn1.x86_64 readline-6.2-6.13.amzn1.x86_64 is a duplicate with readline-6.0-4.12.amzn1.x86_64 rpm-4.11.2-2.54.amzn1.x86_64 is a duplicate with rpm-4.11.1-3.49.amzn1.x86_64 rpm-build-libs-4.11.2-2.54.amzn1.x86_64 is a duplicate with rpm-build-libs-4.11.1-3.49.amzn1.x86_64 rpm-libs-4.11.2-2.54.amzn1.x86_64 is a duplicate with rpm-libs-4.11.1-3.49.amzn1.x86_64 rpm-python-4.11.2-2.54.amzn1.x86_64 is a duplicate with rpm-python-4.11.1-3.49.amzn1.x86_64 rsyslog-5.8.10-8.25.amzn1.x86_64 is a duplicate with rsyslog-5.8.10-7.24.amzn1.x86_64 sqlite-3.7.17-1.9.amzn1.x86_64 is a duplicate with sqlite-3.6.20-1.8.amzn1.x86_64 system-release-2014.03-2.0.noarch is a duplicate with system-release-2013.09-1.0.noarch sysvinit-2.87-5.dsf.14.amzn1.x86_64 has installed conflicts util-linux < ('0', '2.23.2', None): util-linux-ng-2.17.2-13.17.amzn1.x86_64 sysvinit-2.87-5.dsf.14.amzn1.x86_64 is a duplicate with sysvinit-2.87-4.dsf.10.amzn1.x86_64 tcp_wrappers-7.6-75.11.amzn1.x86_64 is a duplicate with tcp_wrappers-7.6-57.9.amzn1.x86_64 tcp_wrappers-libs-7.6-75.11.amzn1.x86_64 is a duplicate with tcp_wrappers-libs-7.6-57.9.amzn1.x86_64 tzdata-2013i-2.23.amzn1.noarch is a duplicate with tzdata-2013c-2.18.amzn1.noarch tzdata-java-2013i-2.23.amzn1.noarch is a duplicate with tzdata-java-2013c-2.18.amzn1.noarch udev-173-4.13.amzn1.x86_64 is a duplicate with udev-173-4.12.amzn1.x86_64 upstart-0.6.5-13.3.13.amzn1.x86_64 is a duplicate with upstart-0.6.5-12.10.amzn1.x86_64 util-linux-2.23.2-6.21.amzn1.x86_64 has installed conflicts coreutils < ('0', '8.20', None): coreutils-8.4-31.20.amzn1.x86_64 util-linux-2.23.2-6.21.amzn1.x86_64 has installed conflicts sysvinit < ('0', '2.87', '5'): upstart-0.6.5-12.10.amzn1.x86_64, sysvinit-2.87-4.dsf.10.amzn1.x86_64 2:vim-common-7.4.027-2.28.amzn1.x86_64 is a duplicate with 2:vim-common-7.2.411-1.8.17.amzn1.x86_64 2:vim-minimal-7.4.027-2.28.amzn1.x86_64 is a duplicate with 2:vim-minimal-7.2.411-1.8.17.amzn1.x86_64 xz-5.1.2-5alpha.10.amzn1.x86_64 is a duplicate with xz-4.999.9-0.3.beta.20091007git.8.amzn1.x86_64 xz-libs-5.1.2-5alpha.10.amzn1.x86_64 is a duplicate with xz-libs-4.999.9-0.3.beta.20091007git.8.amzn1.x86_64 xz-lzma-compat-5.1.2-5alpha.10.amzn1.x86_64 is a duplicate with xz-lzma-compat-4.999.9-0.3.beta.20091007git.8.amzn1.x86_64 yum-3.4.3-137.51.amzn1.noarch is a duplicate with yum-3.4.3-111.46.amzn1.noarch yum-plugin-priorities-1.1.31-18.17.amzn1.noarch is a duplicate with yum-plugin-priorities-1.1.31-17.16.amzn1.noarch yum-plugin-upgrade-helper-1.1.31-18.17.amzn1.noarch is a duplicate with yum-plugin-upgrade-helper-1.1.31-17.16.amzn1.noarch
Paolo (209 rep)
Aug 10, 2014, 12:43 PM • Last activity: Jul 18, 2025, 01:01 AM
1 votes
1 answers
76 views
do-release-upgrade on Ubuntu 18.04 is blocked
I’m trying to move my device from Ubuntu 18.04.6 LTS to 20.04. The first `sudo do-release-upgrade` was interrupted when my Internet died. Ever since, re-running it stops with “Please install all available updates for your release before upgrading.” **Environment** * Board: NVIDIA Jetson Nano * Curre...
I’m trying to move my device from Ubuntu 18.04.6 LTS to 20.04. The first sudo do-release-upgrade was interrupted when my Internet died. Ever since, re-running it stops with “Please install all available updates for your release before upgrading.” **Environment** * Board: NVIDIA Jetson Nano * Current OS: Ubuntu 18.04.6 LTS (bionic) **What I tried** 1. Ran sudo do-release-upgrade, but cancelled midway due to internet issues. 2. Re-ran the command → “Please install all available updates for your release before upgrading.” 3. Tried to bring the system fully up to date: ```bash sudo apt update sudo apt full-upgrade -y Output ends with: 0 upgraded, 0 newly installed, 0 to remove and 1965 not upgraded. **Question** How can I remove the already downloaded updates and any partial upgrade state left by the cancelled run?
iamM (11 rep)
Jul 9, 2025, 10:58 AM • Last activity: Jul 9, 2025, 11:13 AM
0 votes
0 answers
16 views
Upgraded k8 worker node from ubuntu 20.04 to 22.04. DNS resolution inside pods doesn’t work & pods keep crashing/restarting. openebs also crashed
We are facing the issue. Here I mentioned our setup. We have 5 clusters like application clustes, ingestion clusters, MySQL clusters, file server clusters. Each clusters working with 2 masters and rest are worker Os upgrade are going cluster wise.ubuntu os upgrade went smoothly but when we bring the...
We are facing the issue. Here I mentioned our setup. We have 5 clusters like application clustes, ingestion clusters, MySQL clusters, file server clusters. Each clusters working with 2 masters and rest are worker Os upgrade are going cluster wise.ubuntu os upgrade went smoothly but when we bring the pods we are facing issue , specially in statefull set pods Example in ingestion clusters we have 11 instances in that 11 , 2 masters and rest workers, Pods that are running in instances are like kafkatls,Cassandra, wso2, proxysql In some instances we can able to bring up the pods, but when try bring up the pods from another instances from same clusters some of dependency pods frequently restarting and went crashlookback off Note: we just change the iptable settings before upgrading like we manually set iptables legacy to prevent upgrade to nftables Kindly guide us on this if need I will give additional information
Ajmeer Hussain (1 rep)
Jul 9, 2025, 04:51 AM • Last activity: Jul 9, 2025, 05:44 AM
0 votes
1 answers
92 views
Upgraded k8 worker node from ubuntu 20.04 to 22.04. DNS resolution/networking inside pods doesn’t work & pods keep crashing/restarting
I have a k8 cluster based on Ubuntu 20.04 1 master and 3 worker nodes. I drained one of the worker node. Put kubectl,iptables, kubeadm, kubelet & containerd packages on hold. OS upgrade to 22.04, went smooth, but after upgrade pods (kube-system daemon-sets) kept crashing. One of the issue I found is...
I have a k8 cluster based on Ubuntu 20.04 1 master and 3 worker nodes. I drained one of the worker node. Put kubectl,iptables, kubeadm, kubelet & containerd packages on hold. OS upgrade to 22.04, went smooth, but after upgrade pods (kube-system daemon-sets) kept crashing. One of the issue I found is that DNS resolution is not working inside pods residing on upgraded node. When I revert back to ubuntu 20.04 everything works fine. Anyone help/suggestion please
Muhammad Saeed (31 rep)
Mar 2, 2025, 02:50 PM • Last activity: Jul 8, 2025, 08:13 PM
11 votes
3 answers
1568 views
What is the purpose of running `apt-get upgrade` then `full-upgrade` when upgrading to a new Debian release?
The [Debian Upgrade guide from the Debian Wiki][1], in two different places, says to run these commands: $ sudo apt-get upgrade $ sudo apt-get full-upgrade What is the purpose of running both? Doesn't `full-upgrade` do everything that `upgrade` does? [1]: https://wiki.debian.org/DebianUpgrade
The Debian Upgrade guide from the Debian Wiki , in two different places, says to run these commands: $ sudo apt-get upgrade $ sudo apt-get full-upgrade What is the purpose of running both? Doesn't full-upgrade do everything that upgrade does?
kj7rrv (217 rep)
Jun 29, 2025, 09:49 PM • Last activity: Jun 30, 2025, 09:24 AM
1 votes
1 answers
6338 views
Signature from "TNE <tne@garudalinux.org>" is unknown trust - Invalid or Corrupted package
While running `pacman -Syu` After "(8/8) checking package integrity" I'm facing the following issue with these packages: ``` error: 7-zip: signature from "TNE " is unknown trust :: File /var/cache/pacman/pkg/7-zip-23.01-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature))...
While running pacman -Syu After "(8/8) checking package integrity" I'm facing the following issue with these packages:
error: 7-zip: signature from "TNE " is unknown trust
:: File /var/cache/pacman/pkg/7-zip-23.01-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: brave-bin: signature from "TNE " is unknown trust
:: File /var/cache/pacman/pkg/brave-bin-1:1.52.126-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: pamac-aur: signature from "TNE " is unknown trust
:: File /var/cache/pacman/pkg/pamac-aur-11.0.1-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: spotify: signature from "TNE " is unknown trust
:: File /var/cache/pacman/pkg/spotify-1:1.2.13.661-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: visual-studio-code-bin: signature from "TNE " is unknown trust
:: File /var/cache/pacman/pkg/visual-studio-code-bin-1.79.2-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: yay: signature from "TNE " is unknown trust
:: File /var/cache/pacman/pkg/yay-12.1.0-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: zoom: signature from "TNE " is unknown trust
:: File /var/cache/pacman/pkg/zoom-5.15.0-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.
So far, I've tried running this (without success): - sudo pacman -S archlinux-keyring | pacman -Su - pacman -Sy archlinux-keyring | pacman-key --refresh-keys - `pacman-key --delete 91BD8815FE0040FA7FF5D68754C28F4FF5A1A949 | pacman-key --populate archlinux` - `pacman-key --delete D6C9442437365605 | pacman-key --populate archlinux` - sudo pacman -Sc - sudo pacman -Fy
Lucas_Guerra (51 rep)
Jun 26, 2023, 04:25 AM • Last activity: Jun 29, 2025, 03:34 PM
0 votes
1 answers
123 views
In performing an update on F-41, the following conflicts from the repositories were reported. What steps can I take to resolve them...if any?
###### Problem 1: ```none installed package libcurl-minimal-8.9.1-2.fc41.x86_64 conflicts with libcurl(x86-64) provided by libcurl-8.9.1-2.fc41.x86_64 from fedora - package dnf5-plugin-automatic-5.2.6.2-1.fc41.x86_64 from fedora requires libcurl-full(x86-64), but none of the providers can be install...
###### Problem 1:
installed package libcurl-minimal-8.9.1-2.fc41.x86_64 conflicts with libcurl(x86-64) provided by libcurl-8.9.1-2.fc41.x86_64 from fedora
  - package dnf5-plugin-automatic-5.2.6.2-1.fc41.x86_64 from fedora requires libcurl-full(x86-64), but none of the providers can be installed
  - cannot install the best update candidate for package libcurl-minimal-8.9.1-2.fc41.x86_64
  - cannot install the best update candidate for package dnf-automatic-4.21.1-1.fc41.noarch
 Problem 2: problem with installed package
  - installed package libcurl-minimal-8.9.1-2.fc41.x86_64 conflicts with libcurl(x86-64) provided by libcurl-8.9.1-2.fc41.x86_64 from fedora
  - package libcurl-minimal-8.9.1-2.fc41.x86_64 from fedora conflicts with libcurl(x86-64) provided by libcurl-8.9.1-2.fc41.x86_64 from fedora
  - package dnf5-plugin-automatic-5.2.6.2-1.fc41.x86_64 from fedora requires libcurl-full(x86-64), but none of the providers can be installed
  - problem with installed package
  - installed package dnf-automatic-4.21.1-1.fc41.noarch requires python3-dnf = 4.21.1-1.fc41, but none of the providers can be installed
  - package dnf-automatic-4.21.1-1.fc41.noarch from fedora requires python3-dnf = 4.21.1-1.fc41, but none of the providers can be installed
  - cannot install both python3-dnf-4.21.1-2.fc41.noarch from updates and python3-dnf-4.21.1-1.fc41.noarch from @System
  - cannot install both python3-dnf-4.21.1-2.fc41.noarch from updates and python3-dnf-4.21.1-1.fc41.noarch from fedora
  - cannot install the best update candidate for package python3-dnf-4.21.1-1.fc41.noarch
###### Update: The issue with the repositories was resolved by Dnfdragora. I set the program on "To Update" and two selections were identified: update of Python3 and libcurl-minimal. The first was updated and the second removed from the system. I performed a CLI dnf-update check which showed no further conflicts. Hope this helps others.
afrothetics (101 rep)
Nov 6, 2024, 05:09 AM • Last activity: Jun 24, 2025, 10:56 AM
0 votes
1 answers
552 views
Exclude certain packages from upgrading while upgrading everything else in Debian
I use Debian Sid, and this one package, Firefox, has an update with a grave bug found with `apt-listbugs`. I want to exclude that package from upgrading while upgrading everything else. There is a way to do this, but it is tedious with copy and pasting certain packages to upgrade and leaving some pa...
I use Debian Sid, and this one package, Firefox, has an update with a grave bug found with apt-listbugs. I want to exclude that package from upgrading while upgrading everything else. There is a way to do this, but it is tedious with copy and pasting certain packages to upgrade and leaving some packages out. How can I exclude certain packages from upgrading with a single command?
horsey_guy (421 rep)
Jun 21, 2024, 03:19 AM • Last activity: Jun 16, 2025, 07:00 AM
4 votes
1 answers
342 views
Arch Linux Live System Update?
Is there a way to update the live system of Arch Linux? The reason I am asking this is because I absolutely need the newest version of `archinstall`, which currently is 3.0.8 and the current Arch ISO `archlinux-2025.06.01-x86_64.iso` only has version 3.0.7. Executing `pacman -Syu` in order to update...
Is there a way to update the live system of Arch Linux? The reason I am asking this is because I absolutely need the newest version of archinstall, which currently is 3.0.8 and the current Arch ISO archlinux-2025.06.01-x86_64.iso only has version 3.0.7. Executing pacman -Syu in order to update all sources results in errors "could not extract ...tar.gz (Write failed)" which I interpret as not being able to update the live system (educated guess). Now, the next Arch ISO will be the one for 1st of July, but me being impatient would like to just bring all the necessary packages up-to-date and then run archinstall. Why do I need the current archinstall in at least version 3.0.8? Due to an error with a VirtualBox VM + enabled 3D acceleration, and a missing file xf86-video-vmware, it is not possible to install Arch with archinstall. Apparently, this error has been resolved in version 3.0.8.
Socrates (143 rep)
Jun 14, 2025, 09:55 PM • Last activity: Jun 15, 2025, 10:50 AM
0 votes
1 answers
30 views
openSUSE 15.6 sysctl pointing to itself
I have just run ``zypper up`` on a openSUSE 15.6 computer and the installation of the new kernel says ``dracut-install error: /sbin/sysctl is pointing to itself`` and indeed this symbolic link is a loop: ``` king:~ # l /sbin/sysctl lrwxrwxrwx 1 root root 12 Feb 21 15:59 /sbin/sysctl -> /sbin/sysctl...
I have just run `zypper up on a openSUSE 15.6 computer and the installation of the new kernel says dracut-install error: /sbin/sysctl is pointing to itself` and indeed this symbolic link is a loop:
king:~ # l /sbin/sysctl
lrwxrwxrwx 1 root root 12 Feb 21 15:59 /sbin/sysctl -> /sbin/sysctl
~> uname -a
Linux king 6.4.0-150600.23.50-default #1 SMP PREEMPT_DYNAMIC Fri May  9 22:09:52 UTC 2025 (dee422c) x86_64 x86_64 x86_64 GNU/Linux
(I have two other openSUSE 15.6 computers where `/sbin/sysctl` is a elf 64-bit binary of Feb 21 same timestamp which is 27288 bytes in size). Do I need to repair this? by copying the binaries?
R. J. Mathar (121 rep)
Jun 12, 2025, 12:15 PM • Last activity: Jun 12, 2025, 07:12 PM
0 votes
1 answers
2639 views
Frequent crashes after update to Fedora 39
I have updated from Fedora 38 to 39 yesterday. Since then, I am having frequent crashes where the screen goes black for a couple of seconds, then goes back to the login page, and after I enter the password all applications are closed. No mention of the crash appears in the notifications. This occurs...
I have updated from Fedora 38 to 39 yesterday. Since then, I am having frequent crashes where the screen goes black for a couple of seconds, then goes back to the login page, and after I enter the password all applications are closed. No mention of the crash appears in the notifications. This occurs randomly, after maybe 5 minutes of use, not in connection to anything specific that I am doing. I tried booting both the current kernel 6.5.11-300.fc39.x86_64 and on the previous kernel, namely 6.5.10-200.fc38.x86_64, but both have this problem. I don't think that this is related to a hardware issue because Windows, in dual boot, runs ok, and the freezes only appeared after the Fedora 39 update. The computer is a Dell laptop. The graphics card is the integrated Intel one. What can I do to find the cause?
Marco (31 rep)
Nov 11, 2023, 10:59 AM • Last activity: Jun 12, 2025, 01:01 PM
0 votes
1 answers
2086 views
Kali linux 2020.2 have white screen and icons not showing after update
I updated my virtual machine from kali 2020.1 to kali 2020.2 using apt-get upgrade command in the terminal and it completed successfully. Suddenly I got power-cut and I am also not saved the machine state. After I booted up the virtual machine and checked it shows like some sort of stuck white scree...
I updated my virtual machine from kali 2020.1 to kali 2020.2 using apt-get upgrade command in the terminal and it completed successfully. Suddenly I got power-cut and I am also not saved the machine state. After I booted up the virtual machine and checked it shows like some sort of stuck white screen and icons are not showing. If I tried to open any program or terminal, it wont open. Please check for attached screenshot for reference.enter image description here
Xivks (1 rep)
Jun 30, 2020, 12:42 PM • Last activity: Jun 12, 2025, 06:03 AM
Showing page 1 of 20 total questions