Wow.
On Mon, Dec 4, 2023, 5:43 PM Ivan Krylov wrote:
> Dear Artur,
>
> You've got a well-written package. There are some parts I wasn't able
> to understand (e.g. changing the class of a variable by reference using
> SET_CLASS and later changing it back), but there are no obvious places
> where
Dear Artur,
You've got a well-written package. There are some parts I wasn't able
to understand (e.g. changing the class of a variable by reference using
SET_CLASS and later changing it back), but there are no obvious places
where a mistake could be hiding.
On Fri, 1 Dec 2023 23:43:32 +
Artur
Thanks for your offer to providing us with capable multicore servers and
support staff for continuing support of recent Fedora systems.
Best,
Uwe Ligges
On 04.12.2023 18:09, andrew--- via R-package-devel wrote:
I do think that its a reasonable ask that the test machines be running
operating
I do think that its a reasonable ask that the test machines be running
operating systems within their vendor support periods.
-Andrew Robbins
From: R-package-devel on behalf of
Josiah Parry
Sent: Monday, December 4, 2023 11:34 AM
To: Tomas Kalibera
Cc: R Packa
Unfortunately, it is often important for us to pay attention to what
machines our code is being tested on.
I think the point is more or less that we often find ourselves trying to
make super small adjustments for machines and builds that are used by a
number of users in the single digits. The vast
On 12/4/23 15:44, SHIMA Tatsuya wrote:
Thanks for your answer.
Unlike Windows Server, which has a long support period, Fedora's
support period is usually about one year, so it is surprising that the
old Fedora continues to be used.
And, unlike Windows, Linux uses the distribution standard pa
Thanks for your answer.
Unlike Windows Server, which has a long support period, Fedora's support
period is usually about one year, so it is surprising that the old
Fedora continues to be used.
And, unlike Windows, Linux uses the distribution standard packages for
builds, which causes problems
On 03.12.2023 21:19, Sharon Bewick wrote:
I had this package included in a previous upload and it didn’t cause errors.
However, now it is getting flagged as an error. I’ve included biocViews:
phyloseq in the DESCRIPTION file, but that did not help. Unfortunately, I
cannot make phyloseq a we
CRAN knows about Bioconductor packages, so add phyloseq to Depends: , Imports:,
or Suggests: as appropriate.
These CRAN packages seem to Import phyloseq, for instance
> db = available.packages(repos = "https://cloud.R-project.org";)
> rownames(db)[grepl("phyloseq", db[,"Imports"])]
[1] "adaptive
I had this package included in a previous upload and it didn’t cause errors.
However, now it is getting flagged as an error. I’ve included biocViews:
phyloseq in the DESCRIPTION file, but that did not help. Unfortunately, I
cannot make phyloseq a weak dependency. It can be installed through
Bio
On 03.12.2023 16:12, Josiah Parry wrote:
Rafael,
I believe the issue is that packages cannot include binary *executables.* If
you have a binary file (such as a parquet file) in inst/extdata, I do not
think that would be a problem. It would be a good idea to ensure that that
file is small, tho
11 matches
Mail list logo
