Accidental downgrade attempt - now stuck

I accidentally tried to downgrade my gallery installation from 2.3 to 2.2.5 - now I cannot get back to 2.3.

Sequence of events:
- I was running an earlier version of 2.2, installed via RPM for my distribution (Fedora)
- I then decided to upgrade to 2.3 via the tarball downloaded from menalto - upgrade went OK
- Then, some time later I updated my Linux installation, thereby accidentally installing 2.2.5 via RPM (since RPM only knew about the earlier RPM install, not my manual update)

- Next time I visited my gallery, I was presented with the update screen, and proceeded to go through the motions of a supposed update, which was really a downgrade from 2.3 to 2.2.5

- This downgrade proceeded until step 3, where I was presented with the error message

"The installed version is newer than the version you are trying to upgrade to. You cannot downgrade G2. Please replace the gallery2 files with files from the currently installed version or later."

- I then tried to get back to 2.3 by extracting the tarball of 2.3 again, but whenever I visit the gallery, the updater remembers that I was in the process of the downgrade to 2.2.5.

Do you have any hint for me on how to reset the aborted downgrade, so that I can get back to v2.3?

Thanks a lot!

Hi Dave,
thanks for your help!

Unfortunately, I don't have a recent backup, since the 'Upgrade' happened without me knowing that it was about to happen.

Extracting 2.3 over the gallery installation didn't work either: I extracted 2.3, went to the website again, and startet the upgrade - when I reach step 3 again, it will again claim that I'm doint a downgrade from 2.3 to 2.2.5 - I cannot get past step 3 even after extracting 2.3.

To me, it seems like the process has some kind of internal state that still remembers what happened before - does anybody know where such a state might be stored?

Versions.dat contains:

1.3.0
2.3

However, in my installation, versions.dat lives directly inside the directory gallery2, which in turn is in /var/www

On the same level as versions.dat is albums, modules, themes etc.

Result of the SQL query:

So, unfortunately it seems like this is just as it should be.

Could it be that there is some other persistent indicator (either in the DB or in the file system) that there was an update 'in progress', such that any further visit to the website would lead back to the upgrade screen?

Thanks for sticking with me here - I really appreciate your time!

Oh boy - classic case of 'Problem Between Chair And Keyboard!'

Thanks to your prodding me along, I finally found out what happened ...

While creating a parallel gallery2 installation as you suggested, I finally looked into my httpd configuration files, and realized that my real gallery installation lives in /usr/share/gallery2, not /var/www/gallery2 - because that's where my RPM install put it.

The installation I have been fiddling with for the last one and a half days is some old relic of days before, now obsolete and never even looked at by my httpd. I never realized this, because the first thing I tried when things went sour was extracting 2.3 again - so everything looked new and shiny ...

Which basically means all the fixing took place on dead bits; as soon as I tried my very first attempt at a repair on the live installation (extracting 2.3 again over the botched install), everything was OK again.

Dave: Thanks again for your patience - I feel a bit silly now ...