Upgrade from 8.3 on Debian Etch ?

[Dreamforge]

Hi everyone !

Did anybody tried to upgrade a Debian Etch System with Plesk 8.3 to 8.6 ?
Due to the last "problematic" month...i am quite scarried to launch the update process ...
Knowing that somebody would have successfully upgraded to the latest version without any problem on this kind of system would convince me to do so...

re-installing twice some of my server to 8.3 'cause of buggy 8.4 is something id don't want to do anymore....

Hope the upgrade process went without any problem for you...

 

[Dreamforge]

To keep you informed about the update process, here is what i have done :

Installed a fresh Plesk 8.3 on a Debian Etch test box and then upgraded it to 8.6

You will find below, the Plesk Version / Build Number and the package list...before and after

hope this helps..

psa v8.3.0_build83080131.20 os_Debian 4.0

Package listing before upgrade:

awstats 6.5+dfsg-1
bind 1:9.3.4-2etch3
courier-imap 3.0.8-debian4.0.build83071218.18
drweb 4.33-5psa
drweb-qmail 4.33-debian4.0.build83071218.18
httpd 2.2.3-4+etch5
mailman 1:2.1.9-7
mod_bw 0.8-5
mod_perl 2.0.2-2.4
mysql 5.0.32-7etch6
php 5.2.0-8+etch11
psa 8.3.0-debian4.0.build83071218.18
psa-api-rpc 8.3.0-debian4.0.build83080131.20
psa-autoinstaller 3.3.0-build33080201.09
psa-backup-manager 8.3.0-debian4.0.build83080131.20
psa-horde 3.1.5-debian4.0.build83071218.18
psa-imp 4.1.5-debian4.0.build83071218.18
psa-migration-manager 8.3.0-debian4.0.build83080131.20
psa-proftpd 1.3.0-debian4.0.build83071218.18
psa-qmail 1.03-debian4.0.build83071218.18
psa-qmail-rblsmtpd 0.70-debian4.0.build83071218.18
psa-spamassassin 8.3.0-debian4.0.build83071218.18
psa-turba 2.1.5-debian4.0.build83071218.18
spamassassin 3.1.7-2
SSHTerm 0.2.2-debian4.0.build83071218.18
webalizer 2.01.10-32




psa v8.6.0_build86080722.01 os_Debian 4.0


After upgrade :

awstats 6.5+dfsg-1
bind 1:9.3.4-2etch3
courier-imap 3.0.8-debian4.0.build86080722.01
drweb 4.33-5psa
drweb-qmail 4.33-debian4.0.build86080722.01
httpd 2.2.3-4+etch5
mailman 1:2.1.9-7
mod_bw 0.8-5
mod_perl 2.0.2-2.4
mysql 5.0.32-7etch6
php 5.2.0-8+etch11
psa 8.6.0-debian4.0.build86080722.01
psa-api-rpc 8.6.0-debian4.0.build86080722.01
psa-autoinstaller 3.3.2-080710.09
psa-backup-manager 8.6.0-debian4.0.build86080722.01
psa-horde 3.1.7-debian4.0.build86080722.01
psa-imp 4.1.6-debian4.0.build86080722.01
psa-migration-manager 8.6.0-debian4.0.build86080722.01
psa-proftpd 1.3.1-debian4.0.build86080722.01
psa-qmail 1.03-debian4.0.build86080722.01
psa-qmail-rblsmtpd 0.70-debian4.0.build86080722.01
psa-spamassassin 8.6.0-debian4.0.build86080722.01
psa-turba 2.1.7-debian4.0.build86080722.01
spamassassin 3.1.7-2
SSHTerm 0.2.2-debian4.0.build86080722.01
webalizer 2.01.10-32

The update went fine, and i can see no problem for the moment...
it is time to try it on a production server