NetBSD Problem Report #47294

From jmmv@netbsd.org  Fri Dec  7 16:24:42 2012
Return-Path: <jmmv@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	by www.NetBSD.org (Postfix) with ESMTP id C72B363DFC7
	for <gnats-bugs@gnats.NetBSD.org>; Fri,  7 Dec 2012 16:24:41 +0000 (UTC)
Message-Id: <20121207162441.95EB014A26E@mail.netbsd.org>
Date: Fri,  7 Dec 2012 16:24:41 +0000 (UTC)
From: jmmv@netbsd.org
Reply-To: jmmv@netbsd.org
To: gnats-bugs@gnats.NetBSD.org
Subject: Add support for major version upgrades to sysupgrade
X-Send-Pr-Version: 3.95

>Number:         47294
>Category:       pkg
>Synopsis:       Add support for major version upgrades to sysupgrade
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          closed
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Fri Dec 07 16:25:00 +0000 2012
>Closed-Date:    Thu Jul 24 15:04:56 +0000 2014
>Last-Modified:  Thu Jul 24 15:04:56 +0000 2014
>Originator:     Julio Merino
>Release:        NetBSD 5.1_STABLE
>Organization:
Julio Merino
>Environment:


System: NetBSD homeworld.netbsd.org 5.1_STABLE NetBSD 5.1_STABLE (NBMAIL) #2: Mon Jun 11 07:45:45 UTC 2012 root@franklin.NetBSD.org:/home/netbsd/5/amd64/kern-compile/NBMAIL amd64
Architecture: x86_64
Machine: amd64
>Description:
	pkgsrc/sysutils/sysupgrade does not currently support upgrades that
	require a reboot between the installation of the new kernel and the
	installation of new sets.  Such upgrades will break half-way through
	because the new installed binaries will stop working until the user
	reboots.  It's not a critical problem, but it certainly is not a good
	procedure.

	The main idea to fix this is to split the upgrade procedure in two
	pieces: before reboot and after reboot, and add some "heuristics" to
	determine if it's safe to do the upgrade without a reboot in between.
	If the upgrade needs a reboot, the user would be asked to reboot the
	machine after the installation of the new kernel/modules, and type
	a new command to resume the upgrade (e.g. "sysupgrade resume").

	Such resume command may come in handy to also continue upgrades that
	break in the middle of the process, as is the case when some
	postinstall checks fail.

	Additionally, provide an optionally-installable rc.d script that can
	detect an "open upgrade" and resume it during system restart, so that
	the user is not required to type anything else after the reboot.
>How-To-Repeat:
	Upgrade from 5.0 to 6.0 using sysupgrade and see the system "explode"
	along the way.
>Fix:
	SMOP.

>Release-Note:

>Audit-Trail:

Responsible-Changed-From-To: pkg-manager->jmmv
Responsible-Changed-By: jmmv@NetBSD.org
Responsible-Changed-When: Fri, 07 Dec 2012 16:26:18 +0000
Responsible-Changed-Why:
Take this.  Filed it as a to-do item for myself.


Responsible-Changed-From-To: jmmv->pkg-manager
Responsible-Changed-By: jmmv@NetBSD.org
Responsible-Changed-When: Thu, 24 Jul 2014 15:03:53 +0000
Responsible-Changed-Why:


State-Changed-From-To: open->closed
State-Changed-By: jmmv@NetBSD.org
State-Changed-When: Thu, 24 Jul 2014 15:04:56 +0000
State-Changed-Why:
Actually, let me mark this to-do as closed as I moved it to:
https://github.com/jmmv/sysupgrade/issues/1


>Unformatted:

Home	PR Database Search