Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 53561 - coda - bad depedencies order
Summary: coda - bad depedencies order
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Library (show other bugs)
Hardware: x86 Linux
: High minor (vote)
Assignee: Daniel Black (RETIRED)
URL:
Whiteboard:
Keywords:
: 56628 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-06-10 11:52 UTC by re-vax
Modified: 2004-08-10 09:05 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description re-vax 2004-06-10 11:52:47 UTC
# emerge  coda-server
Calculating dependencies ...done!
>>> emerge (1 of 4) net-libs/rpc2-1.22 to /
.
.
.
.
checking location of liblwp... none
configure: error: "Cannot determine the location of liblwp"
 
!!! ERROR: net-libs/rpc2-1.22 failed.
!!! Function econf, Line 365, Exitcode 1
!!! econf failed
 

Reproducible: Always
Steps to Reproduce:
1.emerge  coda-server when liblwp and net-libs/rpc2-1.22 are nedded

Actual Results:  
checking location of liblwp... none
configure: error: "Cannot determine the location of liblwp"


I think that is is trivial problem, this is just the order in which the packages
must be emerged: first lwp then rpc2 :)
Comment 1 Peter Jensen 2004-06-10 12:47:26 UTC
The net-libs/rpc2-1.22 ebuild has these comments in it:

# Questionable dependancies
#       >=sys-libs/lwp-1.10
#       >=sys-libs/ncurses-5
#       >=sys-libs/readline-4.1"

I guess sys-libs/lwp wasn't such a questionable dependency after all :-)
Comment 2 Peter Jensen 2004-07-04 08:45:42 UTC
Adding maintainer to CC.
Comment 3 Daniel Black (RETIRED) gentoo-dev 2004-07-14 14:09:22 UTC
Will fix in  not too distant future
Comment 4 Daniel Black (RETIRED) gentoo-dev 2004-07-15 13:53:23 UTC
thankyou
Comment 5 Maurice van der Pot (RETIRED) gentoo-dev 2004-08-10 09:05:58 UTC
*** Bug 56628 has been marked as a duplicate of this bug. ***