Issue metadata
Sign in to add a comment
|
The stable package disappeared recently from the Google Chrome Yum repository
Reported by
evan.int...@gmail.com,
May 1 2018
|
||||||||||||||||||||||
Issue description
Chrome Version : stable
OS Version: RPM-Based Linux Distributions
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari: N/A
Firefox: N/A
IE/Edge: N/A
What steps will reproduce the problem?
1. Attempt to install the `google-chrome-stable` package from the Yum repository hosted at http://dl.google.com/linux/chrome/rpm/stable/x86_64/
What is the expected result?
The stable version of Google Chrome gets installed.
What happens instead of that?
It doesn't get installed because it's not in the repository right now.
Please provide any additional information below. Attach a screenshot if
possible.
The Google Chrome Yum repository hosted at http://dl.google.com/linux/chrome/rpm/stable/x86_64/ has always had stable, beta, and unstable Chrome packages available in the past. The stable package suddenly disappeared within the last week or two, and this has caused issues for users who rely on this repository to install Chrome on CentOS, RHEL, and other Linux variants. Would it be possible to get the repository updated to include the stable package again?
You can verify that only the beta and unstable packages are available by running the following command.
curl http://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/filelists.xml.gz | zless
I've also attached a `filelists.xml` file that includes the current contents. It has the metadata for the unstable and beta packages, but not for the stable one.
,
May 1 2018
This is a serious regression. Doesn't this mean that all RPM-based distro users are without automatic updates on the stable channel?
,
May 1 2018
Issue 837976 has been merged into this issue.
,
May 1 2018
+release team. Were there any process changes recently? Perhaps related to the new chrome website launch?
,
May 1 2018
+ waffles
,
May 1 2018
Investigating
,
May 1 2018
mmoss, we're missing RPMs in /chrome-signed/desktop-5c0tCh/66.0.3359.139/linux64, any ideas? (Also, I need to make missing RPMs a fatal error in the release framework.)
,
May 1 2018
It looks like they just failed to copy after signing, and nobody noticed :(. They're being copied again now.
,
May 1 2018
Once copied the system should automatically pick them up and publish them, I'll keep an eye out and update this bug again when they publish. Filed a server-side bug to prevent this from recurring.
,
May 1 2018
Yeah, we need to make sure all signed binaries are available before release goes out. Thank you.
,
May 1 2018
The package is now published, this is fixed.
,
May 7 2018
This issue is also affecting the .deb releases as well. Do I need to open a separate issue for that?
,
May 7 2018
Yes, if you don't mind please open another bug with repro steps.
,
May 7 2018
False positive. Nevermind, thanks. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by savethed...@gmail.com
, May 1 2018