I’m on 2.02, and have 0 issues with it. I’ve seen a lot of issues on newer version with the tag (which my site employs).
Should I upgrade? Meaning, is there a critical bug fix, or has it just been improvements over this version?
Login to download the latest version of Mint and your favorite Pepper, purchase additional licenses, or post in the Forum. Don't have an account? Create one!
I’m on 2.02, and have 0 issues with it. I’ve seen a lot of issues on newer version with the tag (which my site employs).
Should I upgrade? Meaning, is there a critical bug fix, or has it just been improvements over this version?
Every time I’ve upgraded Mint I’ve run into problems. It’s becoming notorious in my mind. I’d give it a miss if I were you, unless the updates are critical security updates.
I never had any problems with any Mint update.
Never had any problem either. Just follow the upgrade instructions and you won’t have a problem.
help all.
just upgrading from 1.29. Can’t find directions for upgrading that far back.
stella, the README.txt in the mint download explains upgrading from a version 1 install…
Hope that helps.
Rob
I haven’t had any problems with Mint updates, although I advise you to make a backup first before updating. You never know…
Well, i finally did it. went from 2.02 to 2.12….
and i’ve got nothin but a locked database.
site’s been hanging for 15 min now.
…
I KNEW i should have stayed on 2.02…
I had to restart mysql services.
locked up my quad proc opteron box to a stand-still.
now, i’m afraid to go back to /mint cuz its just going to do it again….
after some investigating, my db was nearly 8 GB and settings for days was set to 99999.
surely, that was the problem.
i have all kinds of broken tables (ie, repair failed) and i’m trying to figure out what’s what, but it seems to be running.
the DB is still huge though… not really sure what i can delete.
Mint is the only program i’ve seen that gives me a + sign next to tables in phpmyadmin, so i have no idea what that even is…
Re: + signs, PhpMyAdmin is trying to be clever and grouping what it thinks are related tables (because of the mint__ prefix on the mint__config table).
Why are you posting troubleshooting requests in an After-Dinnner thread about whether or not to update to Mint 2?
This problem was caused by changing the default database expiry settings in Mint—not the update. The defaults should be 25MB or 5 weeks (there is no “days” setting). I would recommend completely emptying or deleting and then recreating your mint_visit table.
You must be logged in to reply. Login above or create an account