Advice on targetting Leap 16.0

20 views
Skip to first unread message

glid...@googlemail.com

unread,
Oct 19, 2025, 6:55:27 AMOct 19
to kiwi
I'm just trying to convert my appliance to Leap 16.0 and running into problems. I looked here: https://github.com/OSInside/kiwi-descriptions/tree/main/suse/x86_64, but don't see a 16.0 description.

My immediate problem is that no openSUSE-release package is found.

When I moved to 15.6, the problems I ran into was not including all the required repos, but that doesn't look to be the problem this time.

Marcus Schäfer

unread,
Oct 21, 2025, 4:26:22 AMOct 21
to 'glid...@googlemail.com' via kiwi
Hi,
I added an example image build for Leap16 here:

https://github.com/OSInside/kiwi-descriptions/tree/main/suse/x86_64/suse-leap-16.0

You are right, several things changed, but the example should help
to get you started on Leap16

Hope this helps

Regards,
Marcus
--
Public Key available via: https://keybase.io/marcus_schaefer/key.asc
keybase search marcus_schaefer
signature.asc

glid...@googlemail.com

unread,
Oct 21, 2025, 5:55:06 AMOct 21
to kiwi
Awesome, thank you Marcus. Yeah, that'll do it.

glid...@googlemail.com

unread,
Oct 22, 2025, 9:11:40 AMOct 22
to kiwi
That helped a lot, but now I see this:

[ ERROR   ]: 13:55:34 | KiwiCommandError: chroot: stderr: (no output on stderr), stdout: /bin/dracut: line 1087: /sys/module/firmware_class/parameters/path: No such file or directory
dracut[E]: No '/dev/log' or 'logger' included for syslog logging
realpath: /lib/modules/6.12.0-160000.5-default: No such file or directory
dracut[F]: Cannot find module directory
dracut[F]: and --no-kernel was not specified

I'm aware of /lib moving to /usr/lib and the usual presence of a soft link, but the link doesn't seem to be present in the in-construction image directory. I've failed to track down why I'm seeing this and presumably you don't. I've diffed my appliance config with yours. I do have more repos and more packages, but I don't see anything obvious... unless it's my inclusion of the packages kernel-default-extra and kernel-firmware.

Similarly, I can't see the cause of the No /dev/log message. I randomly tried adding syslog-service, but didn't help.

Any more advice would be greatly appreciated.

glid...@googlemail.com

unread,
Oct 24, 2025, 12:21:26 PMOct 24
to kiwi
It's very close to working now. I don't alter my appliance very often, and usually only to update the packages for the main app. I'd forgotten about the root folder. Mine had files in root/lib, which of course now need to be root/usr/lib. Fixing that and taking on some of the changes from the example image, I now have it booting, mounting some nfs shares, attempting to start the app. It fails to start, but I think I'll track the cause of that in time.

glid...@googlemail.com

unread,
Oct 27, 2025, 5:11:34 AMOct 27
to kiwi
All working again. There were several more changes required:
  • Set suid bit on Xorg.bin, rather than on Xorg. Apparently Xorg is now just a wrapper for Xorg.bin
  • Use agetty to autologin and then .bash_profile to call startx, rather than use openvt. I never really got to the bottom of why openvt no longer worked.
  • In the xml description, change keymap from uk to gb
  • Change my bespoke remote control keymap to .toml format (the config now looks for a .toml file - I could of patched the config instead)
Just listing these on the unlikely chance that someone else stumbles into the same problems. Thanks yet again Marcus for the help with what aren't really kiwi problems. It's impressive that - with a little help - kiwi-ng can be used without an in-depth knowledge of the workings of Linux. 

Marcus Schäfer

unread,
Oct 27, 2025, 5:43:07 AMOct 27
to 'glid...@googlemail.com' via kiwi
Hi,

> All working again. There were several more changes required:

Great to hear that, you rock :)

> * Set suid bit on Xorg.bin, rather than on Xorg. Apparently Xorg is
> now just a wrapper for Xorg.bin

Most of it is also wayland these days

> * Use agetty to autologin and then .bash_profile to call startx,
> rather than use openvt. I never really got to the bottom of why
> openvt no longer worked.

No idea either

> * In the xml description, change keymap from uk to gb

Ohh, thanks for sharing this information.

> * Change my bespoke remote control keymap to .toml format (the config
> now looks for a .toml file - I could of patched the config instead)

You mean console keymap or xkb keymap ?

> Just listing these on the unlikely chance that someone else stumbles
> into the same problems. Thanks yet again Marcus for the help with what
> aren't really kiwi problems. It's impressive that - with a little help
> - kiwi-ng can be used without an in-depth knowledge of the workings of

Thanks much, I'm happy if the builder is producing a useful image for you.
Feedback about the issues you had is always very welcome as this list
material can help others. It already helped me... uk vs. gb :)
signature.asc

glid...@googlemail.com

unread,
Oct 28, 2025, 6:58:42 AM (13 days ago) Oct 28
to kiwi
On Monday, October 27, 2025 at 9:43:07 AM UTC Marcus wrote:
> * Change my bespoke remote control keymap to .toml format (the config
> now looks for a .toml file - I could of patched the config instead)

You mean console keymap or xkb keymap ? 

Neither, I think. It's for my Infrared remove control. I had a file at root/etc/rc_keymaps/rc6_mce. I needed to rename it to  root/etc/rc_keymaps/rc6_mce.toml, and change its contents to toml format

Thanks much, I'm happy if the builder is producing a useful image for you.
Feedback about the issues you had is always very welcome as this list
material can help others. It already helped me... uk vs. gb :) 

Oh okay, good. I'll more frequently post potentially useful things that I stumble upon.

Thanks again.

 
Reply all
Reply to author
Forward
0 new messages