Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sympa fake upgrade on sympa 6.2.40 (from 6.1.17) on debian 10 stable #705

Closed
bv-unibs opened this issue Jul 19, 2019 · 1 comment
Closed

Comments

@bv-unibs
Copy link

Hi,
This is related to the issue described in:

#530

After doing the fake upgrade procedure successfully on testing server from sympa 6.1.17 to sympa 6.2.38, like reported in the issue above, I'm trying to repeat the same procedure on the production server with debian 10 stable:

./sympa.pl --upgrade --from=6.1.17 --to=6.2.40

Now I've tried to fake upgrade from 6.1.17 to 6.2.40 and the fake upgrade terminates with errors.

These are the errors I've received after the script was done:

notice Sympa::Upgrade::upgrade() Upgrading admin_table
err main::#890 > Sympa::Upgrade::upgrade#1835 > Sympa::DatabaseDriver::MySQL::delete_field#288 > Sympa::Database::do_query#280 Unable to execute SQL statement "ALTER TABLE admin_table DROP COLUMN date_admin": (42000) Can't DROP COLUMN date_admin; check that it exists
err main::#890 > Sympa::Upgrade::upgrade#1835 > Sympa::DatabaseDriver::MySQL::delete_field#296 Could not delete field date_admin from table admin_table in database sympa
notice Sympa::Upgrade::upgrade() Upgrading subscriber_table
err main::#890 > Sympa::Upgrade::upgrade#1838 > Sympa::DatabaseDriver::MySQL::delete_field#288 > Sympa::Database::do_query#280 Unable to execute SQL statement "ALTER TABLE subscriber_table DROP COLUMN date_subscriber": (42000) Can't DROP COLUMN date_subscriber; check that it exists
err main::#890 > Sympa::Upgrade::upgrade#1838 > Sympa::DatabaseDriver::MySQL::delete_field#296 Could not delete field date_subscriber from table subscriber_table in database sympa

Can you help understand how can I avoid these errors, or If I can ignore them?

thanks

@ikedas
Copy link
Member

ikedas commented Jul 19, 2019

Duplicate of #600.

@ikedas ikedas closed this as completed Jul 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants