Kalpa microos problem during auto-update of the system

Hello to All, first msg in the forum, hoping choose the right section …
auto transactional-update stopped working since some days due to a conflict
Testo preformattato
Apr 02 08:30:50 PC192.168.1.9 transactional-update[16931]: Computing distribution upgrade…
Apr 02 08:30:50 PC192.168.1.9 transactional-update[16931]: Problem: the to be installed patterns-microos-desktop-kde-5.0-87.2.x86_64 requires ‘kf6-baloo-file’, but this requirement cannot be provided
Apr 02 08:30:50 PC192.168.1.9 transactional-update[16931]: not installable providers: kf6-baloo-file-6.0.0-1.2.x86_64[repo-oss]
Apr 02 08:30:50 PC192.168.1.9 transactional-update[16931]: Solution 1: deinstallation of baloo5-file-5.115.0-1.1.x86_64
Apr 02 08:30:50 PC192.168.1.9 transactional-update[16931]: Solution 2: deinstallation of patterns-microos-desktop-kde-5.0-86.1.x86_64
Apr 02 08:30:50 PC192.168.1.9 transactional-update[16931]: Solution 3: keep obsolete patterns-microos-desktop-kde-5.0-86.1.x86_64
Apr 02 08:30:50 PC192.168.1.9 transactional-update[16931]: Solution 4: break patterns-microos-desktop-kde-5.0-87.2.x86_64 by ignoring some of its dependencies
Apr 02 08:30:50 PC192.168.1.9 transactional-update[16931]: Choose from above solutions by number or cancel [1/2/3/4/c/d/?] (c): c
Apr 02 08:30:50 PC192.168.1.9 transactional-update[16931]: 2024-04-02 08:30:50 Application returned with exit status 4.
Apr 02 08:30:51 PC192.168.1.9 transactional-update[16123]: ERROR: zypper --no-cd dup on /.snapshots/87/snapshot failed with exit code 4!
Apr 02 08:30:51 PC192.168.1.9 transactional-update[16123]: Use ‘–interactive’ for manual problem resolution.
Apr 02 08:30:51 PC192.168.1.9 transactional-update[16123]: Removing snapshot #87
Apr 02 08:30:51 PC192.168.1.9 transactional-update[17002]: 2024-04-02 08:30:51 tukit 4.6.0 started
Apr 02 08:30:51 PC192.168.1.9 transactional-update[17002]: 2024-04-02 08:30:51 Options: abort 87
Apr 02 08:30:51 PC192.168.1.9 transactional-update[17002]: 2024-04-02 08:30:51 Discarding snapshot 87.
Apr 02 08:30:52 PC192.168.1.9 transactional-update[17002]: 2024-04-02 08:30:52 Transaction completed.
Apr 02 08:30:52 PC192.168.1.9 transactional-update[16007]: transactional-update finished
Apr 02 08:30:52 PC192.168.1.9 systemd[1]: transactional-update.service: Main process exited, code=exited, status=1/FAILURE
Apr 02 08:30:52 PC192.168.1.9 systemd[1]: transactional-update.service: Failed with result ‘exit-code’.
Apr 02 08:30:52 PC192.168.1.9 systemd[1]: Failed to start Update the system.
Apr 02 08:30:52 PC192.168.1.9 systemd[1]: transactional-update.service: Consumed 6.742s CPU time.
how to solve this conflict ? just wait for some general update and software availability?
Thanks

I did it by myself, transactional-update rm the second choice,
reboot
you may then start a transactional-update dup,
there will be 1000+ packages to fetch

1 Like

The easier way to do this is sudo transactional-update dup -i to make your dup interactive, so you can just tell it to remove baloo5-file as part of the dup process.

3 Likes

Thanks @geoW, @sfalken, super-fast and very effective. Update worked fine as by suggestion.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.