1. I made hard-copy accounts of all current port settings to my current
3.0.4 ComOs setup. (As suggested by Rich Adamson).
2. I followed the ComOs 3.7 Release Notes upgrade instructions by
uncompressing the pmconsole 3.5.3 library in my *already existing*
/usr/portmaster directory, and also mv'd the pm2_3.7 upgrade image to my
*already existing* /usr/portmaster/data directory.
3. When I run pminstall 3.5.3, the menu appears fine, and when I say
"upgrade portmaster", the pm2_3.7 option appears fine.
... sidenote: When I run: pminstall -v *inside the portmaster
directory*, I DO NOT get the version number. However, when I copy this
same pminstall file to another directory, running the same -v flag
returns me the correct version number: 3.5.3 . Does anybody know why
this flag doesn't work INSIDE my pre-existing portmaster directory? I'm
wondering if the older pminstall is still trying to run, hence making
the upgrade fail (I don't see how though, as I mv'd the older pminstall
to a file called pminstall.old)
4. After I select the pm2_3.7 upgrade option, I log into the portmaster,
then get the following error:
"error reading upgrade op code"
"upgrade aborted"
So, following advice from others on this list, I tried upgrading to a
lower ComOs image (ComOs 3.3.3), and got the same results. I didn't
think this would matter anyway, as Livingston says it's OK to upgrade
from 3.0.4 to 3.7 directly.
Everything still seems to be working fine on my original setup for 3.0.4
for now, thank goodness, but I'm just wondering why I'm getting the
above error, which has me at a standstill. Anybody have any ideas?
Thanks a bunch again..
Terry Angel, MID Inc.
Indianapolis
http://www.minfod.com/
terry@minfod.com