[R-pkg-team] Bug#980902: rmatrix: which reverse dependencies need rebuilds?

[Dirk Eddelbuettel]

On 25 January 2021 at 09:17, Graham Inggs wrote:
| Hi
| 
| On Sun, 24 Jan 2021 at 18:06, Graham Inggs <ginggs at debian.org> wrote:
| > I'm awaiting autopkgtest results on the binNMU'd r-cran-tmb.  I will
| > update this bug and #980809 when they are in.
| 
| The autopkgtests for r-cran-tmb [1] and r-cran-glmmtmb [2] have
| completed on all architectures except for s390x, which are still
| queued.  So no definitive answer for #980809 yet.  The latest results
| no longer have the "Package version inconsistency detected" warning.
| 
| On Sun, 24 Jan 2021 at 06:12, Graham Inggs <ginggs at debian.org> wrote:
| > The actual warning message is generated by r-base,
| 
| This is not true, I was confused by a similar error I had seen in
| another package (where the warning does come from r-base):
| 
| Error: package or namespace load failed for ‘DropletUtils’ in
| loadNamespace(j <- imp[[1L]], c(lib.loc, .libPaths()), versionCheck =
| vI[[j]]):
|  namespace ‘Matrix’ 1.2-18 is already loaded, but >= 1.3.2 is required

Hm, but that is a different warning -- AFAIK it comes when you a versioned
Depends or Imports tries to load package and encounters an already installed
(i.e. cannot be replace by R in that session) version that is lower than the
requirement.

(Code search is very useful. As an aside, instead of codesearch.debian.net
you can also search at GitHub in the cran organisation which hits essentially
all mirrored CRAN packages.  17k >> 1k.)
 
| The warning in r-cran-tmb comes from r-cran-tmb itself [3].  I had a
| look on codesearch.debian.net and found the only other occurrences of
| packageVersion("Matrix") were in r-cran-rcpparmadillo and
| r-cran-igraph, and that code seems to be catering for different
| versions of Matrix, not warning against them.  In my opinion, there's
| nothing to be done in rmatrix, and I will reassign this bug to

Looks like we are "finally" on the same page :)

| r-cran-tmb, affecting r-cran-glmmtmb.  I think the solution there is
| to simply upgrade the warning to an error and then it should be caught
| by autopkgtest whenever it wants rebuilding.

Yes. The cleanest might be a test script that just tries library(glmmTMB)
having set options("warn"=2).

Dirk 

-- 
https://dirk.eddelbuettel.com | @eddelbuettel | edd at debian.org