Accepted bubblewrap 0.1.4-1 (source) into unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Tue, 29 Nov 2016 12:55:31 +0000
Source: bubblewrap
Binary: bubblewrap
Architecture: source
Version: 0.1.4-1
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) <gcs@debian.org>
Changed-By: Simon McVittie <smcv@debian.org>
Description:
bubblewrap - setuid wrapper for unprivileged chroot and namespace manipulation
Changes:
bubblewrap (0.1.4-1) unstable; urgency=medium
.
* New upstream release
* d/p/test-run-be-a-bash-script.patch,
d/p/test-run-don-t-assume-we-are-uid-1000.patch,
d/p/Adapt-tests-so-they-can-be-run-against-installed-binaries.patch,
d/p/Fix-incorrect-nesting-of-backticks-when-finding-a-FUSE-mo.patch:
improve the upstream tests
* d/tests/upstream: run the upstream tests as autopkgtests
* d/rules: Do not enable setuid mode at configure time. If we do, we
can't run the build-time tests, and it no longer makes any difference
to the actual code. Make the executable setuid via Debian packaging
instead.
Checksums-Sha1:
36cb4b60f8903c97704d4f508b7d9f5ffdfc9657 2103 bubblewrap_0.1.4-1.dsc
752d89f39ca36ddcde364c3a2dd2473e2d80e94e 91854 bubblewrap_0.1.4.orig.tar.gz
221d993ddf0596f0c59856c348acd66bea3c2909 5720 bubblewrap_0.1.4-1.debian.tar.xz
Checksums-Sha256:
9cd56ed8c25e395e31984a6d3ba035fadf4a712af697b5b70915e029c2537402 2103 bubblewrap_0.1.4-1.dsc
a98cf6aaafa5141a85c3fbd7f55608fb7d3ff4d10e166b27cbf371a100f9be02 91854 bubblewrap_0.1.4.orig.tar.gz
836c0edbc6753a26c41309b85787db995298f84e469d9d6052e775fcb5445ee7 5720 bubblewrap_0.1.4-1.debian.tar.xz
Files:
5535804691590f4ceee7e9ac60cb8b76 2103 admin optional bubblewrap_0.1.4-1.dsc
ace8a6b1aa870473375079ec08abee96 91854 admin optional bubblewrap_0.1.4.orig.tar.gz
ddab5d118bf7d1195f2a715e3f081762 5720 admin optional bubblewrap_0.1.4-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEE2pjyXAhxxJpZ6v8sTej/KmPHzJAFAlg9iAQACgkQTej/KmPH
zJA/JQ/+OEw5SAfup2ycfhzo0/UrMAOfCNA+e/jin4Dp6vQms0OF79u0xtJ9ernz
qXxKyyfBG4gwQRQVOqmSp6stDma6qNT9/wEBlbPkhSbuqp3N4v/q4xf1Kz8JHd9M
y09Av4/4c4AVfM8eUiCMBrRhO6cUNb0+43JQoukeAbQ+yRyJApUkSHyXtqSKtl8E
RBB/aUQeU2oXR/1k5XFQSI5Vekn01pra6OzEj6W2S/QmtDJSgM48btY77QfxTAEU
9MoA7M7DnkEWkQtPfBgAXlx/KVFlcII2JuMTHs+vxgYjtbwHjoY15xpNihTqK25R
CAUGsocVVDqginxeUWTIx5h1MlSmzq9kS3EdszREQOTUROOp7tX9THhhPPbIUjCF
EJIUPt1HHMJ9Stpq5TsMwvPGZilYdU5q/8sufduSB7cbdoEQf1o5rX/eS8MfSFL6
ebnGTxre6TLc1fdgKDZBOYFsoBf+fHaMsmf3tWV/trkw9Q8yMFAAf41Lrd9OKXJ5
+3tpKKG0KGplvQakG9L6f0ZzQxTG4EqoXQlQBVv5ik2ZpYbTZ+EbKWDGDaUxQfWV
0m41cUIkAQD7OdDaAtGCy+37FC9A03excgGjsp0i3NoBB9SoKe5w5M4HCwDH/lXB
l7+M4YTfmhTAt58hNmO0KbW8da41s1Bt/JMqqxOHxc/x690I+pM=
=BwmF
-----END PGP SIGNATURE-----
Reply to: