Bug 14738 - update conflicts: sweet home 3d, jline-2, xbean, slf4j
Summary: update conflicts: sweet home 3d, jline-2, xbean, slf4j
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-06 11:05 CET by Stéphane Couturier
Modified: 2015-01-26 13:22 CET (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Stéphane Couturier 2014-12-06 11:05:46 CET
Hi,

After a very successful update from Mga4 to Mga5beta1 using the DVD upgrade, I have one conflict for the update of the package jline-2:

Désolé, le paquetage suivant ne peut pas être sélectionné :
- jline-2.10-3.mga5.noarch (en raison de conflit avec xbean-3.16-5.mga5.noarch) 

xbean is not installed, and when i try to install it, I get:

Désolé, le paquetage suivant ne peut pas être sélectionné :
- xbean-3.16-5.mga5.noarch (car mvn(commons-logging:commons-logging-api) est non satisfait)

I did not find any package remotly named like this commons-logging.


I also try to uninstall jline-2, which uninstalled Sweet Home 3D (java based).

When trying to install Swwet Home 3D again, I get this result:
Désolé, le paquetage suivant ne peut pas être sélectionné :
- sweethome3d-4.5-2.mga5.noarch (en raison de conflit avec xbean-3.16-5.mga5.noarch, en raison de conflit avec xbean-3.16-5.mga5.noarch, en raison de conflit avec xbean-3.16-5.mga5.noarch)

Is there a dependency issue or is there something broken on my side?
Thank you,
Comment 1 Stéphane Couturier 2014-12-07 08:54:31 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

Comment 2 Christiaan Welvaart 2014-12-07 10:23:41 CET
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

Comment 3 Stéphane Couturier 2014-12-07 11:35:02 CET
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.
Comment 4 Doug Laidlaw 2015-01-18 16:16:33 CET
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

Comment 5 Christiaan Welvaart 2015-01-18 21:20:22 CET
(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.
Comment 6 David GEIGER 2015-01-26 13:22:27 CET
I close this bug as it is now fixed on Cauldron.

All java stack is fixed and ready. :)

Status: NEW => RESOLVED
CC: (none) => geiger.david68210
Resolution: (none) => FIXED


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