Public bug report changed:
https://launchpad.net/malone/bugs/6231

Comment:
Does this mean that in Dapper quicktime etc. will be working correctly by
referencing the new location?

As far as breezy goes, I'm currently forcing the version to the standard
build.
I found that the backport was a little buggy. I couldn't get a capture using
an AVI file type without a crash. Only RAW DV format worked - pritty
restrictive.

Personnally, I think it would be better to pull it as it has a few problems
and as such doesn't reflect too good on backports or ubuntu.

many thanks for your help and great work

On 1/3/06, John Dong <[EMAIL PROTECTED]> wrote:
>
> Public bug report changed:
> https://launchpad.net/malone/bugs/6231
>
> Comment:
>
> http://changelogs.ubuntu.com/changelogs/pool/main/libq/libquicktime/libquicktime_0.9.7-0.4ubuntu1/changelog
>
> QUOTE:
>   * debian/lqt_compat_header.stub: Template for compatibility headers to
>     facilitate the move from /usr/include/quicktime to /usr/include/lqt.
>
>
> The problem is that the quicktime library changed locations from Breezy
> to DApper, and the Dapper package does not have tight enough build
> dependencies to catch the problem.
>
> As far as "fixes", the choices are:
>
> (1) Have Dapper Kino also check in the old header location
> (2) Pull the backport.
>


Attachment: unnamed
Type:       text/html; charset=ISO-8859-1
URL:        http://librarian.launchpad.net/1489063/unnamed

--
ubuntu-backports mailing list
[email protected]
http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports

Reply via email to