From nobody Mon Mar 25 21:11:01 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 4V3Qb46Mkxz5FJbB for ; Mon, 25 Mar 2024 21:11:12 +0000 (UTC) (envelope-from svysh.fbsd@gmail.com) Received: from mail-il1-x131.google.com (mail-il1-x131.google.com [IPv6:2607:f8b0:4864:20::131]) (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 4V3Qb422Tdz44J0 for ; Mon, 25 Mar 2024 21:11:12 +0000 (UTC) (envelope-from svysh.fbsd@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=dWKNf7Ik; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of svysh.fbsd@gmail.com designates 2607:f8b0:4864:20::131 as permitted sender) smtp.mailfrom=svysh.fbsd@gmail.com Received: by mail-il1-x131.google.com with SMTP id e9e14a558f8ab-3688d20b28dso6358165ab.2 for ; Mon, 25 Mar 2024 14:11:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1711401071; x=1712005871; 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=fOPWlUYlmAP1vcEWZ2BD3JoVY+6TqTyvVOYZM/FOJns=; b=dWKNf7Ik5QkOZwHL/ucIWOvIuteyBlMvUTWHQ8GlSmdVVhJEXccHlW7Y9uEyf4vL0Y qiNRhoPQvAb2Hu/3iwkuKStZTmECSxMoJ6paAGUMUTjkgSaCbloD+WAUxNMaqGNaZJb3 fJ1fVoqLvWOclK7febX5OBqCEKKJ5gEmHIclwWBLDGqFeoerO/tjsfiE5FYBmhnlR6H7 v3JFsUj2IclJGtn/6Sh18E4IpRlRFEBGAs5O7Zezh0UwmHETOI+Kf5xNyUeBt04iyUyd Lw3PhM2yfXAVSy7oVoMYEkYlFud36jnGKwa4Ijm+UE5NJMK1j8Hot262XZlPBQuTlZyt ++SA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1711401071; x=1712005871; 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=fOPWlUYlmAP1vcEWZ2BD3JoVY+6TqTyvVOYZM/FOJns=; b=PB8RdZUXZV5x2eZOtzRMK4cXRwEyk+5M9DL1pfU3e0ju00UMYmP0XK9UPTJE7J2Itb /aEEfwrK/80DLaAisAUK8VXpi3j2rYzYhHGRxpl4dB7ubKaLdooOJzl3z0wotsNKO/iI g/0IiMRHj4Wxx3d/krRjhhsSMFUZi5vB2vin+erxn9cv20Wh8JzCK3KkokfIhyIak0ho 1e0oh+AfvoP4cs493LIbyN8SuE3HTUe0M0X4GmO5G6YLeLwO+d4aXLem0cnKuKN3irkC M3RTp15lZ7/kbga+3Eh1wlVDcE7xS+9bPKvHICPX0g4jbqrSo2wPVDZPVr89rKyKA9tu ev4g== X-Gm-Message-State: AOJu0YzHcwZu8j7Wmh2l/MoPaIDsyMrFaVtX9SJ9y0t3yfaWc0Gg2nwB hPlYJS84VNFTBWFD8CVjlsnDHkyhtps831arGaxUOxABV9EGA3pvhQ8wcUoArjYkz1J/zpyYww8 Jigab98Msjy/zssetbzbnTZYkFOpRTSBnIaE= X-Google-Smtp-Source: AGHT+IFUnHEThuaZhsmcMmVWSy5fC/8M6dBWby/fstEZF3t4Y9POk8EaUcsmHK7dEcE1CEDOnFLa3C8OOqr1yyEBruc= X-Received: by 2002:a92:6c08:0:b0:368:82f1:802f with SMTP id h8-20020a926c08000000b0036882f1802fmr5913097ilc.25.1711401070897; Mon, 25 Mar 2024 14:11:10 -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: Sergei Vyshenski Date: Tue, 26 Mar 2024 00:11:01 +0300 Message-ID: Subject: Re: p5-DBD-mysql: Stuck between a rock and a hard place To: FreeBSD Ports Content-Type: multipart/alternative; boundary="000000000000e6361b0614829c6a" X-Spamd-Bar: --- X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_SHORT(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCPT_COUNT_ONE(0.00)[1]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; MID_RHS_MATCH_FROMTLD(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-ports@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; TAGGED_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-ports@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MISSING_XM_UA(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::131:from] X-Rspamd-Queue-Id: 4V3Qb422Tdz44J0 --000000000000e6361b0614829c6a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Remko, It seems that the situation may be even more complicated than you describe. Upstream of DBD-mariadb lately made some unfriendly steps which in certain conditions may cause conflicts (up to crashes) with MariaDB server. 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 On Mon, Mar 25, 2024 at 11:25=E2=80=AFPM SirDice wrote: > 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 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-mysql4 'legacy' version > port. > 2) 'downgrade' p5-DBD-mysql to 4.051 and add a p5-DBD-mysql5 'new' versio= n > 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 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 default is switched to > MariaDB and ports haven't been updated yet to depend on p5-DBD-mariadb or > p5-DBD-mysql4. > > #2 is probably the 'quickest' fix, it restores the status quo. Ports coul= d > include p5-DBD-mysql5 if they have a requirement for the new version (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 > > --000000000000e6361b0614829c6a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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
=
On Mon= , Mar 25, 2024 at 11:25=E2=80=AFPM SirDice <sirdice@gmail.com> wrote:
All,

I took over maintainership of p5-DBD-mysql last week. Apparently I unwit= tingly 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, unmainta= inable. So currently it is broken if you change the default mysql to MariaD= B.

At the moment I see a couple of options

1) leave p5-DBD-mysql at 5.004 and add a p5-DBD-mysq= l4 '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 brea= ks if trying to build with MariaDB. Arguments are made that those ports sho= uld switch to p5-DBD-mariadb instead. But this causes another set of proble= ms, 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 d= efault is switched to MariaDB and ports haven't been updated yet to dep= end on p5-DBD-mariadb or p5-DBD-mysql4.

#2 is= probably the 'quickest' fix, it restores the status quo. Ports cou= ld 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

--000000000000e6361b0614829c6a--