Ubuntu
soundtouch package

why still in 1.3.1? not 1.5?

Asked by toutiwai

Hello,

The version available in ubuntu repositories is 1.3.1, witch is from may 2006!
Why don't you try to update to 1.5.0?

http://www.surina.net/soundtouch/sourcecode.html

Just asking...

Thank you!

Johan

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu soundtouch Edit question
Assignee:
No assignee Edit question
Solved by:
Eliah Kagan
Solved:
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#1

sudo add-apt-repository ppa:micove/experimental; sudo apt-get update; sudo apt-get upgrade

Wil give you 1.5.0 in maverick.

If you log a bug the version may get included

Revision history for this message
toutiwai (owaiboulot) said : 		#2

thank you for such a fast reply!

libsoundtouch installed correctly, but soundstrech depends on "libsoundtouch0" and doesn't want to install...

I'll try a bit more... if I find something i'll tell you!

thanks

Revision history for this message
toutiwai (owaiboulot) said : 		#3

i can install "libsoundtouch0", but it forces to uninstall these packages:
-audacity
-gstreamer0.10-plugins-bad
-libsoundtouch1c2
-transmageddon

(i use maverick 10.10)

Revision history for this message
actionparsnip (andrew-woodhead666) said : 		#4

Sounds like you need them then

Revision history for this message
toutiwai (owaiboulot) said : 		#5

yes! i think so too...

i think audacity, gstreamer-bad and libsounstouch should try to match thier dependencies...

i think transmageddon depends on gstreamer-bad so no problem for it

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

As actionparsnip suggested, if you have not done so already, I recommend logging a bug about this. These packages are unlikely to be upgraded just based on the existence of this Question. Before reporting this as a bug, please read https://help.ubuntu.com/community/ReportingBugs carefully. After reporting the bug, you can link this question to it by using the "Link existing bug" link in this question.

Revision history for this message
toutiwai (owaiboulot) said : 		#7

thank you!the bug is open, should i close this question?

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

I recommend adding all the technical information you provided here (about package conflicts preventing you from using the PPA) to your bug report. You should probably edit the report itself to make it more complete, rather than posting the information in a comment, but either way is OK. There's nothing wrong with the body of your bug report containing a link to this question, but there is no need for it, since a link to the question will always appear in the bug report under Related Questions (on the right side of the page, below the lists of subscribers and notified parties), so long as this question still links to the bug report. Furthermore, it should not be necessary for developers to view this question in order to understand the full content of your bug report (including your complete argument as to why the PPA is, at present, insufficient).

If you no longer are requesting any information about this issue (except that which is covered under the bug report...in a limited sense, any feature request is a request for information, because developers will either implement the requested feature or they won't), then I recommend you close this question by marking it as Solved.

Revision history for this message
toutiwai (owaiboulot) said : 		#9

ok! thank you for all !

Revision history for this message
toutiwai (owaiboulot) said : 		#10

Thanks Eliah Kagan, that solved my question.