reopen 307968 tag 307968 sarge thanks This bug isn't fixed yet in sarge. I reviewed the changes in the new upstream to see if I could just accept it into sarge, and they're not *too* bad, but I'm concerned that accepting the unrelated active.read changes could introduce new bugs into sarge.
Backporting the security fix and uploading via t-p-u seems quite doable. Just moving a couple of free()s, really. Would you/someone like to do that, or is there info about the active.read change that I should know the make a better decision? -- see shy jo
signature.asc
Description: Digital signature
