New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GIGSEA #720
Comments
Hi @zhushijia Thanks for submitting your package. We are taking a quick The DESCRIPTION file for this package is:
|
A reviewer has been assigned to your package Learn what to expect IMPORTANT: Please read the instructions for setting |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. On one or more platforms, the build results were: "ERROR". Please see the build report for more details. |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. On one or more platforms, the build results were: "ERROR". Please see the build report for more details. |
Received a valid push; starting a build. Commits are: 4ec2775 modification for bioconductor |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. On one or more platforms, the build results were: "ERROR, WARNINGS". Please see the build report for more details. |
Received a valid push; starting a build. Commits are: 3a33da6 modification for bioconductor |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. On one or more platforms, the build results were: "skipped, ERROR, WARNINGS". Please see the build report for more details. |
Received a valid push; starting a build. Commits are: 1a9ff6d version |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. On one or more platforms, the build results were: "WARNINGS". Please see the build report for more details. |
Received a valid push; starting a build. Commits are: a8f824d modification for bioconductor |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. On one or more platforms, the build results were: "WARNINGS". Please see the build report for more details. |
Received a valid push; starting a build. Commits are: df4cd5b modification for bioconductor |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. On one or more platforms, the build results were: "skipped, ERROR, WARNINGS". Please see the build report for more details. |
Received a valid push; starting a build. Commits are: 80c31fd modification for bioconductor |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. On one or more platforms, the build results were: "WARNINGS". Please see the build report for more details. |
Received a valid push; starting a build. Commits are: 17bc62e modification for bioconductor |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. Congratulations! The package built without errors or warnings Please see the build report for more details. |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. Congratulations! The package built without errors or warnings Please see the build report for more details. |
Hi ShiJia, @zhushijia Please remove the Your package is close to being accepted. Thank you. Regards, |
Hi LiNk-NY, @LiNk-NY As suggested, I already removed the .Rproj.user folder, and added the .gitignore file. Best |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. On one or more platforms, the build results were: "WARNINGS". Please see the build report for more details. |
Received a valid push; starting a build. Commits are: 84a855b version |
Dear Package contributor, This is the automated single package builder at bioconductor.org. Your package has been built on Linux, Mac, and Windows. Congratulations! The package built without errors or warnings Please see the build report for more details. |
Hi ShiJia, @zhushijia Best regards, |
Your package has been accepted. It will be added to the Thank you for contributing to Bioconductor! |
The master branch of your GitHub repository has been added to Bioconductor's git repository. To use the git.bioconductor.org repository, we need an 'ssh' key to associate with your github user name. If your GitHub account already has ssh public keys (https://github.com/zhushijia.keys is not empty), then no further steps are required. Otherwise, do the following: See further instructions at https://bioconductor.org/developers/how-to/git/ for working with this repository. See especially https://bioconductor.org/developers/how-to/git/new-package-workflow/ to keep your GitHub and Bioconductor repositories in sync. Your package will be included in the next nigthly 'devel' build (check-out from git at about 6 pm Eastern; build completion around 2pm Eastern the next day) at https://bioconductor.org/checkResults/ (Builds sometimes fail, so ensure that the date stamps on the main landing page are consistent with the addition of your package). Once the package builds successfully, you package will be available for download in the 'Devel' version of Bioconductor using https://bioconductor.org/packages/GIGSEA If you have any questions, please contact the bioc-devel mailing list (https://stat.ethz.ch/mailman/listinfo/bioc-devel); this issue will not be monitored further. |
Hi Martin,
Yes, it has ssh public keys. Thank you very much for your help!
Best
Shijia
…On Wed, May 30, 2018 at 1:20 PM, Martin Morgan ***@***.***> wrote:
The master branch of your GitHub repository has been added to
Bioconductor's git repository.
To use the git.bioconductor.org repository, we need an 'ssh' key to
associate with your github user name. If your GitHub account already has
ssh public keys (https://github.com/zhushijia.keys is not empty), then no
further steps are required. Otherwise, do the following:
1. Add an SSH key to your github account
<https://help.github.com/articles/connecting-to-github-with-ssh/>
2. Submit your SSH key to Bioconductor
<https://git.bioconductor.org/BiocCredentials/>
See further instructions at
https://bioconductor.org/developers/how-to/git/
for working with this repository. See especially
https://bioconductor.org/developers/how-to/git/new-package-workflow/
https://bioconductor.org/developers/how-to/git/sync-existing-repositories/
to keep your GitHub and Bioconductor repositories in sync.
Your package will be included in the next nigthly 'devel' build (check-out
from git at about 6 pm Eastern; build completion around 2pm Eastern the
next day) at
https://bioconductor.org/checkResults/
(Builds sometimes fail, so ensure that the date stamps on the main landing
page are consistent with the addition of your package). Once the package
builds successfully, you package will be available for download in the
'Devel' version of Bioconductor using biocLite(\"GIGSEA\"). The package
'landing page' will be created at
https://bioconductor.org/packages/GIGSEA
If you have any questions, please contact the bioc-devel mailing list (
https://stat.ethz.ch/mailman/listinfo/bioc-devel); this issue will not be
monitored further.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#720 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFKtsYXtY7DMdgyjoREM4cCntn1MpA0Kks5t3tTAgaJpZM4TPAoV>
.
|
Hi Marcel,
I would like to submit the corresponding experimental data for the GIGSEA
package: https://github.com/zhushijia/GIGSEAdata
But the submission of GIGSEA has been accepted, and the issue has been
closed. So, may I ask whether I should open a new issue for the GIGSEAdata?
Thank you very much!
Best
Shijia
…On Wed, May 30, 2018 at 11:46 AM, Marcel Ramos ***@***.***> wrote:
Hi ShiJia, @zhushijia <https://github.com/zhushijia>
Thanks for making those changes.
Your package has been accepted.
Best regards,
Marcel
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#720 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFKtseUjNVmmGng3ypxz9HpDb7xvL31_ks5t3r7ugaJpZM4TPAoV>
.
|
Hi Martin,
I would like to submit the corresponding experimental data for the GIGSEA
package: https://github.com/zhushijia/GIGSEAdata
But the submission of GIGSEA has been accepted, and the issue has been
closed. So, may I ask whether I should open a new issue for the GIGSEAdata?
Thank you very much!
Best
…On Wed, May 30, 2018 at 1:20 PM, Martin Morgan ***@***.***> wrote:
Closed #720 <#720>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#720 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFKtsYXtY7DMdgyjoREM4cCntn1MpA0Kks5t3tTAgaJpZM4TPAoV>
.
|
Yes I suggest simply opening another issue. |
Hi Shijia, @zhushijia |
Got it! Thank you very much, Martin.
…On Wed, Jun 6, 2018 at 4:31 PM, Martin Morgan ***@***.***> wrote:
Yes I suggest simply opening another issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#720 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFKtsceqEyH5MDL7wuGy7cW7zBVAdVIIks5t6DwNgaJpZM4TPAoV>
.
|
Hi Marcel, no problem. Got it! Thank you very much!
Best
Shijia
…On Wed, Jun 6, 2018 at 4:31 PM, Marcel Ramos ***@***.***> wrote:
Hi Shijia, @zhushijia <https://github.com/zhushijia>
Sorry I missed your message.
It would've been better to submit both packages in one issue but now that
the issue is closed.
Please create another issue and submit it there.
Thanks!
Regards,
Marcel
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#720 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFKtsR3FljaMa2VKEojNlDz87WH_8g92ks5t6DwSgaJpZM4TPAoV>
.
|
Update the following URL to point to the GitHub repository of
the package you wish to submit to Bioconductor
Confirm the following by editing each check box to '[x]'
I understand that by submitting my package to Bioconductor,
the package source and all review commentary are visible to the
general public.
I have read the Bioconductor Package Submission
instructions. My package is consistent with the Bioconductor
Package Guidelines.
I understand that a minimum requirement for package acceptance
is to pass R CMD check and R CMD BiocCheck with no ERROR or WARNINGS.
Passing these checks does not result in automatic acceptance. The
package will then undergo a formal review and recommendations for
acceptance regarding other Bioconductor standards will be addressed.
My package addresses statistical or bioinformatic issues related
to the analysis and comprehension of high throughput genomic data.
I am committed to the long-term maintenance of my package. This
includes monitoring the support site for issues that users may
have, subscribing to the bioc-devel mailing list to stay aware
of developments in the Bioconductor community, responding promptly
to requests for updates from the Core team in response to changes in
R or underlying software.
I am familiar with the essential aspects of Bioconductor software
management, including:
months, for bug fixes.
(optionally via GitHub).
For help with submitting your package, please subscribe and post questions
to the bioc-devel mailing list.
The text was updated successfully, but these errors were encountered: