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: 6114 SHA256: b20d93dd470df726a1d8317b67b3f2bf679aab9f3ba31b2e216f9c51404c54c2 SHA1: 01ec77250e4662b8f906223d46db8df7024658ee MD5sum: 4f1d335c4d79d3b011969e0edb8c5039 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: 35038 SHA256: 5bcdc06189c8b0ef30926099f963c5b8ae4232a009e2f750a2714f07cb892973 SHA1: e4c5b133c607d85bc8f9a0cbffcbae959228cb5f MD5sum: d368c9562515edc816d013a0bee77e16 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: 26724 SHA256: 53696f53f1481a60e23c7e338567a580ebc931dc91ef07a83e55e99ce9fc8401 SHA1: 21bb6a615be053147c69453976d41ef1a81d9364 MD5sum: cb3a76df3ed1c57594b1a04a228a4bbb 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: accafdd35f1fafad19ecba1751473c76cb7068c22e113c601992960cafe4bbc9 SHA1: 956a3926123b4a6232dc599f9318fe1edb6aea57 MD5sum: 489340d05db705fae6e2bfdc8a1d6738 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: 332214 SHA256: db4ed5ce7aaf59c5b185ea73c3f9a05d02ddbb3513064e67512f20ea500c996b SHA1: 84dabbad5e5d9219fe5e92a3a9c320caff048d9d MD5sum: e13b382e6e6086f286c763175f687da2 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: 288446 SHA256: ec256ac6967aea444dbceac5fc837e135c2bb372e856284aaae1c6c0f044256b SHA1: 68746b1f6ef97c0298f62c9a85b518e13b20747b MD5sum: 0e6f107f5dd826d6b656d93ed9e044bb 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: 149428 SHA256: 94948dbd736953af1cf8e98d5abe546212625e6dd0921167812ceeeec72a7bd3 SHA1: e4394176e43f17100a0043037f6088898caf8a77 MD5sum: 9e3bc8f579a3ba720c07fe1da8a81986 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-backports.ssl-match-hostname, 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: 1231712 SHA256: e8900e113ec38ee0da2c35f6fa26e87896b445457b98c6604a9ef68cbd8cb307 SHA1: 52d9e6103cc81e1984dfa14e82557c92f6443313 MD5sum: 506e98dfd6f9d1b982b41a252a977739 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:any (<< 2.8), python:any (>= 2.7.5-5~), python-six, python-ioflo, python, 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: 95428 SHA256: 0de99888386873aa8edcd455338d1b19467b4054bb3865025a5ddbd5a2bd9de2 SHA1: d97f0d60a1e436a9175a98e1efe9ea39ec9b4acb MD5sum: 91a9a65956e25bf6a3c26122c0c0cead 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: 26804 SHA256: c4ba166015026cc688c7dca1345caa7eacb4c0860d5966073e85f79dcc56a26f SHA1: fa72ffc97ebb209cac3f1ae83cc88d856b956f06 MD5sum: 3f56f98a8f6c2c77f941d9dbff21eaa1 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: 330406 SHA256: ee90dba571decbf548a58e777eb222f17da68e3f53cec09873399c43de8e3b52 SHA1: 650c6d61faf6d3bc873d5c43826e56dd62b9373e MD5sum: c03a0f1a2892046172b19b9ca12ae200 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.3+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_2018.3.3+ds-1_all.deb Size: 12420 SHA256: 7c41cdcd52d874f05efe4879e8703917332de75a6134cfcda6eed16676734536 SHA1: 94aff51b44748036bbd0284fc876dca40e6ce749 MD5sum: 1e40f372cd424bdf95ced02e3552defc 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.3+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 88 Depends: python:any (>= 2.6~), python, salt-common (= 2018.3.3+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.3+ds-1_all.deb Size: 14388 SHA256: d4a059c55b67e310cd6d0bcc0da48c9778cc99255f33c4a265d9437be75475bb SHA1: bf7f8005e29ba71a13929c4f69c2e8c100d44d39 MD5sum: b0b8dc052e47357e27afade2fa80f6d9 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.3+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 25566 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_2018.3.3+ds-1_all.deb Size: 5913828 SHA256: a6eb8064e3948da96cb433749922ce76e61b6001b43ba66d7eddf19d6def30f7 SHA1: 65a41c2f9c0cd65cbb5c61cc0cf03b2cf08e33ab MD5sum: f08274899f202d69db36e6ec6e5fb10b 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.3+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 151 Depends: sysv-rc (>= 2.88dsf-24) | file-rc (>= 0.8.16), python:any (>= 2.6~), python, salt-common (= 2018.3.3+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.3+ds-1_all.deb Size: 40734 SHA256: 5af1125b798de709bafca9f1f3607071cf50c7234503c296da5ff1fa29a6b020 SHA1: 5815884789af002f1b426b76a1270f08ad1e4678 MD5sum: 83eb381f4ec57c3f5cd52875281ca1f2 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.3+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 157 Depends: sysv-rc (>= 2.88dsf-24) | file-rc (>= 0.8.16), python:any (>= 2.6~), python, salt-common (= 2018.3.3+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.3+ds-1_all.deb Size: 27004 SHA256: 6aa5d12a408ca5c4ac317b7693aea91d6a7f8a3af6744303bef108502755e4a9 SHA1: a7555d37b1d691baeb2c159deff587fbf70c94fb MD5sum: ad507ef222c467323120f4cf64440052 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.3+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 73 Depends: python:any (>= 2.6~), python, salt-common (= 2018.3.3+ds-1) Homepage: http://saltstack.org/ Priority: extra Section: admin Filename: pool/main/s/salt/salt-ssh_2018.3.3+ds-1_all.deb Size: 13816 SHA256: 40c940cc68d5043806b031c6dfb2dd965595c116d5b701b6a2adb77752a8a42b SHA1: 2e25070d09196ca6fd9fd3795d320aa8c28123ce MD5sum: 4e803aadaaf0b2252b9426fa1637dd78 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.3+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 (= 2018.3.3+ds-1) Homepage: http://saltstack.org/ Priority: extra Section: admin Filename: pool/main/s/salt/salt-syndic_2018.3.3+ds-1_all.deb Size: 12724 SHA256: 804f6c51ac2e74decd67effa7ffe4d575b85cc678dc8ab56c968c23ae2d2f120 SHA1: 03f1a3ff09a1518b33e3b4d608c01dd04ce64780 MD5sum: 26d16d7d343384fb617d364638e8a3de 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.