From nobody Sat Oct 21 07:23:15 2023 X-Original-To: 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 4SCCbz6qY0z4xdTl for ; Sat, 21 Oct 2023 07:23:27 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (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 4SCCby3nJQz4bC6 for ; Sat, 21 Oct 2023 07:23:25 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of junchoon@dec.sakura.ne.jp has no SPF policy when checking 153.125.133.21) smtp.mailfrom=junchoon@dec.sakura.ne.jp; dmarc=none Received: from kalamity.joker.local (123-1-80-101.area1b.commufa.jp [123.1.80.101]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 39L7NFUb050548 for ; Sat, 21 Oct 2023 16:23:16 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Sat, 21 Oct 2023 16:23:15 +0900 From: Tomoaki AOKI To: ports@freebsd.org Subject: Re: lang/perl5.36: update procedure written in UPDATING is not enough Message-Id: <20231021162315.f9042885e73d7ce1b0b52e4c@dec.sakura.ne.jp> In-Reply-To: <202310210549.39L5npc3045073@nuc.oldach.net> References: <202310210549.39L5npc3045073@nuc.oldach.net> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) 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 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spamd-Bar: / X-Spamd-Result: default: False [0.48 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.94)[-0.935]; NEURAL_SPAM_MEDIUM(0.92)[0.916]; MV_CASE(0.50)[]; ONCE_RECEIVED(0.10)[]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[ports@freebsd.org]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; DMARC_NA(0.00)[sakura.ne.jp]; HAS_ORG_HEADER(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; R_SPF_NA(0.00)[no SPF record]; PREVIOUSLY_DELIVERED(0.00)[ports@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4SCCby3nJQz4bC6 On Sat, 21 Oct 2023 07:49:51 +0200 (CEST) freebsd@oldach.net (Helge Oldach) wrote: > Tatsuki Makino wrote on Sat, 21 Oct 2023 05:39:27 +0200 (CEST): > > The default version of perl has been switched, have you been able to keep up? :) > > Updating according to the procedure written in UPDATING is sufficient to avoid the trouble of not finding the library when perl is executed. > > However, it has not moved the files installed according to the old version number. > > Indeed 20181213 is incomplete; I usually run something like > > portupgrade -f `pkg query %ro-%rv lang/perl5.28` > > instead of the pkg shlib example. > > Kind regards > Helge Usually, I run `portupgrade -m 'DISABLE_VULNERABILITIES=yes' -f p5-\*` between the 2 steps for portupgade. In addition, add " -m 'DISABLE_VULNERABILITIES=yes'" for the last step. Addig this option avoids fallouts because of "marked as vulnerable". To be more paranoids, run it without " -m 'DISABLE_VULNERABILITIES=yes'", and with " -m 'DISABLE_VULNERABILITIES=yes' -n" to find fallouts, and then confirm they are really needed, deinstall now-unneeded ones, finally run with " -m 'DISABLE_VULNERABILITIES=yes'" for vulnerable but really needed ones. And I think `pkg shlib` method is better, as `pkg query` method can cause fallouts by missing explicit dependencies. Not 100% sure, though, but IIRC, when the `pkg shlib` method is first introduced in UPDATING, I tried legacy method first and `pkg shlib` method next, and some more fallouts was rebuilt. -- Tomoaki AOKI