Package: chromium-widevine Source: chromium Version: 73.0.3683.75-1~deb9u1 Installed-Size: 804 Maintainer: Debian Chromium Maintainers Architecture: amd64 Depends: chromium (= 73.0.3683.75-1~deb9u1) Size: 128406 SHA256: 391115b98c361e6d06c1419943bf00cefd410de813ee7aaa2e8193edac5c64e1 SHA1: 300c71d9df41e8173c8a5de26b9a10ebb18e3d41 MD5sum: f54dd1b976db6ae37b6c096ad9701674 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_73.0.3683.75-1~deb9u1_amd64.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: 6280 Maintainer: Debian Games Team Architecture: amd64 Depends: rtcw-common (= 1.50a+dfsg1-3+deb9u1), libc6 (>= 2.15), libcurl3-gnutls (>= 7.16.2), libfreetype6 (>= 2.2.1), libgcc1 (>= 1:3.0), 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: 1686494 SHA256: 68793c7cec0cdb96f12bdf86bbbf808e3bdc6ecdc155691d65b2441655d3cd3b SHA1: 205e609061bbdf13a400d4ed24a6d1679f629d93 MD5sum: cf9f088ca472aa6b4e13359c0fe0d0d0 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_amd64.deb Package: rtcw-common Source: iortcw Version: 1.50a+dfsg1-3+deb9u1 Installed-Size: 2184 Maintainer: Debian Games Team Architecture: amd64 Depends: rtcw-data (>= 1.42b+40) | game-data-packager (>= 40), libc6 (>= 2.14) Size: 705030 SHA256: 5f0742257ad644998815b5c8d8e006d542ef3d3c0849497254479191c4af81df SHA1: 7fb7a8065f7f8ebadea851bec0b53fa712ab3dac MD5sum: bf5d58db70134814db3e33cb8c4e5030 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_amd64.deb Package: rtcw-server Source: iortcw Version: 1.50a+dfsg1-3+deb9u1 Installed-Size: 710 Maintainer: Debian Games Team Architecture: amd64 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: 289652 SHA256: 0f5bd272d9d817a26e374b30c5a35e092e6181da063b447c45d2dfb1b315af5f SHA1: 3bf94df60b7302aebe32b83be98947a358517f01 MD5sum: f48eabb5de3ec683549dd917e7881d27 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_amd64.deb