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: 6122 SHA256: c4f75eb7fed7cbd9b16b685bce4044764c9dfe5a01f93c11768e09bf718065eb SHA1: 9e03bee9327ee8327242f2632ef2c37f055f4024 MD5sum: 764b3ebeb36ed1ee003ccbc81f3e6554 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: 35046 SHA256: 43146d5c04140675bd0ec22589c178b697d0c3a85a71a77567b8ae64eda9012b SHA1: e6a9326319a4b109316bfbd1b6299fab63299d7f MD5sum: 06b2f514ae6255535f545b5fd437152f 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: 26696 SHA256: f4fd37bb1b5a082f1dd7f34235800a9fda84a064664d56f8a982776a09169057 SHA1: 592caa337593b8ee7cd84453426370e11dd5982b MD5sum: 063a2ebf4d7324facb3d69c9fecf443a 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: 12734 SHA256: 67d2e9c72bcbc6ee5889a12ab0661f5de0cc7f11928e1476131a10a3fb96a335 SHA1: 9d2eeadc02dbe75f9cf1ea9273c07d273e40c85d MD5sum: 3d9e40a340fc453a039ccb6735c9fa76 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: 332134 SHA256: 21bbe480104f8237b8e8954d552e267737737bd0c15aab98fbda49a141243e65 SHA1: 3cd0b3368f50e0dba5b7d22ec1e9182d910068c0 MD5sum: bbdef21fef5f7ebca20bcdc70e354073 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: 288482 SHA256: db4d589ad35b3004a226ecfd708c12d301c43b54703fb81e9383e66963dca164 SHA1: 04d014f5bcfecb4084de6f0105da39a970e018ef MD5sum: af675874abf9cb3c4ffb53cdec0ab9ad 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: 149404 SHA256: 52231eb9a8b3900362f66a3b844ab51f3cded5a7808a889637dd5314685de14c SHA1: 4d9341880732c748fa4bcb1fc67734598d4a399b MD5sum: da9b6fe661c0598139b6e043d253eb3f 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.8), python:any (>= 2.7.5-5~), 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: 1231806 SHA256: ed17ea9169f71d32da7080c5731c7819d28152fc146bf36b0158eb70a1491069 SHA1: 86fb59948108c30c67214408cf4ba5beab88fe20 MD5sum: 5d3b4cac40a5cba1fb33cc7bea9d82f6 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-six, python:any (>= 2.7.5-5~), python-enum34, python, python-ioflo, python-libnacl, python:any (<< 2.8) Homepage: https://github.com/saltstack/raet Priority: optional Section: python Filename: pool/main/r/raet/python-raet_0.6.3-1_all.deb Size: 95386 SHA256: b0f275f2c1bacd2c0db9ee4ad529d5ac6f756bb6941e0bdb597e3c17ab198d93 SHA1: 226d688effee3bf0017faea1bdfd2756c1337def MD5sum: 73831b49cd2d1d4811701471dde9c3b4 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: 440594c16f49f56a038612fb875a45a13845e84c43d07607b348859449b2fafe SHA1: de34fcaa059148a0ee70e8f23a88711eb615a463 MD5sum: 71acae8670d83bfc76ded27ecc7bf708 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: 330408 SHA256: 53b1d1b6265a34f374ab4f3bb091a4a5b0a52a93f47cd33824f377e5d2050a51 SHA1: 7249fe547db8f28e9502cd5de9678b97f110cdf5 MD5sum: 949efe5d5f399e440cdff759a87043f8 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.1+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.1+ds-1_all.deb Size: 12418 SHA256: bf5be0c913bb129178e28c2b4cdaf9e3974d5ebda03bd6763c1b6db28612c32f SHA1: fba67d781d3a037570f6b462c3e68f768bec43ac MD5sum: 6dccf09da525fa1cbb5924ac1c4012ce 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.1+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 88 Depends: python:any (>= 2.6~), python, salt-common (= 2018.3.1+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.1+ds-1_all.deb Size: 14392 SHA256: e344a8dc71477f1e15334da7aa80326bb5f079e0e5047c69255ab45b83cffe9f SHA1: 50c51ce6786650b44d32a76dcc3a0b8c741d92d5 MD5sum: 2ff0e4e0647c76ec8ad4e628ab95c401 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.1+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 25105 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.1+ds-1_all.deb Size: 5528238 SHA256: 0776072dea72b6b01f801e07bad1092a1e5559051924c17b06b248e08c834b9f SHA1: 464fffb2decf97b474e03eea8e9fafd96fc91bd5 MD5sum: a72b467b6aa702135238bb7cf7bcde27 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.1+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.1+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.1+ds-1_all.deb Size: 40796 SHA256: bde6ae2a350acbf02df6072a4391eea931dfc9dde9c39880baaf88567d0c0167 SHA1: 5d645bfecef16d0e75caf3a324fb30bb3dae0aab MD5sum: 06eda8b0ac50b61cf7dcffe030d8bcaa 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.1+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.1+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.1+ds-1_all.deb Size: 27024 SHA256: 7682039f0836c101f7e4028a7745c56214d08d46945745e183082dec2958f0df SHA1: f00a1c3464adedf9d41a392f1ccd337f14cb7859 MD5sum: 0a52cfda909da13abdc24e097bd1d921 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.1+ds-1 Architecture: all Maintainer: Debian Salt Team Installed-Size: 73 Depends: python:any (>= 2.6~), python, salt-common (= 2018.3.1+ds-1) Homepage: http://saltstack.org/ Priority: extra Section: admin Filename: pool/main/s/salt/salt-ssh_2018.3.1+ds-1_all.deb Size: 13830 SHA256: 3ddd5f501d233d916a01b863f412263be55140cf755c2c6937745e3cabaad05e SHA1: 4c1d117a754622b5945e698b399d0f7fe70aa2b0 MD5sum: 90892e5a431f23531617e19883709fd1 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.1+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.1+ds-1) Homepage: http://saltstack.org/ Priority: extra Section: admin Filename: pool/main/s/salt/salt-syndic_2018.3.1+ds-1_all.deb Size: 12732 SHA256: 0ef9992f0b08f4a62195d9608617924cf4f2c5f9245111937c6e2201faad1a73 SHA1: c350d6ea55b5f93211621acf865bb2c14c72caae MD5sum: 17e4c8ba55b7f522cfa15c935e429eaf 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.