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 Chromium, but with many lint errors and many missing patches.
BTW, have you tried opening a bug upstream or submitting your ozone patch upstream? Michel Le Bihan On Wed, 9 Dec 2020 04:34:39 +0000 Jeff Blake <jeffbla...@gmail.com> wrote: > On Tue, 08 Dec 2020 12:33:57 +0100 Michel Le Bihan <mic...@lebihan.pl> wrote: > > Hello, > > > > I started work on updating the chromium package (you can see my work > > here: > > https://salsa.debian.org/mimi89999/chromium/-/commit/af70b14701aaf6bdb34e23af01657676e27ba5d4 > > ), but got stuck because `libvpx` is too old in Debian testing. It > > needs to be updated before I can continue work. > > > > Michel Le Bihan > > > > > > > > I've managed to successfully update the ungoogled-chromium debian package > [1], which is based upon > the official debian package. > > Until libvpx is updated (or a new release is made) you could use Chromium's > bundled version of libvpx [2]. > > Feel free to have a look around my repo, as you might well encounter some of > the same problems that > I had in getting things to build. > > > Jeff Blake <jeffbla...@gmail.com> > > > [1] https://github.com/berkley4/ungoogled-chromium-debian/commits/87.0.4280.88 > > [2] > https://github.com/berkley4/ungoogled-chromium-debian/commit/05ffc529e685817aac8a9c5bb419daba17204a66 > > >
