[libvirt] [jenkins-ci PATCH 1/5] guests: Add mapping for augeas-lenses
Jim Fehlig
jfehlig at suse.com
Thu Dec 12 16:49:22 UTC 2019
On 12/12/19 9:19 AM, Andrea Bolognani wrote:
> On Thu, 2019-12-12 at 15:57 +0000, Jim Fehlig wrote:
>> On 12/12/19 8:07 AM, Andrea Bolognani wrote:
>>> On Thu, 2019-12-12 at 15:43 +0100, Fabiano Fidêncio wrote:
>>>> On Thu, Dec 12, 2019 at 3:31 PM Andrea Bolognani <abologna at redhat.com> wrote:
>>>>> + augeas-lenses:
>>>>> + default: augeas
>>>>> + deb: augeas-lenses
>>>>> + OpenSUSE: augeas-lenses
>>>>
>>>> Hmm. I guess it only hits the container, am I right? Because in the VM
>>>> it's installed as part of the base system.
>>>
>>> It looks like it's needed by yast:
>>>
>>> $ sudo zypper remove augeas-lenses
>>> Loading repository data...
>>> Warning: No repositories defined. Operating only with the installed resolvables. Nothing can be installed.
>>> Reading installed packages...
>>> Resolving package dependencies...
>>>
>>> The following 15 packages are going to be REMOVED:
>>> augeas-lenses patterns-yast-yast2_basis yast2-bootloader yast2-country
>>> yast2-installation yast2-ldap yast2-mail yast2-network yast2-online-update
>>> yast2-online-update-frontend yast2-packager yast2-storage-ng yast2-tune
>>> yast2-update yast2-users
>>>
>>> The following pattern is going to be REMOVED:
>>> yast2_basis
>>>
>>> 15 packages to remove.
>>> After the operation, 7.5 MiB will be freed.
>>> Continue? [y/n/v/...? shows all options] (y):
>>>
>>> The container is minimal, and doesn't include yast at all:
>>>
>>> $ rpm -qa | grep yast
>>> $
>>>
>>> So that would explain the difference.
>>
>> If the difference is unwanted we could remove the yast2_basis pattern from
>> autoinst.xml.
>
> What would we lose by doing so? In general we install only the very
> basics through the OS' native installer and then add everything we
> need on top using lcitool, so it certainly sounds like it could make
> sense to drop it...
It's an installation and config management tool. Obviously we don't need it for
installation, and I don't think we'll be using it for management within the VM.
I can try removing it and send a patch if there are no ill effects, but it will
have to wait until next week when I have some free time.
Regards,
Jim
More information about the libvir-list
mailing list