Fedora RPM Failure

[ockham]

Converted from SourceForge issue 1185140, submitted by SourceForge user jcwinnie on 2005-04-18 12:34:23 UTC.

rpm -ivh gourmet-0.8.3.3-1.fedora.noarch.rpm

error: Failed dependencies: metakit is needed by gourmet-0.8.3.3-1.noarch pygtk2>=2.3.96 is needed by gourmet-0.8.3.3-1.noarch

No, I just installed metakit 2.4.9.3 successfully. And,

rpm -q pygtk2

pygtk2-2.4.0-1 And, pygtk2-devel also is installed.

[ockham]

Submitted by SourceForge user jcwinnie on 2005-05-11 13:37:31 UTC.

Logged In: YES user_id=645989

rpm -Uvh gourmet-0.8.4.1-1.noarch.rpm

Holy Toledo! It worked.

[ockham]

Submitted by SourceForge user jcwinnie on 2005-04-30 12:35:37 UTC.

Logged In: YES user_id=645989

Well, it is different...

rpm -Uvh gourmet-0.8.3.5-1.fedora.noarch.rpm

error: Failed dependencies: python-abi = 2.4 is needed by gourmet-0.8.3.5-1.3.noarch gnome-python2-gnomeprint is needed by gourmet-0.8.3.5-1.3.noarch

[ockham]

Submitted by SourceForge user thomas_hinkle on 2005-04-29 20:38:05 UTC.

Logged In: YES user_id=1030390

Could you try the latest fedora RPM (0.8.3.5) and see if it works? I've changed the RPM build process and believe that RPM should fix this problem -- I'll wait for confirmation before closing this bug.

[ockham]

Submitted by SourceForge user nobody on 2005-04-25 01:49:13 UTC.

Logged In: NO

Did you install metakit from an rpm? If not, that could be your problem.

The pygtk2 thing though looks weird.

I've been building and using the following rpms on fc4test series, they should also work on fedora core 3:

http://mpeters.us/fc_extras/gourmet/

You'll want to install the PyRTF rpm first, and then the gourmet. All other dependencies should be installable from either fedora core or fedora extras.

These are not official rpm's from gourmet, the gourmet developer has nothing to do with them other than being kind enough to code an open source project. They are rpm's I am attempting to get into fedora extras, though, and are written to the Fedora Extras packaging guidelines.

If you would prefer to build them yourself for security reasons, the spec files are one directory up.

[ockham]

Submitted by SourceForge user thomas_hinkle on 2005-04-21 15:08:56 UTC.

Logged In: YES user_id=1030390

I have no idea how RPM could produce the above messages given your setup. I also don't use RPM, so I can't test myself. If you or anyone else can track this down, please let me know what's going on. If you want to see how the RPMs are built, download the source and run python build_rpms.py