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
(inactive) Epicopy #39
Comments
Hi @sean-cho Thanks for submitting your package. We are taking a quick The DESCRIPTION file for this package is:
|
AdditionalPackage: https://github.com/sean-cho/EpicopyData |
Can't build unless issue is open and '2. review in progress' label is present, or issue is closed and 'TESTING' label is present. |
Your package has been approved for building. Your package is 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: "skipped, ERROR". Please see the following build report for more details: http://bioconductor.org/spb_reports/Epicopy_buildreport_20160628185900.html |
Looks like you submitted the packages in reverse order -- should have started with the package that does not depend on the other. We'll sort this out manually, but probably not until tomorrow morning. |
Actually, can you be sure to add a web hoook to EpicopyData and then try to increment the version of EpicopyData to 0.99.1? |
Hi Martin, I pushed 0.99.1 to test the webhook. How should I reverse the order on the two packages? Thanks! |
OK, can you try posting a comment like the one above,
|
Actually just post a comment like that in the current issue (#39) |
AdditionalPackage: https://github.com/sean-cho/EpicopyData |
Hi @sean-cho, Starting build on additional package https://github.com/sean-cho/EpicopyData. IMPORTANT: Please read the instructions for setting up a The DESCRIPTION file of this additional package is:
|
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". Please see the following build report for more details: http://bioconductor.org/spb_reports/EpicopyData_buildreport_20160629155134.html |
OK, next issue -- I see that you're using git lfs. The single package builder is not equipped to use lfs, but the right solution is to enable it. Again this will take some work on our end, please be patient. |
Can you try to version bump EpicopyData again? git lfs should be enabled across build systems. |
Received a valid push; starting a build. Commits are: 4efc422 v 0.99.2 - LFS push. |
Just bumped. Thanks for helping me figure this out. |
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 following build report for more details: http://bioconductor.org/spb_reports/EpicopyData_buildreport_20160705184933.html |
One last version bump on the data package, removing Epicopy from the Suggests: field |
Received a valid push; starting a build. Commits are: 03b0ec4 V 0.99.3: Remove Epicopy from suggested packages. |
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". Please see the following build report for more details: http://bioconductor.org/spb_reports/EpicopyData_buildreport_20160708121616.html |
OK, the next steps are up to you -- address the issues in the build report, then bump & commit.
|
If you need help, please let me know. Otherwise, I'll close the issue in a couple of days. |
Hi Martin, Thanks for the feedback and for offering to help. I've made most of the changes you suggested. I'm trying to understand re-compressing the allNormals.rda. It was saved as a default .gz compressed file. I re-compressed as .bz, but I save a small amount (~17MB). Is this in line with your suggestion, or is there another specific re-compression process you were referring to? Thanks, |
I followed the suggestion in the build report and did
and then extracted the relevant file
and then EpicopyData/data/allNormals.rda is 400Mb rather than the original. |
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, WARNINGS, ERROR". Please see the following build report for more details: http://bioconductor.org/spb_reports/Epicopy_buildreport_20160802192656.html |
Received a valid push; starting a build. Commits are: c85590d 0.99.4: Fix getLRR example. |
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, WARNINGS, ERROR". Please see the following build report for more details: http://bioconductor.org/spb_reports/Epicopy_buildreport_20160802224622.html |
Received a valid push; starting a build. Commits are: da7088e 0.99.5: Various fixes. |
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, ERROR". Please see the following build report for more details: http://bioconductor.org/spb_reports/Epicopy_buildreport_20160803182733.html |
Received a valid push; starting a build. Commits are: 9ac2dee 0.99.6: Dependencies. |
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". Please see the following build report for more details: http://bioconductor.org/spb_reports/Epicopy_buildreport_20160814111418.html |
Hi Martin, Epicopy is not building because it is looking for EpicopyData -- do you know if I have to bump EpicopyData again? Thanks, |
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 following build report for more details: http://bioconductor.org/spb_reports/EpicopyData_buildreport_20160818163221.html |
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, WARNINGS, ERROR". Please see the following build report for more details: http://bioconductor.org/spb_reports/Epicopy_buildreport_20160818175623.html |
Hi -- I triggered a manual build of the EpicopyData and then Epicopy packages. It looks like your package is still far from ready to review. I suggest that you remove the github webhook, close this issue, continue developing your package on your own system, and when it is ready for review create a new issue. |
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, WARNINGS, ERROR". Please see the following build report for more details: http://bioconductor.org/spb_reports/Epicopy_buildreport_20160818184603.html |
OK I closed the issue; not a big deal, just start another when your package is building without warnings / errors under the 'devel' version of Bioconductor. |
Thanks Martin. |
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]'
the package source and all review commentary are visible to the
general public.
instructions. My package is consistent with the Bioconductor
Package Guidelines.
to the analysis and comprehension of high throughput genomic data.
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: