python3-samba syntaxwarnings while upgrading

[Piotr Skwarna]

Setting up python3-samba (2:4.19.5+dfsg-1ubuntu1) ...
/usr/lib/python3/dist-packages/samba/tests/dns_forwarder_helpers/server.py:80: SyntaxWarning: invalid escape sequence '\s'
  m = re.match(b'^timeout\s+([\d.]+)$', data.strip())
/usr/lib/python3/dist-packages/samba/tests/samba_tool/join_member.py:43: SyntaxWarning: invalid escape sequence '\s'
  existing_records = re.findall('A:\s+(\d+\.\d+\.\d+\.\d+)\s', out)
/usr/lib/python3/dist-packages/samba/tests/samba_tool/ntacl.py:93: SyntaxWarning: invalid escape sequence '\s'
  self.assertNotRegex(err, '^\s*File [^,]+, line \d+, in',
/usr/lib/python3/dist-packages/samba/tests/samba_tool/user_virtualCryptSHA.py:42: SyntaxWarning: invalid escape sequence '\s'
  p = re.compile("^" + name + ":\s+(\S+)")
/usr/lib/python3/dist-packages/samba/tests/samba_tool/user_virtualCryptSHA_base.py:42: SyntaxWarning: invalid escape sequence '\s'
  p = re.compile("^" + name + ":\s+(\S+)")

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubuntu-release-upgrader-core 1:24.04.7
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Thu Feb 29 12:11:41 2024
InstallationDate: Installed on 2020-04-10 (1420 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: Upgraded to noble on 2024-01-21 (39 days ago)
VarLogDistupgradeXorgFixuplog:
 INFO:root:/usr/bin/do-release-upgrade running
 INFO:root:No xorg.conf, exiting

[Douglas Bagnall (douglasbagnall)]

FWIW, many of these have upstream fixes, e.g.
26ff87dcfeaf5a2aff5f28c0aa5d99437c79a68c
bd8c3afe1060b48fdf640560518d33ee50e675f6

[Sergio Durigan Junior (sergiodj)]

Thank you for the bug report.

These are coming from test cases, so while it is indeed a good thing to fix, it's not something urgent. May I suggest that you raise this issue on Debian, please? If it's fixed there, then it will automatically get picked up by Ubuntu the next time we merge the package.

For now, I am marking this as Triaged but setting a Low priority to it.

Thanks.