[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#605372: tseries: FTBFS on armel: unable to load shared object



On Tue, 2010-12-14 at 14:34 -0600, Dirk Eddelbuettel wrote:
> Hi Adam,
> 
> On 14 December 2010 at 20:12, Adam D. Barratt wrote:
> | On Tue, 2010-12-14 at 12:39 -0600, Dirk Eddelbuettel wrote:
> | > reassign 605372 release.debian.org
> | > thanks
> | 
> | [For reference, at least right now debian-release has only received the
> | result of your control@ mail, not the mail I'm replying to; it's
> | generally a good idea to CC the receiving package]
> 
> [ I was thinking about that but then I didn't know the email handle of the
> virtual BTS entity release.debian.org -- the release list ? ]

Yep.  release.debian.org@packages.d.o works too :-)

> | > Dear release team,
> | > 
> | > Can you please schedule a binary-only rebuild of package
> | > 
> | >     quadprog   		(binary:  r-cran-quadprog)
> | > 
> | > on the 'armel' architecture, and once completed, schedule a binary-only
> | > rebuild of package
> | > 
> | >     tseries 	     	(binary: r-cran-tseries)

fwiw, this will be a give-back rather than a binNMU, as the package has
not successfully built yet.

> | > on the 'armel' architecture.
[...]
> | dpkg-shlibdeps: warning: couldn't find library libRblas.so needed by debian/r-cran-quadprog/usr/lib/R/site-library/quadprog/libs/quadprog.so (ELF format: 'elf32-littlearm'; RPATH: '').
> 
> libRblas is outdated by years.  We used it when we had lapack 3.1.* years,
> and for several years have used Debian's BLAS and LAPACK meaning that R's
> linRblas is no longer built.  

It's still in the r-base-core-ra armel binary package, hence my
mentioning it :-)

In any case, looking at the relative build dates of the previously
successful quadprog and tseries builds on armel, I've concluded I may
have been overly hasty in deciding that a binNMU wouldn't help, so I've
scheduled quadprog/armel.  Assuming the log for that looks happier I'll
give-back tseries afterwards.

Regards,

Adam




Reply to: