On 17 October 2006 at 02:51, Steve Langasek wrote:
| On Sat, Oct 14, 2006 at 02:57:40PM -0500, Dirk Eddelbuettel wrote:
| > That's the one then as I had
|
| > libgfortran.so.0 => /usr/lib/libgfortran.so.0 (0xb747f000)
|
| > How could that have slipped? Whose shlibs file do we need to look at?
|
| The first problem is:
|
| Package: r-cran-fseries
| Architecture: any
| Depends: r-base-core (>= 2.3.0), r-cran-fbasics (>= 201.10059),
r-cran-fcalendar, r-cran-mgcv (>= 1.1.5), r-cran-vr (>= 7.2.8)
|
| You aren't using the shlibs:Depends substitution in your debian/control
| file, so *all* shared library dependencies are missing for the package!
Plonk.
Quite right. Looking at another R package using Fortran (r-cran-tseries)
shows that it correctly display a Depends on libgfortran1. So it's simply my
packaging bug. Sigh. I just checked all my debian/control files, and for
Arch: any it affected (outside of the Rmetrics block) only three other
packages where I have now updated debian/control.
| There is a potential collateral problem with having different packages built
| against multiple versions of libgfortran because libgfortran doesn't use
| versioned symbols, but that's a rather general problem in the archive today
| and doesn't have nearly the same priority as getting these packages'
| dependencies fixed.
Yes. As it happens, I need to update the whole Rmetrics complex of 7 or 8
packages anyway as a new upstream release is out. Just waiting for the NEW
r-cran-fecofin to come out the New queue.
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]
