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: 6122 SHA256: e5a458b319d37ed6153ba26b0c537049913835aaac7af87b616b5fd46c921632 SHA1: daf2392bb92aa19eecdafd8065dc9480b56da429 MD5sum: 35f64565d33fa9dd4fd44c43f096b27c 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: 35050 SHA256: 62af90a63a9b91a71d1ae091353a640ee6ce7610b58b7a5cb4105bf4d4831f82 SHA1: 5d19724ed291c524e186dcf48a7991473be1a65d MD5sum: e6db0f934024b8be59e73aad82602a92 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: 26722 SHA256: ad29edcfb9ee54918f95698c062bb2824cb6e20cb50814ad4a4ef68d5bf8bb14 SHA1: 75e7228aa76d4a3acaa18d2606d7473662d1a2a8 MD5sum: 9a0afd2220dd60cc98c7e7d83d4f32fa 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: 12744 SHA256: 67c7ebe7e7dd08c71af6319fcd0f8e6834f2c1dda1e6c7ca67b0dd3c8ddca1a0 SHA1: dd85cb1d06129e9640fb2c48b01370edf395f694 MD5sum: 43557f4aeeaaf4016340c9005c331391 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: 332168 SHA256: d68af18628a8742c6766a564c7438a0e695263f4a64bd61f17b64750ae57f222 SHA1: 345485e21a010d9f25ca76dec53969fb49a2358f MD5sum: 1e07fce284b7b5ae8a3e5f154dc411e6 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: 288442 SHA256: e3edeaa671ba345fa1a69dc9ea3617413f4720ddd15b9190cda06897cc5cf2ee SHA1: fb7e6835665fcb495c23475cd521b6395150faf2 MD5sum: cb6dac161a73b57fa92979839b627785 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.7.5-5~), python, 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: 149422 SHA256: 517bc58a6cec90e774537f9ffad391f3702d6d7d39077810548158025c2a2e0d SHA1: ac230b2b01f0b10834d09e766c93194444bcd9d3 MD5sum: 69b0473ea7a39f4c2c0dba51a140610f 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.8), python:any (>= 2.7.5-5~), 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: 1234848 SHA256: 39bea2ce0a40a119a059174cdd6ad6782e4436f6d1ef5d8f92f606f845ae8f00 SHA1: e6aa9ac2ca130ce20946d0e17a13d9a1dd950bd5 MD5sum: 02751cf1d789b6b582313ef82ec01aae 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-ioflo, python:any (>= 2.7.5-5~), python-enum34, python-libnacl, python:any (<< 2.8), python, python-six Homepage: https://github.com/saltstack/raet Priority: optional Section: python Filename: pool/main/r/raet/python-raet_0.6.3-1_all.deb Size: 95380 SHA256: c66e9cce4b7dc2b6a1b323c7a9b52a5b9230928384ec3c6a33994d89b5bb3f00 SHA1: 549d50473c01142518058e26ddf896b133cfb8b7 MD5sum: a1ea51f3ad525c5714a0f422f82bd79d 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: 26802 SHA256: 0894d23398178011d994a9dfda1c1f9497a21efd7e626d5a00b07827306c2ecc SHA1: 3c5c2e1256ab8251a000722223ab44970a1c2994 MD5sum: ac7ab0af8c360c05c399b9b1ddc5eef0 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: 330354 SHA256: 878ef5868a33de3558a3abbe07fd5d006d6764b16b5447efea15c51802c2dfa5 SHA1: 7b2dde962f9ae6145706dd11a14213360686dcd4 MD5sum: 71c58287eb41ea38ce24c18622be151e 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.6+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.6+ds-1_all.deb Size: 12416 SHA256: 685d0ad5f8564dd7c72ac42b10a924a3f756f84b2047c6e96755ef487a4d6c0e SHA1: 7706610718993f18f769642ae43b80318e762daf MD5sum: 669a0741aa04bde66bb7db07e6d2febd 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.6+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 88 Depends: python, python:any (>= 2.6~), salt-common (= 2017.7.6+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.6+ds-1_all.deb Size: 14298 SHA256: 4a8ddbaddefa77d5b658f244b30254c42184c9a87d196505ae02f6c67341b37a SHA1: 4e227b0000a84b08464f20839ae90fd67970cb97 MD5sum: 92f41e21950d35d40c652ab81a4ee943 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.6+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 22420 Depends: python:any (<< 2.8), python:any (>= 2.7.5-5~), 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.6+ds-1_all.deb Size: 5049478 SHA256: 89e5b588abf0f84304a23b37d47dffa4a3d3d640490bedd47e5a76226a84cea4 SHA1: 369a766c946c6453d3e8e385f8fb7bc18dc705b0 MD5sum: 3323a458583dc025b0944913034991b0 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.6+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.6+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.6+ds-1_all.deb Size: 40296 SHA256: 39ce638a3a6cd62b9de6eaf2bdb18b7949d28489148404d28d960b7899a8b75f SHA1: 4b11c939f2b1c49145d91373c4eb42704898b373 MD5sum: 0bd2ca1921fd44e87aaf98732b9366b1 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.6+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.6+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.6+ds-1_all.deb Size: 26776 SHA256: c4b2b8e31cac599276a9a898afe8b64e3a031c82c349a654e8cc7e721843665a SHA1: 51ab3474d034dc0667a16a8ad581cc81f989b91a MD5sum: 410df6033434008c54f3ebdaf879575b 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.6+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 73 Depends: python, python:any (>= 2.6~), salt-common (= 2017.7.6+ds-1) Homepage: http://saltstack.org/ Priority: extra Section: admin Filename: pool/main/s/salt/salt-ssh_2017.7.6+ds-1_all.deb Size: 13830 SHA256: 7b545fc328883704bbe1c7af545f8467ab22a7035530e8dd597e42d8af84d6a9 SHA1: 4d917462db5de154a26a0ac89c188580cc9eba2f MD5sum: 6dbbbfc0890e2e2ed80a8df74a02b800 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.6+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.6+ds-1) Homepage: http://saltstack.org/ Priority: extra Section: admin Filename: pool/main/s/salt/salt-syndic_2017.7.6+ds-1_all.deb Size: 12730 SHA256: c24381f8d11e5b59f057c08f200a3e8122d5c4b1cc7aada60cd588f56be82f01 SHA1: 5ae6c37f73b935744ad32c1c89173c70e8cb3716 MD5sum: 927e592180ce514bfcdd9931abd53a3f 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.