Am 02.09.2016 um 16:02 schrieb Dirk Eddelbuettel:
On 2 September 2016 at 14:54, Thomas Petzoldt wrote:
| Hi,
|
| I have the same problem and, at a first look, the issues reported by the
| CRAN checks seemed easy to fix. However, after checking it again locally
| and on http://win-builder.r-proje
On 2 September 2016 at 14:54, Thomas Petzoldt wrote:
| Hi,
|
| I have the same problem and, at a first look, the issues reported by the
| CRAN checks seemed easy to fix. However, after checking it again locally
| and on http://win-builder.r-project.org it appeared that GCC 4.9.3
| (Windows, Rt
Hi,
I have the same problem and, at a first look, the issues reported by the
CRAN checks seemed easy to fix. However, after checking it again locally
and on http://win-builder.r-project.org it appeared that GCC 4.9.3
(Windows, Rtools 3.4), same also on win-builder reports even more
issues, es
Hi Kurt,
I have started to look into this, and I need some guidance about how to
prioritize my repairs. There are basically 4 categories of warnings from
gfortran’s pedantic critique of my packages:
1. Some errant tab characters it doesn’t like,
2. Too many or too few continue
It is A Good Thing to regularize Authors and Maintainers of packages,
particularly for citation()
and toBibTex().
Could I add a suggested TODO item for the maintainer of package.skeleton
and friends to
help reinforce this for new packages:
- Please add appropriate templates for Author@R in th
Thank you Prof. Ripley for identifying the potential cause of the
warnings. From what Kurt says in his email, I can wait a little while
and see if the warnings for r-prerel go away in the future.
On Tue, 2007-04-10 at 21:58 +0200, Kurt Hornik wrote:
> > Prof Brian Ripley writes:
>
> > I only
On Apr 10, 2007, at 3:58 PM, Kurt Hornik wrote:
>> Prof Brian Ripley writes:
>
>> I only see analogue (sic), but is this not related to the
>> Encoding: UTF-8
>
>> ? Debian is very fond of subdividing packages, and I suspect it is
>> the standard glibc UTF-8 locale ("en_US.utf8") that is mis
> Prof Brian Ripley writes:
> I only see analogue (sic), but is this not related to the
> Encoding: UTF-8
> ? Debian is very fond of subdividing packages, and I suspect it is
> the standard glibc UTF-8 locale ("en_US.utf8") that is missing. There
> is an override for such people, to set R_E
I only see analogue (sic), but is this not related to the
Encoding: UTF-8
? Debian is very fond of subdividing packages, and I suspect it is the
standard glibc UTF-8 locale ("en_US.utf8") that is missing. There is an
override for such people, to set R_ENCODING_LOCALES, and looks like they
ha
On Sat, 2007-04-07 at 08:40 +0200, Kurt Hornik wrote:
> Dear maintainers of CRAN packages,
>
> This concerns the packages
>
> And now keep the updates rolling in ...
Dear R Developers,
I was recently emailed by the CRAN maintainers about warnings for my two
packages, analog and cocorresp, that
10 matches
Mail list logo
