NetBSD Problem Report #60173

From www@netbsd.org  Thu Apr  2 20:10:51 2026
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256
	 client-signature RSA-PSS (2048 bits) client-digest SHA256)
	(Client CN "mail.netbsd.org", Issuer "R12" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id AF8CB1A9239
	for <gnats-bugs@gnats.NetBSD.org>; Thu,  2 Apr 2026 20:10:51 +0000 (UTC)
Message-Id: <20260402201050.988461A923C@mollari.NetBSD.org>
Date: Thu,  2 Apr 2026 20:10:50 +0000 (UTC)
From: opensauce04@gmail.com
Reply-To: opensauce04@gmail.com
To: gnats-bugs@NetBSD.org
Subject: enchant2 doesn't install groff dependency, causing build to fail
X-Send-Pr-Version: www-1.0
X-From4GNATS: "opensauce04@gmail.com via gnats" <gnats-admin@NetBSD.org>

>Number:         60173
>Category:       pkg
>Synopsis:       enchant2 doesn't install groff dependency, causing build to fail
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Apr 02 20:15:00 +0000 2026
>Last-Modified:  Fri Apr 03 17:00:02 +0000 2026
>Originator:     Daniel
>Release:        NetBSD 11.0_RC2 / pkgsrc 2026Q1
>Organization:
>Environment:
NetBSD netbook.powerhub 11.0_RC2 NetBSD 11.0_RC2 (GENERIC) #0: Wed Mar  4 21:02:00 UTC 2026  mkrepro@mkrepro.NetBSD.org:/usr/src/sys/arch/amd64/compile/GENERIC amd64
>Description:
No matter what I do, I can't seem to get the current version of enchant2 to automatically install the `groff` package as a dependency. I've tried cleaning enchant2 multiple times in a couple of ways, but it always just doesn't install groff, which it requires for the build, resulting in:

sh: groff: not found

The Makefile does contain this:

USE_TOOLS+=             autoconf gmake groff pkg-config

...so it should be installing, right? Why doesn't it? I don't understand the recipe format of pkgsrc well enough to understand the issue myself.

This issue can be worked around by installing groff manually, but that isn't really a solution to the core problem.
>How-To-Repeat:
Attempt to build textproc/enchant2 on the current 2026Q1 (commit 69636b6fcb37836ed7abd7335dec2db101a65d0c), and observe the build failing with the above message.
>Fix:

>Audit-Trail:
From: Thomas Klausner <wiz@netbsd.org>
To: NetBSD bugtracking <gnats-bugs@netbsd.org>
Cc: 
Subject: Re: pkg/60173: enchant2 doesn't install groff dependency, causing
 build to fail
Date: Thu, 2 Apr 2026 22:26:24 +0200

 On Thu, Apr 02, 2026 at 08:15:00PM +0100, opensauce04@gmail.com via gnats wrote:
 > sh: groff: not found

 groff is part of the NetBSD 'text' set, and pkgsrc assumes that this
 was installed when installing NetBSD itself.
  Thomas

From: Daniel Bradbury <opensauce04@gmail.com>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: pkg/60173: enchant2 doesn't install groff dependency, causing
 build to fail
Date: Thu, 2 Apr 2026 21:36:31 +0100

 > The following reply was made to PR pkg/60173; it has been noted by GNATS.
 >
 > From: Thomas Klausner <wiz@netbsd.org>
 > To: NetBSD bugtracking <gnats-bugs@netbsd.org>
 > Cc:
 > Subject: Re: pkg/60173: enchant2 doesn't install groff dependency, causing
 >   build to fail
 > Date: Thu, 2 Apr 2026 22:26:24 +0200
 >
 >   On Thu, Apr 02, 2026 at 08:15:00PM +0100, opensauce04@gmail.com via gnats wrote:
 >   > sh: groff: not found
 >   
 >   groff is part of the NetBSD 'text' set, and pkgsrc assumes that this
 >   was installed when installing NetBSD itself.
 >    Thomas
 Given that it's clearly possible that this isn't the case, is this 
 really a good assumption to make?

From: Daniel Bradbury <opensauce04@gmail.com>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: pkg/60173: enchant2 doesn't install groff dependency, causing
 build to fail
Date: Fri, 3 Apr 2026 11:49:06 +0100

 > The following reply was made to PR pkg/60173; it has been noted by GNATS.
 >
 > From: Daniel Bradbury <opensauce04@gmail.com>
 > To: gnats-bugs@netbsd.org
 > Cc:
 > Subject: Re: pkg/60173: enchant2 doesn't install groff dependency, causing
 >   build to fail
 > Date: Thu, 2 Apr 2026 21:36:31 +0100
 >
 >   > The following reply was made to PR pkg/60173; it has been noted by GNATS.
 >   >
 >   > From: Thomas Klausner <wiz@netbsd.org>
 >   > To: NetBSD bugtracking <gnats-bugs@netbsd.org>
 >   > Cc:
 >   > Subject: Re: pkg/60173: enchant2 doesn't install groff dependency, causing
 >   >   build to fail
 >   > Date: Thu, 2 Apr 2026 22:26:24 +0200
 >   >
 >   >   On Thu, Apr 02, 2026 at 08:15:00PM +0100, opensauce04@gmail.com via gnats wrote:
 >   >   > sh: groff: not found
 >   >
 >   >   groff is part of the NetBSD 'text' set, and pkgsrc assumes that this
 >   >   was installed when installing NetBSD itself.
 >   >    Thomas
 >   Given that it's clearly possible that this isn't the case, is this
 >   really a good assumption to make?

 Or at the very least, shouldn't there be some warning about this for 
 recipes that assume the existence of packages from a certain set?

 I wasn't aware that the text set was expected in pkgsrc, so I assumed 
 that dependency resolution was just broken in some way.

From: Leonardo Taccari <leot@NetBSD.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: pkg/60173: enchant2 doesn't install groff dependency, causing build to fail
Date: Fri, 03 Apr 2026 18:57:51 +0200

 Daniel Bradbury via gnats writes:
 > [...]  
 > Or at the very least, shouldn't there be some warning about this for 
 > recipes that assume the existence of packages from a certain set?
 >  
 > I wasn't aware that the text set was expected in pkgsrc, so I assumed 
 > that dependency resolution was just broken in some way.

 This is documented in The pkgsrc Guide currently as
 "5.2.1. Requirements":

  | To build packages from source, you need a working C compiler. On NetBSD, you
  | need to install the comp and the text distribution sets. If you want to
  | build X11-related packages, the xbase and xcomp distribution sets are
  | required, too.

 Maybe there could be a check to the corresponding /etc/mtree/set.* files
 to make a bit more helpful warning/error message.

Home	PR Database Search