From nobody Tue Oct 24 22:06:42 2023 X-Original-To: questions@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 4SFR4755P6z4xZjX for ; Tue, 24 Oct 2023 22:07:03 +0000 (UTC) (envelope-from freebsd@gushi.org) Received: from prime.gushi.org (prime.gushi.org [IPv6:2620:137:6000:10::142]) (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 (2048 bits) client-digest SHA256) (Client CN "prime.gushi.org", Issuer "RapidSSL Global TLS RSA4096 SHA256 2022 CA1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SFR456hKJz3DZw; Tue, 24 Oct 2023 22:07:01 +0000 (UTC) (envelope-from freebsd@gushi.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gushi.org header.s=prime2014 header.b=QOOOKlRk; spf=pass (mx1.freebsd.org: domain of freebsd@gushi.org designates 2620:137:6000:10::142 as permitted sender) smtp.mailfrom=freebsd@gushi.org; dmarc=pass (policy=none) header.from=gushi.org Received: from smtpclient.apple (vpn-us.f.root-servers.org [149.20.8.9]) (authenticated bits=0) by prime.gushi.org (8.17.2/8.17.2) with ESMTPSA id 39OM6rGh011243 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 24 Oct 2023 22:06:56 GMT (envelope-from freebsd@gushi.org) DKIM-Filter: OpenDKIM Filter v2.10.3 prime.gushi.org 39OM6rGh011243 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gushi.org; s=prime2014; t=1698185217; bh=NYw8M8SZb3fVd7mhoi3RrAjF8t+EFCLNRbwh1GlLAtk=; h=From:Date:Subject:Cc:To; z=From:=20"Dan=20Mahoney=20(Ports)"=20|Date:=20T ue,=2024=20Oct=202023=2015:06:42=20-0700|Subject:=20Why=20isn't=20 p5-dbd-Pg=20flavored=20for=20various=20postgres=20versions?|Cc:=20 sunpoet@freebsd.org|To:=20questions@freebsd.org; b=QOOOKlRkL/HtZLNvm5yck2k4SwlWXPTZ0hxVxAXscrJobkGZ1FFeHbJJVBrNA/+sq oAJ+0M7AWmFyD2yil2JxCOc9AkRigOk0MGnJNMaa7c99o2/AKhxrF4c5QWfTqVlHNW YHktTWDwtwQr7S9T22lgWE4L0wiQEfbiXUmUbpdDrXZejAeN4r3MGAjcK6746D8+zz 5JpxK6CGtyN4UAyOknNqmin+jSH7OQaS7WTE4YNvoOH6eY2fjhokJH2AYZzVuEWRiU pwl64lsnCmQmFIy9Cv4+3oliGKNWzjkphgf6FmjuJSUp/0+lHYKZMDwf2xyOl4KuCF yFCG/CtLU9qEQ== X-Authentication-Warning: prime.gushi.org: Host vpn-us.f.root-servers.org [149.20.8.9] claimed to be smtpclient.apple From: "Dan Mahoney (Ports)" Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.100.2.1.4\)) Date: Tue, 24 Oct 2023 15:06:42 -0700 Subject: Why isn't p5-dbd-Pg flavored for various postgres versions? Cc: sunpoet@freebsd.org To: questions@freebsd.org Message-Id: <810867E4-B049-4B94-B983-286631E12D15@gushi.org> X-Mailer: Apple Mail (2.3774.100.2.1.4) X-Spamd-Bar: ----- X-Spamd-Result: default: False [-5.10 / 15.00]; DWL_DNSWL_MED(-2.00)[gushi.org:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_DKIM_ARC_DNSWL_MED(-0.50)[]; DMARC_POLICY_ALLOW(-0.50)[gushi.org,none]; MV_CASE(0.50)[]; RCVD_IN_DNSWL_MED(-0.20)[2620:137:6000:10::142:from]; R_DKIM_ALLOW(-0.20)[gushi.org:s=prime2014]; R_SPF_ALLOW(-0.20)[+mx]; ONCE_RECEIVED(0.10)[]; MIME_GOOD(-0.10)[text/plain]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+]; RCPT_COUNT_TWO(0.00)[2]; TO_DN_NONE(0.00)[]; HAS_XAW(0.00)[]; ASN(0.00)[asn:393507, ipnet:2620:137:6000::/44, country:US]; DKIM_TRACE(0.00)[gushi.org:+]; FROM_EQ_ENVFROM(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; MLMMJ_DEST(0.00)[questions@freebsd.org]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4SFR456hKJz3DZw All, I=E2=80=99ve lost another morning to a bad choice made by ports/pkg. Maybe this is a dumb question/rant, but recently, a routine pkg upgrade = of the dayjob=E2=80=99s RT VM (which included an upgrade to perl) = decided to leave me with no ability to connect. After following the = rabbit hole, I hit a database connect error. p5-dbd-pg was still installed, according to pkg, but none of the perl = libraries could find it, because it was in the wrong perl include dir = (/usr/local/lib/perl5/site_perl/mach/5.32/DBD/Pg.pm, when the perl = version was 5.34) Now, postgresql13 is still in pkg, still works, and according to = Freshports indirectly requires postgresql13 (by way of requining libpq), = and it still builds cleanly if you set DEFAULT_VERSIONS+=3Dpgsql=3D13 in = make.conf,=20 But apparently, if you use pkg, and you try to decide you need the perl = driver, you=E2=80=99re boned. But should you attempt to just reinstall = it? Nope. # pkg install p5-DBD-Pg Updating FreeBSD repository catalogue... FreeBSD repository is up to date. All repositories are up to date. Checking integrity... done (2 conflicting) - postgresql15-client-15.4 conflicts with postgresql13-client-13.12 on = /usr/local/bin/clusterdb - postgresql15-client-15.4 conflicts with postgresql13-client-13.12 on = /usr/local/bin/clusterdb Checking integrity... done (0 conflicting) The following 5 package(s) will be affected (of 0 checked): Installed packages to be REMOVED: postgresql13-client: 13.12 postgresql13-server: 13.12 New packages to be INSTALLED: postgresql15-client: 15.4 Installed packages to be UPGRADED: p5-DBD-Pg: 3.16.0 -> 3.17.0 Installed packages to be REINSTALLED: pkg-1.20.8 =3D=3D=3D Also, I love how it doesn=E2=80=99t offer to upgrade the server as well. = Who needs that thing? So the point of view is apparently =E2=80=9Cyeah, you can install a = whole big postgres server/client, anda big language like perl, and all = the dependencies for something complicated like RT without having a full = ports tree, but if you try to install the tiny little stub that lets = perl talk to that database, HAHA nope." This happened a year ago, too. It=E2=80=99s not freebsd=E2=80=99s fault = that Postgres requires a full dump and restore of all your databases to = do an upgrade (where mysql handles major version upgrades just fine), = but the version bumps should be cognizant of this. My fix for this was *sigh* portsnap fetch updete, cd = /usr/ports/databases/p5-dbd-Pg, make, make deinstall, make = reinstall=E2=80=A6pkg lock p5-dbd-Pg Yes, I know that I should be ready to upgrade to 15 at some point, on = whatever quarterly port boundary it=E2=80=99s decided, =E2=80=9CI guess = that=E2=80=99s when=E2=80=9D, with no advance notice, via the full = stupid dump-and-restore process. I don=E2=80=99t run =E2=80=9Cpkg upgrade=E2=80=9D because I=E2=80=99m = interested in the exercise of debugging the latest ports shenanigans, I = run it because =E2=80=9Cpkg audit=E2=80=9D complains at me about = vulnerable things, and in general it=E2=80=99s good to keep things up to = speed But once in a while, I lose a whole morning to nonsense like this, and = it feels preventable. -Dan