Mageia forum

Because I need up-to-date flash and of course Adobe is f_cking the Linux community as a whole on that front. But there are dependencies that can't be satisfied from repo, like "lsb" > 4 (installed, and presumably available is v.2 see my post elsewhere to understand why I use the term "presumably"). Is it safe to go to an upstream (Mandriva or whoever) repo, and get from there, or do I have to go sourceforge and compile it myself. I hate compiling stuff myself.

Please see the MAQeia for Chrome/Chromium: viewtopic.php?f=36&t=2053

I have the same problem, every google-chrome-* package install fails with "(due to unsatisfied lsb[>=4.0]). And it seems that only lsb 2 is available in the repos.
And before everyone links me to the FAQ again, I don't see anything there that would help. I added the repo accoring to the commands there and imported the GPG key. And I don't want to use chromium since the available version is almost half a year old.

How exactly did you try to install chrome, please show the command which you used together with the resulting error message.
FWIW, i've installed Chrome-stable just fine, like it is mentioned in that MAQeia (which i've written, by the way) and receiving updates ever since:

Code: Select all

[doktor5000@Mageia2 ~]$ rpm -qa | grep google-chrome
google-chrome-stable-22.0.1229.94-161065

For your problem with LSB:

doktor5000@Mageia2 ~]$ urpmq --whatprovides lsb
lsb-lib64
[doktor5000@Mageia2 ~]$ urpmf -f -m --name lsb-lib64
Core Release:lsb-lib64-4.1-11.mga2.x86_64
[doktor5000@Mageia2 ~]$ rpm -q --provides lsb-lib64
lsb-amd64 = 4.1
lsb-amd64 = 2.0
lsb-amd64 = 3.0
lsb-amd64 = 3.1
lsb-amd64 = 3.2
lsb-amd64 = 4.0
lsbcxx-amd64 = 3.1
lsb-graphics-amd64 = 3.1
lsbcxx-amd64 = 3.2
lsb-graphics-amd64 = 3.2
lsb-cxx
lsb-graphics
lsb-desktop
lsb-desktop-qt4
lsb = 4.1
lsb-lib64 = 4.1-11.mga2
lsb-lib64(x86-64) = 4.1-11.mga2

Just caught the disclaimer in your sig.

Okay, now that I've sucessfully gotten my repos configured (which required some very careful reading of the wiki help, the illos were a tad midleading) and applied the 350 updates that have accrued since the iso was generated, I might actually have a chance; heretofore I was limited to only what the base install provided.

Bear with me, I'm accustomed to Debian-based distros, Synaptic, and apt-get. These urpm* commands you're casually slinging around are foreign territory for me, k? FWIW, I'm in an i586 architecture, not *64, so my command line results looked like this:

Code: Select all

[me@localhost ~]$ urpmq --whatprovides lsb
lsb-lib
[me@localhost ~]$ urpmf -f -m --name lsb-lib
Core Release (distrib1):lsb-lib-4.1-11.mga2.i586
[me@localhost ~]$

Invoking the gui Software Manager (I'm lazy, I do things via gui as much as possible), I do find that I can now access lsb4.1 (11.mga2). So that hurdle is cleared. After installing same, I'll retry google-chrome-stable_i386.rpm and see what happens. Much was apparently hung up on the logjam of setting up the initial repos.

Update: with rest of system packages up to date, Chrome installed by simply double-clicking said rpm icon in my directory. Simple enough for even me