Bug 23546 - M6.1 plasma5 does not install when choosing all desktop install
Summary: M6.1 plasma5 does not install when choosing all desktop install
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: ISO building group
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-07 23:14 CEST by Ben McMonagle
Modified: 2018-09-21 19:47 CEST (History)
6 users (show)

See Also:
Source RPM: task-plasma5
CVE:
Status comment:


Attachments
install report (204.17 KB, application/x-xz)
2018-09-07 23:19 CEST, Ben McMonagle
Details

Description Ben McMonagle 2018-09-07 23:14:52 CEST
Description of problem: see summary


Version-Release number of selected component (if applicable):


How reproducible:every time


Steps to Reproduce:
1.at select desktop choose custom and select all desktops
2.at reboot grub screen plasma is not available
3.
Comment 1 Ben McMonagle 2018-09-07 23:19:10 CEST
Created attachment 10359 [details]
install report
Comment 2 Marja Van Waes 2018-09-08 13:51:03 CEST
(In reply to ben mcmonagle from comment #1)
> Created attachment 10359 [details]
> install report


* second stage install running (DrakX v17.88.3)

So you're installing using the traditional iso that neoclust built, right?

I didn't look very closely, but this looks funny:
task-plasma5-minimal-5.8.7-2.1.mga6.noarch (due to conflicts with lib64kf5codecs5-5.42.0-1.1.mga6.x86_64)

I mean, shouldn't that be task-plasma5-minimal-5.12.2-1.mga6?

Assignee: bugsquad => isobuild
CC: (none) => kde, marja11

Comment 3 Dave Hodgins 2018-09-08 15:04:47 CEST
(In reply to Marja Van Waes from comment #2)
> (In reply to ben mcmonagle from comment #1)
> So you're installing using the traditional iso that neoclust built, right?
> I didn't look very closely, but this looks funny:
> task-plasma5-minimal-5.8.7-2.1.mga6.noarch (due to conflicts with
> lib64kf5codecs5-5.42.0-1.1.mga6.x86_64)
> I mean, shouldn't that be task-plasma5-minimal-5.12.2-1.mga6?

Yes it should. On an existing mageia 6 x86_64 install
$ rpm -qa|grep task-plasma5
task-plasma5-5.12.2-1.mga6
task-plasma5-minimal-5.12.2-1.mga6
Mounting the Mageia-6.1-rc-x86_64-DVD.iso image on the dir isos ...
$ tree -ifa isos/|grep task-plasma5
isos/x86_64/media/core/task-plasma5-5.8.7-2.1.mga6.noarch.rpm
isos/x86_64/media/core/task-plasma5-minimal-5.8.7-2.1.mga6.noarch.rpm

Looks like the copy of the mirrors being used to create the iso images only
has the versions from Mageia 6 core release, not the latest versions from
core updates.

CC: (none) => davidwhodgins

Comment 4 Martin Whitaker 2018-09-08 15:26:26 CEST
No, the local mirror is OK. And 5.8.7-2.1 comes from the updates section (release is 5.8.7-2). Looking in Mageia-6.1-rc-x86_64-DVD.idx, most of the plasma packages are 5.12.2-1.

CC: (none) => mageia

Comment 5 Martin Whitaker 2018-09-09 00:13:35 CEST
Looking at the ISO build logs on rabbit, in particular

  /tmp/rpmcheck_failure_Mageia-6.1-rc-x86_64

there's a whole raft of problems reported. And similar problems show up in Ben's log file, e.g, our old friend lib64kf5ksieveui_5 vs. lib64kf5ksieveui5.

When I looked at the bcd tool, I was doubtful that the package selection algorithm was reliable when updates are enabled. That's one of the reasons I decided to create a replacement for bcd.
Comment 6 Nicolas Lécureuil 2018-09-10 16:03:11 CEST
does something need to be done "package" side, to fix this issue ?

CC: (none) => mageia

Comment 7 Thomas Backlund 2018-09-10 16:21:36 CEST
Nope, as Martin noted in comment 5, bcd is not always reliable of getting latest rpms, so you might need to do some adding of specific rpms to wanted package list to help it out...

ennael should be able to tell you more...

CC: (none) => tmb

Comment 8 Martin Whitaker 2018-09-10 21:59:26 CEST
Indeed, this was one of the main reasons it took so long to get the 5.1 ISOs out the door. One of the problems is that the package selection process has a random element, so each time you build the ISOs, a fresh set of conflicts may bubble up. ennael eventually managed to get a stable build, but it took many iterations.

Do check the rpmcheck logs. If there are any errors listed there, QA will probably find them too...
Comment 9 Ben McMonagle 2018-09-11 06:54:01 CEST
(In reply to Martin Whitaker from comment #8)

> If there are any errors listed there, QA will
> probably find them too...

thanks for the vote of confidence Martin
Comment 10 Martin Whitaker 2018-09-21 19:47:21 CEST
I've tested an all-DE install using the 6.1 nonfree netinstall ISO, and that completed without any errors. So closing this, as we have abandoned the attempt to produce CI ISOs.

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.