| Summary: | sddm-0.13.0-2mga6 Impossible installation | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Georges Eckenschwiller <paiiou> |
| Component: | RPM Packages | Assignee: | Florian Hubold <doktor5000> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | critical | ||
| Priority: | Normal | CC: | doktor5000 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Georges Eckenschwiller
2016-03-08 15:54:09 CET
This may be caused by a artially synced mirror, or if some of the dependent packages are being updated in the meantime. Can you please show the output from an installed system, where sddm is not installed yet from the command LC_ALL=C urpmi sddm --auto Status:
NEW =>
ASSIGNED This is most likely due to Qt5 being updated to the rc2 version right now. I updated my mirrors with the last version of qt5. I again tried the installation with messages in English The following package cannot be installed because it depend on packages that are older than the installed one: I then reconstructed the sddm package with the last version of qt5, just by modifying the release. I always obtain the same error! It is possible that a component of sddm source is built with an older version of qt ? (In reply to Georges Eckenschwiller from comment #3) > I updated my mirrors with the last version of qt5. So you're using a local mirror? For the dependencies, sddm could be normally installed here, and it's also not listed on http://check.mageia.org/cauldron/dependencies.html hence this shouldn't be the issue. You're also the only one to report this, hence it's probably a local issue. Hello Florian, Yes, it is well a local problem. I was able to determine that it is not a problem due to the local mirror, but in the procedure of installation (more specially packages which are missing) I have again to make a number of test installations to be able to determine what is lissing. (In reply to Georges Eckenschwiller from comment #5) > Yes, it is well a local problem. Closing then. Status:
ASSIGNED =>
RESOLVED Just for information. I confirm that the problem was local. To arrive at the simplest possible installation, I have customized the package mageia-theme: I separated the plymouth animation, to be able to not install it systematically. A consequence was that the line Prospace becomes: mageia-theme-Default = 1.5.0.44-13.paii6 I added Provides: mageia-theme and it works again. Georges (alias Paiiou) |