Hello,
I updated the patch disabling openh264:
https://salsa.debian.org/mimi8/chromium/-/blob/master/debian/patches/disable/openh264.patch
I was able to build Chromium with proprietary codec support, but
without openh264.
Michel Le Bihan
On Mon, 14 Dec 2020 21:04:00 +0100 Michel Le Bihan
Hi,
Good work everyone, I've read the thread with interest.
One patch I would question the need for is fixes/inspector.patch.
I'm not sure if it originally fixed a bug (it's in the fixes folder) or was
desirable for some other reason, but things build fine without it.
It might be better to
Hey,
I have uploaded my stuff to
https://salsa.debian.org/janluca-guest/chromium
We can meet in IRC or Matrix. I am janluca on irc.oftc.net.
Best,
Jan
On Mon, 14 Dec 2020 13:59:53 +0100 Michel Le Bihan
wrote:
> Hello,
>
> My work is in this repo:
>
Hello,
> I suspect that debian's libvpx might need to be build with
experimental features enabled (similar to a previous bug report), in
order to include the absent header files.
This will build the lib, but the header isn't correctly exported. They
don't export the header file for that and the
Hello,
My work is in this repo:
https://salsa.debian.org/mimi8/chromium/-/tree/master
I'm updating the commit every time I make a change. Making a new commit
for each file doesn't really make sense, since those are separate files
anyway.
There is another repo from another person that also
On Sat, 12 Dec 2020 19:47:32 +0100 Michel Le Bihan wrote:
> Hello,
>
> Thank you for your reply. libvpx got updated in Debian, but I can't use
> it because it's missing a lib. I also had issues with harfbuzz, so I'm
> using bundled versions of those libs as you are. I also used your ozone
>
Hallo everybody,
I have done some of the work as well since I have not seen your message
about your efforts. I have uploaded a working build for unstable to
mentors including updated version of the patches:
https://mentors.debian.net/package/chromium/
This version is using the vendor-shipped
Hi there,
Thank you for all of the great work on this so far!
I'm interested in helping with this effort, and very familiar with C++ code
and processes in Google code (though not specifically Chromium). I have
gotten the 83/84 versions in unstable/experimental building locally in a
container
Hello,
Thank you for your reply. libvpx got updated in Debian, but I can't use
it because it's missing a lib. I also had issues with harfbuzz, so I'm
using bundled versions of those libs as you are. I also used your ozone
patch because it is match cleaner than mine. With that I was able to
build
On Tue, 08 Dec 2020 12:33:57 +0100 Michel Le Bihan wrote:
> Hello,
>
> I started work on updating the chromium package (you can see my work
> here:
> https://salsa.debian.org/mimi8/chromium/-/commit/af70b14701aaf6bdb34e23af01657676e27ba5d4
> ), but got stuck because `libvpx` is too old in
Hello,
I started work on updating the chromium package (you can see my work
here:
https://salsa.debian.org/mimi8/chromium/-/commit/af70b14701aaf6bdb34e23af01657676e27ba5d4
), but got stuck because `libvpx` is too old in Debian testing. It
needs to be updated before I can continue work.
Package: chromium
Version: 83.0.4103.116-3.1
Severity: important
Dear Maintainer,
Version 83.x of chromium became unsupported in July, with the release of
Chrome 84. Since that time, two more versions of chromium have been
released, 85.x and 86.x, each with 40-50 security bugs fixed. This has
me
12 matches
Mail list logo
