On Wed, Feb 17, 2021 at 07:57:11AM +0100, Andreas Tille wrote:
> On Fri, Feb 12, 2021 at 01:03:23PM -0500, Joshua N Pritikin wrote:
> > > I submitted a new release to CRAN yesterday. It usually takes a few days
> > > to correct any lingering issues and get it approved.
>
On Sat, Jan 30, 2021 at 08:31:51AM -0500, Joshua N Pritikin wrote:
> On Sat, Jan 30, 2021 at 06:32:48PM +0530, Nilesh Patra wrote:
> > Many thanks for fixes,
> >
> > The freeze has started and soft freeze time is near as well.(2 weeks
> > from now) OpenMx has removals
On Sat, Jan 30, 2021 at 06:32:48PM +0530, Nilesh Patra wrote:
> Many thanks for fixes,
>
> The freeze has started and soft freeze time is near as well.(2 weeks
> from now) OpenMx has removals of a bunch of packages from testing.
>
> Hence, please consider doing a new upstream release if it looks
On Thu, Dec 17, 2020 at 11:04:02AM +0100, Andreas Tille wrote:
> In case it will work at least on arm64 we could ignore armhf issues
> for the most practical use cases and exclude this architecture for
> Debian until it gets finally fixed.
Yeah, that sounds like a good solution. I don't anticipa
On Tue, Oct 06, 2020 at 04:07:59PM +0200, Andreas Tille wrote:
> While I could include this as a patch I wonder whether you plan to do a
> new release featuring this patch in the next couple of days. If this is
> the case I would wait for the new release with an upload to Debian.
Prior to the nex
On Tue, Oct 06, 2020 at 08:06:22AM +0200, Andreas Tille wrote:
> the version 2.18.1 of the openmx CRAN package that was build for Debian
> shows a test suite error on arm64 architecture. Here is an extract of
> the full test log[1] (if you want to inspect the full log I'd recommend
> to seek for s
6 matches
Mail list logo
