Discuss

discuss@lists.centos.org

1 participants
34732 discussions

None
by None 03 Apr '24

03 Apr '24

blank" do you not understand? ;) If you do not believe there is any problem, consider the complexity of Johnny Hughes's solution! If Johnny Hughes's solution works for him and he is happy with it, that is great -- more power to him. (The FAQ includes a write up of Johnny's solution.) I have two replies. 1) Back a couple of months ago, as a test, I tried his solution, and the screen on my Mag DX1495 still went blank with the two nVIDIA cards that I tested. 2) I would rather just plug in a card which works right out of the box on a standard, SUPPORTED kernel, than to go through all the complicated steps in Johnny's solution. But this is just my personal preference. I can use the nVIDIA cards in Linux with compatible monitors or in Windows with any monitor (as far as I know). BTW, the computer on which I am writing this email runs CentOS, and with this Acer 77c monitor, I am using an nVIDIA GeForce display card -- it works fine with THIS hardware. Rick Message: 7 Date: Tue, 21 Sep 2004 23:17:26 -0400 From: Christopher Blume <godsmoke(a)godsmoke.com> To: centos(a)caosity.org Subject: Re: [Centos] nVIDIA on CentOS 3.3 Hello Rick, I have to say, I found your notice of nVidia cards "not working" as a little odd. To begin with -- drivers *generally* do not vary between distributions of linux. So, the fact that your card "doesn't work" with CentOS means that something else went wrong -- not that the drivers don't exist, or don't function properly. First of all, I'd be interested to see where your conclusion that your monitor doesn't work with an nVidia card in linux came from -- what exactly did you experience/test to come to this statement? I don't know anything about Kudzu, but, let me tell you, the nVidia Riva TNT 2 is ABSOLUTELY supported by the linux kernel -- and XFree86 ABSOLUTELY runs on it. If it's not working on your system, instead of making conclusions about Linux as a whole, understand that there are probably issues with the configuration files you either manually wrote, or the programs CentOS/RHEL bundles with the distro did. nVidia cards have the absolute best support under linux of any video card -- and I highly doubt what you experienced was a driver issue -- if it was, it was because of some mangled patch that RedHat applied, because the driver for nVidia TNTs is used by tens of thousands of Linux users. Thank You, Christopher Blume

1 0

[Infra] - Planned outage : lists.centos.org (migration to mailman3) : please read
by Fabian Arrotin 02 Apr '24

02 Apr '24

Due to a needed upgrade , we'll have to move the existing CentOS mailman instance (aka https://lists.centos.org) to a new server/host. Migration is scheduled for """"Tuesday April 8th, 7:00 am UTC time"""". You can convert to local time with $(date -d '2024-04-08 07:00 UTC') The expected "downtime" is estimated to ~60 minutes , time needed to : - take last mailman2 backup - reimport / convert mailman2 archives to mailman3 DB - DNS propagation for A/AAAA/MX records Here are also some important information about the mailman2 => mailman3 migration : # Renamed lists Worth knowing that, based on open discussion on the centos-devel list (see whole thread at https://lists.centos.org/pipermail/centos-devel/2024-March/165576.html) existing lists will be *renamed* , so while we'll put aliases for incoming mails, each list member will start receiving list mails from new list name. So start updating your filters if you filter on email address instead of "subject:" Here is the overview of the new lists names : arm-dev at centos.org => arm-dev at lists.centos.org centos at centos.org => discuss at lists.centos.org centos-devel at centos.org => devel at lists.centos.org centos-announce at centos.org => announce at lists.centos.org centos-automotive-sig at centos.org => automotive-sig at lists.centos.org centos-{cz,de,es,fr,nl,pt-br,zh}(a)centos.org => discuss-{cz,de,es,fr,nl,pt-br,zh}(a)lists.centos.org ci-users at centos.org => ci-users at lists.centos.org centos-gsoc: => gsoc at lists.centos.org centos-mirror at centos.org => mirror at lists.centos.org centos-mirror-announce at centos.org => mirror-announce at lists.centos.org centos-newsletter at centos.org => newsletter at lists.centos.org centos-promo at centos.org => promo at lists.centos.org centos-virt at centos.org => virt at lists.centos.org # Authentication Mailman2 had no real concept of authentication so you could just subscribe to one or more lists, and have a password associated with your email address for that/these subscription(s). Mailman3 itself is split into "core" and "webui" components, so when we'll import mailman2 lists/config into mailman3, your existing subscriptions will continue to work *but* not your password. Mailman3 will be configured to support SSO, and so if you already have a FAS/ACO account (https://accounts.centos.org) you'll be able to login directly into new webui and manage your settings/subscriptions *if* your ACO email address of course matches the one you initially subscribed with for lists.centos.org. If that's not the case, either create an ACO/FAS account that will match and you'll be then able to "link" your mailman3 account with FAS and so manage your settings/subscriptions. If you don't want to, there is always the documented process : https://docs.mailman3.org/en/latest/userguide.html#making-a-mailman-account Thanks for your understanding and patience. on behalf of the Infra team, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

2 1

Out-Of-Office
by Sivaramakrishna Polepalli 02 Apr '24

02 Apr '24

Hello, I will be OOO traveling from 03/28 to 05/06 returning back on 06/07. Please expect delays in my email responses. Please contact Aurus support prodsupport(a)aurusinc.com / Yogesh Baviskar ybaviskar(a)aurusinc.com for any support needs. Thanks Siva Polepalli +1 575-404-3272

1 0

CentOS 7/8s EOL : infrastructure impacts (please read)
by Fabian Arrotin 02 Apr '24

02 Apr '24

Hi all, As you're all aware (we sent multiple mails in the last year about this), CentOS 7 and Stream 8 will go EOL soon : https://blog.centos.org/2023/04/end-dates-are-coming-for-centos-stream-8-an… Let's lists some things that will happen on the CentOS Infrastructure as we'll be approching (or passed) these dates : # CentOS 7/8s content itself Usual process : content will be archived to https://vault.centos.org and removed from mirror.centos.org completely, with just a simple readme file dropped here (for example http://mirror.centos.org/centos/8/readme for already EOL'ed version). Worth knowing that some SIGs are still building for RHEL8, still supported for SIGs through https://cbs.centos.org so such kind of content will continue to be available there as long as SIGs can build against/for it # CBS/koji (https://cbs.centos.org) No impact on CBS env itself ( not running centos 7 nor 8s for a long time now) but the various build tag reflecting centos 7 and 8s will be locked so that nobody would be able to build content anymore : that would even be impossible as content itself will have been removed from mirror.centos.org (internally used for cbs build tags) # CentOS Forums (https://forums.centos.org) : still running on centos 7 and even if that's easy to migrate to newer/supported EL version, it was decided to just shutdown the service (based on discussion with the actual moderation team). An option (to be announced on forums.centos.org ?) is to eventually start moving thread/discussions on Fedora discourse (There is already a CentOS category there : https://discussion.fedoraproject.org/c/neighbors/centos/71) So the plan is just to shutdown forums.centos.org and remove A/AAAA records from DNS # mirrorlist.centos.org service : Starting from Stream 9 (and above), deployed CentOS instance ares using Fedora infra mirrormanager instance for metalink= instead of mirrorlist= in .repo files. We'll just decommission our mirror crawler (also running with a mix of perl/python2 code), so not validating any mirror for legacy/EOL releases. mirrorlist.centos.org A/AAAA records will be removed in the following weeks after c7 will be EOL'ed. That means that people still running CentOS 7 or 8-stream will not have functional yum/dnf stack, except if they point to either vault or have internal mirror but at least people would be aware that distro itself is EOL and that they shouldn't expect to receive any update anymore # CentOS mailing-lists Currently running on mailman2 stack, on top of CentOS 7 linux : there is WIP to port everything to up2date mailman3 stack, actually packaged for EPEL9. We have successfully imported archives into mailman3 and same for lists config but let's start a different/separate thread to discuss changes (like renaming lists, see next coming thread) Kind Regards, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

2 4

Out-Of-Office
by Sivaramakrishna Polepalli 01 Apr '24

01 Apr '24

Hello, I will be OOO traveling from 03/28 to 05/06 returning back on 06/07. Please expect delays in my email responses. Please contact Aurus support prodsupport(a)aurusinc.com / Yogesh Baviskar ybaviskar(a)aurusinc.com or any support needs. Thanks Siva Polepalli +1 575-404-3272

1 0

Re: [CentOS] CentOS 7/8s EOL : infrastructure impacts (please read)
by The GOAT 01 Apr '24

01 Apr '24

Hi, In thread... https://lists.centos.org/pipermail/centos/2024-March/1078098.html ...the mention of the AMIs got me thinking about these images. https://www.centos.org/download/aws-images/ Will the CentOS Linux 7 AMI images continue to be available after June 30 2024, so people can use the last image, attach ELS repos from TuxCare or Perforce and plow on using CentOS 7 for a while? What's the plan for these images AMI references?

1 0

unsubcribe
by Leonardo Cuyar Morales 30 Mar '24

30 Mar '24

-- Imagination is more important than knowledge

2 1

Out-Of-Office
by Sivaramakrishna Polepalli 30 Mar '24

30 Mar '24

Hello, I will be OOO traveling from 03/28 to 05/06 returning back on 06/07. Please expect delays in my email responses. Please contact Aurus support prodsupport(a)aurusinc.com / Yogesh Baviskar ybaviskar(a)aurusinc.com or any support needs. Thanks Siva Polepalli +1 575-404-3272

1 0

CentOS-announce Digest, Vol 218, Issue 2
by centos-announce-request＠centos.org 26 Mar '24

26 Mar '24

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CEBA-2024:1277 CentOS 7 libX11 BugFix Update (Johnny Hughes) 2. CEBA-2024:1275 CentOS 7 lm_sensors BugFix Update (Johnny Hughes) 3. CEBA-2024:1276 CentOS 7 resource-agents BugFix Update (Johnny Hughes) 4. CESA-2024:1249 Important CentOS 7 kernel Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Mon, 25 Mar 2024 15:01:43 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2024:1277 CentOS 7 libX11 BugFix Update Message-ID: <20240325150143.GA5320(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2024:1277 Upstream details at : https://access.redhat.com/errata/RHBA-2024:1277 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 3e22c1e91e6c946f60aaa437911042d67c7e9de92d77cf458a51d5660658186c libX11-1.6.7-5.el7_9.i686.rpm f79bf580272858f3f9343a97221fc561755bb908456a1beb77582f9310486ae1 libX11-1.6.7-5.el7_9.src.rpm 1f4f286b0441b2c508c416f72ee52c1b323a1ba12aae4579f986c007ecde653f libX11-1.6.7-5.el7_9.x86_64.rpm 70bbd71ba6462d9f6702322739a79ddf57ab8a23f41a3ae1e2c47feacb60d0d1 libX11-common-1.6.7-5.el7_9.noarch.rpm 1ef57080cad8889aa2a957bb771d161af38b61bf4aec83a7fcd19e2dfe510079 libX11-devel-1.6.7-5.el7_9.i686.rpm 374f721b5f41a11a081cd23537162130ab654a02ece3e8c55f3840ecd8f839a0 libX11-devel-1.6.7-5.el7_9.x86_64.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)libera.chat Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Mon, 25 Mar 2024 15:01:57 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2024:1275 CentOS 7 lm_sensors BugFix Update Message-ID: <20240325150157.GA5446(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2024:1275 Upstream details at : https://access.redhat.com/errata/RHBA-2024:1275 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 88e82b5a11526a65b2ac8dcbe253868992a00064db1db424255bd509feb452cb lm_sensors-3.4.0-8.20160601gitf9185e5.el7_9.1.src.rpm be4cfd2a6f6ccca83e063fb2eccc0c3e16716ba370638be5de4deda72c80848a lm_sensors-3.4.0-8.20160601gitf9185e5.el7_9.1.x86_64.rpm 95d76c0c65f9a62fc846a490f4d2b19a993d7bfe3b29c8f5435e619d31f10fe5 lm_sensors-devel-3.4.0-8.20160601gitf9185e5.el7_9.1.i686.rpm 552d8f1a349abd352ed882be0cfbe9423589f98f6621627e58afa84d6c83599d lm_sensors-devel-3.4.0-8.20160601gitf9185e5.el7_9.1.x86_64.rpm 189cab5bc603286773946e73c42d38c539c7a0de2d36fdb6fa6aba0763c86a44 lm_sensors-libs-3.4.0-8.20160601gitf9185e5.el7_9.1.i686.rpm 0af4fa113704a011a3594459a6619542c384a68bce85aa250f90448e347431fe lm_sensors-libs-3.4.0-8.20160601gitf9185e5.el7_9.1.x86_64.rpm 60f10f4641f2dac4d689ad5b1ee25cc224768eadce58b7f0d64c3eecf32b94ff lm_sensors-sensord-3.4.0-8.20160601gitf9185e5.el7_9.1.x86_64.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)libera.chat Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Mon, 25 Mar 2024 15:02:10 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2024:1276 CentOS 7 resource-agents BugFix Update Message-ID: <20240325150210.GA5582(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2024:1276 Upstream details at : https://access.redhat.com/errata/RHBA-2024:1276 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 619d5b89b88c559b235692c6c00c5d06cedd0d274f0132dc0732b25bc91bb93e resource-agents-4.1.1-61.el7_9.20.src.rpm 1f633f20c7b2aa6eafb4ac8894d9cd73727c40432189eee52f62aee11daf62e9 resource-agents-4.1.1-61.el7_9.20.x86_64.rpm 6d0aee209b29a68899270b50fbdb5657444b46017f3f4b39ff4652e77f30292c resource-agents-aliyun-4.1.1-61.el7_9.20.x86_64.rpm 639a97b21ae7b51141fd76f2777d2f3ea1bd758549e53130764657fafe2daf7a resource-agents-gcp-4.1.1-61.el7_9.20.x86_64.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)libera.chat Twitter: @JohnnyCentOS ------------------------------ Message: 4 Date: Mon, 25 Mar 2024 15:37:48 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2024:1249 Important CentOS 7 kernel Security Update Message-ID: <20240325153748.GA12778(a)bstore1.rdu2.centos.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2024:1249 Important Upstream details at : https://access.redhat.com/errata/RHSA-2024:1249 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: ebf604edce00a3a3778207eeaac06a3de226dbf62bfb987ed00584aa8d736ea1 bpftool-3.10.0-1160.114.2.el7.x86_64.rpm 4ea83e958a87df368396a4445d79a7047566af99a681051e97005b0c5b61aa05 kernel-3.10.0-1160.114.2.el7.src.rpm d4e1ed8394af297a574fede15b7e0b3dcc28d263998175257f45e728f22fca91 kernel-3.10.0-1160.114.2.el7.x86_64.rpm 18d2703d9432cd3d8353acf0fb1f852fe4c15301b3d49fffac3f0194c6a4aaa0 kernel-abi-whitelists-3.10.0-1160.114.2.el7.noarch.rpm fe01de01f7bcb863a54f276394f9ab097a0d29db56661a42eb33d27e4bef27f8 kernel-debug-3.10.0-1160.114.2.el7.x86_64.rpm cfde4230671763bf6a464de9ec8c191195c9ae864571afd92bc7bea8dfcbb11e kernel-debug-devel-3.10.0-1160.114.2.el7.x86_64.rpm 74dfc146e5e4ab219dba838033e3a2a983e2ad796cee5a175fda1b6c17653193 kernel-devel-3.10.0-1160.114.2.el7.x86_64.rpm b5a460913216927a863650ccef6d332b05a92836c9647e73a369720e9156fe84 kernel-doc-3.10.0-1160.114.2.el7.noarch.rpm 4aeb221b696dbe4b67c7b108b689cf26df6c7baa673fd4a529bd4df444eaf4fc kernel-headers-3.10.0-1160.114.2.el7.x86_64.rpm 2ba740802cbbc7ff23957b8b2a38c06b773a113b40708d05815b6081f7eecb19 kernel-tools-3.10.0-1160.114.2.el7.x86_64.rpm d4ce276deccf36c3cdff38a52ff6f73bd2c271d8df45463c61cc66cdd8dd7e18 kernel-tools-libs-3.10.0-1160.114.2.el7.x86_64.rpm bee03f8565ac02484c05292876b9c0976e9334dad12bbf643dd9f59526e9eb6d kernel-tools-libs-devel-3.10.0-1160.114.2.el7.x86_64.rpm 0af8a6a9e3b24968bed3be9b8de12ef658fbbfc2164edfd7186a7cced585e5ec perf-3.10.0-1160.114.2.el7.x86_64.rpm 850766245b53884b841d001909aa89898b167cf79a244d26c44c42dd775019c3 python-perf-3.10.0-1160.114.2.el7.x86_64.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)libera.chat Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 218, Issue 2 ***********************************************

1 0

CentOS Virt SIG and packages' priority problems?
by Gianluca Cecchi 14 Mar '24

14 Mar '24

Hello, some days ago I followed these instructions https://sigs.centos.org/virt/tdx/host/ and after enabling the repo I installed the tdx necessary bits as indicated, with the command dnf install kernel-tdx qemu-kvm-tdx libvirt-tdx This gave me: libvirt 9.5.0-1.el9s qemu-kvm 8.0.0-15.el9s kernel 5.14.0-395.el9s But now if I run a usual "dnf update" I'm proposed "standard" libvirt and qemu-kvm sw stack, I think because of their version apparently greater (10 vs 9.5 and 8.2 vs 8.0): Upgrading: libvirt x86_64 10.0.0-4.el9 appstream 23 k libvirt-client x86_64 10.0.0-4.el9 appstream 438 k libvirt-client-qemu x86_64 10.0.0-4.el9 appstream 47 k libvirt-daemon x86_64 10.0.0-4.el9 appstream 213 k libvirt-daemon-common x86_64 10.0.0-4.el9 appstream 139 k libvirt-daemon-config-network x86_64 10.0.0-4.el9 appstream 29 k libvirt-daemon-config-nwfilter x86_64 10.0.0-4.el9 appstream 42 k libvirt-daemon-driver-interface x86_64 10.0.0-4.el9 appstream 219 k libvirt-daemon-driver-network x86_64 10.0.0-4.el9 appstream 260 k libvirt-daemon-driver-nodedev x86_64 10.0.0-4.el9 appstream 240 k libvirt-daemon-driver-nwfilter x86_64 10.0.0-4.el9 appstream 255 k libvirt-daemon-driver-qemu x86_64 10.0.0-4.el9 appstream 976 k libvirt-daemon-driver-secret x86_64 10.0.0-4.el9 appstream 216 k libvirt-daemon-driver-storage x86_64 10.0.0-4.el9 appstream 23 k libvirt-daemon-driver-storage-core x86_64 10.0.0-4.el9 appstream 276 k libvirt-daemon-driver-storage-disk x86_64 10.0.0-4.el9 appstream 38 k libvirt-daemon-driver-storage-iscsi x86_64 10.0.0-4.el9 appstream 35 k libvirt-daemon-driver-storage-logical x86_64 10.0.0-4.el9 appstream 39 k libvirt-daemon-driver-storage-mpath x86_64 10.0.0-4.el9 appstream 32 k libvirt-daemon-driver-storage-rbd x86_64 10.0.0-4.el9 appstream 43 k libvirt-daemon-driver-storage-scsi x86_64 10.0.0-4.el9 appstream 35 k libvirt-daemon-lock x86_64 10.0.0-4.el9 appstream 64 k libvirt-daemon-log x86_64 10.0.0-4.el9 appstream 69 k libvirt-daemon-plugin-lockd x86_64 10.0.0-4.el9 appstream 38 k libvirt-daemon-proxy x86_64 10.0.0-4.el9 appstream 211 k libvirt-libs x86_64 10.0.0-4.el9 appstream 4.9 M python3-libvirt x86_64 10.0.0-1.el9 appstream 339 k qemu-img x86_64 17:8.2.0-6.el9 appstream 2.5 M qemu-kvm x86_64 17:8.2.0-6.el9 appstream 68 k qemu-kvm-audio-pa x86_64 17:8.2.0-6.el9 appstream 81 k qemu-kvm-block-blkio x86_64 17:8.2.0-6.el9 appstream 84 k qemu-kvm-block-rbd x86_64 17:8.2.0-6.el9 appstream 86 k qemu-kvm-common x86_64 17:8.2.0-6.el9 appstream 685 k qemu-kvm-core x86_64 17:8.2.0-6.el9 appstream 4.3 M qemu-kvm-device-display-virtio-gpu x86_64 17:8.2.0-6.el9 appstream 92 k qemu-kvm-device-display-virtio-gpu-pci x86_64 17:8.2.0-6.el9 appstream 76 k qemu-kvm-device-display-virtio-vga x86_64 17:8.2.0-6.el9 appstream 77 k qemu-kvm-device-usb-host x86_64 17:8.2.0-6.el9 appstream 90 k qemu-kvm-device-usb-redirect x86_64 17:8.2.0-6.el9 appstream 95 k qemu-kvm-docs x86_64 17:8.2.0-6.el9 appstream 1.2 M qemu-kvm-tools x86_64 17:8.2.0-6.el9 appstream 584 k qemu-kvm-ui-egl-headless x86_64 17:8.2.0-6.el9 appstream 77 k qemu-kvm-ui-opengl x86_64 17:8.2.0-6.el9 appstream 84 k qemu-pr-helper x86_64 17:8.2.0-6.el9 appstream 497 k What is the best option to blacklist the packages in appstream and prioritize the tdx ones? I tried adding priority=1 to the tdx repo file, but now I get this when running "dnf update": Error: Problem: package python3-libvirt-10.0.0-1.el9.x86_64 from appstream requires libvirt.so.0(LIBVIRT_9.7.0)(64bit), but none of the providers can be installed - cannot install both libvirt-libs-10.0.0-2.el9.x86_64 from appstream and libvirt-libs-9.5.0-1.el9s.x86_64 from @System - cannot install both libvirt-libs-10.0.0-3.el9.x86_64 from appstream and libvirt-libs-9.5.0-1.el9s.x86_64 from @System - cannot install both libvirt-libs-10.0.0-4.el9.x86_64 from appstream and libvirt-libs-9.5.0-1.el9s.x86_64 from @System - cannot install both libvirt-libs-9.10.0-1.el9.x86_64 from appstream and libvirt-libs-9.5.0-1.el9s.x86_64 from @System - cannot install both libvirt-libs-9.9.0-1.el9.x86_64 from appstream and libvirt-libs-9.5.0-1.el9s.x86_64 from @System - cannot install the best update candidate for package python3-libvirt-9.3.0-1.el9.x86_64 - cannot install the best update candidate for package libvirt-libs-9.5.0-1.el9s.x86_64 (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages) # Currently I have python3-libvirt-9.3.0-1.el9.x86_64 installed. Thanks for any advise Gianluca

1 0

← Newer
1
2
3
4
5
6
7
...
3474
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss