For the record, here is the log message:
Version bump to trigger package rebuilding now that purl()'ing issue
has been correctly identified. knitr does not create purl()'ed
(Stangle equivalent) .R files if _R_CHECK_TIMINGS_ is set, which
the build system was setting. Now it's not set, so these .R
Thanks, Kasper and Dan, I already found it. Next time something like
that happens, I will first check out the logs.
Best regards,
Ulrich
On 05/17/2016 05:09 PM, Dan Tenenbaum wrote:
For the record, here is the log message:
Version bump to trigger package rebuilding now that purl()'ing issue
Ulrich, "svn log" does not help you here?
On Tue, May 17, 2016 at 9:12 AM, Ulrich Bodenhofer wrote:
> Thanks, Leonardo! Yes, all my four packages use knitr, while the other
> eight packages I mentioned use Sweave. So my question is answered and the
> issue is closed, thanks again! I just wanted
Thanks, Leonardo! Yes, all my four packages use knitr, while the other
eight packages I mentioned use Sweave. So my question is answered and
the issue is closed, thanks again! I just wanted to know what happened,
since I could not find an explaination why the version numbers have been
bumped.
On 17 May 2016 at 13:43, Martin Maechler wrote:
> I also wonder *why* you use \donttest{} so extensively.
> It's clearly better than \dontrun{} (which really distresses
> me, if used more than occasionally).
I totally agree with you that \dontrun is overused and annoying for users.
My main us
Hi,
Does your package use knitr for creating the vignettes? If so, it must
be because of
https://github.com/lcolladotor/derfinder/commit/c70ede92fb14e83a0fe0032353f7f897ff55b5d5
(the equivalent commit for your package).
Best,
Leonardo
On Tue, May 17, 2016 at 4:18 AM, Ulrich Bodenhofer
wrote:
>
> Martin Morgan
> on Sun, 15 May 2016 14:25:01 -0400 writes:
> On 05/15/2016 02:20 PM, Dan Tenenbaum wrote:
>>
>>
>> - Original Message -
>>> From: "Richard Cotton" To:
>>> "bioc-devel" Sent: Sunday,
>>> May 15, 2016 4:45:09 AM Subject: [Bioc-de
Hi all,
I just noticed that the version numbers of many (yet not all) packages
have recently been incremented from x.y.0 to x.y.2 both in the devel and
in the release branch. Actually, this affected all four packages I am
maintaining, but strangely none of the other eight packages that are
ma
