bug#45565: closed ([PATCH 0/2] Add more r-mlr3 add-ons)

[GNU bug Tracking System]

Your message dated Fri, 31 Dec 2021 20:20:53 +0100
with message-id <87lf00fujz.fsf@elephly.net>
and subject line Re: [bug#45565] [PATCH 0/2] Add more r-mlr3 add-ons
has caused the debbugs.gnu.org bug report #45565,
regarding [PATCH 0/2] Add more r-mlr3 add-ons
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
45565: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=45565
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> [PATCH 0/2] Add more r-mlr3 add-ons
>
>
>
>
> Date: 
>
> Thu, 31 Dec 2020 13:46:08 +0100
>
>
>
>
> A false alarm yesterday regarding the r-mlr3pipelines determinism. I
> confused the derivation hash with the build hash. As for r-mlr3ordinal,
> the linter reported
>
> ./gnu/packages/cran.scm:25616:15: r-mlr3ordinal@0.1.0-9000-0.9febac9: the 
> source file name should contain the package name
>
> I don’t know what “source file name” is referenced here, so I’m
> submitting the definition as it is.
>
> Wiktor Żelazny (2):
>   gnu: Add r-mlr3pipelines.
>   gnu: Add r-mlr3ordinal.
>
>  gnu/packages/cran.scm | 62 +++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 62 insertions(+)
>
>
> base-commit: 67497e20890348ebbd41612e2582b1745a80fec5
> -- 
> 2.29.2
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: [bug#45565] [PATCH 0/2] Add more r-mlr3 add-ons
>
>
>
>
> Date: 
>
> Fri, 31 Dec 2021 20:20:53 +0100
>
>
>
>
> User-agent: 
>
> mu4e 1.6.10; emacs 27.2
>
>
>
>
> Hi Wiktor,
>
> I’m terribly sorry for the delay.  These two patches are fine and
> slipped through the cracks.  I updated the packages to the new input
> style and pushed them to the “master” branch.
>
> > As for r-mlr3ordinal, the linter reported
> >
> > ./gnu/packages/cran.scm:25616:15: r-mlr3ordinal@0.1.0-9000-0.9febac9: the 
> > source file name should contain the package name
> >
> > I don’t know what “source file name” is referenced here, so I’m
> > submitting the definition as it is.
>
> This is due to the use of git-reference; you need to provide “file-name”
> to give a name to the source checkout.  I did this when I applied your
> patches.
>
> Thanks for these patches!
>
> -- 
> Ricardo
>
>
> --- End Message ---