Package: python-backports.ssl-match-hostname Source: backports.ssl-match-hostname Version: 3.4.0.2-1 Architecture: all Maintainer: Debian Python Modules Team Installed-Size: 60 Depends: python:any (<< 2.8), python:any (>= 2.7.5-5~) Homepage: https://bitbucket.org/brandon/backports.ssl_match_hostname Priority: optional Section: python Filename: pool/main/b/backports.ssl-match-hostname/python-backports.ssl-match-hostname_3.4.0.2-1_all.deb Size: 6132 SHA256: 148351aae6194fded37a1d86cddbf8bb77ebf133c013762ac83c65c35f7f5bad SHA1: ac06799262762858574993ee7e366bd2798f6b8a MD5sum: 248c5b29ee9ce98db31ebedfeb6de2d0 Description: Backport of the Python 3.2 SSL hostname checking function The Secure Sockets layer is only actually secure if you check the hostname in the certificate returned by the server to which you are connecting, and verify that it matches to hostname that you are trying to reach. . But the matching logic, defined in RFC2818, can be a bit tricky to implement on your own. So the ssl package in the Standard Library of Python 3.2 and greater now includes a match_hostname() function for performing this check instead of requiring every application to implement the check separately. . This package contains a backport of the ssl.match_hostname function for Python 2.4 and above. Package: python-concurrent.futures Version: 3.0.3-1 Architecture: all Maintainer: PKG OpenStack Installed-Size: 217 Depends: python:any (<< 2.8), python:any (>= 2.7.5-5~), libjs-sphinxdoc (>= 1.0) Provides: python-futures Homepage: http://code.google.com/p/pythonfutures/ Priority: optional Section: python Filename: pool/main/p/python-concurrent.futures/python-concurrent.futures_3.0.3-1_all.deb Size: 35080 SHA256: b5d75fd8b333d1c720b284ead3e1ef050243836036c2442fb0179ce24e5b5a9a SHA1: 5aad507968d2fb0c519e2d85b250dbec9c0ee676 MD5sum: b9710e41d673500e7aff5e781c823ecb Description: backport of concurrent.futures package from Python 3.2 The concurrent.futures module provides a high-level interface for asynchronously executing callables. . This is a backport for concurrent.futures as of PEP-3148 and included in Python 3.2 Package: python-enum34 Source: enum34 Version: 1.0.4-1 Architecture: all Maintainer: Barry Warsaw Installed-Size: 216 Depends: python:any (<< 2.8), python:any (>= 2.7.5-5~) Suggests: python-enum34-doc Homepage: https://pypi.python.org/pypi/enum34 Priority: optional Section: python Filename: pool/main/e/enum34/python-enum34_1.0.4-1_all.deb Size: 26710 SHA256: 9f707f772dc3e163fa556be2c007d83e8154b08522ebbfc79417770ac2319d71 SHA1: f3f4d40bc6c29b69c7a2d2d8a9f68a15e01f4b71 MD5sum: 44f4a6bd926ebf7b68549e3d7c63fe71 Description: backport of Python 3.4's enum package PEP 435 adds an enumeration to Python 3.4. This module provides a backport of that data type for older Python versions. It defines two enumeration classes that can be used to define unit sets of names and values: Enum and IntEnum. . This is the Python 2 compatible package. Package: python-enum34-doc Source: enum34 Version: 1.0.4-1 Architecture: all Maintainer: Barry Warsaw Installed-Size: 63 Homepage: https://pypi.python.org/pypi/enum34 Priority: optional Section: doc Filename: pool/main/e/enum34/python-enum34-doc_1.0.4-1_all.deb Size: 12742 SHA256: 71196dffd0b04ca8047c63d53791926512abc1ea8cad6d8cdf9cc9bbe1480a25 SHA1: 83789315e8335b5347371c6b9c27c920428011d6 MD5sum: b60021836f2708aa089f8bfd8cf540cc Description: backport of Python 3.4's enum package PEP 435 adds an enumeration to Python 3.4. This module provides a backport of that data type for older Python versions. It defines two enumeration classes that can be used to define unit sets of names and values: Enum and IntEnum. . This is the common documentation package. Package: python-future Version: 0.14.3-1 Architecture: all Maintainer: PKG OpenStack Installed-Size: 1711 Pre-Depends: dpkg (>= 1.15.6~) Depends: python2.7, python:any (>= 2.7.5-5~), python:any (<< 2.8) Suggests: python-future-doc Homepage: https://python-future.org Priority: optional Section: python Filename: pool/main/p/python-future/python-future_0.14.3-1_all.deb Size: 332234 SHA256: 48122dac0b2fecd8d3fde0b1e899873fd14f44ddf2175c1609a857b1c73446a3 SHA1: 85d897c5ec669258eb5b22a46098b7a1a06ea4ba MD5sum: bd2ac885952d6596bc0945bccd032c5e Description: single-source support for Python 3 and 2 - Python 2.x Future is the missing compatibility layer between Python 2 and Python 3. It allows one to use a single, clean Python 3.x-compatible codebase to support both Python 2 and Python 3 with minimal overhead. . The imports have no effect on Python 3. On Python 2, they shadow the corresponding builtins, which normally have different semantics on Python 3 versus 2, to provide their Python 3 semantics. . This package contains the Python 2.x module. Package: python-future-doc Source: python-future Version: 0.14.3-1 Architecture: all Maintainer: PKG OpenStack Installed-Size: 1545 Pre-Depends: dpkg (>= 1.15.6~) Depends: libjs-sphinxdoc (>= 1.0) Homepage: https://python-future.org Priority: optional Section: doc Filename: pool/main/p/python-future/python-future-doc_0.14.3-1_all.deb Size: 288476 SHA256: 3ebde05a028805eaf03e83611e85943d2ae416655af294b1f7da782870aca6ac SHA1: 83a230930298b27e80f939792371552bb10506e6 MD5sum: a7181e8b911257c4979014e71ebe446d Description: Clean single-source support for Python 3 and 2 - doc Future is the missing compatibility layer between Python 2 and Python 3. It allows one to use a single, clean Python 3.x-compatible codebase to support both Python 2 and Python 3 with minimal overhead. . The imports have no effect on Python 3. On Python 2, they shadow the corresponding builtins, which normally have different semantics on Python 3 versus 2, to provide their Python 3 semantics. . This package contains the documentation. Package: python-ioflo Source: ioflo Version: 1.3.8-1 Architecture: all Maintainer: Samuel M. Smith Installed-Size: 1250 Depends: python:any (<< 2.8), python:any (>= 2.7.5-5~), python Homepage: https://github.com/ioflo/ioflo Priority: optional Section: python Filename: pool/main/i/ioflo/python-ioflo_1.3.8-1_all.deb Size: 149450 SHA256: f261073bd950cec0281c31c6af278cc821007b8702a6e50093ba32751c8c7df5 SHA1: 7eb703cf3efb24628f2a3819dd06d55b3fb92894 MD5sum: 05a5387c4e658674f8c301f904fdf6cc Description: Flow Based Programming Automated Reasoning Engine and Automa Enabling the Programmable World. http://ioflo.com Package: python-libcloud Source: libcloud Version: 1.5.0+ds-1 Architecture: all Maintainer: Debian Python Modules Team Installed-Size: 13066 Depends: python-backports.ssl-match-hostname, python:any (>= 2.7.5-5~), python:any (<< 2.8), python-crypto (>= 2.6), python-lockfile (>= 0.9), python-simplejson Homepage: https://libcloud.apache.org/ Priority: optional Section: python Filename: pool/main/libc/libcloud/python-libcloud_1.5.0+ds-1_all.deb Size: 1232408 SHA256: 0891e951e3b07ab70f9fd4bb7aff6969ea605030626060a24110039bf2eca65c SHA1: 1c3a0bfca69942f7d630e642e8c624b1d80a1e63 MD5sum: 8a638cd40cf9ea3f2d8cc265c30be7b1 Description: unified Python interface into the cloud libcloud is a pure Python client library for interacting with many of the popular cloud server providers using a unified API. It was created to make it easy for developers to build products that work between any of the services that it supports. . * Avoid vendor lock-in * Use the same API to talk to many different providers * More than 30 supported providers total * Four main APIs: Compute, Storage, Load Balancers, DNS * Supports Python 2.5, Python 2.6, Python 2.7, PyPy and Python 3 . Resource you can manage with Libcloud are divided in the following categories: . * Cloud Servers and Block Storage - services such as Amazon EC2 and Rackspace Cloud Servers (libcloud.compute.*) * Cloud Object Storage and CDN - services such as Amazon S3 and Rackspace CloudFiles (libcloud.storage.*) * Load Balancers as a Service, LBaaS (libcloud.loadbalancer.*) * DNS as a Service, DNSaaS (libcloud.dns.*) . libcloud was originally created by the folks over at Cloudkick, but has since grown into an independent free software project licensed under the Apache License (2.0). Package: python-raet Source: raet Version: 0.6.3-1 Architecture: all Maintainer: Samuel M. Smith Installed-Size: 1507 Depends: python-libnacl, python, python:any (>= 2.7.5-5~), python-enum34, python:any (<< 2.8), python-six, python-ioflo Homepage: https://github.com/saltstack/raet Priority: optional Section: python Filename: pool/main/r/raet/python-raet_0.6.3-1_all.deb Size: 95396 SHA256: 6d84f094c9dc41c402b6aca5ebd69907911b03d533f0d7d474a2c7d5f0ff8a07 SHA1: 67d1bf012221d8918efba9659e938c5d06c79e7a MD5sum: 13f45f71c693497557b2a51c79b42076 Description: Reliable Asynchronous Event Transport protocol Asynchronous transaction based protocol using Ioflo. http://ioflo.com Package: python3-enum34 Source: enum34 Version: 1.0.4-1 Architecture: all Maintainer: Barry Warsaw Installed-Size: 216 Depends: python3:any (>= 3.3.2-2~) Suggests: python-enum34-doc Homepage: https://pypi.python.org/pypi/enum34 Priority: optional Section: python Filename: pool/main/e/enum34/python3-enum34_1.0.4-1_all.deb Size: 26794 SHA256: b3a7e5e15636612a620738336a436b0355746a5729073a4e5b83fc9a537e4c79 SHA1: 41f971ffe774111ef8718229589d7cd6df0f662b MD5sum: 45e60374511ea3fe3c362ae10715e783 Description: backport of Python 3.4's enum package PEP 435 adds an enumeration to Python 3.4. This module provides a backport of that data type for older Python versions. It defines two enumeration classes that can be used to define unit sets of names and values: Enum and IntEnum. . This is the Python 3 compatible package. Package: python3-future Source: python-future Version: 0.14.3-1 Architecture: all Maintainer: PKG OpenStack Installed-Size: 1645 Pre-Depends: dpkg (>= 1.15.6~) Depends: python3:any (>= 3.3.2-2~), python3.4 Suggests: python-future-doc Homepage: https://python-future.org Priority: optional Section: python Filename: pool/main/p/python-future/python3-future_0.14.3-1_all.deb Size: 330418 SHA256: cdd8c8733223511d7db1b2f204acc5ae3c2d5619ca7fd3624c4e2514dacec7c9 SHA1: e39f4790b2e701530807f3b1b43cc444c0e09723 MD5sum: 795bdb14cdf3a2b290092e1eaad8746c Description: Clean single-source support for Python 3 and 2 - Python 3.x Future is the missing compatibility layer between Python 2 and Python 3. It allows one to use a single, clean Python 3.x-compatible codebase to support both Python 2 and Python 3 with minimal overhead. . The imports have no effect on Python 3. On Python 2, they shadow the corresponding builtins, which normally have different semantics on Python 3 versus 2, to provide their Python 3 semantics. . This package contains the Python 3.x module. Package: salt-api Source: salt Version: 2017.7.8+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 79 Depends: python, python:any (>= 2.6~), sysv-rc (>= 2.88dsf-24) | file-rc (>= 0.8.16), salt-master Recommends: python-cherrypy3 Homepage: http://saltstack.org/ Priority: extra Section: admin Filename: pool/main/s/salt/salt-api_2017.7.8+ds-1_all.deb Size: 12460 SHA256: 83faeb966a23c43445af856ec3f346687b381e341bca10ce83400c4745c03280 SHA1: 8c4baafc00cf8522a4549ce24887459bdafad27e MD5sum: f8299e0bf9883666bd346f9c3f4d7bf6 Description: Generic, modular network access system a modular interface on top of Salt that can provide a variety of entry points into a running Salt system. It can start and manage multiple interfaces allowing a REST API to coexist with XMLRPC or even a Websocket API. . The Salt API system is used to expose the fundamental aspects of Salt control to external sources. salt-api acts as the bridge between Salt itself and REST, Websockets, etc. Package: salt-cloud Source: salt Version: 2017.7.8+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 88 Depends: python, python:any (>= 2.6~), salt-common (= 2017.7.8+ds-1), python-libcloud (>= 0.14.1-1) Recommends: python-netaddr Suggests: python-botocore Homepage: http://saltstack.org/ Priority: extra Section: admin Filename: pool/main/s/salt/salt-cloud_2017.7.8+ds-1_all.deb Size: 14300 SHA256: 4208b497c3254fc5d43a1ff67e382bc25f53d1c909bcebd0832ddf77901a9db9 SHA1: 7060f2cc8c0abc6dce383e2e9eaa6aed59dd5739 MD5sum: c08d16d67640b4a2d53ade396acced51 Description: public cloud VM management system provision virtual machines on various public clouds via a cleanly controlled profile and mapping system. Package: salt-common Source: salt Version: 2017.7.8+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 22767 Depends: python:any (>= 2.7.5-5~), python:any (<< 2.8), python, python-dateutil, python-jinja2, python-msgpack (>= 0.4), python-apt, python-yaml, python-pkg-resources, python-requests (>= 1.0.0), python-tornado (>= 4.2.1), python-psutil Recommends: lsb-release, python-mako Breaks: python-mako (<< 0.7.0) Homepage: http://saltstack.org/ Priority: extra Section: admin Filename: pool/main/s/salt/salt-common_2017.7.8+ds-1_all.deb Size: 5352564 SHA256: 10aad643cceb477de091c02db33c5f79724739da7996f76d24f4cf3f655610c7 SHA1: 990793d63de4f9647f196b0d6eaf6a04ac3a7186 MD5sum: bab6b90576491d21c53696b959d83c0e Description: shared libraries that salt requires for all packages salt is a powerful remote execution manager that can be used to administer servers in a fast and efficient way. . It allows commands to be executed across large groups of servers. This means systems can be easily managed, but data can also be easily gathered. Quick introspection into running systems becomes a reality. . Remote execution is usually used to set up a certain state on a remote system. Salt addresses this problem as well, the salt state system uses salt state files to define the state a server needs to be in. . Between the remote execution system, and state management Salt addresses the backbone of cloud and data center management. . This particular package provides shared libraries that salt-master, salt-minion, and salt-syndic require to function. Package: salt-master Source: salt Version: 2017.7.8+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 149 Depends: sysv-rc (>= 2.88dsf-24) | file-rc (>= 0.8.16), python, python:any (>= 2.6~), salt-common (= 2017.7.8+ds-1), python-crypto (>= 2.6.1), python-zmq (>= 14.0.0) Recommends: python-git Homepage: http://saltstack.org/ Priority: extra Section: admin Filename: pool/main/s/salt/salt-master_2017.7.8+ds-1_all.deb Size: 40302 SHA256: b78dd298a79a2f7f20a21b4c6faf59929a7e0e8eb312ffda1a490a8ae1127a27 SHA1: 27e4d50fae01ce79551255d5d73bfce7ec73f21d MD5sum: adf0bb8c29d59c525e81cbcf93f7fc46 Description: remote manager to administer servers via salt salt is a powerful remote execution manager that can be used to administer servers in a fast and efficient way. . It allows commands to be executed across large groups of servers. This means systems can be easily managed, but data can also be easily gathered. Quick introspection into running systems becomes a reality. . Remote execution is usually used to set up a certain state on a remote system. Salt addresses this problem as well, the salt state system uses salt state files to define the state a server needs to be in. . Between the remote execution system, and state management Salt addresses the backbone of cloud and data center management. . This particular package provides the salt controller. Package: salt-minion Source: salt Version: 2017.7.8+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 156 Depends: sysv-rc (>= 2.88dsf-24) | file-rc (>= 0.8.16), python, python:any (>= 2.6~), salt-common (= 2017.7.8+ds-1), python-crypto (>= 2.6.1), python-zmq (>= 14.0.0), dctrl-tools Recommends: dmidecode, debconf-utils Suggests: python-augeas Homepage: http://saltstack.org/ Priority: extra Section: admin Filename: pool/main/s/salt/salt-minion_2017.7.8+ds-1_all.deb Size: 26810 SHA256: 0fc5d4e72296e4a78015198d6aa37d7bb1d3c399db814de025292fe8cbcc56c5 SHA1: 937297c12671179fc79ff5de888ca20350be6586 MD5sum: 6a0c1e61d746d2ab65a0bbbf3dfda2b8 Description: client package for salt, the distributed remote execution system salt is a powerful remote execution manager that can be used to administer servers in a fast and efficient way. . It allows commands to be executed across large groups of servers. This means systems can be easily managed, but data can also be easily gathered. Quick introspection into running systems becomes a reality. . Remote execution is usually used to set up a certain state on a remote system. Salt addresses this problem as well, the salt state system uses salt state files to define the state a server needs to be in. . Between the remote execution system, and state management Salt addresses the backbone of cloud and data center management. . This particular package provides the worker / agent for salt. Package: salt-ssh Source: salt Version: 2017.7.8+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 73 Depends: python, python:any (>= 2.6~), salt-common (= 2017.7.8+ds-1) Homepage: http://saltstack.org/ Priority: extra Section: admin Filename: pool/main/s/salt/salt-ssh_2017.7.8+ds-1_all.deb Size: 13852 SHA256: e338e2c696cef93e7e1c050255e46472ae8745d14e3cc6612c39f0eda75bdd9b SHA1: f05f8cd03aeef417791ea353145cfbc8bf23365f MD5sum: fbd506e1990221aad1ca3d55d76af4e7 Description: remote manager to administer servers via salt salt is a powerful remote execution manager that can be used to administer servers in a fast and efficient way. . It allows commands to be executed across large groups of servers. This means systems can be easily managed, but data can also be easily gathered. Quick introspection into running systems becomes a reality. . Remote execution is usually used to set up a certain state on a remote system. Salt addresses this problem as well, the salt state system uses salt state files to define the state a server needs to be in. . Between the remote execution system, and state management Salt addresses the backbone of cloud and data center management. . This particular package provides the salt ssh controller. It is able to run salt modules and states on remote hosts via ssh. No minion or other salt specific software needs to be installed on the remote host. Package: salt-syndic Source: salt Version: 2017.7.8+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 79 Depends: sysv-rc (>= 2.88dsf-24) | file-rc (>= 0.8.16), python, python:any (>= 2.6~), salt-master (= 2017.7.8+ds-1) Homepage: http://saltstack.org/ Priority: extra Section: admin Filename: pool/main/s/salt/salt-syndic_2017.7.8+ds-1_all.deb Size: 12766 SHA256: 4a05359d47431d0c53671d3c2ede7d39c2758ebe489fdca4c4e4662cc17a0fd0 SHA1: 84be8dd744098894a1c6d11a7539bdca8d193592 MD5sum: 336185ffb43126dfbedfdb76e7f203d2 Description: master-of-masters for salt, the distributed remote execution system salt is a powerful remote execution manager that can be used to administer servers in a fast and efficient way. . It allows commands to be executed across large groups of servers. This means systems can be easily managed, but data can also be easily gathered. Quick introspection into running systems becomes a reality. . Remote execution is usually used to set up a certain state on a remote system. Salt addresses this problem as well, the salt state system uses salt state files to define the state a server needs to be in. . Between the remote execution system, and state management Salt addresses the backbone of cloud and data center management. . This particular package provides the master of masters for salt - it enables the management of multiple masters at a time.