[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1051594: bookworm-pu: package samba/2:4.17.11+dfsg-0+deb12u1



10.09.2023 13:11, Michael Tokarev:
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian.org@packages.debian.org
Usertags: pu
X-Debbugs-Cc: samba@packages.debian.org, pkg-samba-maint@lists.alioth.debian.org
Control: affects -1 + src:samba

[ Reason ]
There's a next upstream stable/bugfix release of samba series 4.17,
with a next share of bugfixes.  This is the last regular stable release,
4.17 switched to security-only bugfix mode once 4.19 is out.

Every change in there is worth having in debian stable, as it fixes
some bug.  Generally I think it is better to follow upstream stable
in case of samba as they tend to pick only important fixes for their
stable series.

[ Tests ]
Usual upstream testsuite is obviously passed.  Additionally, I run
this debian release on a few our boxes, both AD-DC mode and stand-
alone server mode, for quite some time.

[ Risks ]
There's always a risk to break something.  As usual for samba stable
releases though, this risk is minimal.

[ Checklist ]
   [*] *all* changes are documented in the d/changelog
   [*] I reviewed all changes and I approve them
   [*] attach debdiff against the package in (old)stable
   [*] the issue is verified as fixed in unstable
     (unstable has next upstream major release from which
      all commits were picked up)

[ Changes ]

Here's the changelog entry in qeustion.  For the upstream
release, it links each change to a bug report at the
upstream bug tracker.  Additionally, there are 2 minor
debian-specific changes - it is the switch to bookworm
branch in the git packaging (Vcs-Git link, specific to
bookworm, not in sid), and a slight rewording of description
of samba-common-bin package (comes from sid).

samba (2:4.17.11+dfsg-0+deb12u1) bookworm; urgency=medium

   * new upstream stable/bugfix release 4.17.11, including:
    o https://bugzilla.samba.org/show_bug.cgi?id=9959
      Windows client join fails if a second container CN=System exists somewhere
    o https://bugzilla.samba.org/show_bug.cgi?id=15342
      Spotlight sometimes returns no results on latest macOS
    o https://bugzilla.samba.org/show_bug.cgi?id=15346
      2-3min delays at reconnect with smb2_validate_sequence_number:
      bad message_id 2
    o https://bugzilla.samba.org/show_bug.cgi?id=15384
      net ads lookup (with unspecified realm) fails
    o https://bugzilla.samba.org/show_bug.cgi?id=15401
      Improve GetNChanges to address some (but not all "Azure AD Connect")
      syncronisation tool looping during the initial user sync phase
    o https://bugzilla.samba.org/show_bug.cgi?id=15407
      Samba replication logs show (null) DN
    o https://bugzilla.samba.org/show_bug.cgi?id=15417
      Renaming results in NT_STATUS_SHARING_VIOLATION
      if previously attempted to remove the destination
    o https://bugzilla.samba.org/show_bug.cgi?id=15419
      Weird filename can cause assert to fail in openat_pathref_fsp_nosymlink()
    o https://bugzilla.samba.org/show_bug.cgi?id=15420
      reply_sesssetup_and_X() can dereference uninitialized tmp pointer
    o https://bugzilla.samba.org/show_bug.cgi?id=15427
      Spotlight results return wrong date in result list
    o https://bugzilla.samba.org/show_bug.cgi?id=15430
      Missing return in reply_exit_done()
    o https://bugzilla.samba.org/show_bug.cgi?id=15432
      TREE_CONNECT without SETUP causes smbd to use uninitialized pointer
    o https://bugzilla.samba.org/show_bug.cgi?id=15435
      Regression DFS not working with widelinks = true
    o https://bugzilla.samba.org/show_bug.cgi?id=15441
      samba-tool ntacl get segfault if aio_pthread appended
    o https://bugzilla.samba.org/show_bug.cgi?id=15446
      DCERPC_PKT_CO_CANCEL and DCERPC_PKT_ORPHANED can't be parsed
    o https://bugzilla.samba.org/show_bug.cgi?id=15449
      mdssvc: Do an early talloc_free() in _mdssvc_open()
    o https://bugzilla.samba.org/show_bug.cgi?id=15451
      ctdb_killtcp fails to work with --enable-pcap and libpcap ≥ 1.9.1
    o https://bugzilla.samba.org/show_bug.cgi?id=15453
      File doesn't show when user doesn't have permission
      if aio_pthread is loaded
    o https://bugzilla.samba.org/show_bug.cgi?id=15463
      macOS mdfind returns only 50 results
   * d/control: indicate the git branch in Vcs-Git URL (-b bookworm)
   * d/control: fix description of samba-common-bin (samba-client)

  -- Michael Tokarev <mjt@tls.msk.ru>  Sun, 10 Sep 2023 12:48:29 +0300

There's one more small change which I'd love to have here too on top of
the above, in addition to Vcs-Git bookworm fix, it's this commit:

commit 24c89104279a12c17582b9b508cb4a9973032c13 (HEAD -> bookworm)
Author: Michael Tokarev <mjt@tls.msk.ru>
Date:   Sun Sep 10 14:53:00 2023 +0300

    d/salsa-ci.yml: set RELEASE to bookworm

diff --git a/debian/changelog b/debian/changelog
index 39291672047..14b7852bf8b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -45,6 +45,7 @@ samba (2:4.17.11+dfsg-0+deb12u1) bookworm; urgency=medium
      macOS mdfind returns only 50 results
   * d/control: indicate the git branch in Vcs-Git URL (-b bookworm)
   * d/control: fix description of samba-common-bin (samba-client)
+  * d/salsa-ci.yml: set RELEASE to bookworm

  -- Michael Tokarev <mjt@tls.msk.ru>  Sun, 10 Sep 2023 12:48:29 +0300

diff --git a/debian/salsa-ci.yml b/debian/salsa-ci.yml
index 93b9571e787..8a5ded86be7 100644
--- a/debian/salsa-ci.yml
+++ b/debian/salsa-ci.yml
@@ -4,6 +4,7 @@ include:
   - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml

 variables:
+  RELEASE: 'bookworm'
   # Until https://bugs.debian.org/976175 is fixed in blhc
   SALSA_CI_DISABLE_BLHC: 1
   # cross-building never worked

which I planned to do for bookworm but forgot to cherry-pick it from a
staging branch. This change does not affect users in any way at all
but helps to get salsa-ci testing working again.  When bookworm has
just been released, salsa-ci worked fine, but now when sid divirged
enough it doesn't work anymore.

Thanks, and please excuse me for the noize..

/mjt


Reply to: