The putback for '245 Need incremental update mechanism for the catalog' is a minor flag day for pkg users. 245 makes a small, but incompatible change to the catalog's timestamp format.
This has the following implications: - Clients that have the change for 245 need to get a full update to their catalog to refresh the timestamp attribute. To receive a full update type, "pkg refresh --full" - Depots that upgrade to the change for 245 need to rebuild their catalog so that it will include a new timestamp. The _first_ time that a depot is started with the new bits, add the --rebuild option to the command line. This is not required, in fact it is counterproductive, for any subsequent invocation. (Subsequent invocations delete the update history. This make it impossible for clients to obtain incremental updates.) - I have tested an old server with a new client, and haven't encountered any issues. - I have tested an old client with new server. I also haven't encountered any issues in this situation. To be clear, the only situation in which the user needs to take action is when an existing client or server is upgraded to the new bits but has an old catalog. If you have any questions, feel free to e-mail me. -j _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
