* dcabaton <[EMAIL PROTECTED]> [2003-06-16 19:55] : > > > > > >Il te manque vraisemblablement liborbit2-dev qui fournit la commande > >orbit2-config (d'après un apt-file search orbit2-config). > > > >Fred > > > > > > > Effectivement mais... > > debian:/home/dcabaton# apt-get install liborbit2-dev > Reading Package Lists... Done > Building Dependency Tree... Done > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > > > Since you only requested a single operation it is extremely likely that <> the package is simply not installable and a bug report against > that package should be filed. > The following information may help to resolve the situation: > > > Sorry, but the following packages have unmet dependencies: > liborbit2-dev: Depends: liborbit2 (= 2.3.107-1) but 1:2.6.1-1woody1 is > to be installed > Depends: liblinc-dev (>= 0.1.20) but it is not going to > be installed > E: Sorry, broken packages
Où as tu récupéré le paquet liborbit2 1:2.6.1-1woody1 ? Pas de l'archive Debian officielle (les versions sont 2.3.107-1 pour stable, 1:2.6.2-1 pour testing et unstable). Du coup, comme la source d'où tu as récupéré ce paquet ne fournit pas les paquets de développement et que les paquets sont liés au niveau du numéro de version, il y a problème. Si les versions 2.3.107-1 de liborbit2 et de liborbit2-dev te suffisent, tu peux installer celles-ci. Que donne un apt-cache policy liborbit2 liborbit2-dev ? Fred -- LA FAQ d-u-f ? http://savannah.nongnu.org/download/debfr-faq/html/