[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#818989: marked as done (ITP: r-cran-r6 -- GNU R classes with reference semantics)

Your message dated Tue, 5 Apr 2016 15:03:47 +0200
with message-id <5703B7B3.6080909@chronitis.net>
and subject line 
has caused the Debian Bug report #818989,
regarding ITP: r-cran-r6 -- GNU R classes with reference semantics
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
818989: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818989
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist
Owner: Andreas Tille <tille@debian.org>

* Package name    : r-cran-r6
  Version         : 2.1.2
  Upstream Author : Winston Chang <winston@stdout.org>
* URL             : https://cran.r-project.org/web/packages/R6/
* License         : MIT
  Programming Lang: GNU R
  Description     : GNU R classes with reference semantics
 The R6 package allows the creation of classes with reference semantics,
 similar to R's built-in reference classes. Compared to reference
 classes, R6 classes are simpler and lighter-weight, and they are not
 built on S4 classes so they do not require the methods package. These
 classes allow public and private members, and they support inheritance,
 even when the classes are defined in different packages.


Remark: This package belongs to a pyramid of dependencies for r-cran-treescape
and will be maintained by the Debian Med team at
  svn://anonscm.debian.org/debian-med/trunk/packages/R/r-cran-r6/trunk/

--- End Message ---
--- Begin Message --- 
Package: r-cran-r6
Version: 2.1.2-1

Package is now in the archive.

--- End Message ---
Reply to: