Hi Junhui,
There is a separate log for checking if your package works without
suggested packages: in the StepReg results
The noSuggests title leads to:
https://www.stats.ox.ac.uk/pub/bdr/noSuggests/StepReg.out
Where you can see that it fails if a user don't have BiocStyle installed.
I don't know
tip. Out of interest, is there a way to make win/Mac
> builder run revdep checks?
>
> Writing: wyclif.substack.com
> Book: www.wyclifsdust.com
>
>
> On Thu, 8 Feb 2024 at 10:26, Lluís Revilla
> wrote:
>
>> Hi David,
>>
>> If you didn't increase the versio
Hi David,
If you didn't increase the version number it could happen that the old
version of the package was used (as CRAN might not be aware that there is a
new version).
The CRAN repository policy says: "Increasing the version number at each
submission reduces confusion so is preferred even when
Dear Uwe and the CRAN team,
Many thanks for maintaining the package for so long (>10 years!).
I see the latest changes are in some internal C code related to
updating the libxml2 library.
In CRAN's experience, is this the highest time consuming task?
I have some questions about how the
Hi Li Gen,
This NOTE is part of the new checks on CRAN to comply with its policy.
The error message was introduced in c85587 (2023/11/22), when
incorporating this suggestion
https://bugs.r-project.org/show_bug.cgi?id=18611.
You can see the changes and checks in the browser here:
Hi Dewey,
Currently there are several packages on a subfolder for human inspection.
I don't think you can do anything else: sending this email might help
drawing attention from your reviewer to your package.
There might be some issues in the package that you'll need to address, try
to find them
The reasons that CRAN has for this (from:
https://cran.r-project.org/src/contrib/PACKAGES.in) are:
X-CRAN-History: Archived on 2023-08-19 for policy violation.
Downloading on installation from github.
Unarchived on 2023-08-30.
X-CRAN-Comment: Archived on 2023-08-31 for policy violation.
.
Hi,
Are you referring to your package formods?
I see it was released the same Friday 17 and it is already on CRAN.
If this is not the package, it might be on the backlog of packages
submitted to CRAN.
You can check the queue at:
https://r-hub.github.io/cransays/articles/dashboard.html
Best,
Dear John,
I think the problem is that the package ggPMX is suggested, but
nlmixr2rpt isn't prepared for when it isn't available.
In such cases, a package shouldn't fail the checks.
>From the CRAN policies https://cran.r-project.org/web/packages/policies.html :
"A package listed in ‘Suggests’ or
Hi,
I can't read any vignettes of gcplyr in Firefox 109.0.1 from a Windows 10.
But sorry, I don't have any solution.
On Thu, 9 Feb 2023 at 21:18, Duncan Murdoch
wrote:
> On 09/02/2023 10:27 a.m., Mike Blazanin wrote:
> > Hi all, my package gcplyr has several vignettes which, from CRAN, appear
tually, I don’t really agree to have to resubmit, and
> my time for doing so is very limited. Maybe in the next few weeks or so.
> >
> > Best
> >
> > Carsten
> >
> >
> > Von: Lluís Revilla [mailto:lluis.revi...@gmail.com]
> > Gesendet: Donnerstag, 22
Hi Carsten,
This seems to be an unfortunate chain of events between different packages:
RcppMLPACK -> emstreeR -> wflo
Package RcppMLPACK was archived on 2021-12-20 as issues were not corrected
despite reminders.
This resulted in the package emstreeR being archived on 2021-12-20 as
requires
I'm ready to take over the package I will ask the CRAN team and
give them more details.
Many thanks to all.
Lluís Revilla
On Fri, 2 Jul 2021 at 08:38, Uwe Ligges wrote:
>
>
>
> On 01.07.2021 23:52, Duncan Murdoch wrote:
> > On 01/07/2021 3:11 p.m., Dirk Eddelbuettel wrote:
&
Thanks Uwe for answering,
I have a question related to changing maintainers.
What happens when the old/current maintainer does not respond to
emails or other methods of contact?
Would the new maintainer need to wait until the package is removed
from CRAN to submit it again?
Best,
Lluís
PS: Not
Hi all,
Some time ago, there was a question[1] about "how long is the average
waiting time when submitting a new package ("newbies") until you get a
manual reply or it's on CRAN, submitting an update with all OK before
it hits CRAN".
I have analyzed the data provided by cransays[2] (Many
bbrev", y="Ref_ID",
cex=1,gap=2.5,degree = 60,
canvas.xlim = c(-5, 5),
canvas.ylim = c(-3, 3),
grid.col = color.grid)
Hope you can solve it.
Cheers,
Lluís
On Thu, 5 Nov 2020 at 22:00, Pablo Fonseca wrote:
>
> Dear Lluís Revilla,
>
> Thank you very much for the com
Hi Pablo,
"The magick package is required to crop" is related to using
BiocStyle for your vignette. Not sure what causes it, but I reported
this error some time ago:
https://github.com/Bioconductor/BiocStyle/issues/77.
On related issues and on bioc-devel mailing list
Hi Anthony,
I stumbled with the same issue for a package I submitted recently, the
problem seems to be that LaTex doesn't know how to map this unicode
character to a typesetting.
My unicode character was \u2229 and I tried several ways to avoid this warning.
On the vignette built with knitr I
18 matches
Mail list logo
