Re: [Bioc-devel] Updating Package Issue

2024-04-02 Thread Kern, Lori via Bioc-devel
ws Sent: Tuesday, April 2, 2024 11:14 AM To: bioc-devel@r-project.org Subject: [Bioc-devel] Updating Package Issue Last week I updated my package to fix a build error and pushed the devel branch back to bioconductor, which I confirmed by cloning the devel branch on a different computer and I see my

[Bioc-devel] Updating Package Issue

2024-04-02 Thread Tallulah Andrews
Last week I updated my package to fix a build error and pushed the devel branch back to bioconductor, which I confirmed by cloning the devel branch on a different computer and I see my changes there. However, the multiplatform build is still using the wrong version (1.28, vs my corrected version 1.

Re: [Bioc-devel] updating package on the development version

2020-06-19 Thread Shepherd, Lori
To: bioc-devel@r-project.org Subject: [Bioc-devel] updating package on the development version Hi, I am trying to update previous release of my package (GISPA) on the development version. I pushed the changes and new release GISPA 1.13.1 following https://secure-web.c

[Bioc-devel] updating package on the development version

2020-06-18 Thread Dwivedi, Bhakti
Hi, I am trying to update previous release of my package (GISPA) on the development version. I pushed the changes and new release GISPA 1.13.1 following https://bioconductor.org/developers/how-to/git/sync-existing-repositories/ But, I do not see the change on the bioconductor development versi

Re: [Bioc-devel] Updating package via git fails

2019-10-24 Thread Spivakov, Mikhail
Sorry have realised I cloned with https! Many apologies. Mikhail From: "Spivakov, Mikhail" Date: Thursday, 24 October 2019 at 17:01 To: "bioc-devel@r-project.org" Subject: Updating package via git fails Hello! I’ve just made some changes to our Chicago package that help avoid some common er

[Bioc-devel] Updating package via git fails

2019-10-24 Thread Spivakov, Mikhail
Hello! I’ve just made some changes to our Chicago package that help avoid some common errors our users have encountered due to mis-specified parameters. I tried pushing the update to github (push origin master), but it fails with “fatal: remote error: FATAL: W any packages/Chicago nobody DENIED

Re: [Bioc-devel] updating package

2019-06-14 Thread Turaga, Nitesh
Hi, It seems like the email is configured correctly on BiocCredentials app. It is because the account is not activated it doesn't work. You'd have to first activate your account before moving forward with setting a password. I've added your GitHub credentials to the account. Best, Nitesh >

[Bioc-devel] updating package

2019-06-14 Thread ostrovni
Hi, I'd like to update my package Clonality https://bioconductor.org/packages/release/bioc/html/Clonality.html I used to do it through svn but as I understand it's not possible now. I can't connect it to my git page with updated package https://github.com/IOstrovnaya/Clonality When I enter my

Re: [Bioc-devel] Updating package development version

2017-08-18 Thread Hervé Pagès
Hi Pedro, The build system didn't pick up your changes because of an issue with the script that we use to propagate the latest package changes to the build machines. Sorry for that. The issue should be fixed now so hopefully you'll see CEMiTool 0.99.9 on tomorrow's build report (the report is upd

Re: [Bioc-devel] Updating package development version

2017-08-18 Thread James W. MacDonald
On Fri, Aug 18, 2017 at 1:46 PM, Pedro Russo wrote: > Dear maintainers, > > I've followed the tutorials for updating my package CEMiTool in the new Git > server as detailed in: > > https://www.bioconductor.org/developers/how-to/git/bug-fix- > in-release-and-devel/ > > including the steps > > git

[Bioc-devel] Updating package development version

2017-08-18 Thread Pedro Russo
Dear maintainers, I've followed the tutorials for updating my package CEMiTool in the new Git server as detailed in: https://www.bioconductor.org/developers/how-to/git/bug-fix-in-release-and-devel/ including the steps git checkout master git push upstream master git push origin master However,

Re: [Bioc-devel] Updating package

2017-01-05 Thread Martin Morgan
On 01/05/2017 01:25 PM, Charles Determan wrote: I committed my changes earlier this morning from the 'devel' branch via the 'git svn dcommit --add-author-from' the website (https://www.bioconductor.org/developers/how-to/git-mirrors/). I have yet to see any changes on the build page though for th

Re: [Bioc-devel] Updating package

2017-01-05 Thread Charles Determan
I committed my changes earlier this morning from the 'devel' branch via the 'git svn dcommit --add-author-from' the website ( https://www.bioconductor.org/developers/how-to/git-mirrors/). I have yet to see any changes on the build page though for the `devel` ( http://master.bioconductor.org/checkR

Re: [Bioc-devel] Updating package

2017-01-05 Thread Charles Determan
That seems to have been the issue. It had been some time since I needed to commit to bioconductor I forgot my username was different. Thank you Martin for pointing that simple problem out. I have now 'dcommit' my 'devel' branch so if I understand correctly the changes should be with bioconductor

Re: [Bioc-devel] Updating package

2017-01-05 Thread Martin Morgan
On 01/05/2017 10:18 AM, Charles Determan wrote: Not to be pushy but did anyone have any insights with this? I would hate to have my package still sitting with the bug fix it requires. maybe svn credentials, git svn rebase --username=c.determan ?? Thanks, Charles On Wed, Jan 4, 2017 at 1

Re: [Bioc-devel] Updating package

2017-01-05 Thread Charles Determan
Not to be pushy but did anyone have any insights with this? I would hate to have my package still sitting with the bug fix it requires. Thanks, Charles On Wed, Jan 4, 2017 at 11:15 AM, Charles Determan wrote: > Hi, > > I received a notification that my package was failing some tests. I have >

[Bioc-devel] Updating package

2017-01-04 Thread Charles Determan
Hi, I received a notification that my package was failing some tests. I have since made the necessary fixes and pushed my changes to the github repo. Previously this would result in http://gitsvn.bioconductor.org/git-push-hook updating the package for bioconductor. I noticed however that this de

[Bioc-devel] Updating package NEWS files for Bioconductor 3.3 release announcement (and biocViews)

2016-04-26 Thread Dan Tenenbaum
Package developers -- Each Bioconductor release is accompanied by release notes that mention new packages and other significant project developments. For the forthcoming release we will include release notes for individual packages, so that users have an easy way to survey changes in their favorit

[Bioc-devel] Updating package NEWS files for Bioconductor 3.2 release announcement (and biocViews)

2015-10-07 Thread Dan Tenenbaum
Package developers -- Each Bioconductor release is accompanied by release notes that mention new packages and other significant project developments. For the forthcoming release we will include release notes for individual packages, so that users have an easy way to survey changes in their favorit

[Bioc-devel] Updating package NEWS files for Bioconductor 3.1 release announcement (and biocViews)

2015-04-01 Thread Dan Tenenbaum
Package developers -- Each Bioconductor release is accompanied by release notes that mention new packages and other significant project developments. For the forthcoming release we will include release notes for individual packages, so that users have an easy way to survey changes in their favorit

Re: [Bioc-devel] Updating package NEWS files for Bioconductor 3.0 release announcement

2014-10-08 Thread Kasper Daniel Hansen
May I suggest that people use the new'ish NEWS.Rd format where the file is placed in inst/NEWS.Rd and the content is written using Rd format. Kasper On Wed, Oct 8, 2014 at 1:30 PM, Dan Tenenbaum wrote: > Package developers -- > > Each Bioconductor release is accompanied by release notes that

[Bioc-devel] Updating package NEWS files for Bioconductor 3.0 release announcement

2014-10-08 Thread Dan Tenenbaum
Package developers -- Each Bioconductor release is accompanied by release notes that mention new packages and other significant project developments. For the forthcoming release we will include release notes for individual packages, so that users have an easy way to survey changes in their favorit