GNU bug report logs -
#34605
ungoogled-chromium: proprietary codecs enabled?
Previous Next
Reported by: Giovanni Biscuolo <g <at> xelera.eu>
Date: Thu, 21 Feb 2019 08:04:01 UTC
Severity: normal
Done: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Sat, 13 Nov 2021 20:29:48 -0500
with message-id <877ddbikxf.fsf <at> gmail.com>
and subject line Re: bug#34605: ungoogled-chromium: proprietary codecs enabled?
has caused the debbugs.gnu.org bug report #34605,
regarding ungoogled-chromium: proprietary codecs enabled?
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
34605: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=34605
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
[Message part 3 (text/plain, inline)]
Hello,
I'm forwarding this, extracted from this message
http://lists.nongnu.org/archive/html/gnu-linux-libre/2019-02/msg00083.html
Luke <g4jc <at> hyperbola.info> writes:
[...]
> Some GN prefs missing from chromium.scm:
> ---
> ;; Disable non-free codecs
> "proprietary_codecs=false"
while ungoogled-chromiun package definition now contains
--8<---------------cut here---------------start------------->8---
;; Don't arbitrarily restrict formats supported by system ffmpeg.
"proprietary_codecs=true"
"ffmpeg_branding=\"Chrome\""
--8<---------------cut here---------------end--------------->8---
does this conflicts with GNU FSDG?
Thanks!
Giovanni
--
Giovanni Biscuolo
Xelera IT Infrastructures
[signature.asc (application/pgp-signature, inline)]
[Message part 5 (message/rfc822, inline)]
Hello,
Ricardo Wurmus <rekado <at> elephly.net> writes:
> Giovanni Biscuolo <g <at> xelera.eu> writes:
>
>> Hello,
>>
>> I'm forwarding this, extracted from this message
>> http://lists.nongnu.org/archive/html/gnu-linux-libre/2019-02/msg00083.html
>>
>> Luke <g4jc <at> hyperbola.info> writes:
>>
>> [...]
>>
>>> Some GN prefs missing from chromium.scm:
>>> ---
>>> ;; Disable non-free codecs
>>> "proprietary_codecs=false"
>>
>> while ungoogled-chromiun package definition now contains
>>
>> --8<---------------cut here---------------start------------->8---
>> ;; Don't arbitrarily restrict formats supported by system ffmpeg.
>> "proprietary_codecs=true"
>> "ffmpeg_branding=\"Chrome\""
>> --8<---------------cut here---------------end--------------->8---
>>
>> does this conflicts with GNU FSDG?
>
> As far as I understand, this lets Chromium use whatever codecs are
> provided by the system ffmpeg. Restrictions in codecs are up to the
> ffmpeg package, not Chromium.
I confirm this is how it works; and that it isn't an FSDG problem. The
source now mentions ";; Do not artifically restrict formats supported by
system ffmpeg.".
Closing.
Thanks for the report!
Maxim
This bug report was last modified 3 years and 268 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.