| Summary: | update conflicts: sweet home 3d, jline-2, xbean, slf4j | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Stéphane Couturier <mageia> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | cjw, geiger.david68210, laidlaws |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
|
Description
Stéphane Couturier
2014-12-06 11:05:46 CET
I can reproduce the issue: - on a VM created from 5alpha2 live KDE 64 and updated with latest packages - on a VM created from a 4.1 live KDE 64 updgaded to 5beta1 and latest packages Messages then selecting sweethome3d the first time: Sorry, the following package cannot be selected: - sweethome3d-4.5-2.mga5.noarch then when selcting it a second time Sorry, the following package cannot be selected: - sweethome3d-4.5-2.mga5.noarch (due to conflicts with slf4j-1.7.5-4.mga5.noarch) Summary:
update conflicts: jline-2, xbean, sweet home 3d =>
update conflicts: sweet home 3d, jline-2, xbean, slf4j In general this is a known issue: a bunch of security issues was reported against java-based packages but nobody fixed them for a long time. Now someone decided to remove those packages (and several others that depend on them) from cauldron. The result is a large number of broken dependencies in cauldron, see http://check.mageia.org/cauldron/dependencies.html . What package(s) that are currently broken do you want to use directly, only sweethome3d? CC:
(none) =>
cjw Yes, SweetHome3D is the only broken package I noticed. As a workaround, I tried using the WebStart version but it isn't working .(net.sourceforge.jnlp.LaunchException: Fatal: Launch Error: Could not launch JNLP file.) So I downloaded and extracted the linux version which includes a jre from the website and ran ./SweetHome3D from a consol in the folder created. This is working fine. I notice python-pycuda in that list, Christiaan. My Beta1 (and 2) seem to come with gdb (the debugger) installed, and that conflicts with CUDA files needed by Wine. Should that be a separate bug? If gdb conflicts with anything else, it could become unusable. I never use it (I wouldn't know how!) so I simply uninstall it. CC:
(none) =>
laidlaws (In reply to Doug Laidlaw from comment #4) > I notice python-pycuda in that list, Christiaan. My Beta1 (and 2) seem to > come with gdb (the debugger) installed, and that conflicts with CUDA files > needed by Wine. Should that be a separate bug? Yes that is most likely a separate issue unrelated to this bug. I close this bug as it is now fixed on Cauldron. All java stack is fixed and ready. :) Status:
NEW =>
RESOLVED |