On Thu, Nov 12, 2009 at 12:50:27AM -0500, Sam Bisbee wrote:
> On Thu, Nov 12, 2009 at 12:23:05AM -0500, Elliot Murphy wrote:
> [snip]
> > One possible thing to test if someone has a moment is just double
> > checking that an upgrade from 0.9.0 to 0.10.0 goes smoothly, since the
> > log locations changed slightly. If that works ok, I think it's ready to
> > upload! Thanks Sam and Sergei for working on this.
>> Yup, I'm hoping to do that tonight. I'm fixing some postrm issues in the purge
> process first, so it'll all fit in.
>> Adding/removing has looked good otherwise though.
Bad news, it looks like the upgrade doesn't work perfectly. When 0.9.0-2 is
removed its code is still running in a beam process. So, when 0.10.0-1 is
installed, everything works fine except that the old code is still loaded (as
seen by / on the server saying that you're running 0.9.0). Killing the beam
process and restarting couchdb makes everything work fine.
So, we could release and make a note in README.Debian that the user has to kill
their process after upgrading from 0.9.0-x to 0.10.0-x (sub-optimal). Or put
something in the preinst file that checks to see if couchdb is loaded in any
beam processes, kill them, and then proceed with the installation (nicer, but
still not all that great).
Thoughts or ideas? It's late so I could be missing something. :-)
--
Sam Bisbee