Since posting the mesasge I did the install and told RPM to ignore dependances. It seems to work ok. By the way, I installed Gnome from the 8.0 CDs and it seems to work fine (so far).
Thanks for your email. Good luck with your upgrade.
On Mon, 22 Apr 2002 21:32:21 +0200 (CEST) Bernd Schandl <schandl@...> wrote:
On Sun, 21 Apr 2002 robertc@... wrote:
> I am trying to install Gramps 0.7.2 on a new SuSE 8.0 installation.
> Gnome, GtK and Python were installed from the SuSE Cds. Installed every
> related library that I found but obviously don't have something.
> When running the rpm install I get the following message: "failed
> dependencies: pygnome-libglade is needed by gramps-0.7.2-2"
> Checked and installed everything I could find related to libglade. Still
> the same issue.
I am using Gramps on SuSE 7.3 and will switch to 8.0 within the next few
days. But I am using Gramps directly from CVS, not the RPM. Probably you
could also use the tar.gz.
This is one of the things where SuSE goes its own way. It is a pretty good
distribution but these little differences to "the mainstream" and their
strong preference for KDE at the cost of Gnome makes me think about
switching to Redhat, Mandrake or Debian. Well, time to think some more...
Tired of spam? Use spamcop.net to complain!
Gramps-users mailing list
From: Don Allingham <dallingham@us...> - 2002-04-23 02:33:43
On Mon, 2002-04-22 at 14:26, robertc@... wrote:
> Since posting the mesasge I did the install and told RPM to ignore dependances. It seems to work ok. By the way, I installed Gnome from the 8.0 CDs and it seems to work fine (so far).
> Thanks for your email. Good luck with your upgrade.
> Friedrichshafen, Germany
The differences between packaging makes distributing RPMs a bit
difficult. Ximian has made it even worse in some cases, where they
package things up different from the distributions.
If you wouldn't mind, try the following command (you may need to change
python1.5 to python2.1 or python2.0):
rpm -query --file /usr/lib/python1.5/site-packages/_gladegnomemodule.so
This command should tell us where Suse has packaged the files. I get the