kiwi-ng autoyast without OBS => dependencies problem

16 views
Skip to first unread message

Gabriel Machado

unread,
Jun 15, 2024, 4:34:06 PMJun 15
to kiwi
Hello, 

 on my laptop to build openSuse microOS iso images.

I modified the kiwi file to use https repos instead of OBS repos:
<!--
<repository type="rpm-md" >
<source path='obsrepositories:/'/>
</repository>
-->
<repository alias="tumbleweed-oss" imageinclude="true">
<source path="https://opensuse.mirror.garr.it/mirrors/opensuse/tumbleweed/repo/oss/"/>
</repository>
<repository alias="tumbleweed-non-oss" imageinclude="true">
<source path="https://opensuse.mirror.garr.it/mirrors/opensuse/tumbleweed/repo/non-oss/"/>
</repository>
<repository alias="tumbleweed-update-oss" imageinclude="true">
<source path="http://download.opensuse.org/update/tumbleweed/"/>
</repository>

And I  succeeded to build an image.


Next, I tried to build an image with an autoyast profile using this documentation https://osinside.github.io/kiwi/working_with_images/setup_yast_on_first_boot.html. But it failed :
[ DEBUG   ]: 21:15:55 | system: Resolving package dependencies...
[ DEBUG   ]: 21:15:55 | system: Problem: 1: the to be installed patterns-microos-base-zypper-5.0-87.3.x86_64 requires 'pattern() = microos_base', but this requirement cannot be provided
[ DEBUG   ]: 21:15:55 | system: not installable providers: patterns-microos-base-5.0-87.3.x86_64[tumbleweed-oss]
[ DEBUG   ]: 21:15:55 | system:  Solution 1: Following actions will be done:
[ DEBUG   ]: 21:15:55 | system:   do not install patterns-microos-base-zypper-5.0-87.3.x86_64
[ DEBUG   ]: 21:15:55 | system:   do not install patterns-microos-basesystem-5.0-87.3.x86_64
[ DEBUG   ]: 21:15:55 | system:   do not install patterns-microos-defaults-5.0-87.3.x86_64
[ DEBUG   ]: 21:15:55 | system:  Solution 2: deinstallation of systemd-presets-branding-Aeon-20231005-4.1.noarch
[ DEBUG   ]: 21:15:55 | system:  Solution 3: break patterns-microos-base-zypper-5.0-87.3.x86_64 by ignoring some of its dependencies
[ DEBUG   ]: 21:15:55 | system: Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): c
 
I attached my kiwi project.
Can you help me to fix this error please ?

Regards,
Gabriel.
openSUSE-microOS.kiwi.tgz

Marcus Schäfer

unread,
Jun 16, 2024, 5:02:18 AMJun 16
to kiwi-...@googlegroups.com
Hi Gabriel,

> [ DEBUG ]: 21:15:55 | system: Resolving package dependencies...
> [ DEBUG ]: 21:15:55 | system: Problem: 1: the to be installed
> patterns-microos-base-zypper-5.0-87.3.x86_64 requires 'pattern() =
> microos_base', but this requirement cannot be provided

This microos patterns are driving everybody crazy. I would wish that
those who designed MicroOS also build it outside of the open buildservice.
This time the issue is not the busybox preference which is handled
differently between the obs resolver and zypper, this time it's the
systemd-presets-branding-MicroOS which has to be installed as early as
possible because for some reason if it's not installed during the
bootstrap phase the zypper resolver fails on the pattern.

I created a workaround patch to openSUSE-MicroOS.kiwi and attached it
to this mail. With this patch it also builds locally.

Please note, this is not a kiwi issue, these are packaging and pattern
issues related to MicroOS and maybe you can report them there too ?
Thanks in advance.

PS:
Please ignore the repo change in the patch. I adapted it because
opensuse.mirror.garr.it did not resolve on my end

Best regards,
Marcus
--
Public Key available via: https://keybase.io/marcus_schaefer/key.asc
keybase search marcus_schaefer
-------------------------------------------------------
Marcus Schäfer Brunnenweg 18
Tel: +49 7562 905437 D-88260 Argenbühl
Germany
-------------------------------------------------------
micro.patch
signature.asc

Gabriel Machado

unread,
Jun 16, 2024, 5:52:29 AMJun 16
to kiwi
Hi Marcus,


Thank you for your help. The patch works.
I'm pleasantly surprised, you even help people on sundays :).

How do you investigate on these kind of issues ? I read the kiwi logs but I don't found revelant informations.

I will report the issues soon as you suggested.


Regards, 
Gabriel.

Marcus Schäfer

unread,
Jun 16, 2024, 3:01:05 PM (14 days ago) Jun 16
to kiwi-...@googlegroups.com
Hi Gabriel,

> Thank you for your help. The patch works.

yay :)

> I'm pleasantly surprised, you even help people on sundays :).

And you seem to read mails on a sunday too ;)

> How do you investigate on these kind of issues ? I read the kiwi logs
> but I don't found revelant informations.

Yeah you will not find anything on the kiwi logging as it's basically
the package manager which cannot resolve the given data. I usually
go the following way.

1. Fetch the zypper error from the kiwi log that says that
some patterns-xxx requires pattern "foo bar" but this requirement
cannot be provided. Actually this error message is a lie ;)
Of course the pattern can be provided but it cannot be resolved.
So what you need are the list of packages the pattern requires.

2. Go to https://software.opensuse.org type in the search field the
patterns-xxx string and look it up.

3. Download that patterns-xxx package and then inspect it locally
via "rpm -qp --requires patterns-xxx....rpm". You will now
get a list of packages that this pattern wants to pull in.

4. Take this list and turn it into

<package name="a"/>
<package name="b"/>
.. and so on

in your kiwi image description and temporary disable the
<package name="patterns-xxx"/> line.

5. Now repeat the build. You will run into the same error
buuut, the zypper resolver will now give you more details what
part of the *f* pattern it could not resolve. And from there
you can workaround the situation in the kiwi image description

It's a cumbersome and stupid debugging process but it will lead
you to the issue. If you can workaround the issue in the kiwi image
description is not guaranteed but in most cases I found a way to
do it. Well the actual bug in the package stays.

> I will report the issues soon as you suggested.

Thanks a ton

Regards,
signature.asc

Gabriel Machado

unread,
Jun 16, 2024, 3:59:26 PM (14 days ago) Jun 16
to kiwi
I reported the issues as promised : https://bugzilla.opensuse.org/show_bug.cgi?id=1226408

I did my best to explain what's wrong.

Thank you for the debugging process.

Regards,
Gabriel.

Gabriel Machado

unread,
Jun 17, 2024, 2:55:28 AM (13 days ago) Jun 17
to kiwi
Hello, 

The iso seems work but I have the following error : "No workflow defined for this installation mode".
What does it mean ? How to fix this ?

I tried with others yast profile but I've always this error.

Regards,
Gabriel.

Marcus Schäfer

unread,
Jun 17, 2024, 4:49:35 AM (13 days ago) Jun 17
to kiwi-...@googlegroups.com
Hi,

> The iso seems work but I have the following error : "No workflow
> defined for this installation mode".
>
> What does it mean ? How to fix this ?
>
> I tried with others yast profile but I've always this error.

Hmm, that I don't know sorry. The documented procedure in kiwi
is information how to start autoyast at boot time. Once autoyast
starts up, which it seems to do according to the message you
got, I have no idea what input data it requires or what the
above error message means.

The information about autoyast in the chapter you read is
relatively old. At the time I wrote the article the procedure
worked but I could imagine that the YaST team has done many
changes to autoyast.

I suggest you get in contact with the YaST team (https://yast.opensuse.org/contact) at SUSE to ask for assistance. I would also be interested in the result
so we can fix the docs if required

Sorry I'm not of great help with YaST
signature.asc
Reply all
Reply to author
Forward
0 new messages