New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 652834 link

Starred by 7 users
Status: Verified
Owner:
waff...@chromium.org
Closed: Oct 2016
Cc:
waff...@chromium.org
mmoss@chromium.org
█ ananthak@chromium.org
█ dimu@chromium.org
█ songbj@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 0
Type: Bug



Sign in to add a comment

Broken chrome stable download URL in official debian repository

Project Member Reported by pwnall@chromium.org, Oct 4 2016 
<b>Version: <Kenneth, what is the frequency?></b>
OS: Linux, Debian/Ubuntu

What steps will reproduce the problem?
(1) Read the repository manifest: curl http://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages
(2) Try to download the unstable build:  wget http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-unstable/google-chrome-unstable_54.0.2837.0-1_amd64.deb
(3) Try to download the stable build: wget http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_52.0.2743.116-1_amd64.deb

What is the expected output?
All steps should succeed.

What do you see instead?
The stable download (step 3) fails.


Please use labels and text to provide additional information.
The repository metadata is most likely pointing to the wrong file.

This is breaking CI tests that rely on being able to download/upgrade Chrome.

The developer who told me about this issue pointed me to the report here: https://productforums.google.com/forum/#!topic/chrome/xJi6KD8qWOs;context-place=forum/chrome

Comment 1 by jacob.sc...@gmail.com, Oct 4 2016 

I'm the original reporter from productforums -- happy to help test a fix or etc if that would help.

Thanks much!

Comment 2 by aga...@chromium.org, Oct 4 2016

Cc: ananthak@chromium.org mmoss@chromium.org
+anatha +mmoss, who understand the release process.

Comment 3 by aga...@chromium.org, Oct 4 2016

Status: Available (was: Untriaged)

Comment 4 by pwnall@chromium.org, Oct 4 2016 

I filed an internal bug at http://b/31940456 before I saw the last few comments.

Comment 5 by mmoss@chromium.org, Oct 4 2016

Cc: waff...@chromium.org dimu@chromium.org
52.0.2743.116?!?! Stable should be 53.xxx.

Comment 6 by mmoss@chromium.org, Oct 4 2016 

Something seems very, very wrong here. Looking at https://omahaproxy.appspot.com/, all the Linux channels got rolled by one major version somehow.

Comment 7 by mmoss@chromium.org, Oct 4 2016

Cc: songbj@chromium.org
+songbj

Comment 8 by waff...@chromium.org, Oct 4 2016

Owner: waff...@chromium.org
Status: Started (was: Available)

Comment 9 by waff...@chromium.org, Oct 4 2016

Status: Fixed (was: Started)
This was caused by something going wrong with an internal cleanup tool that is intended to remove old versions of the linux packages; I believe we've successfully restored the repo to a working condition. Investigation is ongoing into what went wrong and follow-up will take place on the internal bug as it may contain details about our serving infrastructure (sorry to the external folks).

omahaproxy may take some time to catch up.

Please re-open if it's still not working for you.

Comment 10 by jacob.sc...@gmail.com, Oct 5 2016 

This is now working for me!

Comment 11 by pwnall@chromium.org, Oct 5 2016

Status: Verified (was: Fixed)
@waffles: Thank you very much for the quick turnaround on this issue!
►

Sign in to add a comment