Update Center 2.4 Release Home

Release Notes for Update Center 2.4

This document provides release information for the 2.4 release of the Update Center toolkit.

NOTE: Since the 2.4 release is currently under development, these release notes are not yet complete.

Platform Requirements

Supported Platforms

Operating System	Architecture	Platform Notes
Windows XP, Windows Vista, Windows 7, Windows Server 2003, Windows Server 2008	x86 (32- and 64-bit)	Windows 7 is supported only for images installed and managed in a subdirectory of the user's home directory (Issue 1583).
MacOS X 10.4 and later	PPC, x86	Native components of the toolkit are Mac OS X universal binaries.
Solaris 10	SPARC, x86	Solaris 10 8/07 (Update 4) or greater is recommended. The toolkit does not require extra patches on these versions. On Solaris 10 3/05 through Solaris 10 11/06 (Update 3), first install these patches (or later versions of the same patches): SPARC platform: 119963-08, 125211-01 x86 platform: 119964-08, 125212-01
Solaris 9 8/03 (Update 4) and later (CLI only)	SPARC, x86	Only the use of pkg(5) CLI is supported on Solaris 9. The Update Tool GUI, the Software Update GUI, and the Desktop Notifier are not yet supported due to Gnome issue 310. first install these patches (or later versions of the same patches): SPARC platform: 112963-32, 111711-16, 111712-16. x86 platform: 113986-26, 111713-13.
OpenSolaris 2008.11 and later	x86
IBM AIX V6 (CLI only)	POWER	Only the use of pkg(5) CLI is supported on AIX. The Update Tool GUI, the Software Update GUI, and the Desktop Notifier are not yet supported.
openSUSE 11.0	x86 (32- and 64-bit)	On 64-bit x86, first install the libidn-32bit rpm from YaST, the installation and configuration mangement tool for openSUSE.
Red Hat Enterprise Linux 4	x86 (32- and 64-bit)	On 64-bit x86, first install these 32-bit compatibility rpms: compat-libgcc compat-gcc-32 compat-gcc-32-c++ compat-glibc compat-libstdc++ 32-bit libidn
Red Hat Enterprise Linux 5	x86 (32- and 64-bit)	On 64-bit x86, first install these 32-bit compatibility rpms: compat-libstd++ compat-libgcc 32-bit libidn
SUSE Linux Enterprise 10 Server and Desktop	x86 (32- and 64-bit)	On 64-bit x86, first install the libidn-32bit rpm.
Ubuntu 7.10	x86 (32- and 64-bit)	On 64-bit x86, first install the ia32-libs and libidn11 packages from the Ubuntu package repository.
Ubuntu 8.x	x86 (32- and 64-bit)	On 64-bit x86, first install the ia32-libs, libidn11 and lib32nss-mdns packages from the Ubuntu package repository.
Ubuntu 9.04	x86 (32- and 64-bit)	On 64-bit x86, first install the ia32-libs, libidn11 and lib32nss-mdns packages from the Ubuntu package repository.

Packages in This Release

The following table shows the packages that make up Update Center 2.4.

Package Name	Package Version	Description
pkg	version-bb.cccc	pkg(5) tools
pkg-extra-tools	version-bb.cccc	Extra tools for building packages and assembling distributions.
pkg-java	version.cccc	Java API for pkg(5) plus bootstraper
pkg-toolkit	version.cccc	Meta-package. Installing this will install all other packages.
pkg-toolkit-incorporation	version-bb.cccc	Incorporation. Ensures all installed packages are of the correct version.
python2.4-minimal	version-bb.cccc	Minimized python runtime need to support pkg and updatetool. Note that on Mac OS X the version is 2.4.5.
updatetool	version-bb.cccc	GUI tools
wxpython2.8-minimal	version-bb.cccc	WX Python runtime needed to support updatetool.

Note that all the packages in the 2.4 release have the same value, bb.cccc, for the "branch" portion of their package versions. You can use this branch value to identify an Update Center package as a member of the 2.4 release.

pkg(5) Version in This Release

The version of pkg(5) in Update Center 2.4 is based on the version in build XXX of OpenSolaris, with the addition of features and bugs fixes unique to Update Center.

This release of pkg(5) has the following incompatibilities with previous releases.

1. When this version of pkg(5) code accesses an image with older meta-data, the meta-data is automatically upgrade to the new format. Once this happens, the pkg(5) software from previous versions will not be able to access the image. The older software will say that the image directory is an "invalid image."

1. A repository now has a required property called "publisher.prefix". This property can be set by starting the pkg.depotd process with the --set-property publisher.prefix=xyz argument, where xyz is the name of the publisher. Any images that are using the the publisher will be required to use the given name as the name of the publisher. Another way to set the publisher.prefix is to edit the cfg_cache file within the repository.

Converting an Older Repository

There are several steps that are required when upgrading an older repository to use the new pkg(5) software in the UC 2.4 toolkit.

1. The interface used by the pkg.depotd web templates has changed in incompatible ways since the previous release. If you are not using customized templates and are using the templates that come with the distribution, then no change is necessary. If you are using customized templates, then you can either:
   1. Copy the templates from the pkg/lib/web directory of the new version and reapply your customizations, or
   2. Change the CLIENT_API_VERSION value to 6 within the index.shtml and en/base.shtml files, and modify the templates to work with the new API.

Which of these to do depends on the level of customization that has been done to the templates. Use the --content-root argument to the pkg.depotd command to pass in the directory for the new templates.

1. Since the new pkg(5) software requires a repository to have a name, the pkg.depotd server will not start against an older repository that doesn't have a name. To add the name to the repository, start the pkg.depotd process with the --set-property publisher.prefix=xyz argument, where xyz is the name of the publisher that is used within images. Allow reindexing to complete. Then exit pkg.depotd with Ctrl-C.

New Features and Enhancements in This Release

Full List of Features and Enhancements

The following table shows the full list of features and enhancements in the 2.4 release as compared to the 2.3 release.

Issue ID	Description

Bug Fixes in This Release

The following table shows the defects fixed in the 2.4 release as compared to the 2.3 release. It does not include defects discovered and fixed during the course of 2.4 release development.

Issue ID	Description

Known Issues and Workarounds in This Release

Full List of Known Issues

The following table lists all open defects known at delivery of the 2.4 release.

Issue ID	Description

Reporting New Issues

If you find something amiss, please consult the list of open Update Center 2 bugs to see if the problem has already been reported.

This page (revision-4) was last changed on 23-Dec-09 13:55 PM, -0800 by TomMueller.
This page was created on 16-Oct-09 10:45 AM, -0700 by TomMueller.

More info...