Dave Miner wrote: > Dan Price wrote: >> On Fri 25 Jul 2008 at 07:57PM, [EMAIL PROTECTED] wrote: >>>> As I said in the bug report, I hate having to do this, but I hate >>>> bricking people's systems even more. >>> Perhaps we do need to do this now but do we know from either Ethan >>> and/or Jan where we are with >>> >>> 1979 libbe: be_activate needs to run installgrub >>> http://defect.opensolaris.org/bz/show_bug.cgi?id=1979 >>> >>> as I think it would be obviously better to just fix the issue. :-) >>> >>> I suppose refering to a URL on opensolaris.org is fine although I'm >>> wondering if it's time to begin delivering knowledge articles under >>> sun.com/msg. >> Brock pointed out to me that current users won't get this message >> anyway, since they won't be running the bits that contain the >> message if they just type 'image-update' without first updating >> their packaging bits to get the new 'pkg' which contains the >> message. >> >> I was specifically designing this for the *next* nasty flag day, >> not for the one we have now. Although, if we were going to e.g. >> issue an updated 2008.05 based ISO, then it'd be nice to get this >> fix in there. >> > > We are, that's the back-to-school thing, and it is expected to be in > there. The intention is to replace the main download image with that one. > > However, I agree that we are likely to continue to run into flag-day > issues occasionally, and it would be nice to have a way to notify users > of them more directly. I'm not sure the generic "review the notes" > message is going to do it, though; can we use the feed stuff that > Shawn's adding in some way here to get more specific and perhaps make > the message only appear when we believe there's a reason?
There is a critical update flag based on "critical actions" in the manifest of a package that causes the rss feed to indicate an entry for a related update was critical. However, I'm guessing it wasn't intended to be used for "flag days." In addition, while the feed supports it, we currently don't have any actions that get marked as critical. Either way, it seems like we need a tag or attribute for a pkg that indicates that such an update is a major event for the build version tree that it is part of. The rss feed could do something appropriate with it and the client could take advantage of it as well. You'd have to expound on exactly what you think the feed might do in response... -- Shawn Walker _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
