On Thu, Mar 15, 2018, at 11:26 AM, Hervé Pagès wrote:
>
> Just to clarify, all software packages are built and checked every
> night, independently of whether their version got bumped or not.
> The version bump only allows the modified package to propagate
> to the public repo and become available
On Sun, Mar 11, 2018, at 4:10 AM, Egon Willighagen wrote:
> But previously I learned that when you push
> something to the repository, you should bump the question, so currently I
> do this for every change I made, leaving a ridiculous number of minor
> release and really short NEWS entries...
I w
On Mon, Dec 4, 2017, at 12:55 PM, Turaga, Nitesh wrote:
> Hi Tyler,
>
> AFAIK, this is not possible. You need a local repository with valid
> credentials on that local machine to be able to push to the bioconductor
> server.
Too bad! I thought that since I had to upload my ssh public key to
gith
Hi,
I think I have set up proper access to the Bioconductor git repos, and
cloned the repos into a separate github repository. Bioconductor has my
ssh key, and I've also added this key to GitHub.
The only hitch in my development workflow is that my work network blocks
the SSH/git port, so I can't
On Wed, Mar 29, 2017, at 11:23 AM, Martin Morgan wrote:
> On 03/29/2017 09:32 AM, Vladimir Kiselev wrote:
> > Hi Wellinton,
> >
> > As far as I know if you wrap you shiny stuff into an R function that should
> > be enough. Then you can provide both non-interactive and interactive
> > functions and
ng up. We usually release a day or two
> after R does so we don't set a date until R has announced theirs. As
> soon as we know the R schedule we'll make an announcement on bioc-devel
> and the support site. I'll also post the new release schedule.
>
> Valerie
>
&
Hi,
Is there a deadline for for updates to packages for the next release
yet? The webpage hasn't been updated since October
(http://bioconductor.org/developers/release-schedule/), but I think
there is another release in April?
Best,
Tyler
--
plantarum.ca
__
Hi,
My flowPloidy package has been accepted into the devel branch, and I've
now received a warning about a build failure:
http://master.bioconductor.org/checkResults/3.4/bioc-LATEST/flowPloidy/malbec1-buildsrc.html
The error indicates that the flowPloidy vignette failed to compile,
because the f
On Wed, Oct 5, 2016, at 06:31 PM, Martin Morgan wrote:
>
> If your package is added to the repository after the release, then it is
> added to the 'devel' branch and any changes are introduced there for
> availability at the next release.
>
> Any user can opt for the 'devel' branch
>
> Once a
Hello,
I submitted a new package after the deadline, so I understand it won't
be available to users until the next release in 6 months (assuming it's
acceptable).
I'm not clear on what happens once a package is accepted into
Bioconductor. At that point, if I make changes, are they visible to
user
650
>
> Dan
>
>
> - Original Message -
> > From: "Tyler Smith"
> > To: "bioc-devel"
> > Sent: Tuesday, September 27, 2016 2:05:08 PM
> > Subject: [Bioc-devel] SSL connect error on package build machine
>
> > Hi,
> >
> > I'
Hi,
I've just submitted a new package. The automated build generated an
error which I think (?) is a problem on one of the build servers (SSL
connect error in querying the bioc-devel list). I'm not sure if I'm far
enough along in the process for my assigned human to be alerted to this,
or if they'
12 matches
Mail list logo
