From nobody Mon Feb 03 18:43:19 2025 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 4YmwPW1pBwz5mMb7 for ; Mon, 03 Feb 2025 18:43:43 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yb1-xb2d.google.com (mail-yb1-xb2d.google.com [IPv6:2607:f8b0:4864:20::b2d]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YmwPV4HSFz3gDN; Mon, 03 Feb 2025 18:43:42 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=NIJjTk9K; spf=pass (mx1.freebsd.org: domain of kob6558@gmail.com designates 2607:f8b0:4864:20::b2d as permitted sender) smtp.mailfrom=kob6558@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-yb1-xb2d.google.com with SMTP id 3f1490d57ef6-e549dd7201cso4686995276.0; Mon, 03 Feb 2025 10:43:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1738608221; x=1739213021; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ibBhqm/ftCBo7x1hsvBWjAolYl0aDuCg4F9/wiD06OU=; b=NIJjTk9KiWi/2dSlVYlW042lFJVQwcnVhXtCzBPZuq/UnTr4ZKK7/kLaNxlUXfBaAC NdqTfiNZol75FOApo2H0XjYyxvxIUuwbFX3e3ucOTOU5NV06penWb7VjnKwll4GD7409 Q49K1gM+JmcD+8CrIWBLobwXM9Pya+96Hvcca6g96tqh7YTLV9WfNs3VnW2Me6Lt7+1I Ld0jHq32KjV+u8V0IOX8ADZUC+DWjj0jvx/tMSMOzffJUq4Vmx4vF1B8vf//kF2dmGsp X8SLLP4Ra65XemTz2BjFslAvL1gWX/xNFpit8BB6LwN2uXKDQsFJqvvNUGXLBxdLGdQ6 EUUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738608221; x=1739213021; h=cc: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=ibBhqm/ftCBo7x1hsvBWjAolYl0aDuCg4F9/wiD06OU=; b=wxFTTS3HsseumyUEdCPUKQus6SNWvQqVXlx0vbZIZ8qvLEu0cHiIBXMjBBNJ1H+7go cHPBNsyk2a436gnHBciDU3SEOnrJDJNczcZ3WwHZMNhAkEQ+XrCk6HT+P6nYGFdw/p7s d8r/eWfJ5zf8H68DAFy89kYe0qklMgLI5b87qLpDufS4oaFXZj57wYZTa91jSYizC54V W0cl1l/D8nvpIOCA41w1OtMjDH9CvIFpyje55J56oa/7hjC76b1FXG31TV2+dQK/uuhI gOTB7hkMPweXyGVAa6bZXdH8KuRQI3ABusAFvKIYIbX4HAKGOBYTWpxs1QB/TBrkSQOK lBXg== X-Forwarded-Encrypted: i=1; AJvYcCX1gdoOyb72d1LIsp3DGel186Xnjxjui+R9IJ8OoBhLAKXQwEHOJ4Rj+AmWOV2kCNuOi3smi03KBSOKGOFZ@freebsd.org X-Gm-Message-State: AOJu0YxiTkfAPihJRKkSOk9ytmXYl/DzNAbZBZXEAnx/yC81NOWuNhth w6uiUL9BOSYpQ43qbLrSKGQKyNxQDqUCJj+LLN6eA+bMAdBrTdwAKov/xCuE4uIqldrFLh73J/B 9JG4x8xcACCepn4BIch8lFP9RfbwW7w== X-Gm-Gg: ASbGncuDv26KF+esA8racRhD1EHV6ffegBMeJT6eIgiMihPP+QuSJ81abVge72IN8CI 6N/2LY6wQMtqdkLvzTr22HPLtB7VA/jDOGN38zGNmN6Z0RkIIyWDNRh/q8h6+cAr/9xWX/AWZPg == X-Google-Smtp-Source: AGHT+IHX6YRafK/c3wkSpkZ7h7zCU4DgFGZZkxESjfZ9+aK4NYi5XNXOPQEvLBaZ9UNDiQM7NKScO2r6yYXwx+EezgE= X-Received: by 2002:a05:6902:e01:b0:e57:d16a:57a8 with SMTP id 3f1490d57ef6-e58a4aa8575mr15836356276.1.1738608221034; Mon, 03 Feb 2025 10:43:41 -0800 (PST) List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-ports@freebsd.org Sender: owner-freebsd-ports@FreeBSD.org MIME-Version: 1.0 References: <1453319087.51758.1738487855881.JavaMail.zimbra@oav.net> <20250203.030645.406589481977955710.yasu@FreeBSD.org> In-Reply-To: <20250203.030645.406589481977955710.yasu@FreeBSD.org> From: Kevin Oberman Date: Mon, 3 Feb 2025 10:43:19 -0800 X-Gm-Features: AWEUYZmfQPg_M5PnzHJyvFoX2THyvA1RTbuXvgkdq_Rg_P1nlCvyM4ZjYTotDwg Message-ID: Subject: Re: Strange version inconsistency in Samba t* utils (e.g. talloc) To: Yasuhiro Kimura Cc: kiwi@freebsd.org, tatsuki_makino@hotmail.com, freebsd-ports@freebsd.org Content-Type: multipart/alternative; boundary="0000000000006b2289062d4145d3" X-Spamd-Result: default: False [-3.58 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.997]; NEURAL_HAM_SHORT(-0.88)[-0.885]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FORGED_SENDER(0.30)[rkoberman@gmail.com,kob6558@gmail.com]; 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]; MIME_TRACE(0.00)[0:+,1:+,2:~]; TO_DN_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_CC(0.00)[freebsd.org,hotmail.com]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; FREEMAIL_FROM(0.00)[gmail.com]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::b2d:from]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; FROM_NEQ_ENVFROM(0.00)[rkoberman@gmail.com,kob6558@gmail.com]; DKIM_TRACE(0.00)[gmail.com:+]; 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)[]; FREEMAIL_ENVFROM(0.00)[gmail.com] X-Spamd-Bar: --- X-Rspamd-Queue-Id: 4YmwPV4HSFz3gDN --0000000000006b2289062d4145d3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Feb 2, 2025 at 10:08=E2=80=AFAM Yasuhiro Kimura = wrote: > From: Xavier Beaudouin > Subject: Re: Strange version inconsistency in Samba t* utils (e.g. talloc= ) > Date: Sun, 2 Feb 2025 10:17:35 +0100 (CET) > > > I understand, but samba is really picky with their "satellite" librarie= s. > > When you don't use them as embedded tools then you can have strange > results > > if the version it not the one needed. > > For example, net/samba420 needs tdb >=3D 1.4.10, but other net/samba ma= y > not > > work with this version. > > > > This is very unfortunate but also some other tools like sssd2 and sudo > may > > need this libraries as external when compiled with samba support. > > > > Kind regards, > > Xavier > > > > When net/samba420 was added, following ports were added as > dependencies. > > * databases/tdb1410 > * devel/talloc242 > * devel/tevent016 > > But I think we should have taken following steps. > > 1. Repocopy databases/tdb, devel/talloc and devel/tevent to > databases/tdb149, devel/talloc241 and devel/tevent015. > 2. Update dependencies of net/samba416 and net/samba419 from the > former to the latter. > 3. Update databases/tdb, devel/talloc and devel/tevent to the versions > that Smaba 4.20 requires. > > The reason is as following. > > Right now there are 3 Samba ports in ports tree. That is, > > * net/samba416 > * net/samba419 > * net/samba420 > > net/samba416 has already reached its EoL and net/samba419 security > fixes only phase. So it is unlikely they requires update of > dependecies. You may say it is also unlikely net/samba420 requires > update. But when newer version of Samba, for example 4.21, has come to > ports tree, it is very likely it requires newer version of > dependencies and it is still possible net/samba420 works fine with > versions required by 4.21 as is the case with net/samba416 and > net/samba419. And when it really happens all we do is simply updating > generic databases/tdb, devel/talloc and devel/tevent rather than > creating new specific databases/tdbNNNN, devel/tallocNNN and > devel/teventNNN ports and removing old ones. > > This is common practice in ports tree. And by following it we can > minimize the frequency to create and remove port with specific > version. > > --- > Yasuhiro Kimura > This explains what I am seeing, but one issue is that bsd.default-versions.mk still shows EOL samba416 as the default version. Is there a good reason that this has not been updated to either 419 or 420? I obviously don't like running EOL versions, but I also fear that running something other than the default will break a port dependent on it. I assume that maintiners more aware of these issues will deal with them and, in the case of samba, I really don't use it, but it gets pulled in by filesystems/gvfs. --=20 Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --0000000000006b2289062d4145d3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sun, Feb 2, 2025 at 10:08=E2= =80=AFAM Yasuhiro Kimura <yasu@freeb= sd.org> wrote:
From: Xavier Beaud= ouin <kiwi@freebsd= .org>
Subject: Re: Strange version inconsistency in Samba t* utils (e.g. talloc)<= br> Date: Sun, 2 Feb 2025 10:17:35 +0100 (CET)

> I understand, but samba is really picky with their "satellite&quo= t; libraries.
> When you don't use them as embedded tools then you can have strang= e results
> if the version it not the one needed.
> For example, net/samba420 needs tdb >=3D 1.4.10, but other net/samb= a may not
> work with this version.
>
> This is very unfortunate but also some other tools like sssd2 and sudo= may
> need this libraries as external when compiled with samba support.
>
> Kind regards,
> Xavier
>

When net/samba420 was added, following ports were added as
dependencies.

* databases/tdb1410
* devel/talloc242
* devel/tevent016

But I think we should have taken following steps.

1. Repocopy databases/tdb, devel/talloc and devel/tevent to
=C2=A0 =C2=A0databases/tdb149, devel/talloc241 and devel/tevent015.
2. Update dependencies of net/samba416 and net/samba419 from the
=C2=A0 =C2=A0former to the latter.
3. Update databases/tdb, devel/talloc and devel/tevent to the versions
=C2=A0 =C2=A0that Smaba 4.20 requires.

The reason is as following.

Right now there are 3 Samba ports in ports tree. That is,

* net/samba416
* net/samba419
* net/samba420

net/samba416 has already reached its EoL and net/samba419 security
fixes only phase. So it is unlikely they requires update of
dependecies. You may say it is also unlikely net/samba420 requires
update. But when newer version of Samba, for example 4.21, has come to
ports tree, it is very likely it requires newer version of
dependencies and it is still possible net/samba420 works fine with
versions required by 4.21 as is the case with net/samba416 and
net/samba419. And when it really happens all we do is simply updating
generic databases/tdb, devel/talloc and devel/tevent rather than
creating new specific databases/tdbNNNN, devel/tallocNNN and
devel/teventNNN ports and removing old ones.

This is common practice in ports tree. And by following it we can
minimize the frequency to create and remove port with specific
version.

---
Yasuhiro Kimura

This explains wha= t I am seeing, but one issue is that bsd.default-versions.mk still shows EOL samba416 as the default ve= rsion. Is there a good reason that this has not been updated to either 419 = or 420? I obviously don't like running EOL versions, but I also fear th= at running something other than the default will break a port dependent on = it. I assume that maintiners more aware of these issues will deal with them= and, in the case of samba, I really don't use it, but it gets pulled i= n by filesystems/gvfs.
--
Kevin Oberman, Par= t time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
--0000000000006b2289062d4145d3--