Xeva : XEnograft Visualization & Analysis #968

gangeshberi · 2019-01-08T22:58:07Z

Update the following URL to point to the GitHub repository of
the package you wish to submit to Bioconductor

Repository: https://github.com/bhklab/Xeva

Confirm the following by editing each checkbox 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:

The 'devel' branch for new packages and features.
The stable 'release' branch, made available every six
months, for bug fixes.
Bioconductor version control using Git
(optionally via GitHub).

For help with submitting your package, please subscribe and post questions
to the bioc-devel mailing list.

bioc-issue-bot · 2019-01-08T22:58:08Z

Hi @gangeshberiuhn

Thanks for submitting your package. We are taking a quick
look at it and you will hear back from us soon.

The DESCRIPTION file for this package is:

Package: Xeva
Type: Package
Title: Analysis of patient-derived xenograft (PDX) data
Version: 1.0.0
Author: Arvind Mer, Benjamin Haibe-Kains
Maintainer: Benjamin Haibe-Kains <benjamin.haibe.kains@utoronto.ca>
Description: Contains set of functions to perform analysis of patient-derived xenograft (PDX) data.
License: Artistic-2.0
Encoding: UTF-8
RoxygenNote: 6.0.1
LazyData: true
VignetteBuilder: knitr
Suggests: BiocStyle, knitr, rmarkdown
Imports:
  methods,
  stats,
  utils,
  BBmisc,
  Biobase,
  plyr,
  stringr,
  graphics, 
  grDevices,
  ggplot2,
  ComplexHeatmap (>= 1.99.4),
  reshape2,
  PharmacoGx,
  foreach,
  parallel,
  doParallel,
  doSNOW,
  acepack,
  mgcv,
  Rmisc
Depends: R (>= 3.4)
biocViews: GeneExpression, Pharmacogenetics, Pharmacogenomics, Software, Classification, Cancer, Biomarker, Drug
BugReports: https://github.com/bhklab/Xeva/issues

Add SSH keys to your GitHub account. SSH keys
will are used to control access to accepted Bioconductor
packages. See these instructions to add SSH keys to
your GitHub account.

bioc-issue-bot · 2019-01-09T00:19:42Z

A reviewer has been assigned to your package. Learn what to expect
during the review process.

IMPORTANT: Please read the instructions for setting
up a push hook on your repository, or further changes to your
repository will NOT trigger a new build.

bioc-issue-bot · 2019-01-09T00:27:26Z

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: "ABNORMAL".
This may mean there is a problem with the package that you need to fix.
Or it may mean that there is a problem with the build system itself.

Please see the build report for more details.

bioc-issue-bot · 2019-01-09T12:33:47Z

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".
This may mean there is a problem with the package that you need to fix.
Or it may mean that there is a problem with the build system itself.

Please see the build report for more details.

bioc-issue-bot · 2019-01-09T14:52:17Z

Received a valid push; starting a build. Commits are:

357a3f9 changed version
264a706 updated Merge branch 'master' of github.com:bhkla...

bioc-issue-bot · 2019-01-09T14:52:17Z

Received a valid push; starting a build. Commits are:

357a3f9 changed version
264a706 updated Merge branch 'master' of github.com:bhkla...

bioc-issue-bot · 2019-01-09T14:52:53Z

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".
This may mean there is a problem with the package that you need to fix.
Or it may mean that there is a problem with the build system itself.

Please see the build report for more details.

bioc-issue-bot · 2019-01-09T14:53:25Z

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".
This may mean there is a problem with the package that you need to fix.
Or it may mean that there is a problem with the build system itself.

Please see the build report for more details.

bioc-issue-bot · 2019-01-09T14:53:57Z

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".
This may mean there is a problem with the package that you need to fix.
Or it may mean that there is a problem with the build system itself.

Please see the build report for more details.

gangeshberi · 2019-01-09T16:52:57Z

I have changed the version to 0.99.0 and the Github repository has the webhook installed and it seems to have triggered. But still, I am getting the same response "version bump required" from bioc-issue-bot.

mtmorgan · 2019-01-09T17:19:09Z

The version number at submission should have been 0.99.0. the next version 0.99.1, the next 0.99.2.

I think that you have used 0.99.0, but not 0.99.1, so I suggest that you change the version to that number.

That you have used a larger version number already MAY cause problems, and if so @lshep will provide assistance.

bioc-issue-bot · 2019-01-09T17:21:39Z

Received a valid push; starting a build. Commits are:

17c2993 Update DESCRIPTION

bioc-issue-bot · 2019-01-09T17:21:40Z

Received a valid push; starting a build. Commits are:

17c2993 Update DESCRIPTION

gangeshberi · 2019-01-09T17:26:48Z

@mtmorgan Thanks. Looks like it has worked.

bioc-issue-bot · 2019-01-09T20:23:46Z

Received a valid push; starting a build. Commits are:

970e175 Update DESCRIPTION

bioc-issue-bot · 2019-01-09T20:23:46Z

Received a valid push; starting a build. Commits are:

970e175 Update DESCRIPTION

bioc-issue-bot · 2019-02-21T16:51:19Z

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".
This may mean there is a problem with the package that you need to fix.
Or it may mean that there is a problem with the build system itself.

Please see the build report for more details.

bioc-issue-bot · 2019-02-21T16:51:52Z

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".
This may mean there is a problem with the package that you need to fix.
Or it may mean that there is a problem with the build system itself.

Please see the build report for more details.

bioc-issue-bot · 2019-02-21T17:06:00Z

Received a valid push; starting a build. Commits are:

f83523b version 0.99.3

bioc-issue-bot · 2019-02-21T17:06:01Z

Received a valid push; starting a build. Commits are:

f83523b version 0.99.3

lshep · 2019-02-21T17:07:24Z

Hey - It looks like you guys are actively pushing commits and there is still something going very very wrong - Would you be interesting in video chatting/sharing so we can see what you are doing and how your repository settings are set up so we can try to figure out the root of the problem?
@gangeshberiuhn We could send a link to a virtual meeting spot

spocks · 2019-02-21T17:17:22Z

Hi @lshep Once I had version error in build report. But now the last report it says "Git clone Failed". @gangeshberiuhn could you look into it?

bioc-issue-bot · 2019-02-21T17:48:00Z

Received a valid push; starting a build. Commits are:

fa46656 version 0.99.4

bioc-issue-bot · 2019-02-21T17:48:00Z

Received a valid push; starting a build. Commits are:

fa46656 version 0.99.4

bioc-issue-bot · 2019-02-21T17:52:45Z

Received a valid push; starting a build. Commits are:

b528857 0.99.5

bioc-issue-bot · 2019-02-21T17:52:45Z

Received a valid push; starting a build. Commits are:

b528857 0.99.5

bioc-issue-bot · 2019-02-21T17:53:39Z

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".
This may mean there is a problem with the package that you need to fix.
Or it may mean that there is a problem with the build system itself.

Please see the build report for more details.

bioc-issue-bot · 2019-02-21T17:54:14Z

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".
This may mean there is a problem with the package that you need to fix.
Or it may mean that there is a problem with the build system itself.

Please see the build report for more details.

bioc-issue-bot · 2019-02-21T17:54:47Z

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".
This may mean there is a problem with the package that you need to fix.
Or it may mean that there is a problem with the build system itself.

Please see the build report for more details.

bioc-issue-bot · 2019-02-21T17:55:19Z

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".
This may mean there is a problem with the package that you need to fix.
Or it may mean that there is a problem with the build system itself.

Please see the build report for more details.

bioc-issue-bot · 2019-02-21T17:55:52Z

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".
This may mean there is a problem with the package that you need to fix.
Or it may mean that there is a problem with the build system itself.

Please see the build report for more details.

bioc-issue-bot · 2019-02-21T17:56:54Z

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, skipped, ERROR".
This may mean there is a problem with the package that you need to fix.
Or it may mean that there is a problem with the build system itself.

Please see the build report for more details.

lshep · 2019-02-21T18:15:47Z

Okay I think we are set on our end for you to try and create a new issue for this. Thank you again for being so understanding

gangeshberi · 2019-02-21T18:17:03Z

Thanks. I will create a new for this.

gangeshberi · 2019-02-21T18:28:25Z

Hey, Will it be creating any conflict if we open a new issue with the same name as of a closed Issue?

lshep · 2019-02-21T18:29:24Z

It shouldn't because I deleted it from the database of issues - but if there is let me know

gangeshberi · 2019-02-21T18:31:36Z

Cool. Thanks.

gangeshberi · 2019-02-21T18:36:53Z

I have created a new Issue.

spocks · 2019-02-21T19:13:00Z

@lshep we have created a new issue at #1022

lshep · 2019-02-21T19:16:29Z

Yes, thank you - once @mtmorgan puts it into a queue we can monitor what happens when you push changes - If it is still problematic when you guys try to push versions, I'll take over reviewing the package as I can push a manual build when necessary so you can get accurate build reports -

bioc-issue-bot added the 1. awaiting moderation label Jan 8, 2019

bioc-issue-bot added 2. review in progress assign a reviewer and a more thorough review of package code and documentation taking place and removed 1. awaiting moderation labels Jan 9, 2019

bioc-issue-bot assigned dvantwisk Jan 9, 2019

bioc-issue-bot added ABNORMAL VERSION BUMP REQUIRED labels Jan 9, 2019

bioc-issue-bot added ERROR and removed ABNORMAL VERSION BUMP REQUIRED labels Jan 9, 2019

bioc-issue-bot added the VERSION BUMP REQUIRED label Jan 9, 2019

bioc-issue-bot removed the VERSION BUMP REQUIRED label Jan 9, 2019

bioc-issue-bot added the VERSION BUMP REQUIRED label Jan 9, 2019

bioc-issue-bot removed the VERSION BUMP REQUIRED label Jan 9, 2019

bioc-issue-bot removed the ABNORMAL label Feb 21, 2019

bioc-issue-bot added the VERSION BUMP REQUIRED label Feb 21, 2019

bioc-issue-bot removed the VERSION BUMP REQUIRED label Feb 21, 2019

bioc-issue-bot added the WARNINGS label Feb 21, 2019

lshep closed this as completed Feb 21, 2019

lshep removed the 2. review in progress assign a reviewer and a more thorough review of package code and documentation taking place label Feb 21, 2019

Xeva : XEnograft Visualization & Analysis #968

Xeva : XEnograft Visualization & Analysis #968

Comments

gangeshberi commented Jan 8, 2019

bioc-issue-bot commented Jan 8, 2019

bioc-issue-bot commented Jan 9, 2019

bioc-issue-bot commented Jan 9, 2019

bioc-issue-bot commented Jan 9, 2019

bioc-issue-bot commented Jan 9, 2019

bioc-issue-bot commented Jan 9, 2019

bioc-issue-bot commented Jan 9, 2019

bioc-issue-bot commented Jan 9, 2019

bioc-issue-bot commented Jan 9, 2019

gangeshberi commented Jan 9, 2019

mtmorgan commented Jan 9, 2019

bioc-issue-bot commented Jan 9, 2019

bioc-issue-bot commented Jan 9, 2019

gangeshberi commented Jan 9, 2019

bioc-issue-bot commented Jan 9, 2019

bioc-issue-bot commented Jan 9, 2019

bioc-issue-bot commented Feb 21, 2019

bioc-issue-bot commented Feb 21, 2019

bioc-issue-bot commented Feb 21, 2019

bioc-issue-bot commented Feb 21, 2019

lshep commented Feb 21, 2019 • edited Loading

spocks commented Feb 21, 2019

bioc-issue-bot commented Feb 21, 2019

bioc-issue-bot commented Feb 21, 2019

bioc-issue-bot commented Feb 21, 2019

bioc-issue-bot commented Feb 21, 2019

bioc-issue-bot commented Feb 21, 2019

bioc-issue-bot commented Feb 21, 2019

bioc-issue-bot commented Feb 21, 2019

bioc-issue-bot commented Feb 21, 2019

bioc-issue-bot commented Feb 21, 2019

bioc-issue-bot commented Feb 21, 2019

lshep commented Feb 21, 2019

gangeshberi commented Feb 21, 2019

gangeshberi commented Feb 21, 2019

lshep commented Feb 21, 2019

gangeshberi commented Feb 21, 2019

gangeshberi commented Feb 21, 2019

spocks commented Feb 21, 2019

lshep commented Feb 21, 2019

lshep commented Feb 21, 2019 •

edited

Loading