From owner-freebsd-ports@freebsd.org Mon Oct 5 23:45:05 2020 Return-Path: Delivered-To: freebsd-ports@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7BA07432B21 for ; Mon, 5 Oct 2020 23:45:05 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [107.204.234.170]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4C4xzN4S1bz4d9W for ; Mon, 5 Oct 2020 23:45:04 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.16.1/8.15.2) with ESMTP id 095Nj2wn018054; Mon, 5 Oct 2020 23:45:02 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.16.1/8.16.1/Submit) id 095Nj2eU018053; Mon, 5 Oct 2020 16:45:02 -0700 (PDT) (envelope-from david) Date: Mon, 5 Oct 2020 16:45:02 -0700 From: David Wolfskill To: Tatsuki Makino Cc: freebsd-ports@freebsd.org Subject: Re: Might an UPDATING entry be appropriate for a MINIMAL_PKG_VERSION bump? Message-ID: <20201005234502.GD1349@albert.catwhisker.org> Reply-To: freebsd-ports@freebsd.org References: <20201005125430.GU1349@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="+Xnt6BZa+I2KmHWw" Content-Disposition: inline In-Reply-To: X-Rspamd-Queue-Id: 4C4xzN4S1bz4d9W X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of david@catwhisker.org designates 107.204.234.170 as permitted sender) smtp.mailfrom=david@catwhisker.org X-Spamd-Result: default: False [-4.11 / 15.00]; ARC_NA(0.00)[]; HAS_REPLYTO(0.00)[freebsd-ports@freebsd.org]; FREEFALL_USER(0.00)[david]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:107.204.234.170:c]; NEURAL_HAM_LONG(-1.08)[-1.077]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; REPLYTO_DOM_NEQ_FROM_DOM(0.00)[]; DMARC_NA(0.00)[catwhisker.org]; SIGNED_PGP(-2.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.61)[-0.606]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_MEDIUM(-1.03)[-1.026]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_TO(0.00)[hotmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:7018, ipnet:107.192.0.0/12, country:US]; SUBJECT_ENDS_QUESTION(1.00)[]; MAILMAN_DEST(0.00)[freebsd-ports]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Oct 2020 23:45:05 -0000 --+Xnt6BZa+I2KmHWw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 06, 2020 at 08:31:05AM +0900, Tatsuki Makino wrote: > Hello. >=20 > In my case, > -x \*-kmod-\[0-9gv\] is added to portmaster because all packages that > install kernel modules contain -kmod in their names. This excludes *-kmod. > And when they are upgraded, I won't be installing them right away. >=20 > Then to install them I write PORTS_MODULES in src.conf. > PORTS_MODULES=3D\ > graphics/drm-fbsd12.0-kmod\ > graphics/gpu-firmware-kmod >=20 > They are created at the same time as the kernel. > .... But in order for them to be built, you need to have updated ports-mgmt/pkg ahead of time, or this kind of thing happens: | ... | --- kernel.full --- | linking kernel.full | ctfmerge -L VERSION -g -o kernel.full ... | text data bss dec hex filename | 22900304 1840729 3667344 28408377 0x1b17a39 kernel.full | Building /common/S1/obj/usr/src/amd64.amd64/sys/CANARY/kernel.debug | Building /common/S1/obj/usr/src/amd64.amd64/sys/CANARY/kernel | --- all --- | =3D=3D=3D> Ports module x11/nvidia-driver (all) | cd ${PORTSDIR:-/usr/ports}/x11/nvidia-driver; env -u CC -u CXX -u CPP = -u MAKESYSPATH -u MK_AUTO_OBJ -u MAKEOBJDIR MAKEFLAGS=3D"-j 16 -J 15,16= -j 16 -J 15,16 -D NO_MODULES_OBJ .MAKE.LEVEL.ENV=3DMAKELEVEL KERNEL=3Dkern= el TARGET=3Damd64 TARGET_ARCH=3Damd64" SYSDIR=3D/usr/src/sys PATH=3D/comm= on/S1/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin:/common/S1/obj/usr/src/am= d64.amd64/tmp/legacy/usr/bin:/common/S1/obj/usr/src/amd64.amd64/tmp/legacy/= bin:/common/S1/obj/usr/src/amd64.amd64/tmp/usr/sbin:/common/S1/obj/usr/src/= amd64.amd64/tmp/usr/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/l= ocal/sbin SRC_BASE=3D/usr/src OSVERSION=3D1202502 WRKDIRPREFIX=3D/common= /S1/obj/usr/src/amd64.amd64/sys/CANARY make -B clean build | =3D=3D=3D> Cleaning for nvidia-driver-440.100_1 | =3D=3D=3D> nvidia-driver-440.100_1 pkg(8) must be version 1.15.9 or grea= ter, but | you have 1.15.8. You must upgrade the ports-mgmt/pkg port first. | *** Error code 1 |=20 | Stop. Hence my query: Is an UPDATING entry warranted when MINIMAL_PKG_VERSION is bumped? Peace, david --=20 David H. Wolfskill david@catwhisker.org "the end of the pandemic is in sight" -- Donald Trump (while infected with SARS-COV-2) See http://www.catwhisker.org/~david/publickey.gpg for my public key. --+Xnt6BZa+I2KmHWw Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE4owz2QxMJyaxAefyQLJg+bY2PckFAl97r/5fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEUy OEMzM0Q5MEM0QzI3MjZCMTAxRTdGMjQwQjI2MEY5QjYzNjNEQzkACgkQQLJg+bY2 Pcn1aAgAmwxKlqhwC7TpnzSI9CI5cin3hsvgewxOnidvdu5J21Y+3+AKfpy47ajt 8zwsBVcRO/mGQaMH30avNC2pcaOoKO2oVpcTvd0V6XfmVcIsJ+4ux5shP+JiiCC7 8lydwpq/3Q5OoRX35qiZQuYW5lALLornW+Tej0hdCXEtoGtVyR4llhd1OKQrK+bW ihZ025IhdhwalRJWiDgyyqPv35KqtCTNQu+4FBJ8BXwE6OhVSiFNrTIT/dGwphAx mG+VJmkvluQGgfZ08kQFcKkiJvtP5sZKLJJg2ZnFZC7wYfL6YCtr3RhwNJPcTDBB BdIpsc4L+wYsrPKFjny3ID+FvN4glA== =vV65 -----END PGP SIGNATURE----- --+Xnt6BZa+I2KmHWw--