Hi Dirk,
On Sun, Jul 06, 2014 at 10:27:53AM -0500, Dirk Eddelbuettel wrote:
Yes, thanks -- it looks better now. I kept three tabs open on my desktop as
reminder to come back to this 'at some point' (and I may still write a script
to compare the CRAN status and what the Debian DB has -- mainly
Andreas, Don,
Home now after all that R conferencing in Italy and LA -- and thanks again to
Don for a lovely afternoon / early evening outing in LA.
On 30 June 2014 at 18:58, Andreas Tille wrote:
| I know that you checked since we had some conversation about this in
| rstudio WNPP. I told
On 25 June 2014 at 10:22, Andrei POPESCU wrote:
| Control: reassign -1 r-base-dev
|
| On Mi, 25 iun 14, 09:02:53, Andreas Tille wrote:
| Source: r-base-dev
| Severity: normal
|
| Hello,
|
| since debhelper compatibility level 9 some automatic test is approached
| if upstream provides
Hi Dirk,
On Mon, Jun 30, 2014 at 08:37:09AM -0500, Dirk Eddelbuettel wrote:
If a CRAN package fails 'R CMD check' it will not be on CRAN, ie not be
available as a source package.
For any given R package, you can always run R CMD check locally.
I think checking a source tarball and
On 30 June 2014 at 16:11, Andreas Tille wrote:
| I'm trying to implement checks for the binary packages to the best of my
Please write a 'new source available' check, or just use what debian/watch
already gives. And the QA pages. And and and. Dozens of your (ie teams)
packages are MONTHS and
Dear Dirk,
On Mon, Jun 30, 2014 at 09:44:45AM -0500, Dirk Eddelbuettel wrote:
On 30 June 2014 at 16:11, Andreas Tille wrote:
| I'm trying to implement checks for the binary packages to the best of my
Please write a 'new source available' check, or just use what debian/watch
already gives.
On 30 June 2014 at 17:04, Andreas Tille wrote:
| I would be really happy if you would not choose every communication with
| me as a chance to bring up the same topic. Moreover your claim is - at
| least currently - not true.
I tried more gentle suggestions in the past, it didn't work. For
On Mon, 30 Jun 2014, Dirk Eddelbuettel wrote:
If a CRAN package fails 'R CMD check' it will not be on CRAN, ie not
be available as a source package.
It would probably be good to run these at build time too, just in case a
package has local tests which fail because of a dependency which changed
Dear Dirk,
On Mon, Jun 30, 2014 at 10:18:27AM -0500, Dirk Eddelbuettel wrote:
On 30 June 2014 at 17:04, Andreas Tille wrote:
| I would be really happy if you would not choose every communication with
| me as a chance to bring up the same topic. Moreover your claim is - at
| least currently
Source: r-base-dev
Severity: normal
Hello,
since debhelper compatibility level 9 some automatic test is approached
if upstream provides some tests suite in a default way. You can also
add overrides to adapt to specific upstream way to run a test suite.
Since for building R packages cdbs is
Control: reassign -1 r-base-dev
On Mi, 25 iun 14, 09:02:53, Andreas Tille wrote:
Source: r-base-dev
Severity: normal
Hello,
since debhelper compatibility level 9 some automatic test is approached
if upstream provides some tests suite in a default way. You can also
add overrides to
11 matches
Mail list logo
