Hi Kushal,
If you push changes without bumping the version of your package,
the update won't propagate.
You only bumped the version to 1.5.1 today so you need to wait
about 24 hours before seeing this reflected on the landing page
for CountClust.
Also please note that you did the version bump p
Oh, sorry for that.
It seems that I can push it.
Regards,
tiphaine
-Original Message-
From: Martin Morgan [mailto:martin.mor...@roswellpark.org]
Sent: 30 October 2017 17:17
To: Martin, Tiphaine ; bioc-devel@r-project.org
Subject: Re: [Bioc-devel] Push to both Bioconductor and GitHub for
Hi all,
I am the author and maintainer of the CountClust package. I recently
submitted an update (version 1.5.1) to the package through
Bioconductor Git and I can access this updated version when I clone the
source repository
git clone https://git.bioconductor.org/packages/CountClust
However, t
Please try again now.
The form asked for your svn id, but you provided your github id.
Martin
On 10/30/2017 04:21 PM, Martin, Tiphaine wrote:
Hi,
I tried to push my update to GitHub and Bioconductor.
I succeed to create my fork in my GitHub Id following this page (Pull upstream
changes).
Hi,
I tried to push my update to GitHub and Bioconductor.
I succeed to create my fork in my GitHub Id following this page (Pull upstream
changes). I then updated and pushed on GitHub my update, but I cannot for
bioconductor when I follow recommandation on this page (Sync an existing GitHub
Hi,
I tried to push my update to GitHub and Bioconductor.
I succeed to create my fork in my GitHub Id following this page (Pull upstream
changes). I then updated and pushed on GitHub my update, but I cannot for
bioconductor when I follow recommandation on this page (Sync an existing GitHub
Hi,
I tried to push my update to GitHub and Bioconductor.
I succeed to create my fork in my GitHub Id following this page
(http://bioconductor.org/developers/how-to/git/pull-upstream-changes/). I then
updated and pushed on GitHub my update, but I cannot for bioconductor when I
follow recomm
Hi,
I tried to push my update to GitHub and Bioconductor.
I succeed to create my fork in my GitHub Id following this page
(http://bioconductor.org/developers/how-to/git/pull-upstream-changes/). I then
updated and pushed on GitHub my update, but I cannot for bioconductor when I
follow recomma
Thanks Hervé and others for looking into this.
Leonard
On Sun, Oct 29, 2017 at 10:19 PM, Hervé Pagès wrote:
> Thanks Dario and Mike for looking into this.
>
> In the mean time I added makeTxDbFromEnsembl() for creating a TxDb
> object by querying directly an Ensembl MySQL server. Only lightly
>
Dear all,
I maintain the DEGraph and NCIgraph packages.
They are now fixed, my apologies for the inconvenience.
Best,
Laurent
2017-10-20 17:38 GMT+02:00 Hervé Pagès :
> Hi Paolo,
>
> FYI 3 days ago I contacted Gabriele Sale (maintainer of graphite
> and co-author of clipper) about this. See
The BioC 3.6 branch is now ready.
Remember, you always have access to 2 versions of your package in git: the
"release" and "devel" versions. The �release� branch is for bug fixes and
documentation improvements only. The �devel� branch is where normal development
should occur.
To continue using
Thanks Sean.
-- Fathi
Fathi Elloumi, PhD
Bioinformatics Software Engineer
Contractor CSRA
Developmental Therapeutics Branch
NIH/NCI/CCR
Phone: 240-760-6601
From: Sean Davis
Date: Monday, October 30, 2017 at 8:41 AM
To: "Elloumi, Fathi (NIH/NCI) [C]"
Cc: "Turaga, Nitesh" , Bioc-devel
Subjec
Hello BioC developers, We will be creating the Bioconductor 3.6 branch today in
about 30 minutes, around 11:30 am EST. Please stop all pushes/commits to
git.bioconductor.org before 11:30 am EST (3:30 UTC) and do not resume until
further notice. We will send another email when it is OK to resume
Once you push a version bump to the git server, it can take 12-24 hours for
the recent build report to reflect the changes.
The changes from Oct 26 are currently reflected on the
http://bioconductor.org/checkResults/devel/bioc-LATEST/MAIT/
The changes pushed on the 29 will either be reflected
It seems you have submitted a bad id and key to the form.
1. For GitHub ID, it needs to submit as `carleshf`, not `github.com/carleshf`.
2. the SSH key needs the `ssh-rsa` header in front of the key. It was submitted
without it.
Please resubmit.
Your entries need to be,
Email : carles.h
Hi,
You have to wait till tomorrow to see if you package builds successfully.
Hopefully your package builds, and there is a landing page.
Nitesh
> On Oct 30, 2017, at 6:57 AM, sergi.pic...@upc.edu wrote:
>
> Dear Nitesh,
>
> We were able to fix the error on MAIT under the bioc-devel off
Hi, Fathi.
On Fri, Oct 27, 2017 at 5:12 PM, Elloumi, Fathi (NIH/NCI) [C] <
fathi.ello...@nih.gov> wrote:
> Hi Nitesh,
>
> I started merging and updating package rcellminerData following the
> instructions here : https://bioconductor.org/developers/how-to/git/sync-
> existing-repositories/
>
> I h
Thank you, Peter, I will have a look!
On Sun, Oct 29, 2017 at 11:08 PM, Peter Hickey wrote:
> FYI I also began a project to support an additional backend;
> https://github.com/PeteHaitch/matterArray. It's incomplete and may not work
> with the current version of DelayedArray (it's ~3 months old a
Oh, I forgot an important point. Does the seed class need to contain
"Array"? What about "array"? I just remembered that I changed it to
"array" because I have no "Array" in my namespace.
On Mon, Oct 30, 2017 at 11:24 AM, Francesco Napolitano
wrote:
>
>
> Il 29/10/2017 22:45, Hervé Pagès ha scrit
Il 29/10/2017 22:45, Hervé Pagès ha scritto:
In particular, I'd like to read more about how to create a backend for
DelayedArray. Is there any documentation available beyond the
reference manual?
I'm guilty. I plan to remedy this ASAP. In the mean time I'll be glad
to help. Note that other peopl
20 matches
Mail list logo
