I'm not saying that it requires a backport of an unstable version; I'm just
saying that if by chance using dapper-updates to backport that patch does
not work, we can now accomplish the same task via the dapper-backports
manual upload mechanism. Just another failover for this pesky bug :)
On 7/13/06, Sebastien Bacher <email address hidden> wrote:
>
> that's what that bug is about, patching for the logo issue, why do you
> think it requires a backport or an unstable version rather than an easy
> patch?
>
> --
> totem-xine crash on logo (workaround inside)
> https://launchpad.net/bugs/35229
>
I'm not saying that it requires a backport of an unstable version; I'm just
saying that if by chance using dapper-updates to backport that patch does
not work, we can now accomplish the same task via the dapper-backports
manual upload mechanism. Just another failover for this pesky bug :)
On 7/13/06, Sebastien Bacher <email address hidden> wrote: /launchpad. net/bugs/ 35229
>
> that's what that bug is about, patching for the logo issue, why do you
> think it requires a backport or an unstable version rather than an easy
> patch?
>
> --
> totem-xine crash on logo (workaround inside)
> https:/
>