Bug 13823

Summary:	chrome_i386 media cannot be added on an ASUS EEE-PC with i586-version of Mageia
Product:	Mageia	Reporter:	Kristoffer Grundström <lovaren>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	minor
Priority:	Normal	CC:	ftg, jani.valimaa, lovaren
Version:	4
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	google-chrome-stable-current	CVE:
Status comment:
Attachments:	Here's the information about this netbook Here's proof that the signing key has been installed

Description Kristoffer Grundström 2014-07-30 12:07:13 CEST

Description of problem: I found the thread on the Mageia forum on how to add Google medias and after I've successfully imported the signing key with rpm --import linux_signing_key.pub I did urpmi.addmedia --update google-chrome http://dl.google.com/linux/chrome/rpm/stable/$(uname -m | sed -e "s/i.86/i386/") as root as well, this resulted in this error:

[root@localhost ~]# urpmi.addmedia --update chrome_i386 http://dl.google.com/linux/chrome/rpm/stable/i386
adding medium "chrome_i386"
    http://dl.google.com/linux/chrome/rpm/stable/i386/media_info/synthesis.hdlist.cz
retrieval of [http://dl.google.com/linux/chrome/rpm/stable/i386/media_info/synthesis.hdlist.cz] failed (md5sum mismatch)
problem reading synthesis file of medium "chrome_i386"

I know that I don't have any connection problem since pinging google.com works fine.

3.12.21-desktop-2.mga4 is the current kernel being used. 

Fetching the RPM from the Google Chrome-page works perfectly fine and it installs as well.

Version-Release number of selected component (if applicable): 36.0.1985.125

How reproducible: Everytime.


Steps to Reproduce:
1. Install the 32-bit version of Mageia with GNOME on an ASUS EEE-PC.
2. Only use Stable medias (Core and Updates).
3. Make sure you're fully updated.
4. Do wget https://dl-ssl.google.com/linux/linux_signing_key.pub && sudo rpm --import linux_signing_key.pub
5. Now do urpmi.addmedia --update chrome_i386 http://dl.google.com/linux/chrome/rpm/stable/i386
6. Voila! Same error as I had should appear.

Reproducible: 

Steps to Reproduce:

Comment 1 Kristoffer Grundström 2014-07-30 12:08:07 CEST

Created attachment 5319 [details]
Here's the information about this netbook

CC: (none) => kristoffer.grundstrom1983

Comment 2 Kristoffer Grundström 2014-07-30 12:11:56 CEST

Created attachment 5320 [details]
Here's proof that the signing key has been installed

Comment 3 Jani Välimaa 2014-07-31 09:37:09 CEST

Can't reproduce, please test again.

Notice also that you should report this to Google and not to us. We can't do much if Google repos are broken.

Status: NEW => RESOLVED
CC: (none) => jani.valimaa
Resolution: (none) => WORKSFORME

Comment 4 Frank Griffin 2014-07-31 12:23:38 CEST

Is the destination you're using actually an MGA repository, i. e. it has hdlist and all that other good stuff ?  Or is it just the URL of the remote RPM ?

CC: (none) => ftg

Comment 5 Kristoffer Grundström 2014-07-31 17:40:06 CEST

But it works to download the RPM from their Chrome-page so the Repo isn't broken. What else could be causing this? The connection works fine.

Comment 6 Frank Griffin 2014-07-31 17:49:07 CEST

(In reply to Frank Griffin from comment #4)
> Is the destination you're using actually an MGA repository, i. e. it has
> hdlist and all that other good stuff ?  Or is it just the URL of the remote
> RPM ?

Answering myself, it is, and the urpmi.addmedia works fine for me, but I'm using cauldron.