I'm using dia to diagram some things at work. I am running it on two machines one rh8.0 and the other is rh9.0. Both are having issues with writing text in dia(.90). On the 8.0 box it puts an extra space between every letter while the 9.0 box shows a wrinkled effect on the text where part of it is whited out. Both of these translate, respectively, when I export the files as .png's.

The conclusion was to update to either dia .91 or .92.

I'm pretty much a newbie and I get scared when I run an rpm -Uvh --test [meh]. And it gives me a "warning: " list of dependacies.



When do that for .92 I get the same dependancy issues for both of the boxes:

libXcursor.so.1 (where do I get this library from and do I "install" it or do I just put it in there?
gtk+2 (I already have a lot of gtk junk installed, when I try to update this, i get a lot more dependency issues)
xcursor (these three.... i'm sure i won't have any trouble updating)
xft
xrender



.91 issues
update pango
then when I try to update pango I get a huge list of library warnings




I guess I want to know what is safe to do and what isn't. Should I force any of these?

Also does anyone know the name of the option/script/prog that converts .gz's to rpm's, I have checkinstall, but I know there is a direct way of doing it.

Thanks.

If you don't have the all development stuff installed, try getting out your media and installing it--as an update, not a fresh install. (If you don't know how to install the package groups post that--its been a while, so I'll have to look it up).

I found up2date is still working on my machine, but I had kept up with it so I wouldn't get bounced. That is the easiest way to upgrade a group of interdependent applications.

Otherwise, use the rpm command and point it to a file. (Read the man-page for rpm. $>: man rpm) It is easier to write a file with the entire list of packages with the \ right before you hit the return for the next line. This way, the entire package list is the equivalent to one line. If you are a guru-type, you do it as a single rpm command from the command-line--I could do it, but lack the confidence in my typing.

That is the major drawback of rpm. It can be a pain, because it can be cryptic.

It looks to me that both of the installations have dependencies which aren't being met.

When you install the packages, install them using a single rpm command as a list of packages. I found myself in the predicament of having a broken application because of dependencies, and having the rpms which would have fixed the problem refuse to install. Same type of warnings and garbage. When I tried to force it, the package remained broken.

I found, in my case, it was not necessary to uninstall--but I had to include the entire package list using the update option of rpm.

I used the query option to find which packages contained the dependent objects. In my case, they were already part of the package set I had downloaded and had tried to install using separate rpm commands. (In essence, I really had three broken installs instead of one.)
/*It may be faster to: http://www.google.com/linux the packages you want and know about and read dependency list from their respective websites.*/

As far as as the .gz to rpm--I am unaware of it. And wouldn't want it anyhow. When I get a tar.gz package, I have to force myself not to be complacent. Always take the time to read the docs with any package.

Hope that helps. Someone else will explain it better I'm sure.

Howzit

To solve dependancies promblem try the following it will work for most cases.



1.from your RH distro install the rpm rpmdb-redhat-<version that is available>
2. cp -av all three cd onto your hard drive .e.g. /var/ftp/pub/ReHat/RPMS
3. creat the following file /root/.rpmmacros
4. Place the following in that file %_solve_pkgsdir /var/dtp/pub/RedHat/RPMS
5. use the rpm cmd with following switch rpm -Uvh --aid <pakage u installing>

chow