Bug 200256 - F-spot misses a BuildReq on dbus-sharp-devel
Summary: F-spot misses a BuildReq on dbus-sharp-devel
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: f-spot
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Christopher Aillon
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-07-26 15:12 UTC by Roozbeh Pournader
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-07-27 19:57:09 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
spec patch to fix the problem (385 bytes, patch)
2006-07-27 10:20 UTC, Roozbeh Pournader
no flags Details | Diff

Description Roozbeh Pournader 2006-07-26 15:12:32 UTC
Description of problem:
f-spot needs a BuildReq on dbus-sharp-devel.

Version-Release number of selected component (if applicable):
0.1.11-3.1

How reproducible:
Always

Steps to Reproduce:
1. rpm -Uvh f-spot-0.1.11-3.1.src.rpm
2. rpmbuild -bc f-spot.spec
  
Actual results:
Failure with an error ending in:

checking for F... configure: error: Package requirements (libgnome-2.0 >= 2.2
libgnomeui-2.0 >= 2.2 libexif >= 0.5.7 libexif < 0.7.0 gtkhtml-sharp-2.0 >= 2.7
gconf-sharp-2.0 >= 2.7 glade-sharp-2.0 >= 2.7 gnome-vfs-sharp-2.0 >= 2.7
gtk+-2.0 >= 2.6 mono >= 1.1.7 dbus-sharp >= 0.23) were not met:

No package 'dbus-sharp' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables F_CFLAGS
and F_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

error: Bad exit status from /var/tmp/rpm-tmp.94158 (%build)


RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.94158 (%build)

Comment 1 Roozbeh Pournader 2006-07-27 10:20:57 UTC
Created attachment 133140 [details]
spec patch to fix the problem

Attached a patch

Comment 2 Matthias Clasen 2006-07-27 19:57:09 UTC
fixed in 0.1.11-4


Note You need to log in before you can comment on or make changes to this bug.