Thank you, much appreciated!
On Tue, Apr 23, 2024 at 1:08 PM Kern, Lori
wrote:
> I see it is now building and checking cleanly. We will un-deprecate the
> package.
>
> Lori Shepherd - Kern
>
> Bioconductor Core Team
>
> Roswell Park Comprehensive Cancer Center
>
> Department of Biostatistics &
Dear Ivan and Kasper,
Thanks very much for the helpful guidance. I made the changes you described,
including changing the version number (to 1.0.0), changing the URL codes to DOI
codes, using the tempfile() command when generating files, changing the license
to MIT (and excluding the license
> On Apr 24, 2024, at 12:52 AM, Hadley Wickham wrote:
>
>>
>>
>>
ALTREP is part of the official R api, as illustrated by the presence of
src/include/R_ext/Altrep.h. Everything declared in the header files in
>> that
directory is official API AFAIK (and I believe that is more
I see it is now building and checking cleanly. We will un-deprecate the
package.
Lori Shepherd - Kern
Bioconductor Core Team
Roswell Park Comprehensive Cancer Center
Department of Biostatistics & Bioinformatics
Elm & Carlton Streets
Buffalo, New York 14263
The deadline for fixing packages in preparation for the release is this Friday
April 26th. All packages should be installing, building, and checking without
ERROR in the Bioconductor build report. While you can continue to push changes
past this date, this ensures all changes are reflected in
Let me give partial assent to Michael's suggestion: a) have an easy way to
turn this on
and b) add a strong suggestion to do so to the WRE manual. Kurt's example in
the email
shows how to do (a); but I just looked in the WRE manual and don't see any
reference to
it, nor any mention from R
>
>
>
> > > ALTREP is part of the official R api, as illustrated by the presence of
> > > src/include/R_ext/Altrep.h. Everything declared in the header files in
> that
> > > directory is official API AFAIK (and I believe that is more definitive
> than
> > > the manuals).
> > >
> >
> > That is not
I might suggest adding a new ssh key to your BiocCredentials account as it
seems to be having issues with your key
Lori Shepherd - Kern
Bioconductor Core Team
Roswell Park Comprehensive Cancer Center
Department of Biostatistics & Bioinformatics
Elm & Carlton Streets
Buffalo, New York 14263
Thanks Gábor, rig add next installed 4.4.
Richard
On Tue, 23 Apr 2024 at 12:04, Gábor Csárdi wrote:
> The release candidate is R 4.4 currently. For Windows it is at
> https://cran.r-project.org/bin/windows/base/rtest.html, for macos it
> is at https://mac.r-project.org/
>
> If you use rig
All versions of Bioconductor are closely associated to a version of R to
ensure proper testing. We do not currently test packages outside the
current release and devel versions of Bioconductor. The current
Bioconductor release will always run on the current version of R. The
current
R-devel has switched to R 4.5 in prep for the official R 4.4 release
tomorrow (so it might be worth waiting a day) .
The Pre release R 4.4 release might also be designated something like
R-beta or R-rc (release candidate).
Lori Shepherd - Kern
Bioconductor Core Team
Roswell Park
Thank you very much, but still when I run: git push upstream main:devel, I get
the same error message:
error: cannot spawn https://github.com/cmeyring.keys: No such file or directory
error: cannot spawn https://github.com/cmeyring.keys: No such file or directory
fatal: unable to fork
Bioconductor does not have a main branch. Please refer to documentation
http://contributions.bioconductor.org/git-version-control.html
Bioconductor default branch is devel. If you have set up where your default
branch is main do to another remote (like github), You can map main to devel
Hello,
I submitted a package named zitools to Bioconductor. Now I want to committ he
updatest o Bioconductor.
However, this is not working.
My output of:
$ git remote -v
origin https://github.com/kreutz-lab/zitools.git (fetch)
origin https://github.com/kreutz-lab/zitools.git (push)
upstream
The release candidate is R 4.4 currently. For Windows it is at
https://cran.r-project.org/bin/windows/base/rtest.html, for macos it
is at https://mac.r-project.org/
If you use rig (https://github.com/r-lib/rig), you can run
rig add next
which works on Windows, macOS and Linux
G.
On Tue, Apr 23,
I am trying to install the devel version of R, however it seems that now on
CRAN the current version is 4.3.3 while the devel version is 4.5 so I'm not
sure where I can find 4.4.
[[alternative HTML version deleted]]
___
Bioc-devel@r-project.org
So the version of R depended on determines the version of Bioconductor that
the BBS will use when testing the package?
On Tue, 23 Apr 2024 at 04:41, Anatoly Sorokin wrote:
> Hi,
> You can even set 3.5 if your code working with that version of R, but
> BiocManager won't load the latest
Dear Isaac,
В Mon, 22 Apr 2024 17:00:27 +
"Petersen, Isaac T" пишет:
> This my first post--I read the posting guidelines, but my apologies
> in advance if I make a mistake.
Welcome to R-package-devel! You're doing just fine.
> 1) The first note <...> includes the contents of the LICENSE
> Michael Chirico writes:
Michael,
You may have seen that some time ago I added
check.R:cprof <- Sys.getenv("_R_CHECK_EXAMPLES_PROFILE_", "")
etc so one can use the _R_CHECK_EXAMPLES_PROFILE_ env var to specify a
profile to use when running the examples, e.g.
19 matches
Mail list logo
