Package: chromium-widevine Source: chromium Version: 72.0.3626.122-1~deb9u1 Installed-Size: 803 Maintainer: Debian Chromium Maintainers Architecture: armhf Depends: chromium (= 72.0.3626.122-1~deb9u1) Size: 128112 SHA256: 75b159156ec8a1a1753669df2e84dbf4ff355d33f65f3b13e96e3fbe2dfb8aff SHA1: 26f5b01f6cc63d2309d7fa4726cd0e3e073e97cf MD5sum: a5cdaf8a62299bde03c5b65611fc7402 Description: web browser - widevine content decryption support Web browser that aims to build a safer, faster, and more stable internet browsing experience. . This package provides support for the widevine content decryption module. Homepage: http://www.chromium.org/Home Section: contrib/web Priority: optional Filename: pool/contrib/c/chromium/chromium-widevine_72.0.3626.122-1~deb9u1_armhf.deb Package: python-django-anymail Source: django-anymail Version: 0.8-2+deb9u1 Installed-Size: 201 Maintainer: Debian Python Modules Team Architecture: all Depends: python-django, python-requests, python-six, python:any (<< 2.8), python:any (>= 2.7.5-5~) Suggests: python-sparkpost Size: 41254 SHA256: ad9ec36435ce3b4ddf3fa0fa06dce5d29698b6a54f0bf36aa4b78bfd7461e1b2 SHA1: 1539294f1959412f90b2d9da615b26d67f10d1cf MD5sum: c898f7af2f28d8e8e92ed27982596d3f Description: Django email backend for multiple ESPs (Python 2) Anymail integrates several transactional email service providers (ESPs) into Django, with a consistent API that lets you use ESP-added features without locking your code to a particular ESP. . It currently fully supports Mailgun, Postmark, SendGrid, and SparkPost, and has limited support for Mandrill. . Anymail normalizes ESP functionality so it "just works" with Django's built-in `django.core.mail` package. It includes: . * Support for HTML, attachments, extra headers, and other features of Django's built-in email * Extensions that make it easy to use extra ESP functionality, like tags, metadata, and tracking, with code that's portable between ESPs * Simplified inline images for HTML email * Normalized sent-message status and tracking notification, by connecting your ESP's webhooks to Django signals * "Batch transactional" sends using your ESP's merge and template features . This is the Python 2 version of the package. Homepage: https://github.com/anymail/django-anymail Section: contrib/python Priority: optional Filename: pool/contrib/d/django-anymail/python-django-anymail_0.8-2+deb9u1_all.deb Package: python3-django-anymail Source: django-anymail Version: 0.8-2+deb9u1 Installed-Size: 201 Maintainer: Debian Python Modules Team Architecture: all Depends: python3-django, python3-requests, python3-six, python3:any (>= 3.3.2-2~) Suggests: python3-sparkpost Size: 41320 SHA256: 8eb07666ea05647588caaa8753e7143182d30de2c2d5dec0cb2c18c3d50bac20 SHA1: 7d2bd9b1c2b2ee04b3fdb168932c442dc1109f76 MD5sum: 3864352c28b8afd43b7ec7e1237d9126 Description: Django email backend for multiple ESPs (Python 3) Anymail integrates several transactional email service providers (ESPs) into Django, with a consistent API that lets you use ESP-added features without locking your code to a particular ESP. . It currently fully supports Mailgun, Postmark, SendGrid, and SparkPost, and has limited support for Mandrill. . Anymail normalizes ESP functionality so it "just works" with Django's built-in `django.core.mail` package. It includes: . * Support for HTML, attachments, extra headers, and other features of Django's built-in email * Extensions that make it easy to use extra ESP functionality, like tags, metadata, and tracking, with code that's portable between ESPs * Simplified inline images for HTML email * Normalized sent-message status and tracking notification, by connecting your ESP's webhooks to Django signals * "Batch transactional" sends using your ESP's merge and template features . This is the Python 3 version of the package. Homepage: https://github.com/anymail/django-anymail Section: contrib/python Priority: optional Filename: pool/contrib/d/django-anymail/python3-django-anymail_0.8-2+deb9u1_all.deb Package: rtcw Source: iortcw Version: 1.50a+dfsg1-3+deb9u1 Installed-Size: 4300 Maintainer: Debian Games Team Architecture: armhf Depends: rtcw-common (= 1.50a+dfsg1-3+deb9u1), libc6 (>= 2.15), libcurl3-gnutls (>= 7.16.2), libfreetype6 (>= 2.2.1), libgcc1 (>= 1:3.5), libgl1-mesa-glx | libgl1, libjpeg62-turbo (>= 1.3.1), libogg0 (>= 1.0rc3), libopenal1 (>= 1.14), libopus0 (>= 1.1), libopusfile0 (>= 0.5), libsdl2-2.0-0 (>= 2.0.4), libstdc++6 (>= 5), libvorbis0a (>= 1.1.2), libvorbisfile3 (>= 1.1.2), zlib1g (>= 1:1.1.4) Size: 1473062 SHA256: 1c8281dc42842c5886704c0522655c9f79ba31a514565bcfaef0022b2e0bfdf7 SHA1: c42cb80ffe7fa6c6f0559a11fe2aba1bbbb446dc MD5sum: 95a6a9793befae8a44f9501c41319ed9 Description: game engine for Return to Castle Wolfenstein Return to Castle Wolfenstein is a military- and occult-themed first-person shooter game in a Second World War setting, originally released in 2001. It is a sequel to Wolfenstein 3D, which is also available for Debian (in the wolf4sdl package). . This package contains the iortcw game engines for the single-player campaign and multiplayer, based on ioquake3 and the GPL source releases of RTCW. . For security reasons, this version has been modified to prevent native executable code from being unpacked from game packages (PK3 files). Some game modifications will not work as a result of this change. . Return to Castle Wolfenstein requires non-distributable game data files in the rtcw-data package, prepared using the game-data-packager tool. Homepage: https://github.com/iortcw/iortcw/ Recommends: x11-utils | zenity | kde-baseapps-bin Section: contrib/games Priority: optional Filename: pool/contrib/i/iortcw/rtcw_1.50a+dfsg1-3+deb9u1_armhf.deb Package: rtcw-common Source: iortcw Version: 1.50a+dfsg1-3+deb9u1 Installed-Size: 1435 Maintainer: Debian Games Team Architecture: armhf Depends: rtcw-data (>= 1.42b+40) | game-data-packager (>= 40), libc6 (>= 2.7) Size: 612510 SHA256: 80673af1f4d9de2520af44bd092f634fc31cd813873d1b414697a97c04381c81 SHA1: bebf042e835ac34f0214d330c1661695cd5b9200 MD5sum: 64588c4477540e902273a5db0c4090a7 Description: common files for Return to Castle Wolfenstein Return to Castle Wolfenstein is a military- and occult-themed first-person shooter game in a Second World War setting, originally released in 2001. It is a sequel to Wolfenstein 3D, which is also available for Debian (in the wolf4sdl package). . This package contains files shared by the game and the dedicated server. It requires non-distributable game data files from the rtcw-data package, which can be prepared using the game-data-packager tool. Homepage: https://github.com/iortcw/iortcw/ Section: contrib/games Priority: optional Filename: pool/contrib/i/iortcw/rtcw-common_1.50a+dfsg1-3+deb9u1_armhf.deb Package: rtcw-server Source: iortcw Version: 1.50a+dfsg1-3+deb9u1 Installed-Size: 491 Maintainer: Debian Games Team Architecture: armhf Depends: adduser, lsb-base (>= 3.0-6~), rtcw-common (= 1.50a+dfsg1-3+deb9u1), init-system-helpers (>= 1.18~), libc6 (>= 2.15), zlib1g (>= 1:1.1.4) Size: 257318 SHA256: c8235e5be772971b353964f37ce6a5b180b9c7864be134b283ef400a54788cb7 SHA1: a52f3d966062479e42995044c0b1dbebb154344d MD5sum: b15059af61a10afc9fe2b271bfa6a1af Description: standalone server for Return to Castle Wolfenstein Return to Castle Wolfenstein is a military- and occult-themed first-person shooter game in a Second World War setting, originally released in 2001. It is a sequel to Wolfenstein 3D, which is also available for Debian (in the wolf4sdl package). . This package contains the iortcw dedicated server for multiplayer, based on ioquake3 and the GPL source releases of RTCW. It also contains the init script and systemd unit to start the RTCW server, with support for multiple server instances under systemd. . Return to Castle Wolfenstein requires non-distributable game data files from the rtcw-data package, prepared using the game-data-packager tool. Homepage: https://github.com/iortcw/iortcw/ Section: contrib/games Priority: optional Filename: pool/contrib/i/iortcw/rtcw-server_1.50a+dfsg1-3+deb9u1_armhf.deb