From nobody Fri May 26 04:49:24 2023 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 4QSCBt1FPfz4TyVL for ; Fri, 26 May 2023 04:49:42 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yw1-x1134.google.com (mail-yw1-x1134.google.com [IPv6:2607:f8b0:4864:20::1134]) (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 4QSCBs6NF1z3t3s for ; Fri, 26 May 2023 04:49:41 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-yw1-x1134.google.com with SMTP id 00721157ae682-561c1436c75so6552767b3.1 for ; Thu, 25 May 2023 21:49:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685076580; x=1687668580; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=o7axIuHK6bBrUAhXvx9vUqlDOwziRXY39fPT0Qi1V+0=; b=MYL1v4yfIS3VMvkTmwHX/JyfCHqIEiQlriApZ5zduMSYQikEcRmyXAsZHi/kl7ovXN 5lWBoMgOq0Pu6Tfy4ziXRDV3rMQsZKKo6nZOKOckyFYqTZ+ml3LQJ56+Os9Khmn7060S zU5uZ8aW07rF9vBiDwkrtsz/g3ZiuNVp+IEr2q9WzrTk16N72ug0/C11XsopYfzPifuT 2K8UP9vJKINDgIcH/WUJVg34imQphw8zEKO2ufcEjgi4khW678Ma1/pDB+/U+uV+piv2 AYPcKrkqjcV9qHLW8tb/SyBWgYhQDFN3X2RYFNlabjZn/g4LYixpI02JIUG+f++xsJRK G0Yw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685076580; x=1687668580; 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=o7axIuHK6bBrUAhXvx9vUqlDOwziRXY39fPT0Qi1V+0=; b=e//bc7QIAHJIxPpln/3mF91osZXMNL+aY3DadoNrLDRcmTHcXvA+tI4WDCvr3CxWHq FieB2afvk1UmXpKb940hRd5se4BjQ2a4cfCTeUXGd4VOD3Gte8z4A8QFKaQZcWFyvXyk Hp7CTThTQNQwrq7YCZx8++9oAlMUMeG+4yetcvGGadkbGKjP/3TjAf1l6a7ditZU/07b 5UY1nbprVzyZA5a4lg8EMa6ZVWA4OJbaW/9i07aBsTFHOwLWzzBn3VLfnDXCG0UWsRdb ArC6zCABEg015bjE12f6r50uEgb3s/LeMxfabYGhe1gOaJoUCpUC5VPkMdhwqv7vyiEr iNJQ== X-Gm-Message-State: AC+VfDx5hurSzTzyEhq/pe9XaqbuQhWT8jB5ImQqGLi/fuS5BqUDiNs/ SEWiRIhHYHlD/W5O1dUqW9DCZ/eqgZm2B7KroRdq8E15 X-Google-Smtp-Source: ACHHUZ5j256PS+PTBy9Y1IOCJAOaFYT1TcSxZYtvsr6iTpMjKz/jp5RCbCvqeZjIeeEyZ2wvKp5xzK522yZjp7GVYeM= X-Received: by 2002:a0d:dbcc:0:b0:562:6c0:c4d3 with SMTP id d195-20020a0ddbcc000000b0056206c0c4d3mr911688ywe.13.1685076580362; Thu, 25 May 2023 21:49:40 -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: Kevin Oberman Date: Thu, 25 May 2023 21:49:24 -0700 Message-ID: Subject: Re: Samba troubles after 13.1 -> 13.2 upgrade To: Andrea Venturoli Cc: freebsd-ports@freebsd.org Content-Type: multipart/alternative; boundary="000000000000fdf08805fc9176ec" X-Rspamd-Queue-Id: 4QSCBs6NF1z3t3s X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000fdf08805fc9176ec Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, May 25, 2023 at 9:55=E2=80=AFAM Andrea Venturoli w= rote: > Hello. > > FYI: > _ Samba 4.16 working perfectly on 13.1; > _ upgrade 13.1 -> 13.2; > _ pkg upgrade -f (installing the same packages, same versions, but > compiled for 13.2); > _ opening certain shared files gives "directory name is invalid" (I've > seen several mention of this in the forums, going back several years, > but no explanation other than that Windows or Samba mistake these files > for directories); > _ 'find {share} -exec rmextattr user DOSATTRIB "{}" ";"' will fix. > > No questions; just a post for the records in case someone gets into this. > > bye > av. > That's not how packages work. Packages are built for the oldest supported minor version for a given major version, so ports are still built on 13.1 and will be until 13.1 EOLs in, I think, in July. FreeBSD promises that the ABI will not change for the life of a major release. (There have been a couple of mistakes in the past, though.) So there is no reason to re-install packages for minor releases and the issue you are seeing must be an issue in something in the system or, possibly, a change in default options, assuming that the port version has not changed. --=20 Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --000000000000fdf08805fc9176ec Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, May 25, 2023 at 9:55=E2= =80=AFAM Andrea Venturoli <ml@netfence= .it> wrote:
Hello.

FYI:
_ Samba 4.16 working perfectly on 13.1;
_ upgrade 13.1 -> 13.2;
_ pkg upgrade -f (installing the same packages, same versions, but
compiled for 13.2);
_ opening certain shared files gives "directory name is invalid" = (I've
seen several mention of this in the forums, going back several years,
but no explanation other than that Windows or Samba mistake these files for directories);
_ 'find {share} -exec rmextattr user DOSATTRIB "{}" ";&q= uot;' will fix.

No questions; just a post for the records in case someone gets into this.
=C2=A0 bye
=C2=A0 =C2=A0 =C2=A0 =C2=A0 av.

= That's not how packages work.=C2=A0 Packages are built for the oldest s= upported minor version for a given major version, so ports are still built = on 13.1 and will be until 13.1 EOLs in, I think, in July.
= FreeBSD promises that the ABI will not change for the life of a major relea= se. (There have been a couple of mistakes in the past, though.) So there is= no reason to re-install packages for minor releases and the issue you are = seeing must be an issue in something in the system or, possibly, a change i= n default options, assuming that the port version has not changed.


--
Kevin Oberman, Pa= rt time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
<= div>PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
--000000000000fdf08805fc9176ec--