NetBSD Problem Report #46731

From www@NetBSD.org  Sat Jul 21 09:42:19 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 1E4D363B882
	for <gnats-bugs@gnats.NetBSD.org>; Sat, 21 Jul 2012 09:42:19 +0000 (UTC)
Message-Id: <20120721094218.4CA1063B85F@www.NetBSD.org>
Date: Sat, 21 Jul 2012 09:42:18 +0000 (UTC)
From: mrg@eterna.com.au
Reply-To: mrg@eterna.com.au
To: gnats-bugs@NetBSD.org
Subject: terminfo.db not present
X-Send-Pr-Version: www-1.0

>Number:         46731
>Category:       lib
>Synopsis:       terminfo.db not present
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    lib-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jul 21 09:45:00 +0000 2012
>Originator:     matthew green
>Release:        netbsd-6
>Organization:
>Environment:
>Description:
a static tcsh binary i built via pkgsrc standalone-tcsh in 2010
does not work properly today.

the problem is that terminfo.db is no longer present no the filesystem
and the static binary thus no longer has access to this data.

i wouldn't care about this if the binary was recent, but this is quite
an old binary in -current terms and we've never been OK with breaking
binary compat at this level after such long time.

all that needs to happen is to not mark terminfo.db as obsolete, but
it is kind of already too late for me since the file is deleted.

there's an argument that this would break update builds, but that is
not a useful argument since breaking installed users is significantly
worse, and handling the former is handled by UPDATING document.

(while not a netbsd-5 to netbsd-6 binary compat break, this is still
old/long enough for me to consider it a must-have for netbsd-6.)
>How-To-Repeat:
build a static tcsh binary sometime between terminfo.db appearing
and terminfo.cdb appearing.
>Fix:
don't mark terminfo.db obsolete.

Home	PR Database Search