Le 14/05/2016 11:58, Felix Miata a écrit : > > > The "trinity-libarts-akode" package requires the library > > "libakode.so.2", which is supposed to be provided by "trinity-akode" > > package. > > In your case, zypper found that it was provided by "libakode". > > > Notice that the Trinity's package for Akode is split in several smaller > > package, e.g. "trinity-akode" and several "libakode_xxx". > > > I do not even have any 'libakode' package available in my 42.1 > > installation, > > I didn't expect anyone would, since there is no such package in 42.1 > repos for zypper to find. > > > so where does it come from ? > > Maybe it is inherited from a previous opensuse release that you have > > upgraded , or it comes from another 3rd party repository... > > 42.1 in this case is an upgrade (zypper dup) from _Factory_ (before > the name change to Tumbleweed, from an installation last upgraded as > Factory in December 2014). What I don't understand is how to get rid > of the libakode package when the package manager claims other packages > depend on it. Will rpm -e --nodeps not break the TDE packages that > zypper claims depend on it? Why doesn't zypper recognize the trinity* > package(s) you mention as providing the required libs? Are the Trinity > packages broken WRT dependencies? Yes, you can forcibly remove the libakode package (rpm -e --nodeps) and then install trinity-akode , it won't break your system;. It is likely that 'libakode' was installed before Trinity on your computer, and the 'trinity-akode' does not obsolete 'libakode', so it was kept intact. François