Created attachment 8457 [details] packages conflict in automatic update Mageia 6 STA1 Description of problem: Automatic update Mageia 6 STA1 normally occurs, but in the end, there is some packages conflict error message, with the result that several packages are not installed. Version-Release number of selected component (if applicable): During the automatic update Mageia 6 STA1 How reproducible: Steps to Reproduce: 1. 2. 3.
I reported error in the black screen bug https://bugs.mageia.org/show_bug.cgi?id=19294#c11 not know if it is related to this error packets.
From the log plasma-workspace <5.7.3 conflicts with mageia-plasma5-config-6-21.mga6.noarch Assigning to KDE team. Also CC'ing Thierry for: typelib (Cogl) = 2.0 is required by mutter-3.22.0-6.mga6.x86_64 libkeyutils.so.1 () (64bit) is required by gdm-3.22.0-1.mga6.x86_64 libkeyutils.so.1 (KEYUTILS_0.3) (64bit) is required by gdm-3.22.0-1.mga6.x86_64 libkeyutils.so.1 (KEYUTILS_1.5) (64bit) is required by gdm-3.22.0-1.mga6.x86_64
CC: (none) => thierry.vignaudAssignee: bugsquad => kde
CC: (none) => bequimao.de
The missing deps are missing b/c of the first issue (undeclared file conflict, thus detected at transaction install time). The transaction which would lead to a file conflict isn't run by rpmlib, and any further transaction where a package relies on one of the package in a previous skip transaction will also fails b/c of missing dep, ... (cascade effect)
CC: thierry.vignaud => neoclust, zen25000Source RPM: (none) => plasma-workspace-5.7.95-6.mga6.x86_64, mageia-plasma5-config-6-4.4.mga6.noarch
Created attachment 8462 [details] update to plasma-workspace spec Seems that I have the updated plasma-workspace here with the conflict but forgot to commit/push it. @neoclust - please confirm this is OK and I will do it.
seems OK, please do :)
CC: (none) => mageia
In two installations of Mageia 6 STA1 I checked today, October 1st, all the updates were installed without problems. There was no conflict of packages, and the plasma environment is working correctly Thank you
Thanks for testing. Closing then.
Status: NEW => RESOLVEDResolution: (none) => FIXED