It's not a new problem in the sense that we didn't introduce it in POPFile v1.0.0 and it's a nasty bug because it's Perl that's crashing and not us. My suggestion is that we investigate this bug, but that we don't hold 1.0.0 for it.
John.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>> My suggestion is that we investigate this bug, but that we don't hold 1.0.0 for it. <<
I agree. Let's get 1.0.0 out and investigate later.
The release of ActivePerl 5.10.0 has just been announced. Perhaps upgrading to it might make a difference? The last few builds of 5.8.8 introduced some new dependencies that took a while to sort out. I think it is safer to stay with 5.8.8 for the 1.0.0 release.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I agree then. Since it requires UI access and POP download, I am guessing you must have forking turned on to be affected. Since our Windows default is forking off, this shouldn't be a major problem. Probably why it hadn't been found before.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Folks,
One small change (the default skin) and I think we are there...
http://popfile.sf.net/popfile-1.0.0RC8.zip
http://popfile.sf.net/popfile-1.0.0RC8-windows.zip
Anything stopping RC8 from being the final?
John.
I thought this new crash report by Naoki might be worth investigating before we release 1.0.
https://sourceforge.net/forum/message.php?msg_id=4675316
It's not a new problem in the sense that we didn't introduce it in POPFile v1.0.0 and it's a nasty bug because it's Perl that's crashing and not us. My suggestion is that we investigate this bug, but that we don't hold 1.0.0 for it.
John.
>> My suggestion is that we investigate this bug, but that we don't hold 1.0.0 for it. <<
I agree. Let's get 1.0.0 out and investigate later.
The release of ActivePerl 5.10.0 has just been announced. Perhaps upgrading to it might make a difference? The last few builds of 5.8.8 introduced some new dependencies that took a while to sort out. I think it is safer to stay with 5.8.8 for the 1.0.0 release.
Brian
As you say it's not a good idea to go with 5.10.
John.
I agree then. Since it requires UI access and POP download, I am guessing you must have forking turned on to be affected. Since our Windows default is forking off, this shouldn't be a major problem. Probably why it hadn't been found before.
>> Since it requires UI access and POP download, I am guessing you must have forking turned on to be affected. <<
Yes. The user is sharing one POPFile installation with several users
so he needs to use the forking option.
I guess the most of the users are using POPFile without forking on
Windows.
Naoki
>> My suggestion is that we investigate this bug, but that we don't hold 1.0.0 for it. <<
I agree.
I think it's time for us to release POPFile v1.0.0.
Naoki
I ran the release notes through a spell checker and found two missing letters. Paragraph 3 line 2 of Nihongo improvements should be:
was not being shown correctly when invalid characters were used in the
"being" and "correctly" were misspelled.
Other than that, I say go.