apache2-dev dependency is on wheezy/testing

[Afterster]

Since debian wheezy, apache2-dev package required by ampache-debian to create packages is on testing repo.
The real dependency seems to be dh-apache2 which is currently only provided through apache2-dev.
How to replace this dependency with one in stable stage? It messup all dependencies for generated package (see https://github.com/ampache/ampache-debian/releases/tag/3.7.1-develop1 release) with higher and testing versions...

[minnesotags]

Hello, I'm not sure if my issue is related to this. Actually, I'm trying to translate what this comment means. I tried to install 3.7.1-develop1 on wheezy and there are problems with links not working from the initial home page. The links for home, localplay, admin, and modules do not work. They also provoke no response in the logs. Also the links for playing a selection, adding to playlist and some others do not work.

Is the apache2-dev package on testing repo? Or are you saying the ampache-debian in testing repo says it requires apache2-dev package since wheezy, but really requires dh-apache2?

I haven't had any flags saying my dependencies are messed up, but this ampache version (which I upgraded from the 3.6alpha) isn't working, so....

[Afterster]

This issue is a build issue, you shouldn't be impacted if you only downloaded the .deb file.
Yours could be a cache issue (did you try to clear your browser cache?) or maybe something wrong with the package, I will try to takes some time to work again on debian packaging.

[minnesotags]

I changed my directory name, uninstalled and did a fresh reinstal (except for my database) using the Debian apt-get package. This time, after logging in it gave a plain-text theme with broken links to config, etc. (probably a cache thing?). By typing into the address bar I was able to get to an admin page and change themes and now links are working, at least on 3.6-alpha -1-dev. I haven't upgraded yet. So yes, this may have been a cache problem, but also a theme problem?