-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sun, 12 Jan 2025 00:17:49 +0300
Source: samba
Architecture: source
Version: 2:4.21.3+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Samba Maintainers <pkg-samba-maint@lists.alioth.debian.org>
Changed-By: Michael Tokarev <mjt@tls.msk.ru>
Changes:
samba (2:4.21.3+dfsg-5) unstable; urgency=medium
.
* the Fixing Big Mishaps release.
.
* d/rules: fix talloc, tevent, tdb subpackages version numbers, add epoch
.
Due to a mistake, I screwed up sub-packages versions completely,
by using the wrong variable when generating the versions, - so
all mentioned packages had version number of ldb, not their own.
.
Fix this.
.
Unfortunately, the wrong version is larger than all the correct ones.
To compensate, use the same epoch number as is already used by current
samba package (2:).
.
While at it, use common variable to hold the +samba version suffix.
.
* d/*.symbols: mark most recent version markers with 2: epoch too
.
* d/control,d/rules: ensure we use the most recent libtalloc/libtevent/libtdb
for now, to compensate for the wrong versions.
.
* d/control: add explicit Provides of non-t64 libs
.
Apparentlty due to usage of both t64 and pre-t64 packages
(with different build profiles), debhelper is not populating
necessary values for ${t64:Provides}. So libtevent0t64 is
not providing libtevent0 on the relevant architectures.
Ditto for libsmbclient0 providing libsmbclient.
.
Add explicit arch-specific Provides: for libsmbclient0 and
libtevent0t64.
.
List only the affected release architectures in there.
.
This removes the only user of X-Time64-Compat control field
in debian.
.
* d/rules: do not install wscript_build in examples
.
* d/control: fix libtevent wrong build profile when building for mjt's
repository. Does not affect debian thankfully. The problem is that
libtevent0t64 slipped into the repository for older (before-trixie)
distributions, where t64 migration hasn't been completed. This should
not cause actual problems as a problem is only possible when upgrading
to the new debian (or ubuntu) release where t64 transition has happened,
and during such upgrade, new libtevent0t64 will be pulled in - thanks to
the first big mistake above, since it now has 2: epoch.
* d/control: add Breaks for libtevent0t64 on mjt repo. This also
does not affect debian, but makes my life definitely easier.
Checksums-Sha1:
1fbe69e800ac5f52fa0c7d76acd74a97f262738f 5648 samba_4.21.3+dfsg-5.dsc
1142eacc9f7d4a27952e14390000147de151a341 189148 samba_4.21.3+dfsg-5.debian.tar.xz
a2394d4de4697deb2edd4e22c1a8a97050937171 6726 samba_4.21.3+dfsg-5_source.buildinfo
Checksums-Sha256:
ae53b047e35a51997ced4cd646f0ffa70f72b19e45c7e5dc90f9324455e110d8 5648 samba_4.21.3+dfsg-5.dsc
8ebd88ec6874520d45767e0e12dcb38d5f7f14e1c77dc23a955dfa2c27f9d8e0 189148 samba_4.21.3+dfsg-5.debian.tar.xz
a4b55a3ee8d70b3947821d94c798a25be53c535b9d2c62c220e4029e97ec4dde 6726 samba_4.21.3+dfsg-5_source.buildinfo
Files:
6c07ba410e4b5575a6fc45d2e4363ea3 5648 net optional samba_4.21.3+dfsg-5.dsc
2a5d9bf1d7e28cf9f8d12aebd0871a15 189148 net optional samba_4.21.3+dfsg-5.debian.tar.xz
b6abd2b0347979c1d25703b1fe2f4f21 6726 net optional samba_4.21.3+dfsg-5_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEZKoqtTHVaQM2a/75gqpKJDselHgFAmeC4CgACgkQgqpKJDse
lHjukg/+MWVBuHiu6g+bTgeY9MgV7tvCUOz+pnfCZOGyzWdoJcbsMIZuB1coDBCh
B5Pa9t/81uYW9lf6rX7moMzWQ8/fCECEruCbqRn6QT3pWAAEiHLSXB0kbvkYETfw
f5VRQIPUWH+mXHaV4m90pY+XDSfODPtjHLq5JjKWh1MCVE4u8aGMPKchz5uKbjl9
CUVumDaVZOukIKrB4FpD1In92Vv0kBXz5YvmNQvLKmdkalhco9gVeQqRXoy1X1BI
+aTSG/EXMZ8go8J5uzfD/yDwYNsPusKIirJj26oxWmOIMzGHY5NOZEvee0aG7PQ1
1s1LOoMm5J3ckJMmlYZookXz3D8Wh+p9JwxEn0g0/9VEUgfWfgCr5OttqEx4he7N
QLw3hYISrftYyNK5LINMfBNBwv0CsMdNph2lIyuOy2WnXlkVDtTo+TgxRkNRwvcV
5HbOH/ZjWjWKQOx6Jim9AHAEtVzYB3rP8Xh40lowPEl4QRg62Ia7M24C8RFwk0gx
EbFiBIOjbiTbgs6BOnOsXXtVJT05j68mT0OTjGmBQGRVbUMVrgdPgIvX9dijJJso
t9B7pBu87EHRhCcxpSCpD8MzSKkfUiidYyI532VfNJf0K60pqWYNsVP3DxsG2JCY
VY9ssH2iSr9J3wYZkgRgtEk1hpmJmP8HP3btxVeggqanRreC7fo=
=ZYon
-----END PGP SIGNATURE-----
