Hi Vivek,
Are you submitting a package and bumped its version in order to trigger
a new build? The build system used for the submission is the "Single
Package Builder" (SPB) and is not the same as the main builder used
for the daily builds (BBS). It would help if you could provide the link
to
Next time try to add a little more frame of reference (ie. I've submitted my
package brainImageR and the tracker build report is showing ERROR)
I cloned your repository and took a quick peak -
You are using roxygen2 to make your man files
So It looks like you updated the documentation in
Hi at bioc-devel,
I’ve tried a few times now to update the error reported in the build report.
I’ve pushed the fix to GitHub and bumped the version number, but the same error
message keeps coming back. Does anyone know how to fix this? I feel like a
reboot of some kind is needed.
ERROR
The package throwing error is*VariantAnnotation *(coming from function:
locateVariants). I checked it's build for the dev branch and indeed it's
broken. **
All right then I would remove version specification from my package and
I guess I'll wait for**VariantAnnotation to get fixed.
Best,
There is no cache; like users you get the 'current' version of the
package from the relevant repository. If your package used
concatenateObjects, then it needs to be updated. If your package is
broken through a third package, it needs to be fixed (perhaps it has
been but did not propagate, see
Hi All
Is there any build cache on bioc build system? I updated S4Vector and
IRanges in my dependencies and triggered a new build of my package, only
to find that this broke other dependencies due to renaming of function
`concatenateObjects ` to `bindRows` in S4Vector. Now I removed the
We encourage the communication on an issue and the assigned review to occur on
the issue tracker. Your reviewer could also provide some suggestions.
If possibly ideally the solution would be to provide a smaller example set so
that all the functions could be performed within the time
