Accepted cloop 3.14.1.3+nmu1 (source) into unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 22 Dec 2022 12:41:49 -0800
Source: cloop
Architecture: source
Version: 3.14.1.3+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Eduard Bloch <blade@debian.org>
Changed-By: Vagrant Cascadian <vagrant@reproducible-builds.org>
Closes: 787996 1005413 1005414
Changes:
cloop (3.14.1.3+nmu1) unstable; urgency=medium
.
* Non-maintainer upload
.
[ Ben Hutchings ]
* Fix FTBFS with gcc 11 (Closes: #1005413):
- Remove exception specifications
* Fix module build for recent kernel versions (Closes: #1005414):
- Stop generating module vermagic in cloop.c. This has always been handled
by modpost and doing it here now results in build failure.
- Avoid using inode::i_bdev, which was removed in Linux 5.11.
- Use set_disk_ro() instead of set_device_ro(). The latter was not meant to
be used by device drivers and was removed in Linux 5.11.
- Use blk_{mq_alloc,cleanup}_disk() instead of separate queue and disk
allocation and cleanup on Linux 5.15+, since alloc_disk() was removed.
- Handle potential failure of add_disk() on Linux 5.15+.
- Use kernel_read() instead of vfs_read() and set_fs(). set_fs() is no
longer defined on some architectures, and kernel_read() has had large
file support since Linux 2.6.31.
.
[ Vagrant Cascadian ]
* debian/rules: Build tarball reproducibly, using consistent time, uid,
gid and sort order. Thanks to Dhole for the initial patch.
(Closes: #787996)
Checksums-Sha1:
7ddbda26716e2018fb14a3b163162516126c84a6 1111 cloop_3.14.1.3+nmu1.dsc
83ce5cfd8080d6b7db98d6cdd15bde8d73634d75 254136 cloop_3.14.1.3+nmu1.tar.xz
Checksums-Sha256:
615b4fde10fa5026a7a6dbbb4d1272c0ec964ed09cb7c99984a71f9b37990788 1111 cloop_3.14.1.3+nmu1.dsc
04060d88231208b0db8ae8c3b54b0a46ee12139b617ebfc80b03d2ddd2cdb6ba 254136 cloop_3.14.1.3+nmu1.tar.xz
Files:
d6e6da08e382bbdb868056fe3f4692e7 1111 misc optional cloop_3.14.1.3+nmu1.dsc
ab3502c26dd1bed4146396d9d619c756 254136 misc optional cloop_3.14.1.3+nmu1.tar.xz
-----BEGIN PGP SIGNATURE-----
iJYEARYKAD4WIQRlgHNhO/zFx+LkXUXcUY/If5cWqgUCY6TDGCAcdmFncmFudEBy
ZXByb2R1Y2libGUtYnVpbGRzLm9yZwAKCRDcUY/If5cWqhfOAP4vqLUgLLdT5ZA/
r4qJ1HOHeLqOKOkndq+BzBM7pbskJAEA9Nx8y9w1ldUTrYlZeS2LCrYL9LTPaXo4
FPPwBuJzPA4=
=rhHi
-----END PGP SIGNATURE-----
Reply to: