trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: May 2016

Re: [trinity-devel] suse 42.1 - crucial(?) trinity package(s) require an unavailable package

From: Felix Miata <mrmazda@...>
Date: Sun, 15 May 2016 04:21:13 -0400
François Andriot composed on 2016-05-14 12:19 (UTC+0200):

> 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;.

Strange follow-up behavior:

I did rpm -e --nodeps. That caused crash notifier popups on login, and no 
sound for multiple login/logout cycles, including one reboot. Next I force 
reinstalled trinity-libarts-akode, which pulled in trinity-akode. More 
login/logout cycles and still the crashing with no sound. Crashing stopped 
and sound returned after a second reboot following the forced installation.

> 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.

:-(
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/