Chromium 70.0.3538.102 source is unavailable - and please clean up the SPAM

[Eric Hameleers]

Hi

Please check the generation process of the Chromium sources. It's now more than 24 hours after announcing 70.0.3538.102 and the sources are still not available for download.

Second question: please do something about the SPAM.

Thanks, Eric

[Michael Moss]

This is probably due to network maintenance, which has been going on for the past day or so (see message on https://ci.chromium.org/p/chromium/g/main/console), and which probably has the tarball builder offline.

[Olivier Tilloy]

On Sun, Nov 11, 2018 at 11:59 AM Eric Hameleers <al...@slackware.com> wrote:
>
> Hi
>
> Please check the generation process of the Chromium sources. It's now more than 24 hours after announcing 70.0.3538.102 and the sources are still not available for download.

All publish_tarball builds
(https://ci.chromium.org/buildbot/chromium.infra.cron/publish_tarball/)
are failing with the same error: "gen.py: error: no such option:
--no-sysroot".

This commit is likely the cause:
https://gn.googlesource.com/gn/+/df15af47303ffafad009f865bc80679b453eef1b%5E%21/#F0

The publish_tarball script needs to be updated accordingly.

[Kubo Da Costa, Raphael]

Argh. I've filed http://crbug.com/904350 to track this. It should've
been caught earlier, but email notifications for tree breakages have
been broken for a while (see bug 884710).

[Paweł Hajdan, Jr.]

Thanks for the reports.

I added bugs mentioned here to the Chromium-Packagers hotlist (more info).

Also removed the recent spam and banned senders.

Please let me know if you'd like to get added to Chromium-Packagers hotlist editors (context), so you can add bugs there yourself. I hope eventually this will help increase their visibility.

Similarly, help is welcome with list moderation.

Paweł

--
You received this message because you are subscribed to the Google Groups "chromium-packagers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-packag...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-packagers/93c0293784ba7a8da9283d9793418e2fd7de8f84.camel%40intel.com.

[Lei Zhang]

I can help with list moderation, and I would suggest setting the group
to be moderate on first post only. That will stop some of the spam,
though I have seen some spammers try to bypass that with an almost
human sounding first post.

> To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-packagers/CAATLsPaWzoqjFd8YW7y7eUze%3D6ex_L%3Dbieh2f072aVvwpkCO9g%40mail.gmail.com.

[Raphael Kubo da Costa]

The bug that was preventing the creation of new tarballs has been fixed,
and I can see the bot's processing its backlog of Chromium releases.

There's one catch for packagers though: --no-sysroot option
was removed from GN's gen.py, and until a commit I landed yesterday
Chromium's bootstrap.py always invoked gen.py with --no-sysroot unless
it was invoked with --with-sysroot.

This means that, for Chromium releases made since that GN commit Olivier
mentioned above and prior to 72.0.3610.0 (the first release to include
my commit from https://chromium-review.googlesource.com/c/1333391), one
must invoke bootstrap.py with --with-sysroot to actually avoid using a
sysroot. This includes all new M70 and M71 releases, unless the Chromium
folks doing release engineering deem that CL acceptable for M71.

[Olivier Tilloy]

Thanks Raphael for the prompt fix!

I included your commit as a distro-patch in the ubuntu packages
(https://bazaar.launchpad.net/~chromium-team/chromium-browser/cosmic-dev/revision/1475#debian/patches/gn-bootstrap-remove-sysroot-options.patch).

Cheers,

Olivier

[Lei Zhang]

I deleted some more spam and changed the group policy to moderate on
first post. Please let me know if there are any issues.