[Bioc-devel] Committing changes to the release branch
Hi, I would like to make a bug fix to the oligoClasses release. I checked out a working copy of the release using the --username and --password options as suggested in the previous thread appended. However, I get the same error: svn: Commit failed (details follow): svn: Server sent unexpected return value (403 Forbidden) in response to CHECKOUT request for '/bioconductor/!svn/ver/50294/branches/RELEASE_2_7/madman/Rpacks/oligoClasses/DESCRIPTION' any suggestions? Thanks- Rob
On May 3, 2010, at 4:19 PM, Robert Castelo wrote:
Patrick, i tried now with username and password and it works smoothly, i must have been using the readonly user and password by default. sorry for bothering about this issue again, and thanks for your help! robert. On 5/3/10 8:59 PM, Patrick Aboyoun wrote:
Robert, I double-checked the svn authorization file and the BioC 2.6 qpgraph properties are properly specified and you are granted read/write permission. Could you perform the checkout using --username and --password with your username and password to ensure you are using the right account information? Other developers have been able to check into the BioC 2.6 branch, so this doesn't appear to be a global issue anymore. Patrick On 5/3/10 3:35 AM, Robert Castelo wrote:
hi Patrick, i was trying this morning also to update the main help page of my package at the release branch and got this error: svn: Commit failed (details follow): svn: CHECKOUT of '/bioconductor/! svn/ver/46404/branches/RELEASE_2_6/madman/Rpacks/qpgraph/DESCRIPTION': 403 Forbidden (https://hedgehog.fhcrc.org) the preceeding checkout command was: svn co https://hedgehog.fhcrc.org/bioconductor/branches/RELEASE_2_6/madman/Rpacks/qpgraph after which i modified the main help page of the package, the DESCRIPTION and the NEWS file and then i tried the checkin. i'm sorry if i missed anything from the previous discussion but i understood that i should be able to checkin change in the release :-? cheers, robert. On Thu, 2010-04-29 at 09:29 -0700, Patrick Aboyoun wrote:
I was looking into this issue and found it was a typo that was propagated throughout the svn permissions file. Please try committing your changes to the BioC 2.6 branch again. Sorry for the inconvenience. Cheers, Patrick On 4/29/10 6:55 AM, Seth Falcon wrote:
Hi, First, we will investigate the svn permission issues this morning and things going again. On 4/29/10 6:34 AM, Kasper Daniel Hansen wrote:
At this point I would like to highlight the final step on the Bioc HOWTO for updating the release branch: "Send a mail to the main bioconductor email list to announce the new version." It seems almost no-one - including the Biocore team - follows this. Should this requirement be removed (I don't think so personally, but since it is not adhered to, there is not much point in having it)?
This doesn't strike me as a very fair assessment. In many cases, changes are initiated due to discussion on the list and these threads are often resolved with a "fixed in release and devel available in 36hrs" sort of message. In any case, sending an email to the Bioconductor list to announce changes to release packages seems like a useful idea. I would encourage folks to follow it. + seth
_______________________________________________ Bioc-devel at stat.math.ethz.ch mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
_______________________________________________ Bioc-devel at stat.math.ethz.ch mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
_______________________________________________ Bioc-devel at stat.math.ethz.ch mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel