lp:ubuntu/karmic/libvisual-plugins

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

7. By StefanPotyra on 2009-10-11

Refresh 90_autoreconf by running autoreconf to fix FTBFS, LP: #447291.

6. By Loïc Minier on 2008-10-22

New patch, 60_no-const-vispluginfo-in-nastyfft, the static VisPluginInfo
in nastyfft was declared as const, but libvisual write to its refcount
when it visual_object_unref()s it (nasty!). This is broken at various
levels: libvisual shouldn't be writing to this static plugin which is
allocated by a dlopen()ed plugin, and it should also honor the "const
VisPluginInfo" API... Anyway, nastyfft was the only occurrence and this
fixes the crash for now; LP: #287448.

5. By Loïc Minier on 2008-10-21

* Drop autom4te.cache/ from debian/patches/90_autoreconf.patch.
* Build-dep on x11proto-xf86vidmode-dev explicitely for
  extensions/xf86vmode.h.
* Build-dep on mesa-common-dev explicitely for GL/glx.h. Note that
  libglu1-mesa-dev is needed for plugins/actor/actor_lv_gltest.c, but isn't
  checked in configure.ac.
* Drop obsolete and useless xutils and x-dev build-deps.
* Add watch file.
* Bump up standards-version to 3.8.0.
* Add ${misc:Depends} as recommended in debhelper >= 4.

4. By Brandon Holtsclaw on 2007-11-23

* Merged Ubuntu Changes
* Remove libasound-dev from build dep on KFreeBSD-amd64 and
  hurd-i386 (Closes: #451112)
* debian/patches/02_64-bit_JESS_fix.patch (Closes: #400810) applied
  from -1ubuntu3 merge
* Changed Maintainer (Closes: #451213)

3. By David Schleef on 2006-05-19

* New upstream release.
 - builds with gcc-4.x (Closes: #343006)
* Remove libasound-dev from build dep on KFreeBSD-i386 (Closes: #336855)

2. By David Schleef on 2005-09-08

* New package
 - removed plugins/actor/G-Force directory because it contains
   code that is not DFSG-free.
 - This package does not compile with gcc-4.0, thus the need to
   force an older compiler. There is C++ code in here, although
   the interface is completely C-based. Since these are plugins,
   they don't export anything that depends on the C++ ABI, but
   there could theoretically be problems if an application that
   uses a different C++ ABI loads these plugins, thus causing two
   libstdc++ .so's to be loaded simultaneously.

1. By David Schleef on 2005-09-08

Import upstream version 0.2.0.dfsg.1