Hi David,
I can take a look at your package later today on your Github and update the
version on Bioconductor if everything looks good.
The reason you are not able to push is because we prevent “force” pushes on the
bioconductor git server from maintainers.
Give me sometime and I’ll get back
I’m one of the maintainers of NanoStringDiff package on Bioconductor. Now I
want to update this package and add some useful functions. I’m using SVN,
but when committing, it gives me this error: The new canonical location for
Bioconductor software and
data experiment packages is
By example:
https://github.com/Bioconductor/KEGGREST-> github project homepage displays
https://github.com/Bioconductor/BrowserViz -> 404
Yet this works fine:
git clone g...@git.bioconductor.org:packages/BrowserViz.git
Is visibility at github.com/Bioconductor therefore conditional?
Paul,
My understanding was that the Bioconductor github repos were going to die,
and it was up to the maintainer where the source was, and a public source
need not be available. I asked about this previously, and there was too
much confusion between the official Bioconductor repos and developers
Hi Nitesh,
thanks a lot for your message. It makes perfect sense.
Best wishes,
Federico
> On 24 Jan 2018, at 17:33, Turaga, Nitesh
> wrote:
>
> Hi
>
> Only packages maintained by Bioconductor are at that location
> gitHub.com/Bioconductor. Your package is
Hi All,
I’m the maintainer of the ASSIGN package. It’s currently failing the devel
build and when I tried to push a fix for that I noticed that we have a lot of
duplicate commits in the history from a while back, I think from the git-svn
bridge.
I rebased and removed all of the duplicate
Hi Valerie,
the ssh key has now been setup and it works. I had some issues with merging but
at the end I decided to force BioC master to GitHub master (following
https://bioconductor.org/developers/how-to/git/abandon-changes/#force-bioconductor--to-github-