Dead Package - why still in repository?

Asked by KeithG

This is a dead package. Last development was under Hardy!? This has been superseded by forked-daapd which is in the Debian repositories. Why is it not in Ubuntu, yet. In Maverick and Natty, if you enable the squeeze, wheezy or sid repository and install the forked-daapd package, it installs and runs properly on 10.10 and 11.04. Please remove this package and add the current firefly server or just add the forked-daapd as an option in the repository...

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu mt-daapd Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

Adding debian repos is not advised or supported in Ubuntu.

Revision history for this message
KeithG (grider-4) said :
#2

 The question is: "why is the current, under development, replacement for this mt-daapd package not in the ubuntu repositories?"

I get that adding a debian repo is not advised, but that does not answer the question. My point is that it should not be that big of a deal to add it to the ubuntu repository as it 'works' if you add the sid repository and install the package.

Revision history for this message
Eliah Kagan (degeneracypressure) said :
#3

I recommend you report this as a bug affecting mt-daapd. You should tag your bug needs-packaging. Before filing the report, please read https://help.ubuntu.com/community/ReportingBugs carefully. If you want a current version of mt-daapd to be made available for use in already-released versions of Ubuntu (and not just in Oneiric and later), please also read https://help.ubuntu.com/community/UbuntuBackports (especially https://help.ubuntu.com/community/UbuntuBackports#How%20to%20request%20new%20packages). Before reporting the bug, you should search to see if it's already been reported. While reporting it, you should make sure to explain why it is important for mt-daapd to be updated. After reporting it, I recommend linking your bug and this question to each other using the "Link existing bug" link near the top of this bug page. (Nonetheless, your bug report should be complete and self-contained--it should not be necessary for the Ubuntu developers to refer to this question in order to fully understand and appreciate your bug report.)

Can you help with this problem?

Provide an answer of your own, or ask KeithG for more information if necessary.

To post a message you must log in.