Gogalthorp: RPM issues

[MikeH30]

Hi Gogalthorp,

You responded on my USB drive post and I saw your post here. I am also having RPM issues or at least it seems that way. I am attempting to install Hylafax server on Suse Enterprise Server 10.0. I removed the previous version in YAST via "Software Management". I then attempted to install the source code for the latest Suse package (hylafax-4.4.1-1rhel5.src.rpm) which I downloaded from SUSE Packages - hylafax.org.

I still have not installed "GCC". I noticed that this was a "source" RPM. So after downloading the file I double clicked it and package installer proceeded to install it. Afterwards, I went into YAST's Software Mangement and searched for Hylafax. It appeared in the list box of installed programs. However it was in "red" font and had a "padlock" symbol preceeding the name. The status showed that it was installed.

Questions

1. Why is there a padlock symbol and the name of the program in red font? Was there a problem with the install? It appears to be installed as I ran the "set up" script to configure my modem with the software. However, I am puzzled by the status in Software Management.

2. I am running SUSE Enterprise Server 10.0. Was I correct in choosing the source RPM or should I have tried the version for SUSE Enterprise server 9 or SUSE Linux 10 ( this is the desktop version)? These were available at SUSE Packages - hylafax.org.

Thanks.

[gogalthorp]

I don't know what language hylafax is written in but if you don't have gcc or another c compiler it is not written in c or c++ but you must have that language installed since it installed.

It is red because it is a version that is not available from the repositories you have setup in YAST. Locked for the same reason ie the auto-update won't try to install over this version.

I'd have gone for the compiled versions for the system I was installing on. But since it seems to work for you.....

[MikeH30]

It is red because it is a version that is not available from the repositories you have setup in YAST. Locked for the same reason ie the auto-update won't try to install over this version.

I understand now. Do I need to set up other repositories for this? or leave it alone?

I'd have gone for the compiled versions for the system I was installing on. But since it seems to work for you.....

My point here was that there was no compiled version for SUSE Enterprise Server 10. That is why I chose the source RPM. So going forward for future program intallations, if there is no version for my system, I should use the source version (SRPM if available ) - correct? Thanks again.

[gogalthorp]

I understand now. Do I need to set up other repositories for this? or leave it alone?

If you can find a repository with this package it is the easiest way to keep current

My point here was that there was no compiled version for SUSE Enterprise Server 10. That is why I chose the source RPM. So going forward for future program intallations, if there is no version for my system, I should use the source version (SRPM if available ) - correct? Thanks again.

I would bet a large sum the the 10 ver would work on a ver 10 server. But do what works.

[MikeH30]

I went to the openSuse Website to search for more repositories. This warning was there: You may have added these during installation, if so adding them again will be a bad idea.


Questions

1. How can I tell if I already added some of the repositories? Would they be listed in the list box of "Installation Source" in YAST?

2. There are no repositories there for SUSE Enterprise Server 10. Should I install the repos for desktop 10?

3. (Back to the GCC topic above ) The listbox in Software Management shows that I have installed "libgcc" and "cpp". Is "gcc" still in a
seperate repo? Can I find it in one of the SUSE repos - OSS, Non-Oss, GNOME, KDE, etc.?

[gogalthorp]

gcc is in the standard repository It is also on your installation disk.

If you are using the server edition you need to contact Novell. The server edition is most likely the same as the normal Desktop with additional programs for special "server" use. Some of these may be proprietary. So I don't know what to tell you. Have you registered with Novell. Why do you need the server edition anyway??

You can check on the what URL's you have entered by the list in Installation sources. Adding them again is bad since Yast would check the sources several times, it already is slow enough.

Have you run YAST-Software-Update Setup? This should get you set to a standard repository for 10.0 Server. Note this may not be free. The Server is not a free as in beer product even though it is built on free as in speech software.

[MikeH30]

You can check on the what URL's you have entered by the list in Installation sources. Adding them again is bad since Yast would check the sources several times, it already is slow enough.

So I take it if they are not in the listbox then they are not added - correct?

Also, I went to add this source:

Index of /distribution/SL-10.0-OSS/inst-source

and I received 2 warnings. The first stated that it was not digitally signed and asked if I wanted to continue. I said yes. Then the second stated "No Checksum found"

Should I use it anyway? Can I assume that the sources found on openSUSE.org are safe?

Have you run YAST-Software-Update Setup? This should get you set to a standard repository for 10.0 Server. Note this may not be free. The Server is not a free as in beer product even though it is built on free as in speech software.

I have auto updates turned on. Is this what you mean by YAST-Software Update Set up?

[gogalthorp]

RPM maintains a database of the stuff it installed. This is where Yast gets it's lists. If you install from source (ie don't use RPM) then RPM might not know of this install and it will not show up in the list.

I think that OpenSuse.org as safe as your going to get but I find the check sum errors odd RPMs are generally digitally signed. Yast normally asks if you want to add the signature to your OK list. But I run 10.1 so I guess there could be differences.