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: 6126 SHA256: 8d29e7ffb90a034ca0da6a58badb7a29eb686674ff5dbc58ae11df6dcc61b33d SHA1: b5e4baa321952408955d02e5d025e0664b022eab MD5sum: 5c4e2049aecb246edd50cc62478658d7 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: 35078 SHA256: 904dbeff7aeeb43c283ffe127a925d1e67beb34bb33ef7f1a720baa70e37e350 SHA1: 5d8c07b254950e5441bbec98d43210449ec5b946 MD5sum: 14ce8ec18a0e7ecdf2bcb04547318907 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: 26694 SHA256: cdfd91d62d3e62b026ac655a8a9e497e8d218e2dc50b5f5fd288207711fcc744 SHA1: 171e9894072ecaa9b9d72b80451459890ebf90f1 MD5sum: 853b658c80e024e176b72a9c571f491c 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: 93fe30f068ff34fc75bff7872d87b17a605f7112d6c344bbddf995ef25faba8c SHA1: 17e50f4c66aa13f7a5cc6c984d3e2f67ab07b0cf MD5sum: dde18c658ba904adf14b25cda6127831 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: python:any (<< 2.8), python:any (>= 2.7.5-5~), python2.7 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: 332150 SHA256: c42db8cf3aa60debf2b71a701a91669c1789d96662a4a279939b89c793e03e91 SHA1: 035c484d75e41ca9505aad8fc843fe87561698ef MD5sum: 496e36c7da2d1ea884074f9b99d7ac4f 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: 288466 SHA256: 55fefc5775b1c3094b136b773b45b1d261fb9f2c5c13d94a42d890b719a20f4d SHA1: dcb7a2efe0ffa808bd7cc58172875136123a3d26 MD5sum: 0c3c2997a526ee1deef2f8d87059280f 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, python:any (>= 2.7.5-5~), python:any (<< 2.8) 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: e6bf45cd84cdbf31a137c32f5e8758ff347965c03a138675580c97b5bdb6fcb1 SHA1: 0d2a612eb5b2fc723eb7031de1013138c552f858 MD5sum: 9844e9971b22da1a2a0e6dd2d4efda5b 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:any (>= 2.7.5-5~), python:any (<< 2.8), python-backports.ssl-match-hostname, 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: 1234992 SHA256: 2316fc09ad405788877939a594121abf8c72e5fd5083731fd4bc909b4c6c3f20 SHA1: 80d2383ac5b6a7e35feee806e5a91db12d4494ac MD5sum: 69291a95b967503a6c7eca187cda066d 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, python-six, python:any (<< 2.8), python-libnacl, python:any (>= 2.7.5-5~), python-ioflo, python-enum34 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: 9fa301e1c0d5fb4368271d43e58fa9a89ffe6dd38b66514957966d711b314aa0 SHA1: 8795d693c15f7a0f8e62c857128e848b45a91c12 MD5sum: 4e75bfd204cca7e931fbcd0972883eb9 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: 26798 SHA256: 83db180ffddcca32a32544fd11155343a74171a76963fea1828298e77fc2a414 SHA1: 5d14b7800f0415461d14fcb34d6e03a3a0fa3cbf MD5sum: 352d33a7767f39c756df5fe5fa753b5b 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: 330416 SHA256: f3471ebd306ae0b457ea14a6e746e81111414354018780163abe770bb96b9afc SHA1: 9b40de801893d5d15d8053520b324fc3e7c241b2 MD5sum: e18b9cccb8613ecabee5a22688c9a720 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.7+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 79 Depends: python:any (>= 2.6~), python, 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.7+ds-1_all.deb Size: 12422 SHA256: 4ce0f19b29402bdcabd31a15700847143290313c8cf83be4e91b2971647a0123 SHA1: 1e138349dc8e7c16d6402d01fd549c923816f59e MD5sum: 65c180e253aa02a2e689414c44188b8a 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.7+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 88 Depends: python:any (>= 2.6~), python, salt-common (= 2017.7.7+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.7+ds-1_all.deb Size: 14300 SHA256: 35c96ad021f39d03500d479cd5df44bfc885ebdcff88563e966f5e7dae739727 SHA1: aea0734746a9ddeb16fb37811c0c2398cdb9e160 MD5sum: 2d497db8c6206cca3fa164b319f0b104 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.7+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 22441 Depends: python:any (>= 2.7.5-5~), python, python:any (<< 2.8), 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.7+ds-1_all.deb Size: 5073830 SHA256: 375157734a28af4e9570b1b5969829566c51dca02d6ad99c220c659fef7fc380 SHA1: 3150b8580ad011c974b527742dfc6306f4c03aa1 MD5sum: 442e3093aa9c1aaf343d28d2af8d392a 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.7+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 149 Depends: sysv-rc (>= 2.88dsf-24) | file-rc (>= 0.8.16), python:any (>= 2.6~), python, salt-common (= 2017.7.7+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.7+ds-1_all.deb Size: 40264 SHA256: ae4e14d76c27f5db7ef149b9f8036dc5916361790273acc186a8784376b8445e SHA1: 43027c39b1ae2890b976222b81f8eb5e88778024 MD5sum: e0d9ac722ef29db12e23ac222de40325 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.7+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 156 Depends: sysv-rc (>= 2.88dsf-24) | file-rc (>= 0.8.16), python:any (>= 2.6~), python, salt-common (= 2017.7.7+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.7+ds-1_all.deb Size: 26744 SHA256: 3e2e53b1dd00248003822a5c895918e37cb0ad9fcc77ac59d753df06a14d82b5 SHA1: 68280cf746f439e2f9662623cc40cf271348be77 MD5sum: 947d4a28473091979a9c27e35825a6d1 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.7+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 73 Depends: python:any (>= 2.6~), python, salt-common (= 2017.7.7+ds-1) Homepage: http://saltstack.org/ Priority: extra Section: admin Filename: pool/main/s/salt/salt-ssh_2017.7.7+ds-1_all.deb Size: 13822 SHA256: 72a4722f65473517bf9751c289c05c44164c77d2f1293566cc3004399ef8d8a8 SHA1: a8f64141da99057ff743304a4a225af7b9ed79d8 MD5sum: 1e21e0696a0fe5ce6db1149d251365a3 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.7+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 79 Depends: sysv-rc (>= 2.88dsf-24) | file-rc (>= 0.8.16), python:any (>= 2.6~), python, salt-master (= 2017.7.7+ds-1) Homepage: http://saltstack.org/ Priority: extra Section: admin Filename: pool/main/s/salt/salt-syndic_2017.7.7+ds-1_all.deb Size: 12736 SHA256: 3889174e2c6919236bddf9a128bb778cdf888ba23300f8ec9cae61f9ec0b4bf9 SHA1: 8c61f7319236584490072c3853203349f40ce9fb MD5sum: 34b13d384daacf2be5298fc59134e292 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.