I've finally got my act together and packaged up everything from the branch with all of Brian's latest code (Thanks for keeping me updated so well, Brian, and the SSL download is slick).
John, I thought you were going to switch to SQLite2 for 0.22.5 so I changed the installer to only install DBD::SQLite2 (it does not try to delete an existing DBD::SQLite if you upgrade an existing installation).
A clean install of 0.22.5 RC0 failed because it could not find DBD::SQLite.
For clean installs the installer creates a skeleton popfile.cfg file so I could modify the installer to make it add a suitable bayes_dbconnect entry (I'm assuming only that entry needs to be added since the default values for the other database parameters will be used).
For upgrades I could make it change the existing bayes_dbconnect entry. But what about upgrades of a pre-SQLite installation - would they still work properly if the installer adds a bayes_dbconnect entry to the existing popfile.cfg file?
I've not finished work on the SSL patching we discussed (the Inetc bug delayed things a bit). Do you want me to add this feature to 0.22.5 or just leave the existing embedded patch in the installer instead of downloading it from getpopfile.org?
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've fixed the SQLite2 problem. It appears that I never checked in my change to the default connect string. Here's a packaged version for people to try:
Upgrade worked well over 0.22.4 the second time I tried. The first it said something about corrupted installer about 3/4 the way through the first progress bar. But without redownloading I ran setup again and it worked fine.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Was running 22.4 on Windows 2000 and the upgrade went without a hitch. I did shutdown POPFile before running the install, could have been a more thorough test on my end to leave 22.4 running. My usage of the program is such that I leave POPFile running 24x7 on this Windows machine (file server) and use only IMAP and SSL beyond the base product. Installing both of these optional components during the install of 22.5 RC1 completed without issue. I did not configure any email clients during the install.
PeterJ
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've been using RC1 (the Windows version on Windows XP SP2 and the cross-platform version on Mac OS X 10.4.8) for several days and I've not found any problems with it.
The new installer can successfully download SSL modules via proxy servers which need authentication.
Naoki
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just checked in some changes to the URLs in the language files. I removed the Manual link completely. I didn't replace it with a link to the QuickStart pages since those are easy to find on the main wiki which we do link to and that string wouldn't be translated anyway.
I also looked through the checkins since our last release and found some stuff that was only done on 0.23 but likely should be done here as well. Please check on these to see if they belong in this release (or if I missed them and they already are). They look simple enough to easily back port, but I didn't compare the code to be sure. They are from Naoki, John, and Brian.
>>Don't worry about this one - it was in the 0.22.4 release.
Thanks. I knew we had that feature for 0.22.4, but thought maybe you changed something after the release. I guess you just checked it into the other branch after the release.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
0.22.5, like the previous releases, is not compatible with SQLite 3.x so you still need to use the SQLite 2.x library.
However 0.22.5 defaults to using DBD::SQLite2 for new installs. If the popfile.cfg file does not exist, 0.22.5 will create one which uses "dbi:SQLite2:dbname=$dbname" for the bayes_dbconnect parameter.
The 0.22.5 installer will install SQLite2 and change the bayes_dbconnect parameter to sue SQLite2.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've finally got my act together and packaged up everything from the branch with all of Brian's latest code (Thanks for keeping me updated so well, Brian, and the SSL download is slick).
You can download and test 0.22.5 here:
http://popfile.sf.net/popfile-0.22.5RC0.zip
http://popfile.sf.net/popfile-0.22.5RC0-windows.zip
Clearly, the release notes need writing and we need to test the various changes and bug fixes that have gone in.
John.
John, I thought you were going to switch to SQLite2 for 0.22.5 so I changed the installer to only install DBD::SQLite2 (it does not try to delete an existing DBD::SQLite if you upgrade an existing installation).
A clean install of 0.22.5 RC0 failed because it could not find DBD::SQLite.
For clean installs the installer creates a skeleton popfile.cfg file so I could modify the installer to make it add a suitable bayes_dbconnect entry (I'm assuming only that entry needs to be added since the default values for the other database parameters will be used).
For upgrades I could make it change the existing bayes_dbconnect entry. But what about upgrades of a pre-SQLite installation - would they still work properly if the installer adds a bayes_dbconnect entry to the existing popfile.cfg file?
I've not finished work on the SSL patching we discussed (the Inetc bug delayed things a bit). Do you want me to add this feature to 0.22.5 or just leave the existing embedded patch in the installer instead of downloading it from getpopfile.org?
Brian
That must be my screw up. I thought I'd changed the code correctly, but perhaps I didn't check it in. I'll get to that this week.
Changing the bayes_dbconnect entry should work fine for per-SQLite upgrades, but I'll give it quick test.
Let's get the SSL patching stuff in 0.22.5, I think it's a really nice solution.
John.
>> Let's get the SSL patching stuff in 0.22.5, I think it's a really nice solution. <<
OK, I'll do that. I expect to have it ready by the weekend.
Brian
I've fixed the SQLite2 problem. It appears that I never checked in my change to the default connect string. Here's a packaged version for people to try:
http://popfile.sf.net/popfile-0.22.5RC1.zip
http://popfile.sf.net/popfile-0.22.5RC1-windows.zip
John.
Upgrade worked well over 0.22.4 the second time I tried. The first it said something about corrupted installer about 3/4 the way through the first progress bar. But without redownloading I ran setup again and it worked fine.
Was running 22.4 on Windows 2000 and the upgrade went without a hitch. I did shutdown POPFile before running the install, could have been a more thorough test on my end to leave 22.4 running. My usage of the program is such that I leave POPFile running 24x7 on this Windows machine (file server) and use only IMAP and SSL beyond the base product. Installing both of these optional components during the install of 22.5 RC1 completed without issue. I did not configure any email clients during the install.
PeterJ
I've been using RC1 (the Windows version on Windows XP SP2 and the cross-platform version on Mac OS X 10.4.8) for several days and I've not found any problems with it.
The new installer can successfully download SSL modules via proxy servers which need authentication.
Naoki
I just checked in some changes to the URLs in the language files. I removed the Manual link completely. I didn't replace it with a link to the QuickStart pages since those are easy to find on the main wiki which we do link to and that string wouldn't be translated anyway.
I also looked through the checkins since our last release and found some stuff that was only done on 0.23 but likely should be done here as well. Please check on these to see if they belong in this release (or if I missed them and they already are). They look simple enough to easily back port, but I didn't compare the code to be sure. They are from Naoki, John, and Brian.
http://sourceforge.net/mailarchive/forum.php?thread_id=31153263&forum_id=29320
http://sourceforge.net/mailarchive/forum.php?thread_id=31153262&forum_id=29320
http://sourceforge.net/mailarchive/forum.php?thread_id=10269634&forum_id=29320
http://sourceforge.net/mailarchive/forum.php?thread_id=9822894&forum_id=29320
>> http://sourceforge.net/mailarchive/forum.php?thread_id=9822894&forum_id=29320 <<
Don't worry about this one - it was in the 0.22.4 release.
Brian
>>>> http://sourceforge.net/mailarchive/forum.php?thread_id=9822894&forum_id=29320 <<
>>Don't worry about this one - it was in the 0.22.4 release.
Thanks. I knew we had that feature for 0.22.4, but thought maybe you changed something after the release. I guess you just checked it into the other branch after the release.
That change went into 0.22.4 first and about a week later the 0.23.0 changes were made.
Brian
> http://sourceforge.net/mailarchive/forum.php?thread_id=31153263&forum_id=29320
> http://sourceforge.net/mailarchive/forum.php?thread_id=31153262&forum_id=29320
I've already committed these changes to the branch b0_22_2, too.
They are included in 0.22.5 RC1.
Naoki
Does this version support the newer version of SQLite, or do we need to still install the older version as per the cross-platform installation wiki?
0.22.5, like the previous releases, is not compatible with SQLite 3.x so you still need to use the SQLite 2.x library.
However 0.22.5 defaults to using DBD::SQLite2 for new installs. If the popfile.cfg file does not exist, 0.22.5 will create one which uses "dbi:SQLite2:dbname=$dbname" for the bayes_dbconnect parameter.
The 0.22.5 installer will install SQLite2 and change the bayes_dbconnect parameter to sue SQLite2.
Brian