Is it possible that you have the wrong apt sources? On my test machine with Stretch I see as Amarok dependencies:

libpng16-16 (>= 1.6.2-1)
libimobiledevice6 (>= 0.9.7)
libmariadbclient18 (>= 5.5.36)
libruby2.3 (>= 2.3.0~preview2)
libtag1v5 (>= 1.9.1-2.2~)

(In reply to Slávek Banko from comment #1)
> Is it possible that you have the wrong apt sources?

I'm using the ones set by the Devuan installer, which all correctly specify Ascii as the release,

> On my test machine with
> Stretch I see as Amarok dependencies:
> 
> libpng16-16 (>= 1.6.2-1)
> libimobiledevice6 (>= 0.9.7)
> libmariadbclient18 (>= 5.5.36)
> libruby2.3 (>= 2.3.0~preview2)
> libtag1v5 (>= 1.9.1-2.2~)

I see those to, but they aren't what the package dependencies are asking for. Yes, it's true that libpng is libpng, but the package dependencies don't seem to be looking for, i.e. /usr/lib/libpng.so but rather a *package name* of libpng12-0, which is *not* the same package name as libpng16-16. If you hard code package names as dependencies in a distro that frequently package names (as Debian & derivatives do -- they seem to change with the version of the package), then you're going to run into dependency issues when installing your packages even if the dependencies are technically there, and you're going to be forced to rebuild your packages every time dependencies are changed/updated/etc. if you want to resolve those dependency issues.

Since I don't know how dpkg works, I have to ask: is it possible to specify the library (i.e. /usr/lib/<libname>.so) instead of the package name as a dependency? It seems to me a better way to do things as it would immediately resolve issues like this, and something other package managers can do (I know RPM and it's higher-level package managers can handle that just fine).

Created attachment 2860 [details]
Main sources.list for apt

Created attachment 2861 [details]
Apt sources for TDE

In apt sources for Trinity you have one little bug - instead of extras-r14 it should be only extra-r14 (without final 's').

When I set apt sources with this small bug, the correct apt lists were not loaded. This could be the reason why on your machine some old apt lists are used instead of a new one.

When I had properly set up apt sources, the dependencies of amarok packages were fine - as I mentioned them above.

(In reply to Slávek Banko from comment #5)
> In apt sources for Trinity you have one little bug - instead of extras-r14
> it should be only extra-r14 (without final 's').

Corrected, though I'm not sure where I got the extras-r14 from since it wsn't mentioned in the install instructions (only main-r14 and deps-r14 are mentioned).

> When I set apt sources with this small bug, the correct apt lists were not
> loaded. This could be the reason why on your machine some old apt lists are
> used instead of a new one.

Can you point me to which of my apt sources is old? As mentioned before, I am using the ones set up by the Devuan installer. And, I used the TDE install directions here:

https://wiki.trinitydesktop.org/Preliminary_Stable_Builds

> When I had properly set up apt sources, the dependencies of amarok packages
> were fine - as I mentioned them above.

I am now getting the correct dependencies for Amarok (and others), but that is regardless of whether or not I include extra-r14 in my TDE sources. My guess is that whoever is in charge of the packages corrected the dependencies and rebuilt.

(In reply to Kristopher from comment #6)
> (In reply to Slávek Banko from comment #5)
> > In apt sources for Trinity you have one little bug - instead of extras-r14
> > it should be only extra-r14 (without final 's').
> 
> Corrected, though I'm not sure where I got the extras-r14 from since it
> wsn't mentioned in the install instructions (only main-r14 and deps-r14 are
> mentioned).
> 
> > When I set apt sources with this small bug, the correct apt lists were not
> > loaded. This could be the reason why on your machine some old apt lists are
> > used instead of a new one.
> 
> Can you point me to which of my apt sources is old? As mentioned before, I
> am using the ones set up by the Devuan installer. And, I used the TDE
> install directions here:
> 
> https://wiki.trinitydesktop.org/Preliminary_Stable_Builds
> 

I assumed you were upgrading from the previous Debian / Devuan version. In this case, in the /var/lib/ could be apt lists from the previous version => with previous dependencies.

> > When I had properly set up apt sources, the dependencies of amarok packages
> > were fine - as I mentioned them above.
> 
> I am now getting the correct dependencies for Amarok (and others), but that
> is regardless of whether or not I include extra-r14 in my TDE sources. My
> guess is that whoever is in charge of the packages corrected the
> dependencies and rebuilt.

Let me say that I ought to know something about it when I'm the one who prepares and builds these packages :)

You can see that the packages are unchanged from 2018/06/01:

http://mirror.ppa.trinitydesktop.org/trinity-sb/pool/main-r14/a/amarok-trinity/

Because it seems that the problem was due to incomplete apt lists, I close this bug report with the statement that it is not our problem.

(In reply to Slávek Banko from comment #8)
> Because it seems that the problem was due to incomplete apt lists, I close
> this bug report with the statement that it is not our problem.

What am I missing from my apt sources?

(In reply to Kristopher from comment #9)
> (In reply to Slávek Banko from comment #8)
> > Because it seems that the problem was due to incomplete apt lists, I close
> > this bug report with the statement that it is not our problem.
> 
> What am I missing from my apt sources?

Except for minor mistake with 'extras-r14' × 'extra-r14', your apt sources.list looks fine.

The problem is that the dependencies listed in comment 0 correspond to informations from apt sources for Jessie. I do not know if you missed to do apt-get update after changing sources.list or if apt-get update failed for some reason.

As I say on bug 2873, this is not a Debian-side bug, it's not a Trinity-side bug, the problem is in the files on your computer.