On 10 July 2007 at 16:45, Chris Lawrence wrote:
| On 7/9/07, Dirk Eddelbuettel <[EMAIL PROTECTED]> wrote:
| > a) How do I fix the dh_shlibs call to get proper Depends? I do not
| > know how :-/
|
| I think dh_shlibs is getting the depends... the trouble is they're not
| making it into the control file. In r-cran-mvtnorm's case, in
| debian/control:
|
| Depends: r-base-core (>= 2.3.1)
|
| should be:
|
| Depends: r-base-core (>= 2.3.1), ${shlibs:Depends}
But look what the source has:
[EMAIL PROTECTED]:~$ grep Depends src/debian/CRAN/mvtnorm-0.7.5/debian/control
Build-Depends: debhelper (>> 4.1.0), r-base-dev (>= 2.3.1), cdbs
Depends: ${shlibs:Depends}, r-base-core (>= 2.3.1)
[EMAIL PROTECTED]:~$
| That might also fix multcomp, which won't install on AMD64 because
| libgfortran1 isn't available on AMD64.
|
| > b) Given a), should I create a new r-base-* set of packages where
| > r-base-dev unconditionally pulls in gfortran1 ?
|
| That seems icky... at least on AMD64, gfortran2 seems to be the default.
I'm missing something. We *did* switch to gcc-4.2 which *defaults to
gfortran2* which is why you had this bug because you only have gfortran2 and
not gfortran1.
Dirk
--
Hell, there are no rules here - we're trying to accomplish something.
-- Thomas A. Edison
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
