On Fri, Nov 12, 2010 at 02:28:51PM -0500, Michael K. Johnson wrote:
> In particular, the next conary release (later today) will introduce
> a modelcache format change, so AFTER you do the next update that
> includes a new conary, you'll need to remove the
> /var/lib/conarydb/modelcache file before doing further conary
> operations. (If you forget and get a traceback, no harm has been
> done; just remove the modelcache file and try again.)
I just committed conary 2.2.alpha_6a463d51efe7 to the repository,
and this version introduces a modelcache format change. This version
will be in the next groups.
In testing, I realized that my previous instructions aren't quite
right. After updating Conary, the conary process restarts, and
the new conary can't read the modelcache, and it will fail with a
traceback in the middle of the update process. When this happens,
run these two commands:
sudo rm -f /var/lib/conarydb/modelcache
sudo conary sync
The first will remove the now-incompatible model cache; the second
will complete the updateall operation that you started previously.
Thanks for your patience as we make these changes!
One of the benefits involved in changing the modelcache format is
that a do-nothing "conary sync" command (when the system is already
up to date with the model) will generally take less than 10 seconds.
On a slow 32-bit laptop with a simple model with group-gnome-dist
installed, it takes about 6 seconds. It's around 8 seconds for my
main system with group-gnome-dist-devel and lots of extra packages;
about twice as fast as the previous build of Conary.
_______________________________________________
Foresight-devel mailing list
Foresight-devel@lists.rpath.org
http://lists.rpath.org/mailman/listinfo/foresight-devel
