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.7.5-5~), python:any (<< 2.8) 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: 6156 SHA256: 0ecb3f3e0c8a3f3f9186698f697e6dc72b4201edd49e3fc168cef350a42d205d SHA1: cd884482ce2ef3f77595983067a5cb1bf72a3f2d MD5sum: dcafe514cd050cb5d53d42a86c35f410 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.7.5-5~), python:any (<< 2.8), 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: 35074 SHA256: b75afc64c1fc48f0eccdbfa718a2cec0580faa6e2f0c6cff3f380d68cd210e03 SHA1: 9d9be0525be18e26c6b620db0b6c152fabe2303f MD5sum: 05efcab034421b8bee71e48c7117f1ba 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.7.5-5~), python:any (<< 2.8) 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: 26658 SHA256: d0895ffa747cf246d9187587b8c017013fdca862913258b7d7f5b9df4fc565ee SHA1: 23e99d7d2e41f1e53b275519aa424f2bdd929381 MD5sum: 634cd9b3ef9d653110e57e743116c6b9 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: 12752 SHA256: b75101f43ddadef649839be371efae63b1ac7298ebb61fe1e73912c79df17f92 SHA1: 1d8784ee4e9328b2f82d86b34b65f8e6a2022e6c MD5sum: 493d8ea3def64fccd9f19a296e117a03 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.7.5-5~), python:any (<< 2.8), 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: 331882 SHA256: dbceaea6a7d8dc69243d427b931f489dfd5283d4d6532715dd31da5c07b424e0 SHA1: 2b8036a027ddb032e9706b24413faac0d8badd7d MD5sum: 0d8d589930549cad192491cb91a0f5d3 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: 288788 SHA256: 90483c77f244d14c6a96a033110463a74b66a42662f8224611a07736fb11cc91 SHA1: 337bd9717f8c86c2716bde264bbfe2fd01a657bb MD5sum: ac2ab51ce29b98b9407f3ef0e99fe1c6 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: 149306 SHA256: 443bf3879200206c5304d6108732d4df9a700b790140efda86dee2e1375f33c9 SHA1: 5e9759e1d3ecb6459e015790b3ff8901a6b7a0a3 MD5sum: 50ab2a081bbdfec47fd56f906035514b 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: 1235212 SHA256: 22f278811d4f8ec465619625ecbdcc223a0e474278639b32109c163020112c44 SHA1: 14b99f287596e832b0d4376e13aed614bff3d7a8 MD5sum: 5f451cd9a86c94078bf2657785156413 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:any (>= 2.7.5-5~), python-libnacl, python:any (<< 2.8), python-ioflo, python-enum34, python-six, python Homepage: https://github.com/saltstack/raet Priority: optional Section: python Filename: pool/main/r/raet/python-raet_0.6.3-1_all.deb Size: 95444 SHA256: ff6fa3e8cbcc8c0ead8b262164e6346a1bdebb9eafb960bbcdb92a5d6c7cb867 SHA1: b600d98a9e20175f3aa7add5aca7a6fa03311087 MD5sum: 4dd2d17e48407e1d97b9f168962f1ef9 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: 26740 SHA256: 5b0c41d611da9eaf850dbe5b712eed9e9b16b3f6b6364374f3d78732354ca338 SHA1: 84950b80158024295bce07411b19951aaf57f784 MD5sum: 7047b6ecc981d2e9d959cfbb979bfb56 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.4, python3:any (>= 3.3.2-2~) 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: 330212 SHA256: 5094aedb0e24ea31fb5a76b0ea658bf0dee8f0f5bd4957a3203e82d4e07ec52e SHA1: 520396ca5480fdfe1045b1de324f871659b4ad4c MD5sum: bcb30cf04e49b7fcc497ab3e182cbe04 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: 2018.3.4+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_2018.3.4+ds-1_all.deb Size: 12414 SHA256: 6c948bd2aaab20798f85cff8c3635f92ef6e50e9dc4456d292b2ce282c2b8d03 SHA1: 9ef43e31a46113df19a57b5593b1ce40a7eaf3d4 MD5sum: ff7e20a9b9ae8804ca277ddf321d2dd5 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: 2018.3.4+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 88 Depends: python, python:any (>= 2.6~), salt-common (= 2018.3.4+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_2018.3.4+ds-1_all.deb Size: 14344 SHA256: 15281574e1c7daaa7d6a54b8506cc4ce7baf6fc8749d977d56bdca2a6573f235 SHA1: 9b62a1a9323754fd4bb25fbe094c74db2a685acd MD5sum: 0a5a67c7069252d4bb45783ab20a63ac 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: 2018.3.4+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 25843 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-concurrent.futures, 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_2018.3.4+ds-1_all.deb Size: 5938158 SHA256: 7322441d6cac89371a76fa0fc92e123abb30f9ad77f76910e369b057213f1749 SHA1: d584fa740b0316b86d973ab5b73494e686d5eb3e MD5sum: 316e3b02b998a96db942ebdb758ca2e4 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: 2018.3.4+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 150 Depends: sysv-rc (>= 2.88dsf-24) | file-rc (>= 0.8.16), python, python:any (>= 2.6~), salt-common (= 2018.3.4+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_2018.3.4+ds-1_all.deb Size: 40362 SHA256: 0ee7aba22816bfc199808ea47a80f16eba81f3815301b6be51064f0614827ebb SHA1: 8431af1e879c8d966ae26165da14fc069356661c MD5sum: 1d72ee4e3e7f799069ce3e73d6f3fee6 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: 2018.3.4+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 157 Depends: sysv-rc (>= 2.88dsf-24) | file-rc (>= 0.8.16), python, python:any (>= 2.6~), salt-common (= 2018.3.4+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_2018.3.4+ds-1_all.deb Size: 27036 SHA256: dd3e680c06e9a1085153971b207d7b2777c4900527873a371d7905ad4fd86067 SHA1: 151ac1aa68e8f1f503e8b2e33a8a9ea4291c1824 MD5sum: 1653a3a3f0b2e84de862867bad903d9f 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: 2018.3.4+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 73 Depends: python, python:any (>= 2.6~), salt-common (= 2018.3.4+ds-1) Homepage: http://saltstack.org/ Priority: extra Section: admin Filename: pool/main/s/salt/salt-ssh_2018.3.4+ds-1_all.deb Size: 13798 SHA256: 35322503aadbae693acb2317c81e71fa57550a02b95550c4384f98360bc85c34 SHA1: cd98e3dec461e2c139e80fa6f3d577869a76c459 MD5sum: 17adbc8d85fb3cc180a90a1a8825e057 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: 2018.3.4+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 (= 2018.3.4+ds-1) Homepage: http://saltstack.org/ Priority: extra Section: admin Filename: pool/main/s/salt/salt-syndic_2018.3.4+ds-1_all.deb Size: 12734 SHA256: 00f22b8a5d10d90d54cea87070e497fbd1bfceab0f4119a1912ebe58bd1ecf64 SHA1: 78dc87b2657d84714adf4f9ab48e9fc9471115d5 MD5sum: 0136771fdebceb0c99fd9cd886f7422f 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.