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

Accepted python-redis 2.10.5-1~bpo8+1 (source all) into jessie-backports



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

Format: 1.8
Date: Fri, 01 Jul 2016 08:24:09 +0200
Source: python-redis
Binary: python-redis python3-redis
Architecture: source all
Version: 2.10.5-1~bpo8+1
Distribution: jessie-backports
Urgency: medium
Maintainer: Chris Lamb <lamby@debian.org>
Changed-By: Chris Lamb <lamby@debian.org>
Description:
 python-redis - Persistent key-value database with network interface (Python libr
 python3-redis - Persistent key-value database with network interface (Python 3 li
Changes:
 python-redis (2.10.5-1~bpo8+1) jessie-backports; urgency=medium
 .
   * Rebuild for jessie-backports.
 .
 python-redis (2.10.5-1) unstable; urgency=medium
 .
   * New upstream release.
   * wrap-and-sort -sa
   * Drop 001-Fix-tests-under-Redis-3.x-we-can-be-of-an-embedded-s.patch; merged
     upstream.
 .
 python-redis (2.10.3-8) unstable; urgency=medium
 .
   * Add '@' to autopkgtest `Depends:` line so that the packages we wish to test
     is actually installed.
 .
 python-redis (2.10.3-7) unstable; urgency=medium
 .
   * Actually test against the installed (and patched) version by removing the
     library from the local source tree.
 .
     We remove the contents (ie. with "redis/*") instead of the entire directory
     so that upstream's setup.py does not complain.
 .
 python-redis (2.10.3-6) unstable; urgency=medium
 .
   * Replace `-B` with `Restrictions: allow-stderr` in autopkgtests.
 .
     Failures were due to "no previously-included files found matching
     '__pycache__'" being written to stderr, caused by MANIFEST.in attempting to
     exclude these files which did not exist as it is a clean source checking.
 .
     Adding '-B' in 2.10.3-5 therefore had no effect, and would have actually
     prevented these files ever existing.
 .
     It does not appear possible to silence this message, so the options are
     either to:
 .
      a) Ensure these files exist so the warning never occurs (!).
      b) Remove the MANIFEST.in file.
      c) Permit stderr output. This is presumably safe as pytest is fairly
         robust.
 .
 python-redis (2.10.3-5) unstable; urgency=medium
 .
   * Run tests with -B flag to try and avoid .pyc and __pycache__ issues.
 .
 python-redis (2.10.3-4) unstable; urgency=medium
 .
   * Add patch to fix tests under Redis 3.x; discovered by debci.
Checksums-Sha1:
 704e089e6fce3790530f2f45dd79aee786a01dff 2041 python-redis_2.10.5-1~bpo8+1.dsc
 8fd231ec445f9cac433d8a9aad08453a56e05271 86029 python-redis_2.10.5.orig.tar.gz
 7a613a6c870dbe86731c0534f718b1f487775989 3916 python-redis_2.10.5-1~bpo8+1.debian.tar.xz
 96f52249389ca548a73338ef75cb1d896443ae63 54502 python-redis_2.10.5-1~bpo8+1_all.deb
 c8b39f6cf99b743aa3ee5f9acd52c61be624bde5 54584 python3-redis_2.10.5-1~bpo8+1_all.deb
Checksums-Sha256:
 6543b99f4faecb9851bbabc32b02cde41586f25d987a534730ce8a7b43228ac7 2041 python-redis_2.10.5-1~bpo8+1.dsc
 159835ac5f09822bb3c578bdf848b9d137a67c2e4ae4b7aa05390dac33087def 86029 python-redis_2.10.5.orig.tar.gz
 6b871418f66231d64145fc6fc0e4faaee04c14b2b9f2474d3b2599f0157b1bca 3916 python-redis_2.10.5-1~bpo8+1.debian.tar.xz
 8609385b62524e46b870f2fba9bb0138c05110ea3da1ce0e884d688a8dab920b 54502 python-redis_2.10.5-1~bpo8+1_all.deb
 a3d45752a62fad63df8666e67b2dbe7b849e91394c0ca60e4ee1f31451f394a8 54584 python3-redis_2.10.5-1~bpo8+1_all.deb
Files:
 933ec291af63cc63999a004fe32ba243 2041 python optional python-redis_2.10.5-1~bpo8+1.dsc
 0bd17cf92f1078f5bc0a4863d90fedeb 86029 python optional python-redis_2.10.5.orig.tar.gz
 033f5c341b7831283e1aaf50c71f5e3f 3916 python optional python-redis_2.10.5-1~bpo8+1.debian.tar.xz
 acc7f613266c8781f2581e7723aa1df6 54502 python optional python-redis_2.10.5-1~bpo8+1_all.deb
 ce5e19cc87f7e8081d816058735847a8 54584 python optional python3-redis_2.10.5-1~bpo8+1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJXeAi8AAoJEB6VPifUMR5YTVcP/2N//CKgZxPhBn3Y3Xp3MVf9
xrHBge1EObxrnYHRHX0s6+DqpacCnioeTnw2b9LRQgUBEsNzqhjC3qXmttcEDoPr
DYgPxbteIv6DC/4Ce0oHPTmDa/ScIlclzPMaiKulUqZCUSrEJ7OEM4UZyx9EoLY9
ggz9LvDGOMVDAvhGRxMGHoh0bguz0SNnhyQH8hmPVueynPJYqx1nBR9bH1Ccww7k
JBNWe/flVFJNX+aGCoMbiQwvM34kFjxsL81k6j5a0eRSC8Dvz1EQhxPD/625XJNl
fR4loxCY5ascAQjLPnNOOHb0CoM+jUvgNd59BjrWB38nfkYqrOoGEKRJpU6etZ19
5Zo1ClFjq1BUGqf3SC7h+Qxj2inSwHUSX+IZ6KewpnzkGogOJ8YaoSABXRnfbRCq
TiKggQ3MB0iDZO239G6Oful3/MRk/LbpOAJW/EEUxl5yCxV5+Zset5SyoyTiwnMj
BV8QZW5i1Mz82MPn880CNckE6VH3n6jZStk+g4iOpNobMEapKQcRcx1/f6hiksaL
vOE4WCYVZDLtYlNITNyb688CK/tk1PQWFPweeCa0nE8Pj3dFrl6V3QGh+uf8T5FL
pwi1DQCcixJA1SMBsROaBa5IUNhuyOB4WGioEKvwne++yD48juclmAbh25rlCQNJ
+NxSKB0JyX8pHwZ1yHEH
=dxfd
-----END PGP SIGNATURE-----


Reply to: