From nobody Tue Mar 26 01:30:39 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 4V3XMB3w4Pz5FkrG for ; Tue, 26 Mar 2024 01:31:18 +0000 (UTC) (envelope-from estrabd@gmail.com) Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4V3XM93fQ0z4WJX for ; Tue, 26 Mar 2024 01:31:17 +0000 (UTC) (envelope-from estrabd@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=iK9ut1D7; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of estrabd@gmail.com designates 2a00:1450:4864:20::62c as permitted sender) smtp.mailfrom=estrabd@gmail.com Received: by mail-ej1-x62c.google.com with SMTP id a640c23a62f3a-a4734ae95b3so456168066b.0 for ; Mon, 25 Mar 2024 18:31:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711416675; x=1712021475; darn=freebsd.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=USKpIiW0mU8wYNcSCCKvZj6AQVAU5NiUhM8NH0Q3ZnY=; b=iK9ut1D7b7o5etDpUUq76jbtgCDpL0P/Lmrym24B9AzbkfG4iciFUnomAELX6Garr+ wQQrGp/HufqMAmi+6Pb0uFCbSvQ24Hzy/cdv3ZJjH45uh7vxjZJzfZkKptxt+/5pDAOy FEpslXksPhHWzaReZkyNnvyq7fnUF9EVd48uveULqFah38+ULIEEZBDSCx3Y4jukksA7 YaXxRJGrgcAugBBF47sbLwzFt/LpDLWKS3r+NmnmPXnwmDbIq7IKm8qpj7lhJRlVEF88 oCZyHX6Txz/aWfpwPhrU3Y1r4lh0tgq6GV/N8LklZxNVfSWHRUArQkXfKrw3WgJsrC4a /oOg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711416675; x=1712021475; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=USKpIiW0mU8wYNcSCCKvZj6AQVAU5NiUhM8NH0Q3ZnY=; b=bYT8OT113P5p9uQZKylgg6UWpHnZY8Oup9lbBLj/W4kXsOEtIEL+TEvB6uNSp+R20p FESXtvNenDnqWShzv+3hsT2Xw9922FwtdP+/ruwYJswi+8z05kh+fo0Red7FgHWZvRGK GwvJAzoeBoqXqVGM60RI5b08LhmKyl96DIkCAMiWtDdbSlLj6qoqfWQpKSK7u6EDBZHQ lRHEqREEMYOsg4XJryFBJl/3rptzYKF6Hu74aMwTRS0KgzmmPbHDPmARmy9jWKxu1nYa uz0XFDezob5uqLBawvLlCVyGIndToh5TzxOUU+PKNT3x5sFAnxiuHvHA90yFzMLHtS4O 2UbA== X-Gm-Message-State: AOJu0Yy9LYIr/bVta/M6YjidacrEgfAOZwvmN8coaAtJJdIB2qIL/k3K VTpk/1ycr+Kd3fXdSk7rGvIxx363TQQqnuLkQmhoGWH6+ipVdBhCa+4Gw3HEN5Nqm4CFlwAwwUS oaPLx55uOXp65lXq0Na89IEzsjqwFbU5C X-Google-Smtp-Source: AGHT+IEVOqYaRW6Bd2Bcbi04YO6O5jdi5dDCCndUib/1nL5fzLN+A4cBjeECSGcMnnpFU4QyHSLE0d2+hSV+k7QlCos= X-Received: by 2002:a17:906:3650:b0:a46:8c03:b659 with SMTP id r16-20020a170906365000b00a468c03b659mr5678386ejb.42.1711416675376; Mon, 25 Mar 2024 18:31:15 -0700 (PDT) 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 References: In-Reply-To: From: Brett Estrade Date: Mon, 25 Mar 2024 20:30:39 -0500 Message-ID: Subject: Re: p5-DBD-mysql: Stuck between a rock and a hard place To: FreeBSD Ports Content-Type: multipart/alternative; boundary="000000000000ffab180614863e46" X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.68 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.998]; NEURAL_HAM_SHORT(-0.98)[-0.984]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FORGED_SENDER(0.30)[brettestrade@gmail.com,estrabd@gmail.com]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MID_RHS_MATCH_FROMTLD(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-ports@freebsd.org]; FROM_NEQ_ENVFROM(0.00)[brettestrade@gmail.com,estrabd@gmail.com]; TAGGED_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-ports@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; MISSING_XM_UA(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::62c:from] X-Rspamd-Queue-Id: 4V3XM93fQ0z4WJX --000000000000ffab180614863e46 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Mar 25, 2024 at 4:11=E2=80=AFPM Sergei Vyshenski wrote: > Hi Remko, > > It seems that the situation may be even more complicated than you describ= e. > > Upstream of DBD-mariadb lately made some unfriendly steps which in > certain conditions may cause conflicts (up to crashes) with MariaDB serve= r. > It is the reason why DBD-mysql has been a good escape until version > DBD-mysql-5.004 appeared this March. Looks like a software war between 3 > upsteams, from which we had better keep aside (and even move as far as to > PostgreSQL or such). > > Some of my ports implicitly depend on a couple (MariaDB + DBD-mysql), and > hence they are broken today. > > Let me vote to preserve the old name p5-DBD-mysql for the last good and > working version, and create a new port named p5-DBD-mysql-5 or whatever. > > Regards, Sergei > Hi, In addition to whatever y'all decide about p5-DBD-mysql, I would ensure that p5-DBD-MariaDB can be installed and working along side it while still depending on mysql57-client. A failed workaround when I was hit with this some weeks ago was to use p5-DBD-MariaDB, but it was being marked as "in conflict" with whatever was getting pulled in for p5-DBD-mysql. I was not aware of issues with upstream DBD::MariaDB, but that might cause complications to what I'm suggesting. My "fix" was to install mysqll57-client from Ports, then an older version of DBD::mysql from CPAN. In any case, I appreciate that this is being addressed. Cheers, Brett > > On Mon, Mar 25, 2024 at 11:25=E2=80=AFPM SirDice wrot= e: > >> All, >> >> I took over maintainership of p5-DBD-mysql last week. Apparently I >> unwittingly managed to poke a hornets nest. Upstream author changed the >> code to make it only compatible with MySQL 8.x. I've tried patching out >> some of those changes but it requires quite an effort and is, in the end= , >> unmaintainable. So currently it is broken if you change the default mysq= l >> to MariaDB. >> >> At the moment I see a couple of options >> >> 1) leave p5-DBD-mysql at 5.004 and add a p5-DBD-mysql4 'legacy' version >> port. >> 2) 'downgrade' p5-DBD-mysql to 4.051 and add a p5-DBD-mysql5 'new' >> version port. >> >> #1 works for the default MySQL (still at 8.0) but breaks if trying to >> build with MariaDB. Arguments are made that those ports should switch to >> p5-DBD-mariadb instead. But this causes another set of problems, it's no= t a >> drop-in replacement and some ports seem to have problems with DBD-MariaD= B. >> Those ports could switch to the 'legacy' version until those issues are >> resolved upstream. #1 also poses a problem if the default is switched to >> MariaDB and ports haven't been updated yet to depend on p5-DBD-mariadb o= r >> p5-DBD-mysql4. >> >> #2 is probably the 'quickest' fix, it restores the status quo. Ports >> could include p5-DBD-mysql5 if they have a requirement for the new versi= on >> (and add a restriction to only build with MySQL 8.x). >> >> While typing this out, trying to get some advice, I'm inclined to go for >> #2. But how can I go back a version? Bump PORTEPOCH? >> >> Sorry for the noise this caused. It wasn't intended. >> >> Greetings, >> >> Remko C. aka SirDice >> >> --000000000000ffab180614863e46 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, Mar 25, 2024 at 4:11=E2=80=AFPM S= ergei Vyshenski <svysh.fbsd@gmail.com> wrote:
=
Hi= =C2=A0 Remko,

It seems that the situation may be even mor= e complicated than you describe.

Upstream of DBD-mariadb = lately=C2=A0made some unfriendly steps which in certain=C2=A0conditions may= cause conflicts (up to crashes) with MariaDB server. It is the reason why = DBD-mysql has been a good escape until=C2=A0version=C2=A0 DBD-mysql-5.004 appeared this March. Looks like a software war between 3 up= steams, from which we had better keep aside (and even move as far as to Pos= tgreSQL or such).

Some of my ports implicitly depe= nd on a couple (MariaDB + DBD-mysql), and hence they are broken today.=C2= =A0

Let me vote to preserve=C2=A0the old name p5-D= BD-mysql for the last good and working version, and create a new port named= p5-DBD-mysql-5 or whatever.

Regards, Sergei
=

Hi,

In= addition to whatever y'all decide about p5-DBD-mysql, I would ensure t= hat=C2=A0p5-DBD-MariaDB can be installed and working along side it while st= ill depending on=C2=A0mysql57-client.

A failed wor= karound when I was hit with this some weeks ago was to use p5-DBD-MariaDB, = but it was being marked as "in conflict" with whatever was gettin= g pulled in for p5-DBD-mysql. I was not aware of issues with upstream DBD::= MariaDB, but that might cause complications to what I'm suggesting.

My "fix" was to install mysqll57-client fro= m Ports, then an older version of DBD::mysql from CPAN.

In any case, I appreciate that this is being addressed.
Cheers,
Brett
=C2=A0

On Mon, Mar 25, 2024 at 1= 1:25=E2=80=AFPM SirDice <sirdice@gmail.com> wrote:
All,

I took over maintainership of p5-DBD-mysql last week. Apparently I unwitt= ingly managed to poke a hornets nest. Upstream author changed the code to m= ake it only compatible with MySQL 8.x. I've tried patching out some of = those changes but it requires quite an effort and is, in the end, unmaintai= nable. So currently it is broken if you change the default mysql to MariaDB= .

At the moment I see a couple of options

1) leave p5-DBD-mysql at 5.004 and add a p5-DBD-mysql= 4 'legacy' version port.
2) 'downgrade' p5-D= BD-mysql to 4.051 and add a p5-DBD-mysql5 'new' version port.
=

#1 works for the default MySQL (still at 8.0) but break= s if trying to build with MariaDB. Arguments are made that those ports shou= ld switch to p5-DBD-mariadb instead. But this causes another set of problem= s, it's not a drop-in replacement and some ports seem to have problems = with DBD-MariaDB. Those ports could switch to the 'legacy' version = until those issues are resolved upstream. #1 also poses a problem if the de= fault is switched to MariaDB and ports haven't been updated yet to depe= nd on p5-DBD-mariadb or p5-DBD-mysql4.

#2 is = probably the 'quickest' fix, it restores the status quo. Ports coul= d include=20 p5-DBD-mysql5 if they have a requirement for the new version (and add a res= triction to only build with MySQL 8.x).

While= typing this out, trying to get some advice, I'm inclined to go for #2.= But how can I go back a version? Bump PORTEPOCH?

= Sorry for the noise this caused. It wasn't intended.=C2=A0
Greetings,

Remko C. aka SirDice

--000000000000ffab180614863e46--