Assuming that this really is a bug in the kernel... Given that the reporter claimed that the problem affected 2.6.8-1-sparc64-smp 2.6.8-5 too, should it really be blocking kernel-image-2.6.8-2-sparc64 from entering sarge?
Attachment:
p7sDVvV9_46zu.p7s
Description: S/MIME cryptographic signature