Prashant Srinivasan wrote:
Brock Pytlik wrote:
Prashant Srinivasan wrote:
Hello,
I'm seeing the following pkg behavior on a 2008.11 system(it's an EC2
instance actually, but that probably doesn't matter). The instance
runs snv_101b. It has SUNWruby18 (from b101) installed. I'd like to
upgrade SUNWruby18 to the version in the dev repository( from
snv_111) that has the latest versions of Ruby/Rubygems. I changed
the preferred package authority to be http://pkg.opensolaris.org/dev
and attempted to upgrade the package, but pkg does not spot any updates.
Can someone please point out what I'm doing wrong here? (if it turns
out to be a bug, I'd be happy to file it as well).
pkg and your system is working as expected. SUNWruby18 is part of the
entire incorporation. That means you can't take just that package
forward,
Thanks for the quick response.
hmmm . . . what does pkg do under the hood when I issue a "pkg install
SUNWruby18" and it responds with "No updates available for this image. "?
It's not checking for a new rev. of the package, since that test would
have resulted in the finding of an updated version. It couldn't have
tested for the availability of a new image, since that test, in my
configuration, would have lead it to find updates to the entire image.
What does it do that makes it get back with "No updates are available
for this image"?
Install only shows packages you *can* install given the constraints in
place. So, the message was correct.
If you wanted to see if updates were available for your image, you would
need to use "pkg image-update -nv".
that's roughly equivalent to dim sum patching, which isn't allowed
under IPS. You can either wait for the next release,
Good to know that this feature is in the pipeline! I've had some Ruby
users mention that they didn't want to do the image-update/reboot to
update( though the aversion is probably more psychological than anything
else ).
image-update your system to b111, or publish your own version of
SUNWruby18 against build 101.
hmmm . . . for this instance, I'll just pick up the Ruby build from the
SFWNV gate and install it on my EC2 instance. I'll look forward to the
individual package update feature.
I think you've misunderstood.
IPS can already update individual packages today. However, the
*packages* as they are currently published are constrained to not allow
you to update between builds.
At some later point, some packages will be changed to allow you to
update individual ones. However, which packages, when, and how that
will be done hasn't been decided yet.
Cheers,
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
