On 2 August 2010 21:48, Neil Williams <[email protected]> wrote: > It is possible (even likely) that libforks-perl will have to be removed from > testing but it would appear that gscan2pdf could revert to the internal perl > threading support (as in previous releases) as part of the fix for the RC bug > against gscan2pdf (#589796).
#589796 wasn't a bug in gscan2pdf, but in libglib-perl, which was fixed over the weekend. gscan2pdf has never used Perl's threading module, as libsane-perl, which is what is handled in the thread, is not thread-safe. > There is a simple patch (prepared by Chris Butler) but there should be some > discussion about the options and implications. It seems unlikely that > libforks- > perl can be reliably fixed and if converting gscan2pdf to revert to internal > perl threading support means that other bugs would appear as regressions, then > maybe gscan2pdf itself would have to be removed alongside libforks-perl. This is a huge change, and it would be good to do some extended testing before pushing this to unstable. What is the timescale? -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
