Le 16/08/2019 à 13:29, Johnny Hughes a écrit :
> CR is normally completely empty. The only time CR is normally populated
> is for a small time before a new release is done .. and it is populated
> with packages that will go into the new release. Right now, for
> example, CR is empty:
Thanks for
On 8/15/19 8:20 AM, Nicolas Kovacs wrote:
> My suspicion is that some stuff from CR broke dependencies.
CR is normally completely empty. The only time CR is normally populated
is for a small time before a new release is done .. and it is populated
with packages that will go into the new
Le 15/08/2019 à 15:20, Nicolas Kovacs a écrit :
> I have to investigate this further.
I found the culprit, after a few unnerving hours of trial and error.
Turns out I'm using a hardcoded EPEL mirror in France to bypass my
filtering proxy. Unfortunately this mirror is not quite in sync, and
Le 15/08/2019 à 14:51, Ulf Volmer a écrit :
> Could you post the output of
>
> yum info 389-adminutil
I just installed a vanilla CentOS 7.6 on a sandbox machine.
Left configuration as is.
Upgraded system : yum update.
Configured EPEL without customizing anything.
And all the 389-related
On 15.08.19 14:31, Nicolas Kovacs wrote:
> Le 15/08/2019 à 13:49, Ulf Volmer a écrit :
>> No issues here. libadmsslutil.so.0 comes from 389-adminutil.
>> Do you have a recently updated system?
>
> I'm using yum-cron on all my CentOS servers, so yes.
Could you post the output of
yum info
Le 15/08/2019 à 13:49, Ulf Volmer a écrit :
> No issues here. libadmsslutil.so.0 comes from 389-adminutil.
> Do you have a recently updated system?
I'm using yum-cron on all my CentOS servers, so yes.
--
Microlinux - Solutions informatiques durables
7, place de l'église - 30730 Montpezat
Site :
On 15.08.19 13:27, Nicolas Kovacs wrote:
> Error: Package: 389-admin-1.1.46-1.el7.x86_64 (epel)
>Requires: libadminutil.so.0()(64bit)
No issues here. libadmsslutil.so.0 comes from 389-adminutil.
Do you have a recently updated system?
Best regards
Ulf
7 matches
Mail list logo
