Libass is outdated and needs updating *patches included*

Bug #326051 reported by Eric Appleman
4
Affects Status Importance Assigned to Milestone
libass (Ubuntu)
Fix Released
Undecided
Rolf Leggewie
Nominated for Jaunty by Eric Appleman

Bug Description

Binary package hint: libass1

Package: libass1 and libass-dev
Version: 0.9.5-2
Severity: normal

Patches that mitigate this problem can be found here: http://greg.geekmind.org/mplayer/

-- System Information:
Debian Release: 5.0
  APT prefers jaunty-updates
  APT policy: (500, 'jaunty-updates'), (500, 'jaunty-security'), (500, 'jaunty-proposed'), (500, 'jaunty-backports'), (500, 'jaunty')
Architecture: i386 (i686)

Kernel: Linux 2.6.28-6-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libass1 depends on:
ii libc6 2.9-0ubuntu9 GNU C Library: Shared libraries
ii libenca0 1.9-6 Extremely Naive Charset Analyser -
ii libfontconfig1 2.6.0-1ubuntu4 generic font configuration library
ii libfreetype6 2.3.7-2ubuntu1 FreeType 2 font engine, shared lib
ii zlib1g 1:1.2.3.3.dfsg-12ubuntu1 compression library - runtime

libass1 recommends no packages.

libass1 suggests no packages.

-- no debconf information

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: libass1 0.9.5-2
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: libass
Uname: Linux 2.6.28-6-generic i686

Tags: apport-bug
Revision history for this message
Eric Appleman (erappleman) wrote :
Revision history for this message
Eric Appleman (erappleman) wrote :

Just a heads up, the coder says that there will be more fixes in the near future.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

Thank you for reporting this issue and providing patches. They are much more likely to get anyone's attention if you attach them here and mark them as patches. Some people have set up searches for this kind of thing. You're currently flying below their radar.

Revision history for this message
Eric Appleman (erappleman) wrote :

Those patches are outdated. Here are the newest ones by Greg.

(13 patches in a zip. BE SURE TO "SAVE AS".)

Revision history for this message
Eric Appleman (erappleman) wrote :

Those patches are outdated. Here are the newest ones by Greg.

(13 patches in a zip. BE SURE TO "SAVE AS".)

Revision history for this message
Eric Appleman (erappleman) wrote :

Sorry for the double post. The files are identical.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

Alright. Thank you for the update.

Just out of curiousity. Have you tried pushing these patches upstream or to Debian?

Revision history for this message
Rolf Leggewie (r0lf) wrote :

It looks like Debian has removed what Ubuntu ships as libass1 from their archives. They only ship libass3. There are no open bug reports in the Debian BTS against libass3.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

Most of the patches you have attached here either reverse-apply (IOW, they have been incorporated upstream) or they fail and thus are outdated. Is there anything left to be done for the Karmic version?

Changed in libass (Ubuntu):
assignee: nobody → Rolf Leggewie (r0lf)
status: New → Incomplete
Revision history for this message
Eric Appleman (erappleman) wrote :

Yeah, libass could use further packaging as it gets updated to 0.9.7 in the near future.

http://code.google.com/p/libass/

Revision history for this message
Rolf Leggewie (r0lf) wrote :

Thank you for the quick reply.

Packaging needs arising in the future will be dealt with in due course (and it's best to deal with them in Debian). Closing this ticket as fix released.

Thank you for bringing this issue to our attention.

Changed in libass (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.