From: Dieter S. <dsi...@sq...> - 2008-02-06 17:18:50
|
On Wed, 6 Feb 2008, Roy W Pennington wrote: > On February 5, 2008, Dieter Simader wrote: >> duh, Roy, if this error does not happen in the upgrade from 2.6.27-2.8.0 >> but it happens in the upgrade 2.8.0-2.8.2 why should it be in the UPGRADE >> docs for 2.6.27-2.8.0 ? >> > But it DOES happen when upgrading from 2.6.27 to 2.8.12 Roy, I told you the error happens when you upgrade from 2.8.0-2.8.2 The fact that you are upgrading from 2.6.27 has nothing to do with the error when it happens. If you were to upgrade to 2.8.0 there is no such error but because you are continuing with the upgrade to 2.8.12 the error crops up. Do you understand it now? > I never meant to suggest it should be in the 2.6.27-2.8.0 doc Yes, this is what you suggested and are still suggesting, see above. |