Thanks for all of the notes. [EMAIL PROTECTED] wrote: > >> With regard to the URL, it *should* be something as easy as that. >> Doesn't it have more affinity to indiana or the OpenSolaris distro >> though? ipkg is ostensibly portable, and the image-update subcommand is >> somewhat OpenSolaris specific. There appears to be an official (yet >> unmaintained) doc here: >> http://dlc.sun.com/osol/docs/content/IPS/ggfwk.html > > Actually, that *is* the official documentation and it is maintained but > perhaps the "workaround" isn't documented there (like many such > limitations, it's often documented in the release notes which folks may > or may not read).
Good points. The page I pointed to seemed to be about "image-update" and includes a section on updating from RC2, but I guess that was all for the official release. It does make sense for any 'late breaking' news like image-update issues to go into release notes in some ways and I'm sure that's the regular way of doing things. To me, with the web being what it is, it seems to be a bit anachronistic. I hope my saying "yet unmaintained" wasn't taken the wrong way. It's intended as constructive feedback. To me it just appeared that way since it did cover updating with image-update, and I had read things sent to the mailing lists which weren't covered there. When I went to update, I looked for something that had the contents of the email sent out to indiana-discuss and the only place I could find it was in the mail archives. The main place I looked was the project page on opensolaris.org, but also used my search engine. Now I know the release notes are to cover these updates (and will have a more specific image-update note at some point). Maybe I didn't do enough searching, but I suspect I did more than the average user. > >> The last time I needed to find the notes on the update, I had to dig >> into the mail archives. > > We've talked about providing a feed of each of the release notes on a > build-by-build basis but I don't believe anyone has scoped that out > yet. But it would be great to have a well known page or perhaps a > OpenSolaris knowledge article like the ones available on sun.com/msg. Having pkg display a message (or URL) could be useful. Dan's fix to at least getting them to the release notes sounds simple enough to me as a start. :) > >> I didn't mind a slight bit of pain from the initial release, but it >> seems each image-update is requiring a separate workaround or two. I >> even read things carefully and got hung up on updating SUNWipkg, since >> it wasn't obvious that it was updating to a newer timestamp of the same >> version. > > As the release notes indicate, there shouldn't be any workarounds > required at the moment if you're running build 93 or later already. No, but I had to run the same command from b86 to b91 (along with the beadm mount), though I'm not sure if it's for the same reasons. I assume I need to do this for b91 to b93 as well? The release notes don't seem to cover this case. I know it's likely idempotent anyway, but it's still not really clear what I need to do. > That's the case whether you installed from the build 93 ISO or had > previously done an image-update. Of course, that doesn't guarantee > we're not going to face similar sorts of flag-days in the future which > means we need 1) a mechanism to help the user across those jumps and 2) > to do better testing prior to pushing out packages. And I'd suggest build to build (i.e. 86 to 91 to 93). This means I'd need to know if what to do if transitioning 86 -> 91 (when it's current) or 86 -> 93 (once it's current) and 91 -> 93 (if I'd already updated once). I don't know if all of these are intended at the moment. I've been updating because I like to be able to run/test the latest software and file/comment on bugs as I run into them. > > Of course, the other issue is that the default authority was pointing > to the (unstable) trunk. In the future, we're likely to change this by > pointing the default authority to a stable sustaining branch and a "pkg > image-update" will by default bring over a more extensively tested set > of packages. This last point makes the most sense to me for most end users. One question. Would it make sense to force the user (unless they run with a -f flag or some such change) to always have to pkg update their SUNWipkg to the latest for their given build before running an image-update? By definition you need to have access to a repository, so this could be checked before actually performing the image-update. Since so many things rely on a working SUNWipkg, this could be a good policy to avoid as many issues as possible. - Matt _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
