Ispcp v1.0.3 testers needed

[tango]

somehow there is a technical error for example I check my translation in the line 795 in the uploaded file is missing it, I've uploaded it again and hope it is resolved.

[sci2tech]

Turkish translation is 100% complete. Thank you.

[aseques]

There's a problem when updating from 1.0.2 to 1.0.3 for the great minority using dovecot.
I found when updating that /usr/sbin/makeuserdb is required (wich sounds ok), but somehow the installer (perl ispcp-update) changes the ispcp.conf value that I had previously (CMD_MAKEUSERDB = /bin/true)

It can be fixed installing courier-authlib-userdb , but if possible I rather prefer to keep the CMD_MAKEUSERDB variable from the already installed ispcp.conf.
It shouldn't break anything for the courier users, and make us the users of dovecot a bit happier.

I'll keep on the install and post the results afterwards...

---

Just upgraded to 1.0.3, first impression is that everything is ok, I found another problem tough.
When I go to edit an existant resseller appear's the message "Reseller data inconsistency! e-mail"
I could create another resseller without problem and with the same contact address. looking on the database for some oddities on the data, I see that the values for the disk amount are in negative is that fine? Other than that I have all the values set to 0 (unlimited) so the funcion that's giving the error shouldn't complain.

| id | reseller_id | current_dmn_cnt | max_dmn_cnt | current_sub_cnt | max_sub_cnt | current_als_cnt | max_als_cnt | current_mail_cnt | max_mail_cnt | current_ftp_cnt | max_ftp_cnt | current_sql_db_cnt | max_sql_db_cnt | current_sql_user_cnt | max_sql_user_cnt | current_disk_amnt | max_disk_amnt | current_traff_amnt | max_traff_amnt | customer_id | reseller_ips |
+----+-------------+-----------------+-------------+-----------------+-------------+-----------------+-------------+------------------+--------------+-----------------+-------------+--------------------+----------------+----------------------+------------------+-------------------+---------------+--------------------+----------------+-------------+--------------+
| 1 | 2 | 3 | 0 | 2 | 0 | 4 | 0 | 150 | 0 | 9 | 0 | 11 | 0 | 13 | 0 | -7500 | 0 | -76800 | 0 | | 1; |



Any suggestions, shall I post this to the track? If so, where?

[DiXeoN]

Is it possible to upgrade from 1.0.1 ?

[aseques]

(09-03-2009 12:45 AM)DiXeoN Wrote:  Is it possible to upgrade from 1.0.1 ?

Yes, you shouldn't have problems, but as always you should always make a backup.
Also, the recommended version is r1958 from the svn (reading on this thread) so I'd suggest to download that one.

[sci2tech]

It`s better to use last available trunk, because after r1958 only bugfixes are allowed. About aseques problem I`ll take a look to see if something is broken, or problem was generated prior upgrade

[aseques]

(09-03-2009 03:03 AM)sci2tech Wrote:  It`s better to use last available trunk, because after r1958 only bugfixes are allowed.

Good to know that

Quote:About aseques problem I`ll take a look to see if something is broken, or problem was generated prior upgrade

Sure, in case you need me to test anything I still have that stuff broken (since it's a testing server I can still wait a little)

[sci2tech]

I`ll need if possible a dump of database before and after upgrade. If you have something like this please strip all passwords and all other confidential data. I`m mostly interest in tables admin, domain and reseller_props. And what version do you have before update?

[aseques]

(09-03-2009 11:35 PM)sci2tech Wrote:  I`ll need if possible a dump of database before and after upgrade. If you have something like this please strip all passwords and all other confidential data. I`m mostly interest in tables admin, domain and reseller_props. And what version do you have before update?

I think I found the root of the problem, I just opened a ticket in the trac
http://www.isp-control.net/ispcp/ticket/1974

[sci2tech]

(09-04-2009 06:48 PM)aseques Wrote:  I think I found the root of the problem, I just opened a ticket in the trac http://www.isp-control.net/ispcp/ticket/1974

Lately somebody did try to correct this problem. That why you get that message . Now that I can reproduce, I`ll fix it. Thank you