Hi
When I look at ipkg.sfbay/dev, there is a 134 and 134.0.1 for entire.
0.5.11,5.11-0.134:20100302T023003Z
0.5.11,5.11-0.134.0.1:20100423T215423Z
There will soon be a 134.0.2
I am in Release Engineering so I have access to a test version of /dev
that does have 134.0.2
Anyway, I see what you mean. The entire incorporation will pull in the
the most recent 134 version of pkgs. Which in my case is 134.0.2. So
while ' pkg info entire ' says 134, the pkgs that were installed on the
system are 134.0.2.
Thanks
Lou Ann
On 11/06/2010 10:05 AM, Shawn Walker wrote:
On 06/11/10 09:46 AM, Lou Ann Smith wrote:
While I was trying to verify a bug fix I tried to install build 134 (not
build 134.0.2) using the AI installer. In the manifest I defined entire
to be
<pkg name="[email protected],5.11-0.134:20100302T023003Z"/>
Using the full FMRI
I am also pointing at the /dev repository.
The machine installs 134.0.2 instead of 134. Is this the intended
behavior?
The ipkg /dev repository doesn't have 134.0.2 at the moment, but it
also doesn't have the version of entire that you've listed above, so I
assume you really meant 134.0.1?
With that said, what version of 'entire' was actually installed?
From what I recall, the incorporation for [email protected],5.11-0.134
allows packages from 134.0.2.
Cheers,
-Shawn
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
