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

Accepted redis 3:3.2.8-2~bpo8+1 (source) into jessie-backports->backports-policy, jessie-backports



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 11 Mar 2017 12:55:09 +0000
Source: redis
Binary: redis-server redis-tools redis-sentinel
Architecture: source
Version: 3:3.2.8-2~bpo8+1
Distribution: jessie-backports
Urgency: medium
Maintainer: Chris Lamb <lamby@debian.org>
Changed-By: Chris Lamb <lamby@debian.org>
Description:
 redis-sentinel - Persistent key-value database with network interface (monitoring)
 redis-server - Persistent key-value database with network interface
 redis-tools - Persistent key-value database with network interface (client)
Closes: 850534 852347 856116
Changes:
 redis (3:3.2.8-2~bpo8+1) jessie-backports; urgency=medium
 .
   * Rebuild for jessie-backports.
 .
 redis (3:3.2.8-2) unstable; urgency=medium
 .
   * Avoid conflict between RuntimeDirectory and tmpfiles.d(5) both attempting
     to create /run/redis with differing permissions.
 .
     This prevents an installation error on Jessie where /run/redis was first
     being created by the tmpfiles.d(5) mechanism and then subsequently via the
     RuntimeDirectory directive. Due to a bug in Jessie's systemd, this caused a
     package installation error as systemd was too strict about permissions if
     the target already exists: <https://github.com/systemd/systemd/pull/896>
 .
     The redis-{server,sentinel} daemon would actually start successfully a few
     milliseconds later due to the Restart=always directive.
 .
     We work around this this by dropping the tmpfiles.d(5) handling and moving
     entirely to RuntimeDirectory{,Mode}; we are not using any special handling
     requiring tmpfiles.d(5) and we appear to need RuntimeDirectory anyway for
     #846350. (Closes: #856116)
 .
 redis (3:3.2.8-1) unstable; urgency=medium
 .
   * New upstream release.
 .
 redis (3:3.2.7-1) unstable; urgency=medium
 .
   * New upstream release.
 .
 redis (3:3.2.6-6) unstable; urgency=medium
 .
   * Use --cpu-list 0 (not --cpu-list 1) to ensure compilation on single-CPU
     machines. (Closes: #852347)
 .
 redis (3:3.2.6-5) unstable; urgency=medium
 .
   * Re-add taskset calls to try and avoid FTBFS due to parallelism in upstream
     test suite.
 .
 redis (3:3.2.6-4) unstable; urgency=medium
 .
   * Expand the documentation in redis-server.service and redis-sentinel
     regarding the default hardening options.
 .
 redis (3:3.2.6-3) unstable; urgency=medium
 .
   * Don't ship a "duplicate" redis-server binary in redis-tools as
     /usr/bin/redis-check-rdb (it checks argv to change its behaviour) by
     replacing it with a symlink. Found by <https://dedup.debian.net/>.
 .
 redis (3:3.2.6-2) unstable; urgency=medium
 .
   * Rename RunTimeDirectory -> RuntimeDirectory in .service files.
     (Closes: #850534)
   * Refresh all patches with pq import -> pq export.
   * Tidy all patches, updating descriptions and use Pq-Topic to organise.
Checksums-Sha1:
 a332ce9eccbb011bc1aed47f373866edae79d424 2013 redis_3.2.8-2~bpo8+1.dsc
 c9e83c39b68d5f3980cae8b8f15b16ffcf83bfdd 36300 redis_3.2.8-2~bpo8+1.debian.tar.xz
Checksums-Sha256:
 26bb4896664369da6b9b51140203670b5f4aa2291f55b2ba3a1fa6907bfe69c3 2013 redis_3.2.8-2~bpo8+1.dsc
 19b97f08e16a96c11f6771a5ea15687e84b83a912e364876a33c88ae71fc3113 36300 redis_3.2.8-2~bpo8+1.debian.tar.xz
Files:
 421d2256768e6585d6f02a4c09bc0ef8 2013 database optional redis_3.2.8-2~bpo8+1.dsc
 65d231a9327f9aac2efbc52cf8ba91e2 36300 database optional redis_3.2.8-2~bpo8+1.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAljK3vMACgkQHpU+J9Qx
HlgS+Q//ck8uyW9VbFvvZcKapW9hkDQRD7Bj480WoxsQ4XecTCPC+L03/BEwLnzJ
75YkYemUT0Ss1/RWoMqLrszKm18qms5goL+2HqbVR67TrF7Dkx7If8U4e6nqtp/6
Xm9NSDetIAJy5BMRRGoVx/coOgp73S+PitPWZed0kMjd9ZY/PbwUp9IDE6QrLl2b
nIop1XtYxis1nOrGmYhs9xBp1fsLJ4USbrLlBdso0LD7BYVmzIX8dQu6YT8WAwrG
W/EkWC3zlE2POsxGC9FbkxsYkpLOr1RpVvgBPdyDDKUp1jFjc3dct+NGM7ax9HOv
cWjF7Vgd/SnWREnKQLXR0qeQdHdeM5z+4Dl8x2Jw63H3ldXk3VImKIPzhGQN13gp
+FHVlMNUNAtCNECTLTeSLZ/F3xz/wqJPIHMTYhPRX+6ND4J9ZMg8mDJLzD5cEEDD
wm5dx6XruWVadLyLXC3aYZevbGqqRQYqJxMfKHkmDyIQJd5v+pR1HSQfICtxh7ki
YZz3Gfhuh6eB/UvHQwajiJQlw/bnP1Ny+2RUYoTPXhUPikC2KPWuhY23yG/CBDFZ
prpzKzArwbPd7qTvf0lq+Cs7Ki996e/kn3Vmsuw57iZv74lYDadvkJYhmAuwxRDx
s9wIJ/T5ZAQaumH24pjbu1uIaoty822Ibb11zAb836LHEY3rH28=
=VWJP
-----END PGP SIGNATURE-----


Reply to: