On 12/02/11 16:14, Zhenghui Xie wrote:
On 12/02/11 16:08, Alan Coopersmith wrote:
On 12/02/11 16:00, Zhenghui Xie wrote:
I wonder if I might mis-set some env variables in my nightly env file
which
cause the versioning info wrong in my private image . Is there any
way to find
out the versioning information of a nightly binary? Would somebody
please help?
You can get a list of packages & versions in the repo you built with:
% pkgrepo list -s packages/i386/nightly-nd/repo.redist system/kernel
PUBLISHER NAME O VERSION
on-nightly system/kernel 0.5.11,5.11-0.174.0.0.0.0.17683:20110823T072036Z
If you don't include a package name like "system/kernel" it will list all
packages in the repo.
interesting...
the output shows my private image is
coupe:/i386/nightly> pkgrepo list -s repo.redist system/kernel
PUBLISHER NAME O VERSION
on-nightly system/kernel 0.5.11,5.11-0.175.1.0.0.4.18222:20111202T210757Z
the image installed on the test machine is
pkg://solaris/system/[email protected],5.11-0.175.0.0.0.2.1:20111019T075711Z
Looks like the private nightly's version is higher. Why does
image-update complain there is "no updates"?
"No updates available" doesn't necessarily mean that there aren't newer
versions available. It can also mean that there are no *allowed*
updates available based on package constraints.
To find out why the solver doesn't think you can update, you need to
tell it what you want to update to:
pkg update '*@latest'
...as an example, tells pkg update to attempt an update to the latest
version of all packages, and fail with an error explaining why if it cannot.
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
