NetBSD Problem Report #47095

From www@NetBSD.org  Sat Oct 20 02:17:16 2012
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	by www.NetBSD.org (Postfix) with ESMTP id 448ED63DFCC
	for <gnats-bugs@gnats.NetBSD.org>; Sat, 20 Oct 2012 02:17:16 +0000 (UTC)
Message-Id: <20121020021715.8F81B63DFAE@www.NetBSD.org>
Date: Sat, 20 Oct 2012 02:17:15 +0000 (UTC)
From: jakllsch@kollasch.net
Reply-To: jakllsch@kollasch.net
To: gnats-bugs@NetBSD.org
Subject: MKREPRO=yes is unacceptable for releases
X-Send-Pr-Version: www-1.0

>Number:         47095
>Category:       misc
>Synopsis:       MKREPRO=yes is unacceptable for releases
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    misc-bug-people
>State:          closed
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Sat Oct 20 02:20:00 +0000 2012
>Closed-Date:    Fri Jun 17 17:33:40 +0000 2022
>Last-Modified:  Fri Jun 17 17:33:40 +0000 2022
>Originator:     Jonathan Kollasch
>Release:        6.0
>Organization:
>Environment:
>Description:
MKREPRO=yes builds are unacceptable for release builds.
>How-To-Repeat:
install 6.0, be unable to find any useful information about who or what built the release
>Fix:
don't bulid releases with MKREPRO=yes

>Release-Note:

>Audit-Trail:
From: Alan Barrett <apb@cequrux.com>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: misc/47095: MKREPRO=yes is unacceptable for releases
Date: Sat, 20 Oct 2012 12:32:09 +0200

 On Sat, 20 Oct 2012, jakllsch@kollasch.net wrote:
 >>Description:
 >MKREPRO=yes builds are unacceptable for release builds.
 >>How-To-Repeat:
 >install 6.0, be unable to find any useful information about who or what built the release
 >>Fix:
 >don't bulid releases with MKREPRO=yes

 I agree that this is problem, but I have a different idea for a 
 fix:

 Modify MKREPRO to allow it to insert sanitised information into 
 places like /etc/release, the output from sysctl kern.version, 
 and the output from uname -v.  Two MKREPRO builds with the same 
 sanitised information should be identical, but two MKREPRO builds 
 with different sanitised information should be different.

 I have been meaning to work on this, but I have not got around to 
 it.  For my own use, I want the framework to allow me to embed my 
 private branch name and revision number into the kernel version,
 along with comments like "testing a patch for PR nnnn", so that
 "uname -a" can help me verify that I booted the correct test kernel.

 --apb (Alan Barrett)

State-Changed-From-To: open->feedback
State-Changed-By: kre@NetBSD.org
State-Changed-When: Fri, 17 Jun 2022 04:35:36 +0000
State-Changed-Why:
I believe that recent releases are with MKREPRO=yes and that all now
seems to be happy.

Is there any reason that this PR should not be closed?


State-Changed-From-To: feedback->closed
State-Changed-By: jakllsch@NetBSD.org
State-Changed-When: Fri, 17 Jun 2022 17:33:40 +0000
State-Changed-Why:
There's enough info in the kernel version string these days with MKREPRO to satisfy me


>Unformatted:

Home	PR Database Search