ffaudio plugin still not being built; no autoconf being done

[Doug McMahon]

Update -
audacious-plugins (3.2.1-1ubuntu2) precise released, still without the ffaudio plugin

Have had a bug on this for quite some time to no avail, Bug 880192, lets try again in light of todays build of the 3.1.2 source
The configure.ac & configure in the 3.2.1 source are requiring libavcodec53.40.0 as the min., likely based off of the FFmpeg source
Precise is using libav, the current libavcodec is 53.34.0 which is quite acceptable for building/using the plugin but obviously doesn't meet the source's min.

Please adjust as needed & as seen fit & do a rebuild.
Attached is a SAMPLE patch used here on the current Precise audacious-plugin source, resultant package has ffaudio enabled & working fine.

(this was additionally reported here in Onieric though the issue was slightly different. The suggested fix by RT was not ever adopted in 11.10 & may or may not be applicable now?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641701

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: audacious-plugins 3.2-1
ProcVersionSignature: Ubuntu 3.2.0-10.18-generic-pae 3.2.1
Uname: Linux 3.2.0-10-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Sat Jan 28 01:11:31 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120108)
SourcePackage: audacious-plugins
UpgradeStatus: No upgrade log present (probably fresh install)

[Doug McMahon (mc3man)]

Just to add - at least these filetypes, which should be supported, aren't due to this
.ape
.wma (2 & 3
.tta
.mpc
It's quite unbelievable that this has splipped by for the complete 11.10 dev & release whereit was fairly simple to fix & now in 12.04 where it is even simpler.

[Doug McMahon (mc3man)]

You can add .alac to that list

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Bob Bib (bobbib)]

Why did you open a new bug while the older one (#880192) is not closed yet?
I think this info should be added to that older bug and this new bug could be marked as duplicate :)

[Doug McMahon (mc3man)]

On 01/29/2012 12:09 PM, Bob Bib wrote:
> Why did you open a new bug while the older one (#880192) is not closed yet?
> I think this info should be added to that older bug and this new bug could be marked as duplicate :)
>
Because the old bug was for 11.10, a different version of audacious &
had a different reason why ffaudio was not being built. .
Additionally it has basically been upstreamed to a debian bug & it's
quite possible will not be 'closed'

So I'm calling this a new bug, if you or anyone else wish to dupe it ,
feel free

[Doug McMahon (mc3man)]

Interesting, hopefully if it's going to be rebuilt they'll get to it soon enough to resolve a ftbfs on `g_module_* that's now going to occur

[Doug McMahon (mc3man)]

And if if it's rebuilt for 12.04 - for self builders just configure the plugins with
./configure LDFLAGS='-lgmodule-2.0'
or just get rid of the LADSPA plugin altogether

[Dmitry Tantsur (divius)]

I've dispatched builds for Audacious and Audacious Plugins from Debian testing in my ppa, but they've failed:
https://launchpad.net/~divius/+archive/extreme/+build/3230849
https://launchpad.net/~divius/+archive/extreme/+build/3230850

Any ideas?

[Dmitry Tantsur (divius)]

Doug, could you help with this ftbfs issue?

[Yuri Glushaev (y-glushaev)]

Please, see a changelog of
https://launchpad.net/ubuntu/precise/+source/audacious-plugins/3.2.1-1ubuntu1

[Dmitry Tantsur (divius)]

Cool, waiting for updated packages to be published!

[Doug McMahon (mc3man)]

I will reserve judgment till the package actually shows in the repo but this doesn't look good - from the i386 build log for audacious-plugins_3.2.1-1ubuntu2

Input Plugins
  -------------
  MPEG-1 Layer I/II/III (mpg123): yes
  MPEG-2/4 AAC (aac): yes
  FFaudio (ffaudio): no

For something so Simple to fix .....

[Dmitry Tantsur (divius)]

You're right, Doug. There's no ffaudio.so in 3.2.1-1ubuntu2 as well..

[Doug McMahon (mc3man)]

The problem is they've patched configure.ac but are NOT running an autoconf to adjust the configure so the version changes aren't being applied for the build
Doing so here then allows ffaudio to be enabled, haven't finished the build yet to test if it works, there may be an additional issue with "output"

As ex. will attach the produced configure patch from an autoconf & dpkg-source --commit, note just an *example* from local build

[Dmitry Tantsur (divius)]

Well, ffaudio.diff in Debian needs 'autoreconf'

[Dmitry Tantsur (divius)]

You were faster =)

[Dmitry Tantsur (divius)]

I tried to report it to Debian maintainers, but their bug tracker is something insane, and I'm not sure whether my message is lost or just awaits publication.

[Doug McMahon (mc3man)]

Dmitry - I'm sure that they'll realize this soon and adjust as needed
Anyway the plugin now works fine here though I had to also rebuild the audacious source locally - the current repo version would just segfault once the new locally built plugin package was installed (i386

So all should be well soon though I still don't get why maintainers or packagers don't review the build logs?

[Launchpad Janitor (janitor)]

This bug was fixed in the package audacious-plugins - 3.2.1-2

---------------
audacious-plugins (3.2.1-2) unstable; urgency=low

  * Team upload.
  * Add gmodule.patch to fix build failure on Ubuntu.
  * Bump Standards-Version to 3.9.3, no changes needed.
  * Update machine-readable copyright Format to 1.0.
  * Do not disable PSF any more.
  * Run autoconf again to really apply the FFaudio patch
    (Closes: #640931, #641701, LP: #880192, #922985).

 -- Benjamin Drung <email address hidden> Sat, 25 Feb 2012 17:57:39 +0100