On Wed, Jul 22, 2009 at 09:14:20PM +0200, Pierre-Emmanuel Andr? wrote: > On Wed, Jul 22, 2009 at 04:55:27PM +0200, Henning Brauer wrote: > > * Jason Dixon <ja...@dixongroup.net> [2009-07-21 23:06]: > > > On Tue, Jul 21, 2009 at 03:36:54PM -0500, Matthew Weigel wrote: > > > > Anil Madhavapeddy wrote: > > > > > > > >> Most users wont read the commit log, but do will a binary package > > > >> upgrade when the next release it out; can we have a post-install > > > >> message or something that warns people of this? > > > > > > > > Isn't post-install a little late? :-) > > > > > > > > IIRC, I had this problem moving from 8.2 to 8.3 (when upgrading my > > > > server from OpenBSD 4.3 to 4.4), and that happened when I was following > > > > > > > > the upgrade guide that specifically calls out the issue in the upgrade > > > > guide (http://www.openbsd.org/faq/upgrade44.html). > > > > > > > > Post-install isn't actually too late, since installing is not the same > > > > as running (which is where the problem is), but on a system with a > > > > decent number of packages it's hard to go through the post-install > > > > messages of EVERY upgraded package looking for problems at OS upgrade > > > > time. I dunno what a better solution is, having it in the upgrade > > > > guide > > > > seems like the best spot but obviously it's not perfect either. > > > > > > Reasonable solution (examples): > > > > > > http://marc.info/?l=openbsd-ports-cvs&m=120637961514930&w=2 > > > http://marc.info/?l=openbsd-misc&m=120631560919405&w=2 > > > http://undeadly.org/cgi?action=article&sid=20080324162049 > > > > > > Expect an Undeadly story soonish. > > > > the upgrade47.html entry is the most important really. > > I agree with Henning: the upgrade47.html is the most important. > And why not a little story on Undeadly (jason@ ?) ?
It's already in the queue. -- Jason Dixon DixonGroup Consulting http://www.dixongroup.net/
