Bug 1013710 - dbh version too old
dbh version too old
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: dbh (Show other bugs)
rawhide
Unspecified Linux
unspecified Severity unspecified
: ---
: ---
Assigned To: Gwyn Ciesla
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-30 11:58 EDT by Antonio Trande
Modified: 2013-10-01 12:27 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-10-01 09:10:05 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Antonio Trande 2013-09-30 11:58:49 EDT
Description of problem:
dbh is currently available in 1.0.24 version; it's too old compared to newer release now online: http://sourceforge.net/projects/dbh/files/dbh/.

I wish to present a new package review of Rodent file-manager (http://sourceforge.net/projects/xffm/files/) that needs dbh >= 5.0.6

...
configure: *** *** You may download dbh from http://sf.net/projects/dbh *** ***
checking for dbh2 >= 5.0.6... not found
*** The required rodent dbh2 was not found on your system.
*** Please install dbh2 (atleast version 5.0.6) or adjust
*** the PKG_CONFIG_PATH environment variable if you
*** installed the rodent in a nonstandard prefix so that
*** pkg-config is able to find it.
error: Bad exit status from /var/tmp/rpm-tmp.7IY4tj (%build)

If possible, dbh should be updated to a newer version.


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

dbh-1.0.24-14.fc19.x86_64
Comment 1 Gwyn Ciesla 2013-10-01 08:32:20 EDT
Major change, will be rawhide only, but I should have this out today.
Comment 2 Gwyn Ciesla 2013-10-01 09:10:05 EDT
Built in rawhide.
Comment 3 Antonio Trande 2013-10-01 12:27:03 EDT
(In reply to Jon Ciesla from comment #2)
> Built in rawhide.

Thank you !

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