| Summary: | 64-bit install aborts if core 32 rep is enabled, works if it is disabled | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Frank Griffin <ftg> |
| Component: | Installer | Assignee: | Mageia tools maintainers <mageiatools> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | kde, marja11 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | drakx-installer-stage2 | CVE: | |
| Status comment: | |||
| Attachments: |
ddebug.log.gz
install.log |
||
|
Description
Frank Griffin
2018-02-19 01:35:47 CET
Created attachment 9995 [details]
ddebug.log.gz
Created attachment 9996 [details]
install.log
(In reply to Frank Griffin from comment #0) > The question is why a 64-bit install would require both the i586 > and x86_64 versions of wacom2. The install enables all of the repositories, > 32-bit and 64-bit alike. No idea, assigning to the mageiatools maintainers CC:
(none) =>
marja11 To clarify, this only occurs if Plasma is selected as a desktop in the Custom install package selection panel. If it isn't, the install completes. I worked around this by de-selecting all DEs and then adding them in once the new system was booted. So it's definitely related to Plasma, although maybe only to the default package selection list used by the installer for Plasma. (In reply to Frank Griffin from comment #4) > To clarify, this only occurs if Plasma is selected as a desktop in the > Custom install package selection panel. If it isn't, the install completes. > I worked around this by de-selecting all DEs and then adding them in once > the new system was booted. So it's definitely related to Plasma, although > maybe only to the default package selection list used by the installer for > Plasma. CC'ing the KDE maintainers CC:
(none) =>
kde Additional info: As with all my fresh installs, I enable all repositores including the 32-bit ones even though this is a 64-bit install. That might be what triggers the inclusion of both libwacom2 packages. Still happening today. (In reply to Frank Griffin from comment #6) > Additional info: > > As with all my fresh installs, I enable all repositores including the 32-bit > ones even though this is a 64-bit install. That might be what triggers the > inclusion of both libwacom2 packages. > > Still happening today. I did a new round of testing, and the symptoms change from day to day in cauldron, but I believe I've narrowed it down. What causes the problem is enabling the Core 32 repository. Plasma is no longer the primary suspect. An install with all desktops (and all package categories except Games) selected will succeed if Core 32 is disabled and fail if it is enabled. An install with Plasma unselected but Core 32 enabled fails as well. The curious thing is that with Core 32 disabled, no errors at all are produced, which makes me wonder why packages from Core 32 are brought in with it enabled but cause no failed dependencies with it disabled.
Frank Griffin
2018-04-08 20:13:59 CEST
Summary:
Plasma Install Aborts =>
64-bit install aborts if core 32 rep is enabled, works if it is disabled This appears to have been fixed. Resolution:
(none) =>
FIXED |