,
Hiroaki Yutani
[1]: https://doc.rust-lang.org/nightly/rustc/platform-support.html
[2]: https://cran.r-project.org/package=cargo
[3]: https://cran.r-project.org/package=baseflow
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman
Sorry, I pointed a wrong package. I meant,
[2]: https://cran.r-project.org/package=gifski
[3]: https://cran.r-project.org/package=baseflow
Best,
Hiroaki Yutani
2021年8月5日(木) 8:17 Hiroaki Yutani :
>
> Hi,
>
> I recently submitted my package, which needs compilation of Rust code,
&g
So, probably no one knows the right answer...
Best,
Hiroaki Yutani
[1]: https://cran.r-project.org/web/checks/check_results_string2path.html
[2]: https://stat.ethz.ch/pipermail/r-package-devel/2021q3/007262.html
2021年9月24日(金) 23:50 Roy Mendelssohn - NOAA Federal via R-package-devel
:
>
> Hi All
ting quickly! Then, it seems I should wait for the
problem to be solved on systemfonts' side. I'm curious what's the
difference between r-devel-windows-x86_64-new-TK, on which the check
doesn't fail, by the way.
Best,
Hiroaki Yutani
2021年12月16日(木) 23:57 Uwe Ligges :
>
>
>
> On 16.12.202
version to avoid this test
failure. Note that, the other Windows r-devel machine
(r-devel-windows-x86_64-new-TK) doesn't fail. So, it might be just
that something is wrong with r-devel-windows-x86_64-new-UL.
Any suggestions?
Best,
Hiroaki Yutani
__
R
Thanks for the details and the suggestions. My package uses
systemfonts package for illustration purposes only in the examples, so
I'm not that desperate to find the root cause this time. I'll try
using winbuilder in case I need to.
Best,
Hiroaki Yutani
2021年12月17日(金) 0:52 Tomas Kalibera
Yes, it's my fault that I didn't consider the case when no fonts are
available. I'll improve the code until the next submission to CRAN.
Thanks for your advice!
Best,
Hiroaki Yutani
2021年12月17日(金) 1:40 Tomas Kalibera :
>
>
> On 12/16/21 5:16 PM, Hiroaki Yutani wrote:
> > Thanks
Hi,
I'm trying to create a Rust library that can implement an R graphic
device[1], but the R session crashes on `dev.off()` on Windows with R
4.1.2. Strangely, it works without errors on Linux, on macOS, and even
on Windows with R-devel.
Looking at the stack trace below by WinDbg, the problem is
I see, thanks. I filed here:
https://bugs.r-project.org/show_bug.cgi?id=18292
Best,
Yutani
2022年1月27日(木) 1:35 Tomas Kalibera :
>
> Hi Yutani,
>
> On 1/26/22 16:42, Hiroaki Yutani wrote:
> > Hi Tomas,
> >
> > Thanks, but, if I understand correctly, there'
but let me
hold off for a while.
Best,
Yutani
2022年1月27日(木) 0:21 Tomas Kalibera :
>
>
> On 1/26/22 15:44, Hiroaki Yutani wrote:
> > Hi Tomas,
> >
> > Thanks for your helpful advice. This time, it seems the cause of the
> > error was an allocator mismatch; I mistake
Simon,
> it's assumed that GitHub history is the canonical source with the
provenance, but that gets lost when pulled into the package.
No, not GitHub. You can usually find the ownership on crates.io. So, if you
want a target to blame, it's probably just a problem of the script to
auto-generate
pe the R community and the Rust community have
respect for each other.
Best,
Yutani
[1]: https://crates.io/crates/addr2line
[2]: https://github.com/gimli-rs/addr2line/blob/0.20.0/Cargo.toml
[3]:
https://doc.rust-lang.org/cargo/reference/manifest.html#the-authors-field
2023年8月27日(日) 12:07 Simon U
ntel macOS.
>
> Also. make sure that the authorship and copyright of code you download
> (and hence include in the package) is clear from the DESCRIPTION file.
> as required by the CRAN policy.
>
Best,
Hiroaki Yutani
[1]: https://cran.r-project.org/package=string2path
[2]:
https://g
ath/pull/35 (work in
progress)
2022年7月27日(水) 17:12 Tomas Kalibera :
>
> On 7/27/22 08:08, Tomas Kalibera wrote:
> >
> > On 7/27/22 00:30, Hiroaki Yutani wrote:
> >> Hi,
> >>
> >> Recently I got the following email from the CRAN maintainer about my
>
Hi,
I'm glad to see CRAN now has its official policy about Rust [1]!
It seems it probably needs some feedback from those who are familiar with
the Rust workflow. I'm not an expert, but let me leave some quick feedback.
This email is sent to the R-package-devel mailing list as well as to cran@~
so
em, because it's not
>> uncommon to use R in environments that have no Internet access, but the
>> download is a concession for extreme cases where the tar balls may be too
>> big to make it part of the package, but it's yet another can of worms...).
>>
>> Cheers,
&g
he tar balls may be too
> big to make it part of the package, but it's yet another can of worms...).
>
> Cheers,
> Simon
>
>
>
> > On 13/07/2023, at 12:37 PM, Hiroaki Yutani wrote:
> >
> > Hi,
> >
> > I'm glad to see CRAN now has its official policy about
Thank you for the correction. I see.
Best,
Yutani
2023年7月13日(木) 16:08 Tomas Kalibera :
>
> On 7/13/23 05:08, Hiroaki Yutani wrote:
> > I actually use cargo vendor.
> >
> >
> https://github.com/yutannihilation/string2path/blob/main/src/rust/vendor.sh
> >
> >
Simin,
Sorry that my question was not clear. Let me clarify.
I think we all agree that "cargo vendor" is the primary option. Since
downloading without explicit permission is not allowed on CRAN in general,
it's reasonable. I'm happy that the instructions will describe it clearly.
But, some R
Thanks so much for the quick response. It answered everything!
It was my mistake that I didn't consider these types of installations.
I'll fix my package as soon as I can.
Best,
Yutani
2023年7月10日(月) 17:51 Martin Maechler :
> >>>>> Hiroaki Yutani
> >>>>>
Hi,
My package, string2path, using Rust fails on the CRAN check of MKL [1],
with an error that seems irrelevant to MKL. The error says:
> thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value:
Os { code: 2, kind: NotFound, message: "No such file or directory" }',
.org/inside-rust/2023/01/30/cargo-sparse-protocol.html
[3]: https://packages.debian.org/testing/cargo (it seems 0.66 means 1.66)
2023年7月14日(金) 9:58 Hiroaki Yutani :
> Simin,
>
> Sorry that my question was not clear. Let me clarify.
>
> I think we all agree that "cargo
22 matches
Mail list logo
