FS#19452 - [moc] wavpack support missing

Attached to Project: Arch Linux
Opened by Philipp (hollunder) - Thursday, 13 May 2010, 23:07 GMT
Last edited by Dan Griffiths (Ghost1227) - Thursday, 22 July 2010, 04:44 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Dan Griffiths (Ghost1227)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I noticed that some files don't play anymore since the recent update. It turns out that wavpack support is missing, at least in the x86_64 built.

Additional info:
* package version(s)
moc 2.4.4-1

Steps to reproduce:
Try to add a .wv in moc 2.4.4-1, it won't let you.
This task depends upon

Closed by  Dan Griffiths (Ghost1227)
Thursday, 22 July 2010, 04:44 GMT
Reason for closing:  None
Additional comments about closing:  Please let me know if/when upstream support is readded.
Comment by Philipp (hollunder) - Friday, 14 May 2010, 00:33 GMT
Is it confirmed that i686 isn't affected? I can only test x86_64.
Comment by Dan Griffiths (Ghost1227) - Friday, 14 May 2010, 02:10 GMT
Last time they were rebuilt, they were built with --with-wavpack... Are you sure you have wavpack itself installed? It's an optdepend...
Comment by Philipp (hollunder) - Friday, 14 May 2010, 02:17 GMT
Yes, I'm certain I have wavpack installed. It also stopped working after the recent update. I believe that wavpack simply wasn't installed when the binary was built. And as I said, I can't say whether both branches are affected or not, i686 would need to be tested.
Comment by Dan Griffiths (Ghost1227) - Friday, 14 May 2010, 02:31 GMT
Hmm... it was built in a clean chroot, and wavpack is a makedepend so i can almost guarantee it was installed. I've been wrong before however :P I'll do a rebuild in a few minutes and we can test it out
Comment by Philipp (hollunder) - Friday, 21 May 2010, 12:13 GMT
Actually I just want to comment on it. It still doesn't work, and now I start to understand why. I tried building it locally and it didn't work either. It very much looks like wavpack support was dropped by upstream. It's missing in the output of ./configure --help and it can't be found in /decoder_plugins/ unlike all the others. Sorry for not noticing this earlier. I'll try to contact upstream and see what comes out of it. Best, Philipp

Loading...