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.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 34605 in the body.
You can then email your comments to 34605 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#34605
; Package
guix
.
(Thu, 21 Feb 2019 08:04:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Giovanni Biscuolo <g <at> xelera.eu>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Thu, 21 Feb 2019 08:04:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (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)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#34605
; Package
guix
.
(Thu, 21 Feb 2019 15:52:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 34605 <at> debbugs.gnu.org (full text, mbox):
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.
--
Ricardo
Reply sent
to
Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
:
You have taken responsibility.
(Sun, 14 Nov 2021 01:30:03 GMT)
Full text and
rfc822 format available.
Notification sent
to
Giovanni Biscuolo <g <at> xelera.eu>
:
bug acknowledged by developer.
(Sun, 14 Nov 2021 01:30:03 GMT)
Full text and
rfc822 format available.
Message #13 received at 34605-done <at> debbugs.gnu.org (full text, mbox):
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
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sun, 12 Dec 2021 12:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 2 years and 97 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.