hi all,
i could use some guidance in debugging an issue on centos 7.9 where
"suddenly" yum refuses to install a package. the package has multiple
version in 2 repos: highest version is in a repo with prio=5, the other
lower versions are in a repo without any priorities set.
we however require a sp
hi all,
i'm stuck debugging a problem that appeared after this update made it to
our systems:
http://lists.centos.org/pipermail/centos-announce/2015-January/020856.html
GDBM_File fails simple operation (which works with 1.8.0-36 of gdbm)
could someone with same perl and gdbm confirm the
hi brian,
isn't the attribute named Requires (with an s)?
stijn
On 02/20/2015 07:50 PM, Bryan Wright wrote:
Hi folks,
For complicated reasons, I'd like to have a service (lightdm) start
after sshd starts. (This is on CentOS 7.) I've tried adding "sshd.service"
to the lists of "Acti
hi all,
i have a general question (a bit surprised ti's not on the centos faq):
we found a bug in a package in a centos install, and we are wondering
what the best approach is to get TUV to fix it (and release an update),
so it gets fixed in centos rebuild and thus on our nodes. or at the very
hi all,
i'm trying to understand an issue i'm having with a yum repo (it's a
mirror of the c74 repo).
there's an rpm in the repo (ibutils-libs in this case); but the client
using this repo says it cannot find this rpm (i did yum info
ibutils-libs --disablerepo=* --enablerepo=c74 to exclude all ot
hi johnny,
>> anyone any hints how to debug this or some clues what could be going
>> wrong here.
>
> Do you have an exclude in /etc/yum.conf for ibutils-libs?
how embarassing. there was indeed an exclude on ibutils-libs. (this must
be some leftover from using mlnx ofed. we are switching from c7
that the
exclude will be removed.
i've seen worse in vendor-provided rpms, but i guess it caught me
offguard ;)
stijn
On 09/30/2017 11:51 AM, Stijn De Weirdt wrote:
> hi johnny,
>
>>> anyone any hints how to debug this or some clues what could be going
>>> wrong her
hi all,
latest kmod update 20-15.el7_4.6 is broken on our systems, while
previous 20-15.el7_4.4 was working fine (and downgrading fixes the issue).
the issue is with modules from mellanox kmod rpms that are symlinked in
the weak-updates dir. the config files in /etc/depmod.d look ok (and do
work
emi Yagi wrote:
>>
>> On Thu, Dec 7, 2017 at 6:23 AM, Stijn De Weirdt
>> wrote:
>
>>> latest kmod update 20-15.el7_4.6 is broken on our systems, while
>>> previous 20-15.el7_4.4 was working fine (and downgrading fixes the issue).
>>>
>>>
hi all,
can someone help explaining what we are seeing? it makes no sense to us.
this is a host running centos 7.4 with 3.10.0-693.17.1 kernel, and it
has 192GB of ram
> [] free -b
> totalusedfree shared buff/cache
> available
> Mem:201402642432 14413479
hi rob,
>> can someone help explaining what we are seeing? it makes no sense to us.
>> this is a host running centos 7.4 with 3.10.0-693.17.1 kernel, and it
>> has 192GB of ram
>>
>>> [] free -b
>>> total used free shared
>>> buff/cache available
>>> Mem: 20
hi mark,
>> can someone help explaining what we are seeing? it makes no sense to us.
>> this is a host running centos 7.4 with 3.10.0-693.17.1 kernel, and it
>> has 192GB of ram
>>
>>> [] free -b
>>> totalusedfree shared buff/cache
>>> available
>>> Mem:2014
hi all,
we have hosts that we want to pxeboot first, always. with uefi,
anaconda/kickstart always set the freshly installed disk as first
bootdevice and there seems to be no way to disable this behaviour.
the rhel7 docs describe a "leavebootorder" option
(https://access.redhat.com/documentation/e
hi all,
i'm trying to rebuild the current sssd-client.i686 rpm that is part of
the x86_64 repo, but i fail to do so. rebuilding the sssd.src.rpm on
x86_64 does not produce this rpm.
i can rebuild sssd.src.rpm with --target=i686, but that sssd-client rpm
has conflicts and a whole bunch of i686 dep
On 02/15/2017 02:39 AM, Stijn De Weirdt wrote:
>>> hi all,
>>>
>>> i'm trying to rebuild the current sssd-client.i686 rpm that is part of
>>> the x86_64 repo, but i fail to do so. rebuilding the sssd.src.rpm on
>>> x86_64 does not produce this rpm.
:10 AM, Stijn De Weirdt wrote:
> hi johnny,
>
> apologies, yes this is centos7 on x86_64.
>
> i had to set PKGCONFIG_DIR, but that looked like the only thing.
>
> i'll give mock a try and see what comes out.
>
> thanks a lot
>
> stijn
>
> On 02/15/201
16 matches
Mail list logo