The OpenSolaris development package repository
http://pkg.opensolaris.org/dev/
has been updated to reflect the changes up to and including snv_134 for
both the x86/x64 and SPARC platforms.
Starting with build 133, almost all packages in the development package
repository have been renamed with hierarchical. smf(5)-style names[1].
For general information on the the format of package names, see the
pkg(5) manual page[2].
Before updating a system, review the "New issues" and "Existing issues"
sections of this document for all of the known issues that may affect
the update.
The development builds have undergone limited testing and users should
expect to uncover issues as the next release is developed. Bug reports
and requests for enhancement are welcome through
http://defect.opensolaris.org/
Users who wish to update their system to the development build can do
so by setting their preferred publisher to the above URL and using the
"image-update" facility provided by the pkg(1) command or by the
"Update All" facility of the Package Manager GUI.
Existing issues in this repository update or in updating to it
==============================================================
3106 action upgrade needs to consider a missing origin
http://defect.opensolaris.org/bz/show_bug.cgi?id=3106
When using image-update or the Package Manager to update, the
packaging operation may fail with messages of the form
Action removal failed for 'path/to/some/file'
(pkg:/<some package>):
OSError: [Errno 2] No such file or directory:
'/tmp/tmp3E7vFO/path/to/some/file'
.
.
.
File "/usr/lib/python2.4/vendor-packages/pkg/misc.py",
line 85, in copyfile
fs = os.lstat(src_path)
OSError: [Errno 2] No such file or directory:
'/tmp/tmp3E7vFO/path/to/some/file'
Work-around: This failure occurs if an "editable" file has been
removed from the system prior to updating to build 133 or
later.
To restore the file in question
user at host$ pfexec pkg fix <some package>
At this point the above packaging operation can be restarted.
14570 file install logic discommoded by excessive cleverness if preserve=rename*
http://defect.opensolaris.org/bz/show_bug.cgi?id=14570
When using image-update or the Package Manager to update, the
packaging operation may fail with messages of the form
Action upgrade failed for 'etc/mail/sendmail.cf'
(pkg://opensolaris.org/service/network/smtp/sendmail):
OSError: [Errno 2] No such file or directory
.
.
.
File
"/usr/lib/python2.6/vendor-packages/pkg/portable/os_unix.py",
line 232, in rename
os.rename(src, dst)
OSError: [Errno 2] No such file or directory
Work-around: This failure occurs if an "editable" file that has
been marked "renameold" has been modified from the system prior
to updating to build 133 or later.
An example of such a file is the sendmail(4) configuration
file, /etc/mail/sendmail.cf. Special instructions[3] are
available in cases where /etc/mail/sendmail.cf has been
modified.
In other cases, first preserve the contents of the existing
file
user at host$ cp -p /path/to/file /path/to/file.orig
Restore the modified file by searching for the package that
delivers it
user at host$ pkg search -l /path/to/file
INDEX ACTION VALUE PACKAGE
path file /path/to/file pkg:/<some package>@ ...
Then restore the file as follows
user at host$ pfexec rm /path/to/file
user at host$ pfexec pkg fix <some package>
At this point the above packaging operation can be restarted.
Once booted into the new boot environment, changes recorded in
/path/to/file.orig can be merged, if necessary, into the
/path/to/file.
6914346 upgrade from OpenSolaris 2009.06 (111b2) to 130 fails with stale
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6914346
After updating to build 130 or beyond, the system may panic
with messages of the form
/kernel/misc/amd64/pci_autoconfig:
undefined symbol 'pcie_get_rc_dip'
WARNING: mod_load: cannot load module 'pci_autoconfig'
panic[cpu0]/thread=fffffffffbc2e3a0:
failed to load misc/pci_autoconfig
Work-around: Boot the original boot environment (BE) instead
and correct the boot archive as follows
<reboot into the earlier BE>
user at host$ pfexec beadm mount <name of new BE> /mnt
user at host$ pfexec bootadm update-archive -F -R /mnt
user at host$ pfexec beadm unmount <name of new BE>
At this point, the new BE can be booted into.
12380 image-update loses /dev/ptmx from /etc/minor_perm
http://defect.opensolaris.org/bz/show_bug.cgi?id=12380
When using image-update or the Package Manager to update to
build 125 or greater, remote access to the system via ssh(1) or
rlogin(1) may become unavailable. Alternatively, using
terminal programs such as gnome-terminal(1) or xterm(1) may
result in characters not being echoed or commands unable to be
typed.
Work-around: Boot the original boot environment (BE) instead
and correct the /etc/minor_perm file contained within as
follows
<reboot into the earlier BE>
user at host$ pfexec beadm mount <name of new BE> /mnt
user at host$ pfexec sh -c \
"grep ^clone: /etc/minor_perm >> /mnt/etc/minor_perm"
user at host$ pfexec touch /mnt/reconfigure
user at host$ pfexec bootadm update-archive -R /mnt
user at host$ pfexec beadm unmount <name of new BE>
At this point, the new BE can be booted into.
13534 "Could not update ICEauthority file /.ICEauthority" on bootup of build 130
http://defect.opensolaris.org/bz/show_bug.cgi?id=13534
After the system boots, the following warning dialog boxes may
be displayed
Could not update ICEauthority file /.ICEauthority
There is a problem with the configuration server
(/usr/lib/gconf-sanity-check-2 exited with status 256)
Work-around: Clicking on the "Close" button for each dialog box
will permit one to login normally. Once logged in, enter the
following command to correct the home directory for the "gdm"
user
user at host$ pfexec usermod -d /var/lib/gdm gdm
11051 default ai 121 dev ai build should point to /dev
http://defect.opensolaris.org/bz/show_bug.cgi?id=11051
When using the Automated Installer (AI) to install development
builds over the network, the manifest used for the install
service should be updated to reflect that packages should be
installed from the development repository.
First copy the default manifest from your install image.
Assuming the name of the create AI service is <svc_name>, then
AI<svc_name> represents the name of the smf(5) property group
that contains the path to the image
user at host$ image_path=`svcprop -c -p AI<svc_name>/image_path`
Next copy the default.xml file from that image and change the
"main url" attribute of the "ai_pkg_repo_default_publisher"
element from "http://pkg.opensolaris.org/release"; to
"http://pkg.opensolaris.org/dev";
user at host$ cp ${image_path}/auto_install/default.xml /tmp
user at host$ <edit /tmp/default.xml as described>
Finally associate the modified manifest with the install
service
user at host$ pfexec installadm add -m /tmp/default.xml \
-n <svc_name>
Note that users of the "bootable" AI CD and USB ISO should make
a similar change to the custom manifest that can specified as
part of its installation procedure.
13233 /contrib packages should not depend on "entire"
http://defect.opensolaris.org/bz/show_bug.cgi?id=13233
If packages from the "/contrib" repository have been installed
on the system, attempts to update the system may cause the
following error to occur
pkg: Requested "install" operation would affect files that
cannot be modified in live image.
Please retry this operation on an alternate boot environment.
Work-around: Uninstall the packages from "/contrib" which are
causing the issue. The list can be found through the following
command
user at host$ pkg contents -Ho pkg.name,action.raw -t depend | \
grep fmri=entire@ | cut -f1
Once these packages have been uninstalled, repeat the packaging
update.
11523 only permit FMRIs from same publisher for network repositories
http://defect.opensolaris.org/bz/show_bug.cgi?id=11523
When performing certain packaging operations, errors of the
following form may be displayed
pkg: The following pattern(s) did not match any
packages in the current catalog. Try relaxing the
pattern, refreshing and/or examining the catalogs:
or
The catalog retrieved for publisher '<some name>' only
contains package data for these publisher(s):
opensolaris.org. To resolve this issue, update this
publisher to use the correct repository origin, or add
one of the listed publishers using this publisher's
repository origin.
These both reflect that the name of publisher has been
incorrectly set to a value other than "opensolaris.org". When
using http://pkg.opensolaris.org/dev/ as an origin URI, the
name of the publisher must be "opensolaris.org" and there
should be no other publishers with that name.
In addition, specifying a publisher for both the
http://pkg.opensolaris.org/dev/ and
http://pkg.opensolaris.org/release/ origin URIs is an error as
only one of them should be in use at a time, using a publisher
of "opensolaris.org".
Work-around: If there is a publisher "publisher name" defined
for the http://pkg.opensolaris.org/release/ origin URI, remove
this first
user at host$ pfexec pkg unset-publisher <publisher name>
Then reset the publisher back to the correct value
user at host$ pfexec pkg set-publisher \
-O http://pkg.opensolaris.org/dev/ opensolaris.org
8347 Move boot archive from /boot/x86.microroot to /platform/i86pc/boot_archive
http://defect.opensolaris.org/bz/show_bug.cgi?id=8347
Automated Installer servers must themselves be updated to at
least build 128a in order to serve build 128a or greater
images. In addition, systems running the Distribution
Constructor should also be updated in order to build images
based on build 128a or greater.
10630 driver action gets confused by driver_aliases entries not covered by an
http://defect.opensolaris.org/bz/show_bug.cgi?id=10630
When using image-update or the Package Manager to update to
build 121 or later, messages of the following form may be
displayed
The 'pcieb' driver shares the alias 'pciexclass,060400'
with the 'pcie_pci' driver, but the system cannot
determine how the latter was delivered. Its entry on
line 2 in /etc/driver_aliases has been commented out.
If this driver is no longer needed, it may be removed
by booting into the 'opensolaris-2' boot environment
and invoking 'rem_drv pcie_pci' as well as removing
line 2 from /etc/driver_aliases or, before rebooting,
mounting the 'opensolaris-2' boot environment and
running 'rem_drv -b <mount point> pcie_pci' and
removing line 2 from <mount point>/etc/driver_aliases.
Work-around: These messages can be ignored.
6877673 add_drv fails with a permissions entry with a minor name including a
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6877673
When using image-update or the Package Manager to update,
messages of the following form may be displayed
driver (clone) upgrade (removal of minor perm
'vnic 0666 root sys') failed with return code 252
command run was: /usr/sbin/update_drv -b /tmp/tmp65jZ-x -d
-m vnic 0666 root sys clone
command output was:
------------------------------------------------------------
No entry found for driver (clone) in file
(/tmp/tmp65jZ-x/etc/minor_perm).
------------------------------------------------------------
or
driver (asy) upgrade (addition of minor perm
'*,cu 0600 uucp uucp') failed with return code 255
command run was: /usr/sbin/update_drv -b /tmp/tmp65jZ-x -a
-m *,cu 0600 uucp uucp asy
command output was:
------------------------------------------------------------
Option (-m) : missing token: (*)
------------------------------------------------------------
Work-around: These messages can be ignored.
9568 image-update produces driver removal of policy warnings
http://defect.opensolaris.org/bz/show_bug.cgi?id=9568
When using image-update or the Package Manager to update from
builds prior to 123, warnings of the following form may be
displayed during a packaging update
driver (ibd) upgrade (removal of
policy'read_priv_set=net_rawaccess write_priv_set=net_rawaccess)
failed: minor node spec required.
Work-around: These messages can be ignored.
10778 image-update to snv_120 produces warnings about etc/sma/snmp/mibs
http://defect.opensolaris.org/bz/show_bug.cgi?id=10778
When using image-update or the Package Manager to update to
build 120 or later, a message of the following form may be
displayed
Warning - directory etc/sma/snmp/mibs not empty - contents
preserved in
/tmp/<path>/var/pkg/lost+found/etc/sma/snmp/mibs-<time stamp>
Work-around: This message can be ignored.
11602 Failures seen after rebooting from a image-update from 2009.06 to snv_124
http://defect.opensolaris.org/bz/show_bug.cgi?id=11602
When booting the system the first time after updating to build
124, messages of the following form may be displayed
inetd[5503]: Failed to update state of instance
svc:/application/x11/xfs:default in repository: entity not found
Work-around: These messages can be ignored.
10010 reconfigure transport timeouts
http://defect.opensolaris.org/bz/show_bug.cgi?id=10010
When installing packages on or updating from builds 118 or 121,
the operation may fail with messages of the form
1: Framework error: code: 28
reason: Operation timed out after 30000 milliseconds
with <some number> out of <some other number> bytes received
Work-around: Set the environment variable PKG_CLIENT_TIMEOUT to
15 minutes (900 seconds) or more, depending on the throughput
to the repository and the size of the files in the package in
question
user at host$ PKG_CLIENT_TIMEOUT=900
user at host$ export PKG_CLIENT_TIMEOUT
user at host$ pfexec pkg install <name of packages>
14354 cacao 2.2.3.0 SMF common-agent-container-1 service fails to start on
http://defect.opensolaris.org/bz/show_bug.cgi?id=14354
When booting build 132, a smf(5) service of the form
"application/management/common-agent-container-1" may end up in
the maintenance state.
Work-around: The initial heap size of the Java Virtual Machine
(JVM) used by Cacao needs to be increased. First determine the
current value using the cacaoadm(1M) command
user at host$ cacaoadm get-param -v java-flags
-Xms4M -Xmx128M -Dcom.sun.management.jmxremote
-Dfile.encoding=utf-8
-Djava.endorsed.dirs=/usr/lib/cacao/lib/endorsed
Next increase the value from 4MB to a larger value such as 8MB
using the following command
user at host$ pfexec cacaoadm set-param java-flags="-Xms8M \
-Xmx128M -Dcom.sun.management.jmxremote \
-Dfile.encoding=utf-8 \
-Djava.endorsed.dirs=/usr/lib/cacao/lib/endorsed"
ISO image information
=====================
ISO images for the Automated Installer[4] and [5], CD-R/CD-RW and USB
are being made available for this build via BitTorrent. Torrent files
are provided as follows
SPARC Automated Installer image, 278MB
http://dlc.sun.com/torrents/info/osol-dev-134-ai-sparc.iso.torrent
x86/x64 Automated Installer image, 280MB
http://dlc.sun.com/torrents/info/osol-dev-134-ai-x86.iso.torrent
x86/x64 Automated Installer USB image, 337M
http://dlc.sun.com/torrents/info/osol-dev-134-ai-x86.usb.torrent
x86/x64 All Languages CD image, LZMA compression, 655MB
http://dlc.sun.com/torrents/info/osol-dev-134-x86.iso.torrent
x86/x64 All Languages USB image, LZMA compression, 787MB
http://dlc.sun.com/torrents/info/osol-dev-134-x86.usb.torrent
The ISO images are also available for HTTP download from
http://www.genunix.org/
MD5 checksums for these images can be downloaded from
http://hub.opensolaris.org/bin/download/Project+indiana/files/md5sums134.txt
USB images can be copied to a USB device using the "usbcopy" program
that is part of the SUNWdistro-const package or by downloading the
script[6].
Image Packaging System (IPS) specific bugs addressed in this repository update
==============================================================================
791 stack trace when installing directory or file with missing mandatory
1530 file install fails if user is unknown during install
9632 verify can traceback if group or user is unknown or attribute is missing
12555 SUNWgnome-utility-applets should depend on SUNWgnome-python26-desktop
13191 Sun Studio 12 Update 1 needs to be updated with patches in /dev
13451 upgrade GCC to 4.3.3, update install location to /usr/gcc/4.3
13558 Add bluefish to the Development/Editors category
13813 progress cursor for "pkg verify" doesn't cleanup after long package names
13814 extraneous blank lines now printed after plan creation
13994 References to package names may need to change
14042 get_release_notes_url needs an update
14176 copytree callers must catch shutil.Error and not traceback
14274 time-slider-setup returns Service Dependency Error on snv_131
14292 pkg list doesn't exit with partial failure when some names are unmatched
14360 baseline.txt should only enumerate tests not expected to pass
14607 Problem with display of Repository description
14609 Unexpected error in Package Manager
14625 incorrect error message for 'contents -a foo'
14632 Python flavor regular expression is too restrictive
14634 64-bit VirtualBox not able to run after image-update
14641 Couple of CDE packages lack or have lost their summary
14654 temporary download directory is created regardless of use and never
14660 Empty name displayed in Package Manager
14665 script to update the startpage should allow to update other then
14673 zones update gets confused on update with renamed packages
14677 Rename of SUNWstmf pkg to 'network/iscsi' is incorrect and misleading
14680 TestPkgSearchBasics.test_bug_12271_14088 fails sporadically
14683 transport cleanup can fail causing client traceback
14699 packagemanager traceback during cache load
14702 file action removal fails if file is missing and original_name is set
14712 Search in all publishers causes traceback
14713 pkg fix can traceback for unprivileged users
14715 tests needed to ensure missing, preserved files don't cause operation
14788 sometimes upgrade from osol 133 to onips 133 (with renames) doesn't work
14789 SUNWdistro-const should depend on SUNWxcu4
14798 image-update with zones causes error on read-only /export
14800 traceback on exit when PKG_CACHEDIR is set but not writable
14813 some osnet group package ownerships were over-reaching
14826 network/iscsi dependency in StorageServer needs to be adjusted
14832 pkg info traceback for renamed packages with no variant-applicable
14833 resync repository to snv_134
14834 include Net-SNMP documentation as part of the default install
14856 image-create / set-publisher shouldn't require repository configuration to
14866 missing info retrieval unit tests for renamed packages
14867 pkg(1) usage message doesn't match man page
14882 pkgdiff can print empty difference strings when multi-valued attrs change
14885 solver diagnostics hampered by fix for 13846
14887 Package Version Info dialog doesn't work for uninstalled packages
14888 developer/opensolaris/osnet depends upon non-existent library/cde
14890 update OpenOffice.org to 3.2.0
14893 Rename multiple packages
14899 library/security/openssl misdelivers work-around link
14941 Bit of rename cleanup with dependencies necessary
14942 Traceback when getting package info after search
14949 PM Search All Publishers (Installed) traceback
Caiman installer specific bugs addressed in this repository update
==================================================================
13193 transfer module log messages when building images aren't reported in the
14041 new iso.sort update for the release
14464 additional installer graphic screen needed
14475 installer appears to remove /boot/grub/menu.lst
14539 fix ups for messages from installadm create-service
14617 Need to update Distribution Constructor guide and man pages for build 134
14681 /contrib needs some alone time
14738 Updates to AI Guide
Change logs are also available for this build for the ON[7], SFW[8] and
X[9] consolidations.
[1]
http://hub.opensolaris.org/bin/view/Project+indiana/Renamed+Packages+in+Build+133
[2] http://src.opensolaris.org/source/xref/pkg/gate/src/man/pkg.5.txt
[3] http://blogs.sun.com/jbeck/entry/managing_sendmail_cf_across_upgrades
[4] http://dlc.sun.com/osol/docs/content/dev/AIinstall/
[5] http://blogs.sun.com/aalok/entry/automated_installer_from_media
[6]
http://src.opensolaris.org/source/raw/caiman/slim_source/usr/src/cmd/install-tools/usbcopy
[7] http://dlc.sun.com/osol/on/downloads/b134/on-changelog-b134.html
[8] http://dlc.sun.com/osol/sfw/downloads/b134/BUGS
[9]
http://hub.opensolaris.org/bin/view/Community+Group+x_win/changelogs-nv_130#HBuild134
