From nobody Thu Apr 04 17:07:51 2024 X-Original-To: freebsd-ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4V9Sjq5shvz5Fc4p for ; Thu, 4 Apr 2024 17:07:59 +0000 (UTC) (envelope-from portmaster@bsdforge.com) Received: from udns.ultimatedns.net (udns.ultimatedns.net [24.113.41.81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "ultimatedns.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4V9Sjq309wz4hDr for ; Thu, 4 Apr 2024 17:07:59 +0000 (UTC) (envelope-from portmaster@bsdforge.com) Authentication-Results: mx1.freebsd.org; none Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.16.1/8.16.1) with ESMTP id 434H7qjG077730; Thu, 4 Apr 2024 10:07:58 -0700 (PDT) (envelope-from portmaster@bsdforge.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ultimatedns.net; s=mx99; t=1712250478; x=1712251078; r=y; bh=wQtgkSAJk833CQlpCxr+KtWw5Wli9Z8qdoMY50mN9cQ=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=pZ4nIX4c0OVNLu+efYWXgaw84TwwB6SpXm2PCIC4sVEWtiW4HPrG2TlpevMX1+231 q6suRLC6k6UVw6cg2mx0OPxqMZb1b0T35kLb2HQ6HNn/TfbTydPUwRVmx58gkNb/P9 kzUA3AI0Fs18kK2XrYT4ajtl5GlPDpXMdTEX2ChQe5fsHupYsr5IeZzyAaht1dGv70 NFf6sDCxqDi5DOlCNv4WNpCDNio0hbaqcpm/iZjRSsiV8aaKGhFPKjd6hs+o5LKvKe SK2cXF0Krcc6uMWp7iw6Oj2950foFlvGIGhe2+TnSoISS3ioYZ5YAlEzQZDSWRcGX6 LHYFmSfHQgKXw== List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 Date: Thu, 04 Apr 2024 10:07:51 -0700 From: Chris To: Michael Gmelin Cc: freebsd-ports Subject: Re: poudriere(8) short circuits my ability to build packages In-Reply-To: <9391BCFF-61B6-4151-92E8-7D2984563DF6@grem.de> References: <78550638a3787fd0897093fdad463a00@bsdforge.com> <9391BCFF-61B6-4151-92E8-7D2984563DF6@grem.de> User-Agent: UDNSMS/17.0 Message-ID: <4fb5eddd1ec4b42ded9ff224006bf358@bsdforge.com> X-Sender: portmaster@bsdforge.com Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US] X-Rspamd-Queue-Id: 4V9Sjq309wz4hDr On 2024-04-04 03:43, Michael Gmelin wrote: >> On 4. Apr 2024, at 09:31, Chris wrote: >> >> I do all of my development in jails. As such I have no use for >> poudriere(8). >> But an attempt to build editors/vscode threw the following: >> >> The limit imposed by poudriere(8) for the maximum number of files allowed >> to be >> opened by a jail (default 1024) is exceeded during the build of vscode. >> To successfully build vscode with poudriere(8), you must add the following >> line to poudriere.conf: >> MAX_FILES_vscode=8192 >> > > This message is coming from here and is shown unconditionally: > > https://cgit.freebsd.org/ports/tree/editors/vscode/Makefile#n184 > > It is not an error message, it tells you what to configure when building > that port > with poudriere. If you dislike it, please suggest better wording to the port > maintainer. It *appears* (from the message) that poudriere would be building the package. Not make(1) within the ports framework within my already created/running jail. Maybe omit the "limit imposed by poudriere(8)" portion from the message? Which, I guess is moot. Now that the limit appears to have been increased. > >> What the... I just want to build a package. Why do I care about poudriere >> limitations, or poudriere at all? How can I just build a package. Users >> (or Maintainers) aren't forced to use poudriere, are they? > > Even though poudriere is probably not your problem here, learning how to use > poudriere effectively would be time well spent. Indeed. As a maintainer, I do attempt to stay abreast of any changes regrding poudriere. This error appeared to be a new change, which brought me to inquire here. :) Thanks for taking the time to help, Michael! :) > > -m -- --Chris Hutchinson