[Please reply-to-all, including the bug address.]

On Sat, 2011-05-28 at 23:17 +0000, Peter . wrote:
> The issue is now resolved after updates deployed some time last
> week.  
> 
> Do you think there would be any value in determining which update
> resolved it, or should we consider this a closed / invalid issue ?
[...]

The most important thing is the version, really.  I assume it was
2.6.39-1?

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to