Quoting Andres Salomon (2022-02-14 08:55:22)
> I've finally give up and am just using ALL the bundled node packages:
> https://salsa.debian.org/chromium-team/chromium/-/commit/a418d219f0217d6398a01c30035d35c42f7a76f1
>
> It's not ideal, but at least with this we'll match all of the node
> stuff
On 2/14/22 02:27, Pirate Praveen wrote:
2022, ഫെബ്രുവരി 13 9:36:11 PM IST, Roger Shimizu ൽ എഴുതി
On Sat, Feb 12, 2022 at 2:12 AM Andres Salomon wrote:
Yes, that's the error. "String.matchAll is only available from Node.js
12.0 onwards", according to
https://stackoverflow.com/questions/585582
2022, ഫെബ്രുവരി 13 9:36:11 PM IST, Roger Shimizu ൽ എഴുതി
>On Sat, Feb 12, 2022 at 2:12 AM Andres Salomon wrote:
>> Yes, that's the error. "String.matchAll is only available from Node.js
>> 12.0 onwards", according to
>> https://stackoverflow.com/questions/58558257/string-matchall-is-undefined
>
On Sat, Feb 12, 2022 at 2:12 AM Andres Salomon wrote:
>
> On 2/11/22 06:18, Roger Shimizu wrote:
>
> > Dear Andres,
> >
> > Thanks for your work for chromium!
> >
> > On Mon, Jan 3, 2022 at 7:33 PM Andres Salomon wrote:
> I saw
> https://salsa.debian.org/dilinger/chromium/-/commit/5c05f
On 2/11/22 06:18, Roger Shimizu wrote:
Dear Andres,
Thanks for your work for chromium!
On Mon, Jan 3, 2022 at 7:33 PM Andres Salomon wrote:
I saw
https://salsa.debian.org/dilinger/chromium/-/commit/5c05f430e192961527ec9a64bbaa64401dc14d95
, but buster now also includes LLVM/clang 11 (it was
Dear Andres,
Thanks for your work for chromium!
On Mon, Jan 3, 2022 at 7:33 PM Andres Salomon wrote:
> > > I saw
> > > https://salsa.debian.org/dilinger/chromium/-/commit/5c05f430e192961527ec9a64bbaa64401dc14d95
> > > , but buster now also includes LLVM/clang 11 (it was introduced to
> > > suppo
On Mon, Jan 10, 2022 at 02:21:48PM -0500, Andres Salomon wrote:
> On 1/10/22 05:01, Mattia Rizzolo wrote:
> > On Sun, Jan 09, 2022 at 11:23:20PM -0500, Andres Salomon wrote:
> > > Btw, https://salsa.debian.org/dilinger/chromium/-/tree/stable is my branch
> > > with cleaned-up commits. That's what I
On 1/10/22 05:01, Mattia Rizzolo wrote:
On Sun, Jan 09, 2022 at 11:23:20PM -0500, Andres Salomon wrote:
Btw, https://salsa.debian.org/dilinger/chromium/-/tree/stable is my branch
with cleaned-up commits. That's what I'll use for the NMU, which I'm
preparing now.
If you all agree, you could fi
On Sun, Jan 09, 2022 at 11:23:20PM -0500, Andres Salomon wrote:
> Btw, https://salsa.debian.org/dilinger/chromium/-/tree/stable is my branch
> with cleaned-up commits. That's what I'll use for the NMU, which I'm
> preparing now.
If you all agree, you could finalize the tree, then I'll build again,
On Sun, Jan 09, 2022 at 12:56:28AM -0500, Andres Salomon wrote:
>
> On 1/8/22 15:57, Mattia Rizzolo wrote:
> > On Thu, Jan 06, 2022 at 02:55:20AM -0500, Andres Salomon wrote:
> > > If you want to try with chromium 97; it now builds as an official build,
> > > so
> > > those DCHECKs shouldn't even
On 1/9/22 19:06, Andres Salomon wrote:
On 1/9/22 02:27, Andres Salomon wrote:
On 1/9/22 00:56, Andres Salomon wrote:
On 1/8/22 15:57, Mattia Rizzolo wrote:
On Thu, Jan 06, 2022 at 02:55:20AM -0500, Andres Salomon wrote:
If you want to try with chromium 97; it now builds as an official
bui
On 1/9/22 02:27, Andres Salomon wrote:
On 1/9/22 00:56, Andres Salomon wrote:
On 1/8/22 15:57, Mattia Rizzolo wrote:
On Thu, Jan 06, 2022 at 02:55:20AM -0500, Andres Salomon wrote:
If you want to try with chromium 97; it now builds as an official
build, so
those DCHECKs shouldn't even be c
On 1/9/22 00:56, Andres Salomon wrote:
On 1/8/22 15:57, Mattia Rizzolo wrote:
On Thu, Jan 06, 2022 at 02:55:20AM -0500, Andres Salomon wrote:
If you want to try with chromium 97; it now builds as an official
build, so
those DCHECKs shouldn't even be compiled in. It also supports wayland
autom
On 1/8/22 15:57, Mattia Rizzolo wrote:
On Thu, Jan 06, 2022 at 02:55:20AM -0500, Andres Salomon wrote:
If you want to try with chromium 97; it now builds as an official build, so
those DCHECKs shouldn't even be compiled in. It also supports wayland
automatically, in case that's related to your
On Thu, Jan 06, 2022 at 02:55:20AM -0500, Andres Salomon wrote:
> If you want to try with chromium 97; it now builds as an official build, so
> those DCHECKs shouldn't even be compiled in. It also supports wayland
> automatically, in case that's related to your slowdowns.
>
> https://salsa.debian.
On Thu, Jan 06, 2022 at 02:55:20AM -0500, Andres Salomon wrote:
> If you want to try with chromium 97; it now builds as an official build, so
> those DCHECKs shouldn't even be compiled in. It also supports wayland
> automatically, in case that's related to your slowdowns.
>
> https://salsa.debian.
On 1/5/22 13:14, Mattia Rizzolo wrote:
On Wed, Jan 05, 2022 at 01:52:33PM +0100, Mattia Rizzolo wrote:
I suppose I'll see how it goes in the coming few days.
So it's not crashing but it's being unbearably slow in gmail, to the
point that I just wasn't able to type a mail there, while throwing o
On 1/5/22 13:14, Mattia Rizzolo wrote:
On Wed, Jan 05, 2022 at 01:52:33PM +0100, Mattia Rizzolo wrote:
I suppose I'll see how it goes in the coming few days.
So it's not crashing but it's being unbearably slow in gmail, to the
point that I just wasn't able to type a mail there, while throwing o
On Wed, Jan 05, 2022 at 01:52:33PM +0100, Mattia Rizzolo wrote:
> I suppose I'll see how it goes in the coming few days.
So it's not crashing but it's being unbearably slow in gmail, to the
point that I just wasn't able to type a mail there, while throwing one
CPU core to 100%.
Also it was kind go
On Tue, Jan 04, 2022 at 06:46:46PM -0500, Andres Salomon wrote:
> On 1/4/22 15:15, Mattia Rizzolo wrote:
> > On Tue, Jan 04, 2022 at 02:50:20PM -0500, Andres Salomon wrote:
> > > I pushed a commit to the skip-a11y-checks branch, please give that a try.
> > > I
> > > need to take a look at other di
On 1/4/22 15:15, Mattia Rizzolo wrote:
On Tue, Jan 04, 2022 at 02:50:20PM -0500, Andres Salomon wrote:
Okay, that's funny - appears to be a fatal error due to being run under gdb.
Well, it was also crashing outside of gdb ^^
I pushed a commit to the skip-a11y-checks branch, please give that
On Tue, Jan 04, 2022 at 02:50:20PM -0500, Andres Salomon wrote:
> Okay, that's funny - appears to be a fatal error due to being run under gdb.
Well, it was also crashing outside of gdb ^^
> I pushed a commit to the skip-a11y-checks branch, please give that a try. I
> need to take a look at other
On 1/4/22 11:46, Mattia Rizzolo wrote:
[...]
[413:413:0104/174404.300230:FATAL:render_process_host_impl.cc(4227)] Check
failed: host->GetBrowserContext() == browser_context (0x645f47d0 vs.
0x658dcb30) Single-process mode does not support multiple browser contexts.
Okay, that's
On Mon, Jan 03, 2022 at 01:47:15PM -0500, Andres Salomon wrote:
> Thanks for testing! Are you doing this under sid?
yes!
> Hm, that's a new one.
>
> Looks like upstream turned those assert crashes into debug statements in
> newer releases. Please try to following patch:
>
> https://chromium.goo
Thanks for testing! Are you doing this under sid?
On 1/3/22 7:39 AM, Mattia Rizzolo wrote:
On Sun, Jan 02, 2022 at 06:53:52PM +0100, Mattia Rizzolo wrote:
the v96 branch of https://salsa.debian.org/dilinger/chromium
FWIW, I'm trying to build it myself as well
Here it started chrashing as soo
On Mon, Jan 03, 2022 at 01:39:21PM +0100, Mattia Rizzolo wrote:
> On Sun, Jan 02, 2022 at 06:53:52PM +0100, Mattia Rizzolo wrote:
> > > > the v96 branch of https://salsa.debian.org/dilinger/chromium
> >
> > FWIW, I'm trying to build it myself as well
>
> Here it started chrashing as soon as I tri
On Sun, Jan 02, 2022 at 06:53:52PM +0100, Mattia Rizzolo wrote:
> > > the v96 branch of https://salsa.debian.org/dilinger/chromium
>
> FWIW, I'm trying to build it myself as well
Here it started chrashing as soon as I tried to open a new tab, and
after that it refuses to load my main profile (but
On Sun, 2 Jan 2022 15:32:28 -0500
Andres Salomon wrote:
> On Sun, 2 Jan 2022 20:15:01 +0100
> Moritz Muehlenhoff wrote:
>
> > On Sat, Jan 01, 2022 at 01:23:09PM -0500, Andres Salomon wrote:
> > > How should I handle this? NMU to sid, let people try it out, and
> > > then deal with buster/bull
On Sun, 2 Jan 2022 20:15:01 +0100
Moritz Muehlenhoff wrote:
> On Sat, Jan 01, 2022 at 01:23:09PM -0500, Andres Salomon wrote:
> > How should I handle this? NMU to sid, let people try it out, and
> > then deal with buster/bullseye?
>
> Yeah, let's proceed with unstable first in any case.
>
> >
On Sat, Jan 01, 2022 at 01:23:09PM -0500, Andres Salomon wrote:
> How should I handle this? NMU to sid, let people try it out, and then
> deal with buster/bullseye?
Yeah, let's proceed with unstable first in any case.
> Upload everything all at once? I'm also
> going to try building for buster, u
On 1/2/22 12:53 PM, Mattia Rizzolo wrote:
On Sat, Jan 01, 2022 at 01:23:09PM -0500, Andres Salomon wrote:
I've got 96.0.4664.110 building on both bullseye and sid
Trying it, I see it still build-depends on python-jinja2. That package
is now gone, so it's not actually buildable in sid anymore
On Sun, Jan 02, 2022 at 06:53:51PM +0100, Mattia Rizzolo wrote:
> Correlated, do you know how long do they plan on keeping using python2?
> That's plainly unsuitable, it really is not going to last much longer in
> debian.
Current state of the Python 3 upstream migration can be found here:
https:/
On Sat, Jan 01, 2022 at 01:23:09PM -0500, Andres Salomon wrote:
> > I've got 96.0.4664.110 building on both bullseye and sid
Trying it, I see it still build-depends on python-jinja2. That package
is now gone, so it's not actually buildable in sid anymore.
Correlated, do you know how long do they
On Thu, 23 Dec 2021 01:49:53 -0500
Andres Salomon wrote:
> On 12/13/21 5:31 PM, Moritz Muehlenhoff wrote:
> > On Sun, Dec 12, 2021 at 08:11:00PM -0500, Andres Salomon wrote:
> >> On 12/5/21 6:41 AM, Moritz Mühlenhoff wrote:
> >>> Am Sun, Dec 05, 2021 at 10:53:56AM +0100 schrieb Paul Gevers:
>
On 12/13/21 5:31 PM, Moritz Muehlenhoff wrote:
On Sun, Dec 12, 2021 at 08:11:00PM -0500, Andres Salomon wrote:
On 12/5/21 6:41 AM, Moritz Mühlenhoff wrote:
Am Sun, Dec 05, 2021 at 10:53:56AM +0100 schrieb Paul Gevers:
Exactly that.
I'd suggest anyone who's interested in seeing Chromium suppo
On Fri, 2021-12-17 at 11:28 +0100, Moritz Mühlenhoff wrote:
> Could anyone who's using Chromium on Debian please create a page on
> wiki.debian.org which lists the alternative options to use a current
> Chromium (Flatpak, ungoogled Chromium from elsewhere, snap, whatever
> else there is)?
The exi
Mattia Rizzolo schrieb:
>
> --FJqzFV9NFse93u4l
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
>
>> Am Sun, Dec 05, 2021 at 10:53:56AM +0100 schrieb Paul Gevers:
>> > The problem really is lack of maintenance. In my opinion,
On Sun, Dec 12, 2021 at 08:11:00PM -0500, Andres Salomon wrote:
> On 12/5/21 6:41 AM, Moritz Mühlenhoff wrote:
> > Am Sun, Dec 05, 2021 at 10:53:56AM +0100 schrieb Paul Gevers:
> > Exactly that.
> >
> > I'd suggest anyone who's interested in seeing Chromium supported to first
> > update it in unst
On 12/5/21 6:41 AM, Moritz Mühlenhoff wrote:
Am Sun, Dec 05, 2021 at 10:53:56AM +0100 schrieb Paul Gevers:
Exactly that.
I'd suggest anyone who's interested in seeing Chromium supported to first
update it in unstable (and then work towards updated in bullseye-security).
I started doing just th
On 06.12.21 20:43, Noah Meyerhans wrote:
On Sun, Dec 05, 2021 at 07:58:17PM +0300, Dmitry Alexandrov wrote:
So what's happening with chromium in both sid and stable? I saw on d-release
that it was removed from testing (#998676 and #998732), with a discussion
about ending security support for
Noah Meyerhans wrote:
> The biggest difficulty, as far as I can tell from my look at Chromium from
> several months ago, is that our patch set [1] needs a lot of attention with
> every chromium release.
And let me ask another silly question: where can we actually see a CI log for a
failed buil
Noah Meyerhans wrote:
> On Sun, Dec 05, 2021 at 07:58:17PM +0300, Dmitry Alexandrov wrote:
>> >> So what's happening with chromium in both sid and stable? I saw on
>> >> d-release that it was removed from testing (#998676 and #998732), with a
>> >> discussion about ending security support for i
On Mon, Dec 06, 2021 at 08:53:37PM +0100, Paul Gevers wrote:
> I have good experience with some of my upstreams where they supported me by
> adapting their build system to enable building without the bundled/vendored
> dependencies. Has this been tried? Would it be worth pursuing?
It has been, yes
Hi,
On 06-12-2021 20:43, Noah Meyerhans wrote:
One lesson we may take from Mint, though, is that it's not worth trying
to patch Chromium as much as we'd like. Anything that we can do to
simplify the Chromium packaging will help us keep the package
up-to-date, which in turn will help us keep our
On Sun, Dec 05, 2021 at 07:58:17PM +0300, Dmitry Alexandrov wrote:
> >> So what's happening with chromium in both sid and stable? I saw on
> >> d-release that it was removed from testing (#998676 and #998732), with a
> >> discussion about ending security support for it in stable.
> >
> > The pro
Paul Gevers wrote:
> On 05-12-2021 03:36, Andres Salomon wrote:
>> So what's happening with chromium in both sid and stable? I saw on d-release
>> that it was removed from testing (#998676 and #998732), with a discussion
>> about ending security support for it in stable.
>
> The problem really
> Am Sun, Dec 05, 2021 at 10:53:56AM +0100 schrieb Paul Gevers:
> > The problem really is lack of maintenance. In my opinion, chromium deserves
> > an active *team* to support it in Debian.
[..]
> > We'll not ship it in bookworm unless we see steady uploads
> > in unstable and we see security uploa
Am Sun, Dec 05, 2021 at 10:53:56AM +0100 schrieb Paul Gevers:
> Hi Andres,
>
> On 05-12-2021 03:36, Andres Salomon wrote:
> > So what's happening with chromium in both sid and stable? I saw on
> > d-release that it was removed from testing (#998676 and #998732), with a
> > discussion about ending
Hi Andres,
On 05-12-2021 03:36, Andres Salomon wrote:
So what's happening with chromium in both sid and stable? I saw on
d-release that it was removed from testing (#998676 and #998732), with a
discussion about ending security support for it in stable. I'm willing
to help out with chromium pac
On Sun, 24 Oct 2021 15:06:50 -0400 Andres Salomon wrote:
> Stable (bullseye) still contains chromium 90, which has had many
> security issues. Testing & unstable contain 93, and stable should really
> be quickly updated via stable-security to at least chromium 93 (as its
> already been packaged an
50 matches
Mail list logo
