On Thu, Jun 22, 2017 at 5:35 PM, Uwe Ligges
wrote:
> On 22.06.2017 17:35, Dirk Eddelbuettel wrote:
>>
>>
>> On 22 June 2017 at 16:23, Gábor Csárdi wrote:
>> | So, along these lines, I was thinking if we could / should build a
>> | pandoc R package, that could just pull the right binary at install
On 22.06.2017 17:35, Dirk Eddelbuettel wrote:
On 22 June 2017 at 16:23, Gábor Csárdi wrote:
| So, along these lines, I was thinking if we could / should build a
| pandoc R package, that could just pull the right binary at install
| time.
And drops it in the package? Then we cannot provide bin
On 22 June 2017 at 16:23, Gábor Csárdi wrote:
| So, along these lines, I was thinking if we could / should build a
| pandoc R package, that could just pull the right binary at install
| time. Would that make sense? It is a bit unusual, but I think a lot of
| users would like it, and it would help
So, along these lines, I was thinking if we could / should build a
pandoc R package, that could just pull the right binary at install
time. Would that make sense? It is a bit unusual, but I think a lot of
users would like it, and it would help standardizing pandoc versions
and usage.
The static bi
On 22 June 2017 at 16:36, Uwe Ligges wrote:
| This should be resolved in general now.
I appreciate your work on this, as well Gabor's help in providing new binaries.
But correct me here if I wrong: It still does not help with this issue as
long as _any other pandoc binary_ is called, correct?
This should be resolved in general now.
Best,
Uwe Ligges
On 03.06.2017 15:51, Dirk Eddelbuettel wrote:
On 3 June 2017 at 08:30, Dirk Eddelbuettel wrote:
|
| On 27 May 2017 at 22:18, Emmanuel Blondel wrote:
| | Dear Uwe, i clearly understand the CRAN team needs time on this. I have
| | no pro
On 3 June 2017 at 08:30, Dirk Eddelbuettel wrote:
|
| On 27 May 2017 at 22:18, Emmanuel Blondel wrote:
| | Dear Uwe, i clearly understand the CRAN team needs time on this. I have
| | no problem in postponing on my side, and resubmit later next month.
|
| As the problem appears to be somewhat h
On 27 May 2017 at 22:18, Emmanuel Blondel wrote:
| Dear Uwe, i clearly understand the CRAN team needs time on this. I have
| no problem in postponing on my side, and resubmit later next month.
As the problem appears to be somewhat hard and rooted in two areas that are
difficult to effectuate ch
Dear Uwe, i clearly understand the CRAN team needs time on this. I have
no problem in postponing on my side, and resubmit later next month.
Thanks & best regards
Le 27/05/2017 à 16:25, Uwe Ligges a écrit :
> For geometa:
>
> If you resubmit without the access to "img.shields.io", we can publish
On 27.05.2017 16:37, Spencer Graves wrote:
On 2017-05-27 9:25 AM, Uwe Ligges wrote:
For geometa:
If you resubmit without the access to "img.shields.io", we can publish
now. Otherweise, as we have not yet managed to get a univesally
working pandoc on the CRAN master, we cannot publish your
On 2017-05-27 9:25 AM, Uwe Ligges wrote:
For geometa:
If you resubmit without the access to "img.shields.io", we can publish
now. Otherweise, as we have not yet managed to get a univesally
working pandoc on the CRAN master, we cannot publish your package yet.
Uwe:
Might it be appr
For geometa:
If you resubmit without the access to "img.shields.io", we can publish
now. Otherweise, as we have not yet managed to get a univesally working
pandoc on the CRAN master, we cannot publish your package yet.
Best,
Uwe Ligges
On 27.05.2017 16:20, Emmanuel Blondel wrote:
Thanks
Thanks Uwe for your clarifications. Can you let me know if i need to
change something on my side, and/or resubmit the package to CRAN? (the
warning on Pandoc was the only one) Thanks in advance
Best,
Emmanuel
Le 26/05/2017 à 00:11, Uwe Ligges a écrit :
This is currently under inspection by the
This is currently under inspection by the CRAN team. Apparently
img.shields.io have changed the cypher settings and pandoc fails with
the new settings. We may have to disable *.md processing for some time.
Best,
Uwe Ligges
On 25.05.2017 20:59, Emmanuel Blondel wrote:
Dear all,
I've just su
Dear all,
I've just submitted a new package named geometa, for which i received the
message below. Indeed i had sent in my submission some question mark about the
warning i obtain during R CMD check:
In case of R release and R devel, I got the following warning:
Conversion of 'README.md' faile
15 matches
Mail list logo
