Bug#495620: any chance of fix making it to release?

The latest libcairo2_1.6.4-6.1 did not contain this fix. I had to downgrade using your packages. Any chance your patch to libcairo2_1.6.4-6.0.1 can make it into the next upgrade? Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL

Bug#495620: any chance of fix making it to release?

Mark Hedges wrote: The latest libcairo2_1.6.4-6.1 did not contain this fix. I had to downgrade using your packages. Any chance your patch to libcairo2_1.6.4-6.0.1 can make it into the next upgrade? I don't now where this fix that was in Mike's build called libcairo2_1.6.4-6.0.1 came from.

Bug#495620: any chance of fix making it to release?

On Mon, 20 Oct 2008, Dave Beckett wrote: I don't now where this fix that was in Mike's build called libcairo2_1.6.4-6.0.1 came from. It's not in the #495620 comments and I don't have the source to this build either. So those are reasons enough for not including it; apart from not wanting

Bug#495620: any chance of fix making it to release?

On Mon, Oct 20, 2008 at 12:21:53PM -0700, Mark Hedges wrote: On Mon, 20 Oct 2008, Dave Beckett wrote: I don't now where this fix that was in Mike's build called libcairo2_1.6.4-6.0.1 came from. It's not in the #495620 comments and I don't have the source to this build either. So