Debian bug report logs - #1099
perl bug

Package: perl; Reported by: jimr@simons-rock.edu; 109 days old.

Message received at debian-bugs:


From simons-rock.edu!jimr Fri Jul 14 14:17:07 1995
Return-Path: <jimr@simons-rock.edu>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0sWs6d-00065oC; Fri, 14 Jul 95 14:17 PDT
Received: from plato.simons-rock.edu by pixar.com with SMTP id AA09008
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Fri, 14 Jul 1995 14:15:33 -0700
Received: from simons-rock.edu by plato.simons-rock.edu with smtp
	(Smail3.1.29.1 #3) id m0sWs6W-000018C; Fri, 14 Jul 95 17:17 EDT
Message-Id: <m0sWs6W-000018C@plato.simons-rock.edu>
Reply-To: jimr@simons-rock.edu
X-Mailer: MH 6.8.3
To: Debian Bugs <debian-bugs@pixar.com>
Dcc: 
Subject: perl bug
Date: Fri, 14 Jul 1995 17:17:00 -0400
From: "James A. Robinson" <jimr@simons-rock.edu>


Package: perl
Version: 5.001-3

perl's postinst does not prompt the user when warning about running
perlconfig.  Wouldn't it be better if it said "... press any key to
continue: "?

Odd occurance: I did a `dpkg --auto --install --no-also-select ./` in
the devel directory, and dpkg unpacked an configured everything
(correctly), but perl's postinst failed to detect
/usr/include/linux/kernel.h, and warned me that it was not going to
run perlconfig.  Well, I've looked at the source package, and it does
not create/destroy the /usr/include/linux, and source was unpacked
before perl's postinst was called...  So I can't figure out why it
didn't detect the header file before.  I've re-run the postinst, and
it works again.  Any ideas on what might have happened?

Acknowledgement sent to jimr@simons-rock.edu:
New bug report received and forwarded. Full text available.
Report forwarded to debian-devel@pixar.com:
Bug#1099; Package perl. Full text available.
Ian Jackson / iwj10@thor.cam.ac.uk, with the debian-bugs tracking mechanism
This page last modified 07:43:01 GMT Wed 01 Nov