similar to: Where can I find centos-release-8.1-1.1911.0.9.el8.src.rpm

On Mon, 17 Aug 2020 16:37:20 -0500 Gregory P. Ennis wrote: > "This system is not registered to Red Hat Subscription Management. You can use > subscription-manager to register." It sounds like you have something installed that doesn't need to be or shouldn't be installed. Under what circumstances does that message appear? I haven't seen it on any of my C8 systems,

All, While updating my package using dnf update all I allow dnf to clean some package with unresolved dependencies. I would like to reinstall some of them but got an error message "but none of the providers can be installed" during the install process as dnf is trying to install the dependencies. . This happens for some critical package like boost-openmpi-devel (see below for

I am doing a dnf install package_without_version for instance for g++: [piot at paris opal]$ sudo dnf install gcc-c++ Last metadata expiration check: 0:01:06 ago on Thu 16 Jan 2020 06:45:59 AM CST. Error: Problem: package gcc-8.3.1-4.5.el8.x86_64 requires glibc-devel >= 2.2.90-12, but none of the providers can be installed - package glibc-devel-2.28-72.el8.i686 requires glibc-headers, but

This is a quick recovery and fix for the machines rendered unbootable after the grub2/shim yum update. It is written for CentOS 8.2.2004 but similar should work for any CentOS 8 or 7 as long as you get the correct shim file, that is, the one from the latest installation media. I am running on an x86_64 architecture (see uname -i). Please use the correct shim file for your architecture

On 16/10/19 02:31, Ranbir wrote: > Hello Everyone, > > Has anyone tried to install BackupPC v4 on CentOS 8 from epel? I just did and this happened: > > [root at resurrect ~]# dnf --enablerepo epel install BackupPC > Last metadata expiration check: 0:18:41 ago on Tue 15 Oct 2019 08:03:59 PM EDT. > Error: > Problem: conflicting requests > - nothing provides

Hello everybody, A recent update of the sssd-common-2.8.1-1.el8.x86_64 package is causing sssd.service systemctl failures all over my CentosOS machines. What is the best way to report this issue and when can we expect an update from the sssd-common package for this regression bug? I think sssd-common is part of the baseos repository and installed even when the configuration file is not

><snip> > > I'll post here again once we have pushed the EL8 and CentOS Stream updates. > >OK .. I have also now pushed the CentOS Linux 8 update .. you should see >an update to SHIM .. the new versions are: > >PowerTools/x86_64/os/Packages/shim-unsigned-x64-15-8.el8.x86_64.rpm >BaseOS/x86_64/os/Packages/shim-ia32-15-15.el8_2.x86_64.rpm

On Tue, 5 May 2020 05:30:26 -0400 Eddie O'Connor wrote: > Are there .conf files for the desktop?....what about logs?....something's > got to be amiss somewhere....and Linux always complains when it is.....in > logs. Just wondering out loud... What happens if he sets up a new user? Does the desktop work then? -- Can we uninstall 2020 and install it again? This one has a virus.

> On 1/3/23 05:17, Orion Poplawski wrote: >> On 12/30/22 04:06, Jelle de Jong wrote: >>> On 12/27/22 22:55, Gordon Messmer wrote: >>>> On 2022-12-25 07:44, Jelle de Jong wrote: >>>>> A recent update of the sssd-common-2.8.1-1.el8.x86_64 package is >>>>> causing sssd.service systemctl failures all over my CentosOS >>>>>

On 1/3/23 13:41, Simon Matter wrote: >> On 1/3/23 05:17, Orion Poplawski wrote: >>> On 12/30/22 04:06, Jelle de Jong wrote: >>>> On 12/27/22 22:55, Gordon Messmer wrote: >>>>> On 2022-12-25 07:44, Jelle de Jong wrote: >>>>>> A recent update of the sssd-common-2.8.1-1.el8.x86_64 package is >>>>>> causing sssd.service

> On 1/3/23 13:41, Simon Matter wrote: >>> On 1/3/23 05:17, Orion Poplawski wrote: >>>> On 12/30/22 04:06, Jelle de Jong wrote: >>>>> On 12/27/22 22:55, Gordon Messmer wrote: >>>>>> On 2022-12-25 07:44, Jelle de Jong wrote: >>>>>>> A recent update of the sssd-common-2.8.1-1.el8.x86_64 package is

On 8/2/20 2:04 AM, Alessandro Baggi wrote: > > Il 01/08/20 22:03, Greg Bailey ha scritto: >> On 8/1/20 6:56 AM, david wrote: >>> At 02:54 AM 8/1/2020, Alessandro Baggi wrote: >>>> Hi Johnny, >>>> thank you very much for clarification. >>>> >>>> You said that in the centos infrastructure only one server got the >>>>

At 06:10 AM 8/2/2020, you wrote: >On 8/2/20 8:04 AM, david wrote: > > > >> <snip> > > > > > > > >> > I'll post here again once we have pushed the EL8 and CentOS Stream > >> updates. > >> > >> OK .. I have also now pushed the CentOS Linux 8 update .. you should see > >> an update to SHIM .. the new

Hi, I can find latest sssd RPM at http://mirror.centos.org/centos/8.1.1911/BaseOS/x86_64/os/Packages/sssd-2.2.0-19.el8_1.1.x86_64.rpm, but I can't find his source RPM at http://vault.centos.org/8.1.1911/BaseOS/Source/SPackages/ ( https://centos.pkgs.org/8/centos-baseos-x86_64/sssd-2.2.0-19.el8_1.1.x86_64.rpm.html ) Is there something wrong with latest sssd src RPM? I have also noticed that

On 12/27/22 22:55, Gordon Messmer wrote: > On 2022-12-25 07:44, Jelle de Jong wrote: >> A recent update of the sssd-common-2.8.1-1.el8.x86_64 package is >> causing sssd.service systemctl failures all over my CentosOS machines. > ... >> [sssd] [confdb_expand_app_domains] (0x0010): No domains configured, >> fatal error! > > > Were you previously using

On 12/30/22 04:06, Jelle de Jong wrote: > On 12/27/22 22:55, Gordon Messmer wrote: >> On 2022-12-25 07:44, Jelle de Jong wrote: >>> A recent update of the sssd-common-2.8.1-1.el8.x86_64 package is >>> causing sssd.service systemctl failures all over my CentosOS machines. >> ... >>> [sssd] [confdb_expand_app_domains] (0x0010): No domains configured,

Following some update or the other (I think) on my CentOS Stream 8 system, I'm no longer able to use ping as a regular user; I get $ ping www.centos.org ping: socket: Operation not permitted Does anyone else see this? It it a bug, or were the system/default permissions deliberately changed? Can anyone suggest a fix/workaround? Actually, I can find several different ones via a simple web

Hello all-- These instructions are somewhat OK but my messed up box is the only one I've got basically to help with this problem. Where can we find "correction" instructions using a "rescue" CD or flash drive? I understand RedHat provided detailed instructions to supported customers. Thanks. _______________________ Sent from MzK's phone. ---------- Forwarded message

> > Simon and others > Here's a very simple and hopefully reproducible test-case > > Select as your boot ISO: > ?CentOS-8.1.1911-x86_64-dvd1.iso > Choose to reclaim all space on the disk > Choose 'Minimal Install' as the software selection > Connect yourself to the network (I use a wired connection) > Don't bother creating a user, just provide your

On Mon, 17 Aug 2020 17:03:24 -0500 Gregory P. Ennis wrote: > I downloaded a Centos 8 image file : > > CentOS-8.1.1911-x86_64-dvd1.iso > > then I installed it as a kvm guest on a Centos 7 host machine. > > I installed a lot of the software; gui and server to give it a test drive. > > Nothing unusual about what I did that I can identify. And the message came up when