Some Success on RH7.2 was (Re: gnome pilot under redhat 7.2)

[Robert Sean Hartnett <tardis mediaone net>]

Like many of the postings of late I have had many problems getting Gnome
Pilot working on RH 7.2. Dependency issues and such. I have had some
success yesterday on a RH 7.2 freshly installed and upgraded box through
the Red Hat network, this box does not have Ximian installed.

What I finally did was to remove all the pilot-link and Gnome-Pilot
RPMs. Upgrading packages did not seem to work correctly. After trying
several methods using non Ximian packages, and not having much success I
went to rpmfind.net and downloaded all the Ximian latest RPM packages
for pilot-link and Gnome-pilot and such from this site. I also grabbed
another package that was listed as needed "lbstdc" or something like
that. I am trying to recall this from memory.

In order installed and tested as "root",
no other dependicies appeared...
Pilot-Link
Pilot-Link-Devel

Gnome-Pilot
Gnome-Pilot-Devel

Gnome-Pilot-Conduits

Gnome-Pim (1.4, not 1.2)
Gnome-Pim-Devel (Same as above)
   (I had to add Gnome Address and Calender to the menu manually)
   (I guess since this is a Ximian package, is why it did not appear.)

Gnome-Pim-Conduits

After all above was installed, again they are the Ximian packages for RH
7.2, the conduits appeared in the Control Center, and I was able to
communicate with my Palm to get my user ID.
However when I tried to sync, I was getting my Palm reporting
communications was lost. After trying a few things, I decided to do a
reboot of the box, nothing else was left that I could think of. After it
came up, I was able to sync the address book, which is all I had enabled
at the time. The sync window however looked washed out a bit, but hey it
is working. After I tried the Time Sync conduit, it did not sync my Palm
time to the system time.
Last thing I tried last night before going to bed, was to try to sync
the Calender. That appears to have not worked, though I have always had
problems, even on previous RH releases syncing the Calender. Where
exactly does the file after syncing up the Calender get placed, and its
name? I thought it was the .gnome directory. Unfortunatley you can't
specify the Calender settings like you can with the address book.

I hope this helps anyone trying to deal with this problem. I will check
other conduits when I have some time.

				Sean


On Fri, 2001-11-30 at 18:13, Paul Oliver wrote:
> > These are the errors I get when I attempt to install the various rpm's
> > 
> > rpm -Uvh  pilot-link-0.9.6-cvs.i386.rpm
> > 
> > error: failed dependencies:
> >     libstdc++.so.2.10   is needed by pilot-link-0.9.6-cvs
> >     pilot-link = 0.9.5 is needed by pilot-link-devel-0.9.5-8
> >     libpisock.so.3   is needed by jpilot-0.99-7
> >     libpisock.so.3   is needed by kdepim-pilot-2.2-1
> 
> 
> 
> First off, don't install pilot-link-0.9.6-cvs.  I'd install
> pilot-link-0.9.5.rpm.  I've heard about and had problems with
> that version and evolution.
> 
> Judging by your messages you need to uninstall some packages.
> Do this unless you use jpilot and kdepim-pilot:
> 
> rpm -e jpilot
> rpm -e kdepim-pilot
> rpm -e pilot-link-devel
> 
> If you see any more packages that are errors either delete them
> (using rpm -e), or use --nodeps:
> 
> rpm -e jpilot --nodeps
> rpm -e kdepim-pilot --nodeps
> rpm -e pilot-link-devel --nodeps
> 
> 
> > rpm -Uvh gnome-pim-1.4.3-1.i386.rpm
> > error: failed dependencies:
> >     gnome-pim = 1.2.0 is needed by gnome-pim-devel-1.2.0-13
> 
> 
> Once again, get rid of gnome-pim-devel:
> 
> 	rpm -e gnome-pim-devel
>          rpm -Uvh gnome-pim
> 
> 
> > rpm -Uvh gnome-pilot-0.1.63-1.i386.rpm
> > 
> > error: failed dependencies:
> >     libpisock.so.4   is needed by gnome-pilot-0.1.63-1
> > 
> 
> 
> This will be fixed when you get pilot-link installed, I believe.
> 
> 
> > As you can tell, I am very new to linux, so any help will be
> > greatly appreciated.
> 
> 
> Actually, the fact you're posting here for help means you're
> getting along pretty well.
> 
> Hope I helped a little bit.  The RPM dependency problems can
> be pretty tricky.  The best thing to do when you deleting packages
> is to kind of "drill down" as you delete.
> 
> For example:
> 
> rpm -Uvh package-a-1.0
> error: failed dependencies:
>       package-a depends on package-b
>       package-c depends on package-a-0.95
> 
> Well, we can see that we will need package-b FIRST before we
> install package-a.  So the next step would be to get that
> package and install it.
> 
> Also, package-c is telling me that I can't delete the old version
> of package-a because it depends on it.  This is where the moment
> of truth comes in.
> 
> We can either:
>       1) delete package-c. . . but it may have other packages that
>          depend on it as well, and packages that depend on *those*
>          packages.  So then you get into a delete-fest.  Plus, you
>          most likely want some of the packages that you'll delete.
>          Delete a package:   rpm -e package-c  or force it with
>          --nodeps if it keeps protesting about other packages.
> 
> 
>       2) Force an upgrade (what I usually do).  The package that
>          is protesting might actually be fine with the new version.
>          Force the upgrade like this:  rpm -Uvh package-a --nodeps
> 
> 
> 
>       3) Drop the RPM system altogether and learn how to compile
>          tarballs (.tar.gz, or .tgz) files.  That's a little
>          trickier, but I would recommend learning how to do this
>          sometime.
>