NetBSD Problem Report #50727

From www@NetBSD.org  Fri Jan 29 18:55:23 2016
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.NetBSD.org [199.233.217.200])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.netbsd.org", Issuer "Postmaster NetBSD.org" (verified OK))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 3710A7ABF7
	for <gnats-bugs@gnats.NetBSD.org>; Fri, 29 Jan 2016 18:55:23 +0000 (UTC)
Message-Id: <20160129185522.3AFB77ACB5@mollari.NetBSD.org>
Date: Fri, 29 Jan 2016 18:55:22 +0000 (UTC)
From: richard@NetBSD.org
Reply-To: richard@NetBSD.org
To: gnats-bugs@NetBSD.org
Subject: ghostscript-agpl seems inoperational, missing gs_init.ps
X-Send-Pr-Version: www-1.0

>Number:         50727
>Category:       pkg
>Synopsis:       ghostscript-agpl seems inoperational, missing gs_init.ps
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    pkg-manager
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Jan 29 19:00:00 +0000 2016
>Closed-Date:    Wed May 06 10:22:48 +0000 2020
>Last-Modified:  Wed May 06 10:22:48 +0000 2020
>Originator:     Richard PALO
>Release:        current
>Organization:
>Environment:
SunOS omnis 5.11 omnidev-0-g4ba11dd i86pc i386 i86pc

>Description:
having changed to give recent ghostscript-agpl a try where before I used -gpl, seems to cause no end of problems... of the sort:

GPL Ghostscript 9.18: Can't find initialization file gs_init.ps.

First noticed in a failed bulkbuild for the devel/doxygen package
all on SunOS i386.
>How-To-Repeat:
built ghostscript-agpl

simply 'gs' is enough to reproduce.

my options are:
Any of the following general options may be selected:
	debug	 Enable debugging facilities in the package.
	disable-compile-inits	Disable compile time implicit initialization.
	fontconfig	 Enable FONTCONFIG (fonts/fontconfig) support.
	x11	 Enable X11 support.

These options are enabled by default:
	fontconfig x11

These options are currently enabled:
	fontconfig x11

You can select which build options to use by setting PKG_DEFAULT_OPTIONS
or PKG_OPTIONS.ghostscript.

Option cups is unsupported, so disabling it has no effect.

>Fix:

>Release-Note:

>Audit-Trail:
From: "John D. Baker" <jdbaker@mylinuxisp.com>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: pkg/50727: ghostscript-agpl seems inoperational, missing gs_init.ps
Date: Thu, 11 Feb 2016 12:12:18 -0600 (CST)

 "Me, too!"

 System:

 NetBSD skuld 7.0_STABLE NetBSD 7.0_STABLE (SKULD) #15: Sat Feb  6 17:02:24 CST 2016  sysop@yggdrasil.technoskunk.fur:/r0/build/netbsd-7/obj/amd64/sys/arch/amd64/compile/SKULD amd64

 Context:  Same as submitter, updating "devel/doxygen".

 I've been using "print/ghostscript-agpl" for a few years now, including
 building "devel/doxygen" on a number of platforms (mostly i386/amd64
 but also macppc and evbmips64-el) and this is the first time it's failed.

 -- 
 |/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
 |\ / jdbaker[snail]mylinuxisp[flyspeck]com    OpenBSD            FreeBSD
 | X  No HTML/proprietary data in email.   BSD just sits there and works!
 |/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645

From: "John D. Baker" <jdbaker@mylinuxisp.com>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: pkg/50727: ghostscript-agpl seems inoperational, missing gs_init.ps
Date: Thu, 11 Feb 2016 20:36:51 -0600 (CST)

 And just like that, it "magically" succeeded this time.  I don't really
 know what was different between the first several attempts and now.

 As I was running 'pkg_rolling-replace' in each case, after the most
 recent failed attempt, I set about cleaning up "leftovers" in my
 ${WRKOBJDIR} before trying again.

 On the next attempt, it completed configuration and "devel/doxygen" is
 now building.

 -- 
 |/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
 |\ / jdbaker[snail]mylinuxisp[flyspeck]com    OpenBSD            FreeBSD
 | X  No HTML/proprietary data in email.   BSD just sits there and works!
 |/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645

From: "John D. Baker" <jdbaker@mylinuxisp.com>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: pkg/50727: ghostscript-agpl seems inoperational, missing gs_init.ps
Date: Thu, 11 Feb 2016 20:53:51 -0600 (CST)

 On Thu, 11 Feb 2016, John D. Baker wrote:

 > On the next attempt, it completed configuration and "devel/doxygen" is
 > now building.

 Oops.  I wasn't paying attention to just when the failure occurred.  It
 was at the end of the build, not during config.  It still fails as before.

 -- 
 |/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
 |\ / jdbaker[snail]mylinuxisp[flyspeck]com    OpenBSD            FreeBSD
 | X  No HTML/proprietary data in email.   BSD just sits there and works!
 |/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645

From: "John D. Baker" <jdbaker@mylinuxisp.com>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: pkg/50727: ghostscript-agpl seems inoperational, missing gs_init.ps
Date: Fri, 19 Feb 2016 07:42:00 -0600 (CST)

 When building "doxygen" on a completely clean system, "ghostscript-agpl"
 works.  On a machine with a previous older installation, even after
 removing and rebuilding "doxygen" and "ghostscript-agpl" from scratch,
 it fails.

 -- 
 |/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
 |\ / jdbaker[snail]mylinuxisp[flyspeck]com    OpenBSD            FreeBSD
 | X  No HTML/proprietary data in email.   BSD just sits there and works!
 |/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645

From: "John D. Baker" <jdbaker@mylinuxisp.com>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: pkg/50727: ghostscript-agpl seems inoperational, missing gs_init.ps
Date: Thu, 24 Mar 2016 11:38:35 -0500 (CDT)

 On Thu, 11 Feb 2016, John D. Baker wrote:

 > "Me, too!"
 > 
 > System:
 > 
 > NetBSD skuld 7.0_STABLE NetBSD 7.0_STABLE (SKULD) #15: Sat Feb  6 17:02:24 CST 2016  sysop@yggdrasil.technoskunk.fur:/r0/build/netbsd-7/obj/amd64/sys/arch/amd64/compile/SKULD amd64
 > 
 > Context:  Same as submitter, updating "devel/doxygen".

 So far, I've observed this failure only on (semi-)diskless amd64 systems
 (netbsd-7 and -current).  That is, they have local disk for swap, "/tmp"
 and to hold ${WRKOBJDIR}, but are otherwise operating entirely over NFS.
 The same machines, building entirely to local disk (netbsd-7 only) do
 not encounter this problem.

 That is, "gs_init.ps" truly does not exist, but building/updating "doxygen"
 fails only in the NFS case on amd64 hosts.

 My likewise (semi-)diskless i386 systems do not exhibit this failure.

 I have not tried building this package on any other architecture so far,
 whether local disk or (semi-)diskless.

 -- 
 |/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
 |\ / jdbaker[snail]mylinuxisp[flyspeck]com    OpenBSD            FreeBSD
 | X  No HTML/proprietary data in email.   BSD just sits there and works!
 |/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645

From: "John D. Baker" <jdbaker@mylinuxisp.com>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: pkg/50727: ghostscript-agpl seems inoperational, missing gs_init.ps
Date: Fri, 3 Jun 2016 15:45:50 -0500 (CDT)

 It seems that the underlying filesystem of ${WRKOBJDIR} determines whether
 "print/ghostscript-agpl" will succeed or fail when "devel/doxygen" is
 building its "stage-install" phase.

 If ${WRKOBJDIR} is on ffs on local disk when "ghostscript-agpl" is
 built/installed, the later stage-install of "doxygen" will succeed
 regardless of where ${WRKOBJDIR} is located during the build of "doxygen".

 If ${WRKOBJDIR} is on tmpfs or NFS when "ghostscript-agpl" is
 built/installed, the later stage-install of "doxygen" will fail as noted
 previously in this PR, regardless of where ${WRKOBJDIR} is when building
 "doxygen".

 In neither case does the file "gs_init.ps" appear anywhere under
 ${PREFIX} (i.e., typically "/usr/pkg").

 -- 
 |/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
 |\ / jdbaker[snail]mylinuxisp[flyspeck]com    OpenBSD            FreeBSD
 | X  No HTML/proprietary data in email.   BSD just sits there and works!
 |/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645

State-Changed-From-To: open->feedback
State-Changed-By: leot@NetBSD.org
State-Changed-When: Sat, 30 Mar 2019 12:16:41 +0000
State-Changed-Why:
Richard, John, can you still reproduce this problem?

I have retried to run `gs' and it seems that I am not able to
reproduce it but according the discussion probably that's
dependes on the setup/environment.  Given that default used
ghostscript is ghostscript-agpl it's probably worth to try
to investigate that further if still problematic.


Thanks!


State-Changed-From-To: feedback->closed
State-Changed-By: leot@NetBSD.org
State-Changed-When: Wed, 06 May 2020 10:22:48 +0000
State-Changed-Why:
<richard> has no longer the setup the reproduce that and
asked to close it.

John, can you still reproduce that?

(I think that was probably fixed in more recent ghostscript-agpl
versions but if you still see that do not hesitate to reply to
this PR so we can reopen it.)


>Unformatted:

Home	PR Database Search