Question: Is there a simple way to merge local changes when "installing" one of these Release Candidates on a Linux system?
I know that after the release is tagged in CVS that I can retrieve it from there and that my local changes will then be "automagically" merged into it. I am just wondering about participating in the RC evaluation process.
--
Jim
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So I should ignore the cross platform zip file for RC3 and just do an anonymous cvs update to get it? I know that if I do a cvs update it will merge my local changes. I just don't know if I'll be getting RC3 in the process.
--
Jim
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, assuming that the very last commit that John did is in RC3, then yes, you would be getting essentially the cross-platform parts of POPFile that compose RC3.
Timing is everything tho... if one of the developers commits anything after John packaged up RC3, then you would get something other than RC3....
Scott
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I finally had a little time to get my CVS setup working again, so one developer did make a commit after RC3. It shouldn't affect your testing RC3 though Jim. Its a minor skin fix, affecting only the OceanBlue skin.
On IE6 the help box of the OceanBlue skin could become invisible some of the time so I wanted to get that fixed, just didn't have working CVS to post it. I have tested it on as many browsers as I could. I have not been able to do any Mac testing, but I don't think the original version got any either. It does make it a little worse in IE5, but IE5 was already ugly and hardly anyone uses it anymore.
If I am too late for this release thats fine.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am having a lot of trouble trying to download RC3. Average throughput is around 300 bytes per second (normally it is about ten times that rate for RC versions). I've tried over a dozen times so far over a period of several hours, using more than one ISP (download speeds from other sites are OK).
While waiting for the file, I tried running the "Mutex" tests using the new version of Mutex.pm. As reported elsewhere, the flock() version failed on my Win98SE system because flock() is not implemented on this platform.
After getting the new version of Mutex.pm I ran the "Mutex" tests again. I'm not familiar with the test suite but it was clear something was not working - the console just showed:
Running TestMutex.tst... at line:
I wondered if something had gone wrong with creating the mutex so I searched my hard disk and found that the flock() attempt had created a mutex file which meant that the new Mutex.pm was unable to create the mutex directory (because it uses the same name as the file left behind by the flock() version).
I deleted the old mutex file and the mutex test sprang into life, the spinner appeared and all 7 tests ran OK.
Can this situation happen in POPFile - if POPFile is terminated abruptly, can it leave behind a mutex that causes problems the next time POPFile is used?
So far I've managed to get 43% of RC3 and it looks like it'll take another 3 hours to get the rest.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Seems that downloading them now, I get the regular speed. In the last couple of days, sf has updated hardware and software. I guess the slowness was related to the upgrade.
Manni
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>Can this situation happen in POPFile - if POPFile is terminated abruptly, can it leave behind a mutex that causes problems the next time POPFile is used?
My Mutex code will delete the Mutex 'derectory' but will not delete the Mutex 'file'.
This problem may happen when we use RC3 after using RC2 (and RC2 crashed unexpectedly).
If POPFile is terminated abruptly, the Mutex directory will remain, but it doesn't matter. POPFile will remove the remained directory.
(You can verify this by creating a Mutex directory manually before running the test suite.)
Naoki
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks to Manni's mirror I was able to download RC3
RC3 includes addssl.zip v0.0.9 instead of the current version (0.0.10, created 3 December). If v0.0.9 is used to add SSL Support to 0.22.2 then the user will see an "exclamation mark" message box with the message:
"Module.pm patch status: No suitable patches were found"
addssl.zip 0.0.10 does not display this message (this is the only difference between these two versions).
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just noticed the welcome strings for the nttp and smtp modules are not being updated on upgrade. The POP welcome string was upgraded fine. I still have 0.21.0 for the other two. PF knows they are not default values though, it bolds the variable name on the Advanced page.
I have been using the default installer options and not manually selecting to install the extra modules for several versions. When the installer realizes I already have those installed, it always warns me using old versions is bad and lets me choose to upgrade them which I do. Its possible that is causing the problem, but needs to be fixed anyway eventually. Its very minor so could easily wait till 0.23.
Here are the settings from my popfile.cfg:
nntp_welcome_string NNTP POPFile (v0.21.0) server ready
pop3_welcome_string POP3 POPFile (v0.22.2) server ready
smtp_welcome_string SMTP POPFile (v0.21.0) welcome
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>> the welcome strings for the nttp and smtp modules are not being updated on upgrade. The POP welcome string was upgraded fine. <<
The installer does not do anything with these three "Welcome strings. It seems that POPFile always updates the POP3 "Welcome" string to use the current version number but if the NNTP and SMTP "Welcome" strings already exist in popfile.cfg then they are not updated to use the current version number.
If you shutdown POPFile and manually delete the NNTP and SMTP "Welcome" strings, new strings with the correct version number will be created the next time you start POPFile (even if NNTP and SMTP are not enabled in popfile.cfg).
>> I have been using the default installer options and not manually selecting to install the extra modules for several versions. When the installer realizes I already have those installed, it always warns me using old versions is bad and lets me choose to upgrade them which I do. Its possible that is causing the problem <<
There is no difference between manually selecting these options and answering "Yes" when the installer reminds you - both methods set the same flag which is used later on to decide which POPFile files to install.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The way the string is updated is a bit cleverer than you suggest. We look to see if the user has changed it from the default and if they have then we don't touch it; if they have not touched it then we update it.
The code that does this for POP3 needs to be copied into NNTP and SMTP.
John.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Folks,
I think we are close now. RC3 is different from RC2 in these ways:
1. New Mutex implementation from amatubu which eliminates problems on Win9x and Mac OS 9 systems.
2. Update configuration page template.
3. Improved split header parsing from Sam.
http://getpopfile.org/popfile-0.22.2RC3.zip
http://getpopfile.org/popfile-0.22.2RC3-windows.zip
John.
Question: Is there a simple way to merge local changes when "installing" one of these Release Candidates on a Linux system?
I know that after the release is tagged in CVS that I can retrieve it from there and that my local changes will then be "automagically" merged into it. I am just wondering about participating in the RC evaluation process.
--
Jim
Not sure how you have your's setup, but I just do a cvs update and it merges the local changes just fine.
Scott
So I should ignore the cross platform zip file for RC3 and just do an anonymous cvs update to get it? I know that if I do a cvs update it will merge my local changes. I just don't know if I'll be getting RC3 in the process.
--
Jim
Well, assuming that the very last commit that John did is in RC3, then yes, you would be getting essentially the cross-platform parts of POPFile that compose RC3.
Timing is everything tho... if one of the developers commits anything after John packaged up RC3, then you would get something other than RC3....
Scott
I finally had a little time to get my CVS setup working again, so one developer did make a commit after RC3. It shouldn't affect your testing RC3 though Jim. Its a minor skin fix, affecting only the OceanBlue skin.
On IE6 the help box of the OceanBlue skin could become invisible some of the time so I wanted to get that fixed, just didn't have working CVS to post it. I have tested it on as many browsers as I could. I have not been able to do any Mac testing, but I don't think the original version got any either. It does make it a little worse in IE5, but IE5 was already ugly and hardly anyone uses it anymore.
If I am too late for this release thats fine.
I am having a lot of trouble trying to download RC3. Average throughput is around 300 bytes per second (normally it is about ten times that rate for RC versions). I've tried over a dozen times so far over a period of several hours, using more than one ISP (download speeds from other sites are OK).
While waiting for the file, I tried running the "Mutex" tests using the new version of Mutex.pm. As reported elsewhere, the flock() version failed on my Win98SE system because flock() is not implemented on this platform.
After getting the new version of Mutex.pm I ran the "Mutex" tests again. I'm not familiar with the test suite but it was clear something was not working - the console just showed:
Running TestMutex.tst... at line:
I wondered if something had gone wrong with creating the mutex so I searched my hard disk and found that the flock() attempt had created a mutex file which meant that the new Mutex.pm was unable to create the mutex directory (because it uses the same name as the file left behind by the flock() version).
I deleted the old mutex file and the mutex test sprang into life, the spinner appeared and all 7 tests ran OK.
Can this situation happen in POPFile - if POPFile is terminated abruptly, can it leave behind a mutex that causes problems the next time POPFile is used?
So far I've managed to get 43% of RC3 and it looks like it'll take another 3 hours to get the rest.
Brian
I thought RC2 was a little slow to download. Compared to RC3 it was lightning fast. I gave up, it said 3 hours to start with for me on broadband.
About an hour ago the entire SF.net site was down so they must be having trouble.
I've given up and asked my ISP to download the file for me - they'll let me know when they have it so I can get it from their server.
Brian
>> they'll let me know when they have it so I can get it from their server. <<
It turns out that my ISP's robot has less patience than I have - it gave up after getting only 106,496 bytes of the Windows version of RC3.
Brian
Seems I was lucky. I got the Windows version and put it on my server:
http://popfile.manni-heumann.de/popfile-0.22.2RC3-windows.zip
I wasn't that lucky with the cross-platform version, though.
Manni
Manni,
Thanks. I've got RC3 from your server.
I could download the cross-platform version and mirrored at
http://idisk.mac.com/amatubu/Public/POPFile/popfile-0.22.2RC3.zip
Naoki
Seems that downloading them now, I get the regular speed. In the last couple of days, sf has updated hardware and software. I guess the slowness was related to the upgrade.
Manni
Brian,
>Can this situation happen in POPFile - if POPFile is terminated abruptly, can it leave behind a mutex that causes problems the next time POPFile is used?
My Mutex code will delete the Mutex 'derectory' but will not delete the Mutex 'file'.
This problem may happen when we use RC3 after using RC2 (and RC2 crashed unexpectedly).
If POPFile is terminated abruptly, the Mutex directory will remain, but it doesn't matter. POPFile will remove the remained directory.
(You can verify this by creating a Mutex directory manually before running the test suite.)
Naoki
>> (You can verify this by creating a Mutex directory manually before running the test suite.) <<
Yes, I should have tried this before posting. As you said, the test works OK when the mutex directory already exists.
Brian
Thanks to Manni's mirror I was able to download RC3
RC3 includes addssl.zip v0.0.9 instead of the current version (0.0.10, created 3 December). If v0.0.9 is used to add SSL Support to 0.22.2 then the user will see an "exclamation mark" message box with the message:
"Module.pm patch status: No suitable patches were found"
addssl.zip 0.0.10 does not display this message (this is the only difference between these two versions).
Brian
I'll fix that before release.
Who has tried RC3?
John.
I finally tried RC3 tonight. Install worked fine and everything seems fine, but other than a quick look I did no testing.
I'm using RC3 from yesterday. I have no problem with RC3.
I think the forking problem in Japanese environment is completely fixed.
Naoki
I just noticed the welcome strings for the nttp and smtp modules are not being updated on upgrade. The POP welcome string was upgraded fine. I still have 0.21.0 for the other two. PF knows they are not default values though, it bolds the variable name on the Advanced page.
I have been using the default installer options and not manually selecting to install the extra modules for several versions. When the installer realizes I already have those installed, it always warns me using old versions is bad and lets me choose to upgrade them which I do. Its possible that is causing the problem, but needs to be fixed anyway eventually. Its very minor so could easily wait till 0.23.
Here are the settings from my popfile.cfg:
nntp_welcome_string NNTP POPFile (v0.21.0) server ready
pop3_welcome_string POP3 POPFile (v0.22.2) server ready
smtp_welcome_string SMTP POPFile (v0.21.0) welcome
>> the welcome strings for the nttp and smtp modules are not being updated on upgrade. The POP welcome string was upgraded fine. <<
The installer does not do anything with these three "Welcome strings. It seems that POPFile always updates the POP3 "Welcome" string to use the current version number but if the NNTP and SMTP "Welcome" strings already exist in popfile.cfg then they are not updated to use the current version number.
If you shutdown POPFile and manually delete the NNTP and SMTP "Welcome" strings, new strings with the correct version number will be created the next time you start POPFile (even if NNTP and SMTP are not enabled in popfile.cfg).
>> I have been using the default installer options and not manually selecting to install the extra modules for several versions. When the installer realizes I already have those installed, it always warns me using old versions is bad and lets me choose to upgrade them which I do. Its possible that is causing the problem <<
There is no difference between manually selecting these options and answering "Yes" when the installer reminds you - both methods set the same flag which is used later on to decide which POPFile files to install.
Brian
The way the string is updated is a bit cleverer than you suggest. We look to see if the user has changed it from the default and if they have then we don't touch it; if they have not touched it then we update it.
The code that does this for POP3 needs to be copied into NNTP and SMTP.
John.
I have implemented the same logic as POP3 in the SMTP and NNTP modules and this will be in rc4.
John.
"the welcome strings"
Please refresh my memory. Where/when are these strings displayed? What is their purpose?
--
Jim
This is the banner string that the POP3/SMTP/NNTP proxies print to the connecting client when a connection is made. e.g. for POP3 we say
POP3 POPFile (0.22.2) server ready
on connection.
John.