From max@bourbon.sfc.wide.ad.jp  Sat May  3 13:04:50 1997
Received: from bourbon.sfc.wide.ad.jp (bourbon.sfc.wide.ad.jp [203.178.139.171])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA12682
          for <FreeBSD-gnats-submit@freebsd.org>; Sat, 3 May 1997 13:04:48 -0700 (PDT)
Received: from bourbon.sfc.wide.ad.jp (localhost [127.0.0.1]) by bourbon.sfc.wide.ad.jp (8.8.5/3.5Wpl104/21/97) with ESMTP id FAA14076; Sun, 4 May 1997 05:04:25 +0900 (JST)
Message-Id: <199705032004.FAA14076@bourbon.sfc.wide.ad.jp>
Date: Sun, 04 May 1997 05:04:24 +0900
From: Masafumi NAKANE/=?ISO-2022-JP?B?GyRCQ2Y6LDJtSjgbKEI=?= <max@wide.ad.jp>
Sender: max@bourbon.sfc.wide.ad.jp
To: jin@pesto.lbl.gov
Cc: FreeBSD-gnats-submit@freebsd.org
In-Reply-To: Your message of "Tue, 1 Apr 1997 13:18:29 -0800 (PST)"
Subject: Re: ghostscript-2.6.2 install script has a wrong chmod 444
References: <199704012118.NAA16984@pesto.lbl.gov>

>Number:         3483
>Category:       junk
>Synopsis:       Re: ghostscript-2.6.2 install script has a wrong chmod 444
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    gnats-admin
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat May  3 13:10:01 PDT 1997
>Closed-Date:    Sat May 3 17:32:08 PDT 1997
>Last-Modified:  Tue Nov 27 19:23:56 PST 2001
>Originator:     
>Release:        
>Organization:
>Environment:
>Description:
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: asami 
State-Changed-When: Sat May 3 17:32:08 PDT 1997 
State-Changed-Why:  
Bogus new PR, was a followup but didn't have the original PR# in subject. 
>Unformatted:
     > 	ghostscript-2.6.2 installation script has a chmod 444 command
     > on lib/ghostscript. This "chmod 444 command" causes none can
     > access lib/ghostscript directory, all ghostscript command fail.

This problem doesn't seem to be present in the current port.  And I
can't find any traces that this problem used to exist.

Please be specific which file has the chmod command in question.

     Thanks,
Max

-----------------------------------------------------------------------
          Masafumi NAKANE, Keio Univ., Dept. of Environmental Information
E-Mail : max@wide.ad.jp / max@FreeBSD.ORG
[URL] :  http://www.sfc.wide.ad.jp/~max/
