YAST RPM issue: Failed to cache repo (1)

English Install/Boot/Login
1

Hello,

I am using SuSE 12.3 newly installed on a x86_64 machine. My WiFi card is not working, and I have to install a special RPM. Having problems installing it.

I downloaded rpms to install. I downloaded them into a directory /home/john/RPM . I created that directory RPM .

In YAST, I added the depository for the local directory /home/john/RPM

When I try and access RPMs in this new depository via YAST to install the new RPMs, I get the error below. Why?

An error occurred during repository initialization.
‘RPM’: |] Failed to cache repo (1).
History:

  • ‘repo2solv.sh’ ‘-o’ ‘/var/cache/zypp/solv/RPM/solv’ ‘-R’ ‘/home/john/RPM’
    rpms2solv: broadcom-wl-kmp-default-5.100.82.112_k3.7.10_1.4-11.2.x86_64.rpm: not a rpm
    rpms2solv: broadcom-wl-kmp-desktop-5.100.82.112_k3.7.10_1.4-11.2.x86_64.rpm: not a rpm
    rpms2solv: broadcom-wl-kmp-xen-5.100.82.112_k3.7.10_1.4-11.2.x86_64.rpm: not a rpm

Regards,

2

Ok. I checked the RPMs. Apparantly they are missing the GnuPG signature as described in this link

Novel Link

I ran the command rpm --checksig b* since all three files start with the letter b. It says “not rpm” for each.

I got these files off
PackMan link to the SuSE 12.3 files I need

for SuSE 12.3

So I don’t get it.

3

Maybe I do not fully understand you, but the broadcom-wl package is in the Packman repo. Add the Packman repo (if you do not have it already) and you must be able to find it in YaST > Software > Software Management with the Search function.

And when you do not have the Packman repo, use YaST > Software > Repositories, use the Add button and the Community Repos and there you should be able to find Packman.

4

On 05/12/2013 01:56 PM, hcvv pecked at the keyboard and wrote:
> Maybe I do not fully understand you, but the broadcom-wl package is in
> the Packman repo. Add the Packman repo (if you do not have it already)
> and you must be able to find it in YaST > Software > Software Management
> with the Search function.
>
> And when you do not have the Packman repo, use YaST > Software >
> Repositories, use the Add button and the Community Repos and there you
> should be able to find Packman.
>
>

This is the kind of reply people get when the person doing the reply
fails to read the entire original post.
From the original:

“I am using SuSE 12.3 newly installed on a x86_64 machine. My WiFi card
is not working, and I have to install a special RPM. Having problems
installing it.”

As you can see he is having trouble with the wifi card, hence no
internet access. :slight_smile:

5

On 2013-05-12 19:26, gz1968 wrote:
>
> Ok. I checked the RPMs. Apparantly they are missing the GnuPG signature
> as described in this link
>
> ‘Novel Link’ (2.3. RPM — the Package Manager)

Hold on. That document is for SUSE LINUX 9.1, ie, SLES, the commercial
product.

You said “I am using SuSE 12.3”, and I must tell you that such product
does not exist. There is an “openSUSE 12.3”, and there is also a “SUSE
11”, which is, I think, currently at service pack 2.

So, if you are using “openSUSE 12.3” that documentation you point to
above does not apply to you. The verification procedure is correct, but
the signature probably not.

The third one is the equivalent chapter:


> http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/
> http://doc.opensuse.org/documentation/html/openSUSE/opensuse-startup/
> http://doc.opensuse.org/documentation/html/openSUSE/opensuse-startup/cha.sw_cl.html#sec.rpm

On the other hand, if you are using SLES or SLED, the commercial
product, you are in the wrong forum (and the packman rpm is also wrong
for you). You have to go here: SLES/SLED forums - the login/pass are the same as here, no need to
register again.

And then, this thread will be closed fast.

I ran the command rpm --checksig b* since all three files start with
the letter b. It says “not rpm” for each.

I got these files off
‘PackMan link to the SuSE 12.3 files I need’
(PackMan :: Package details for broadcom-wl)

for SuSE 12.3

I’ll assume you mean openSUSE 12.3 - you have to be precise in what you
say and do with computers.

We are touchy on that name, so don’t get it wrong :wink:

Ok, I tried downloading and checking the same rpm as you did.



> cer@Telcontar:~/tmp/test> wget http://packman.links2linux.org/download/broadcom-wl/1408062/broadcom-wl-kmp-default-5.100.82.112_k3.7.10_1.4-11.2.x86_64.rpm
> asking libproxy about url 'http://packman.links2linux.org/download/broadcom-wl/1408062/broadcom-wl-kmp-default-5.100.82.112_k3.7.10_1.4-11.2.x86_64.rpm'
> libproxy suggest to use 'direct://'
....
>
> 2013-05-13 01:12:19 (97,7 KB/s) - `broadcom-wl-kmp-default-5.100.82.112_k3.7.10_1.4-11.2.x86_64.rpm' saved [647447/647447]
>
> cer@Telcontar:~/tmp/test> l
> total 640
> drwxr-sr-x  2 cer users     77 May 13 01:12 ./
> drwxr-xr-x 53 cer users   4096 Apr 30 17:22 ../
> -rw-r--r--  1 cer users 647447 May  4 11:50 broadcom-wl-kmp-default-5.100.82.112_k3.7.10_1.4-11.2.x86_64.rpm
> cer@Telcontar:~/tmp/test> file broadcom-wl-kmp-default-5.100.82.112_k3.7.10_1.4-11.2.x86_64.rpm
> broadcom-wl-kmp-default-5.100.82.112_k3.7.10_1.4-11.2.x86_64.rpm: RPM v3.0 bin i386/x86_64
> cer@Telcontar:~/tmp/test> rpm --checksig broadcom-wl-kmp-default-5.100.82.112_k3.7.10_1.4-11.2.x86_64.rpm
> broadcom-wl-kmp-default-5.100.82.112_k3.7.10_1.4-11.2.x86_64.rpm: rsa sha1 (md5) pgp md5 OK
> cer@Telcontar:~/tmp/test>

So you see, mine verifies - if you downloaded the same file and it does
not verify, your file is corrupted.

Download it again.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

6

On 2013-05-12 19:56, hcvv wrote:
>
> Maybe I do not fully understand you, but the broadcom-wl package is in
> the Packman repo. Add the Packman repo (if you do not have it already)
> and you must be able to find it in YaST > Software > Software Management
> with the Search function.

He can not: he has no network.

He needs to install some rpms so that his network works, and he has
problems with yast accepting those rpms.

–
Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

7

When you created the local repository in YaST, did you
1.Click the “Add” button on the “Configured Software Repositories” page,
2.Click the “Local directory” radio button on the next page,
3. Check the “Plain RPM Directory” box on the next page?

That is what works for me with downloaded RPMs in openSUSE 12.3.

If you missed the “Plain RPM Directory” box, you can get back to it by selecting the repository on the “Configured Software Repositories” page and clicking edit.

Regards,
Howard

8

I read that, but it a very vague statement and I even reread it several times, but it still could not follow fully what you did and specialy why. Thus my “Maybe I do not fully understand you”. And why we love to help, we love it more to help on the original problem then on the problems one gets when trying to avoid the original problem by maybe walking a dead alley. In short IMHO this falls under “Describe the cause, not the step”.

9

On 2013-05-12, Ken Schneider <suse-list3@bout-tyme.net> wrote:
> On 05/12/2013 01:56 PM, hcvv pecked at the keyboard and wrote:
>> Maybe I do not fully understand you, but the broadcom-wl package is in
>> the Packman repo.
<SNIP>
>
> This is the kind of reply people get when the person doing the reply
> fails to read the entire original post.

You will notice that hcvv commences his response with `Maybe I do not fully understand you’ and I believe that caveat
exonerates him of your glib contention.

10

On 05/13/2013 06:08 AM, flymail pecked at the keyboard and wrote:
> On 2013-05-12, Ken Schneider <suse-list3@bout-tyme.net> wrote:
>> On 05/12/2013 01:56 PM, hcvv pecked at the keyboard and wrote:
>>> Maybe I do not fully understand you, but the broadcom-wl package is in
>>> the Packman repo.
> <SNIP>
>> This is the kind of reply people get when the person doing the reply
>> fails to read the entire original post.
> You will notice that hcvv commences his response with `Maybe I do not fully understand you’ and I believe that caveat
> exonerates him of your glib contention.
How can he not understand that the wifi is NOT working? The OP was very
explicit about stating it is NOT working. Therefore there is NO access
to the packman repo.

11

I am working all the time with a not working Wifi. Which realy does not stop me from using the Packman repo. But you can all stop discussing my case, which will distract from the OP’s problem. I hate it to participate in problems where half of the info is supposed to land in my brains by clairvoyance, thus I ill detach from this thread.