Skip to content
Prev 49432 / 63424 Next

Problem understanding behaviour of versionCheck for loadNamespace (and when versions for Imports packages are checked)

Many thanks Duncan for the quick response. 

A bug is a relief in a way. I've been digging my way deeper into this (and
learning more as I go) for several days now - but it is a diversion from (a
diversion from) my main goal :-(

Is there somewhere specific I should report or log the bug or will that
happen from this mailing-list automatically? (I have seen the Bug Tracking
link on the r-project page and followed that, but don't yet have a Bugzilla
account, nor know the precise mechanics and protocols for notifying a bug)

Geoff

PS Building package2 - via devtools::build('package2', binary = TRUE) does
check and insist that I have an appropriate version of the 'to be imported'
package1 installed in my .libPath().

It was only when I simulated a user who has and older version of the
Imported package1 (by overwriting the later version of package 1 with an
earlier version), then trying to load or attach package2 that the (failure
of the version checking) at loadNamespace time for package1 became apparent
(well apparentish after quite a bit of digging)

-----Original Message-----
From: Duncan Murdoch [mailto:murdoch.duncan at gmail.com] 
Sent: Thursday, 27 November 2014 10:57 AM
To: Geoff Lee; r-devel at r-project.org
Subject: Re: [Rd] Problem understanding behaviour of versionCheck for
loadNamespace (and when versions for Imports packages are checked)

Summary:  I think you've found a bug.
On 26/11/2014, 5:39 PM, Geoff Lee wrote:
I would have assumed they are checked when you try to install the package.
If you ask for version 3.0, and only have 0.3, the install should fail.

But as you've found, the documents say something else...
...
"
later).
According to what you have written, that should have failed.  So it looks
like a bug.
That does seem like a typo.

Duncan Murdoch
version))."
bug?