From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Chromium package contains non-free components (Widevine)
Date: Sun, 22 May 2022 04:10:06 +0200 [thread overview]
Message-ID: <20220522021006.ysttjVtOF5SbgdlWD96mO8fneCI1u1UG8UmJvhtB5aQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29273@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1311 bytes --]
Closed issue by selfisekai on void-packages repository
https://github.com/void-linux/void-packages/issues/29273
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname: `Void 5.10.19_1 x86_64 AuthenticAMD uptodate rrmFF`
*output of ``xuname`` (part of xtools)*
* package: `chromium-88.0.4324.182_1`
*affected package(s) including the version*: ``xbps-query -p pkgver <pkgname>``
### Expected behavior
A package downloaded from outside of the nonfree repository should not contain/download non-free components
### Actual behavior
Chromium downloads the Widevine component and uses it, which is not really transparent to the user.
### Steps to reproduce the behavior
- `xbps-install chromium`
- `chromium`
- open `chrome://components` and force an update of Widevide CDM, or just wait until it gets triggered itself
- try playing a Widevine-protected video, like here: https://bitmovin.com/demos/drm
prev parent reply other threads:[~2022-05-22 2:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 18:05 [ISSUE] " selfisekai
2021-03-06 18:44 ` ericonr
2021-03-06 22:09 ` selfisekai
2021-03-06 22:19 ` q66
2021-03-06 22:19 ` q66
2021-03-06 23:42 ` ptrcnull
2021-03-06 23:43 ` ptrcnull
2021-03-06 23:52 ` ptrcnull
2021-03-07 1:30 ` q66
2021-03-07 1:40 ` ericonr
2021-03-07 1:40 ` ericonr
2021-03-07 2:11 ` q66
2021-03-07 2:27 ` ericonr
2021-03-07 2:32 ` q66
2022-05-07 2:06 ` github-actions
2022-05-22 2:10 ` github-actions [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220522021006.ysttjVtOF5SbgdlWD96mO8fneCI1u1UG8UmJvhtB5aQ@z \
--to=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).