chromium-packagers

Hello, Currently, it's not possible for non-Chrome browsers to get access to the Optimization

There's a related bug for that issue [1]. Can you verify if the patch [2] fixes the issue? [1]

luci-notify detected a status change for builder "infra/cron/publish_tarball" at 2022-08-31

On 08-07-2022 21:50, Andres Salomon wrote: > Arch seems to have updated to 114 with their git

I see the other email thread about building cast_shell is also from you. I hope my reply on that

Just set `kNumberOfChromeInternalsPathURLs` to 0? On Fri, May 27, 2022 at 4:50 PM Pandey <

Hi Lei, filed it as https://crbug.com/1314342 (I was a bit hesitant to file it on crbug due to the

+list again I guess that explains it :-) Please file a bug so that it's easier to track; I'm

Well this is interesting. https://ci.chromium.org/ui/p/infra/builders/cron/publish_tarball_dispatcher

On Fri, 2021-10-29 at 07:19 +0200, Robert Nagy wrote: > Hi > > The extended channel tarballs

This was announced a while ago in chromium-dev, but it's also relevant to this list: https://

Thanks, Tom. I ended up doing something different in https://chromium-review.googlesource.com/c/

On another issue, we found base::debug::DumpWithoutCrashing() gave us the feedback we needed without

All these published and released 32-bit builds of Chromium 90.0.4430.xxx crash unless run with the

Dear all (especially chrome devs) 1. What are the limits of sync API? I cannot find anything at https

In general, when a downstream distribution wants something that the upstream project would prefer not

Hi Matt Unfortunately the saga continues - now with the next unimplemented syscall (0383): ../../

It's an internal name and means "login scoped token" and gives you broad access to the

(replying again to the group): Sorry about that. I agree that the commits shouldn't have just

Official Chrome and Chromium builds fetched by bisect-builds.py are unaffected. Could this be an

On Fri, Feb 5, 2021 at 9:27 PM Raphael Kubo Da Costa <raphael.kubo.da.costa@intel.com> wrote:

This restriction is actually an extension of the decision that was made a couple of years ago on

Thanks Raphael! On Wed, Oct 7, 2020 at 2:01 PM Raphael Kubo Da Costa <raphael.kubo.da.costa@intel.

Thanks for the info. 86.0.4240.72 is available now and some of canary tarballs. Hopefully 86.0.

If you're building GN from scratch, you are likely picking up https://gn.googlesource.com/gn/+/

For the record, geolocation started working again on July 29th. I am not optimistic it won't

For the record, I think https://bugs.chromium.org/p/chromium/issues/detail?id=941669 is also relevant

I managed to compile a Chromium 81 package on Slackware 14.2 using the Debian sysroot. There were

That worked like a charm! Thanks for the suggestion. I still have changes to do since we have our own

I had a local patch that was messing things up. The --use-custom-libcxx flag works fine. On 3/16/20