Comment 2 for bug 1463630

Okay, I've uploaded new 1.10.4 release packages that have the correct release string. So now if you download the releases from Launchpad, they will read "1.10.4" instead of "1.10.5testing".

I've also bumped the database version number, so if you replace your erroneous "1.10.5testing" packaged install with this new package, it will change it to read "1.10.4".

(On the git side of things, there actually hadn't been any further commits in the 1.10_STABLE git branch since the 1.10.4 release, so I took care of this in the git history by adding a new commit to the top of the 1.10_STABLE branch which bumps the DB version and changes the release string from 1.10.5testing to 1.10.4. I then moved the 1.10.4_RELEASE signed tag to point at this new commit. Lastly I created another commit that changes the release back to 1.10.5testing and bumps the DB version again. I considered doing a git push --force to get rid of the erroneous commit from our history, but I decided against it because it might make future merges just a tiny bit more complicated. Of course, git doesn't really support moving tags around, so anyone who has already fetched the old 1.10.4_RELEASE tag will not see the new one. But that's not such a big deal.)

Cheers,
Aaron