Hello,
I am a maintainer of the ASpediaFI package.
Recently, I made few changes to the package and found the error in the
build report only for the Windows platform.
R CMD build and check ran without errors on my machine (Windows) and Linux
server as well, so I wonder what caused the error.
Th
The Bioconductor Team is continuing to identify packages that will be
deprecated in the next release to allow for the Bioconductor community to
respond accordingly. The list will be updated monthly. This is the current list
of deprecated packages for Bioc 3.11 :
Maintainer requested deprecation
The deadline for packages to pass R CMD build/check without error is Friday
April 24.
This ensures a build report with the committed changes.
The branch will be frozen Monday April 27th to branch for the Release of
Bioconductor 3.11.
Please see the release schedule for other important deadlin
The release 3.10 branch will be frozen April 14th All code changes should be
committed by April 13th. After this date there will be no updates to
Bioconductor 3.10 packages in Bioconductor.
Lori Shepherd
Bioconductor Core Team
Roswell Park Comprehensive Cancer Center
Department of Biostati
This is a reminder: The new package and docker image deadline is this Friday
April 3rd.
Please note: submission by this date does not guarantee it will be included -
the package must undergo an official review and be accepted by Wednesday April
22nd.
Some guidelines can be found at the foll
Hi Martin,
Thanks for your reply!
Best,
Carlos
Em seg., 30 de mar. de 2020 às 15:37, Martin Morgan
escreveu:
> Hi Carlos --
>
> Our Docker acceptance process is in it's infancy; please bear with us as
> we work through this. We'll process your contribution manually, so the
> issue has been re-o
Yes. I see the changes pushed this morning. They should be reflected on
tomorrow's build report.
Lori Shepherd
Bioconductor Core Team
Roswell Park Comprehensive Cancer Center
Department of Biostatistics & Bioinformatics
Elm & Carlton Streets
Buffalo, New York 14263
_
Hi Carlos --
Our Docker acceptance process is in it's infancy; please bear with us as we
work through this. We'll process your contribution manually, so the issue has
been re-opened and a reviewer assigned. Please follow up on the issue you've
opened.
https://github.com/Bioconductor/Contribut
Hello,
Yes thank you. I am very new on git and will definitively have a look.
However I think that I might have correctly pushed my changes to the
CNORfeeder and the CNORode packages. Can someone please confirm if that the
case? If not, I will carefully read the links before for the next time.
Be
Hi Enio,
Based on the conversation you, Lori and I had, it seems that you are having a
hard time with git as a version control system in general and not the
Bioconductor git repository in general.
Please consider going through some good learning material so you can get
started with git.
Ther
Please read the instructions on this document carefully, and follow the steps.
If in doubt, do NOT push but check your `git log`, and make sure everything is
as expected.
https://bioconductor.org/developers/how-to/git/sync-existing-repositories/
Best,
Nitesh
> On Mar 30, 2020, at 8:09 AM, R
That is asking you to make a commit message to summarize the changes. It is
traceable when you use git log. You should type a commit message summarizing
what you want to say
Lori Shepherd
Bioconductor Core Team
Roswell Park Comprehensive Cancer Center
Department of Biostatistics & Bioinfo
Hi,
Ok thank you. I do the commit as following: 'git commit -a #update
CNORfeeder' and then I get the following:
# Please enter the commit message for your changes. Lines starting
# with '#' will be ignored, and an empty message aborts the commit.
#
# On branch master
# Your branch is up to d
Hi everyone, hope you're all ok,
I found that the devel version was not synced up with my local/
personnal git version, even when I fetch merge and pull.
My local/personnal git are stucked to 1.1.0 and the devel is 1.1.1.
How could I force my git to 1.1.1 bioconductor version.
Best,
Raphael
I do not see any changes in the git.bioconductor.org server on the master
branch.
Did you remember to do the following to commit your changes before you tried
pushing?
git commit -a
In general a good basic workflow for working on the devel (master) branch is
git fetch --all
git pull
git pull
Hi,
Thank you very much. After following your suggestion I went to set up the
SSH and I was also able to clone the packages I was maintaining locally.
Next I did my desired changes to the cloned package locally and I wanted to
push these changes to the Bioconductor repositories. For that I used th
Hi all,
I am a co-maintainer of BitSeq. About a year ago, we were offered help
in migration from Rsamtools to Rhtslib and we took the offer.
The commit pushed by BioC team added a file src/bam_plbuf.c with just
one line:
#include
This is now making our Windows build fail because of an infi
17 matches
Mail list logo