William/Mark
In master branch this function is checkPackageAndLoad() and it's found in src/cockpit/389-console/src/ds.jsx, or in older versions it's somewhere in ds.js (it has a different function name though), then just rebuild cockpit
Already did that (even before your suggestion), but I just wonder like William if there's no "smart" way to check if already has 389 in the system.
Thanks anyway.
Alberto Viana
On Tue, Mar 3, 2020 at 9:32 PM William Brown <wbrown@xxxxxxx> wrote:
> On 4 Mar 2020, at 04:07, Mark Reynolds <mreynolds@xxxxxxxxxx> wrote:
>
>
>
> On 3/3/20 1:01 PM, Mark Reynolds wrote:
>>
>>
>> On 3/3/20 12:28 PM, Alberto Viana wrote:
>>> Hi Guys,
>>>
>>> I'm testing some versions of 389 and I realise that in newer versions, cockpit stopped to work to me:
>>>
>>> There is no 389-ds-base package installed on this system. Sorry there is nothing to manage...
>>>
>>> In my case (due to internal reasons) we compile our version of 389.
>>>
>>> Is this an expected behavior? Is it suppose to only work if I have a 389 package installed in the system? There's any workaround for that?
>> It's looking for an rpm via:
>>
>> rpm -q 389-ds-base
>>
>> Just install the official rpm, and overwrite it with your private build.
>>
> If you are doing a private build anyway, you could just remove this check from the UI code:
>
> In master branch this function is checkPackageAndLoad() and it's found in src/cockpit/389-console/src/ds.jsx, or in older versions it's somewhere in ds.js (it has a different function name though), then just rebuild cockpit
Couldn't we do an instance list instead? That way it would catch anything that's in /etc/dirsrv or /data?
>
>
>
>>
>>
>> HTH,
>>
>> Mark
>>
>>>
>>> Thanks
>>>
>>>
>>> _______________________________________________
>>> 389-users mailing list --
>>> 389-users@xxxxxxxxxxxxxxxxxxxxxxx
>>>
>>> To unsubscribe send an email to
>>> 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
>>>
>>> Fedora Code of Conduct:
>>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>>>
>>> List Guidelines:
>>> https://fedoraproject.org/wiki/Mailing_list_guidelines
>>>
>>> List Archives:
>>> https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
>> --
>>
>> 389 Directory Server Development Team
>>
>>
>>
>> _______________________________________________
>> 389-users mailing list --
>> 389-users@xxxxxxxxxxxxxxxxxxxxxxx
>>
>> To unsubscribe send an email to
>> 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
>>
>> Fedora Code of Conduct:
>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>>
>> List Guidelines:
>> https://fedoraproject.org/wiki/Mailing_list_guidelines
>>
>> List Archives:
>> https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
> --
>
> 389 Directory Server Development Team
>
> _______________________________________________
> 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
—
Sincerely,
William Brown
Senior Software Engineer, 389 Directory Server
SUSE Labs
_______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
