tmccormi wrote on Tuesday, April 02, 2013:
SF
We’ve released a new version of our “forge” software. Encourage your project admin to upgrade to take advantage of all the new features.
Really, it’s time now…
-Tony
tmccormi wrote on Tuesday, April 02, 2013:
No interest in this I see…
sunsetsystems wrote on Tuesday, April 02, 2013:
There is interest and it will necessarily be done, the main issue is time and resources.
yehster wrote on Tuesday, April 02, 2013:
It’s annoying that the link to this page…
https://sourceforge.net/p/upgrade/
Isn’t included in the banner suggesting upgrading. (I saw this url when I pushed an official commit yesterday).
Note that the URLs used to access your code repositories will change, and an email will be sent to all project developers with the new URLs after the upgrade is complete.
At a minimum I suspect that the mirroring processes in place to update other repos like github will need to be updated
I’m guessing that the easiest thing for me in the future will be to create a new clone of the sourceforge repo with the new url on my local machine and work from that for when I want to make updates on sourceforge.
My day to day process when I’m using github should be unaffected.
https://sourceforge.net/p/allura/wiki/Features/#threaded-discussion-forums
I’m most excited about threaded forum discussions. Couldn’t tell, but hopefully there is a “sticky post” feature.
bradymiller wrote on Wednesday, April 03, 2013:
Hi,
In ongoing discussions with sourceforge on this to ensure nothing bad happens when we do this. It will be forced in Q1 of 2014 anyways. Just want to make sure myself or Rod are very available to do something if it goes awry. At this point, it sounds like the only thing that will require changing is links to the sourceforge repo (especially on the mirroring script). it appears that even the old forum links posts will indefinitely go to the migrated forum posts, which is very good news considering all the forum post links we have on the wiki.
-brady
OpenEMR
tmccormi wrote on Wednesday, April 03, 2013:
If there is anything I can do to help just holler
-Tony
yehster wrote on Wednesday, April 03, 2013:
it appears that even the old forum links posts will indefinitely go to the migrated forum posts, which is very good news considering all the forum post links we have on the wiki.
Sounds like the content will be preserved but the links will be temporarily broken.
Does it make sense to come up with an “Under Construction” type of banner to display on the wiki page while we transition? Is there a good way to identify the wiki pages which have links to the forum?
“worst case” scenario I see for the repo itself is that if something goes wrong/takes extra time, we won’t be able to commit into the canonical repository. People will still be able to continue their own work on github unaffected. Just no official changes can be published while any problem exists.
BTW, if you take a look at the Allura features page, you can very clearly see an “Edit” button on the forum screenshots 
bradymiller wrote on Saturday, April 06, 2013:
Hi,
The project upgrade button has been clicked, so in a few hours we should be upgraded. I’ll post the new sourceforge repo link when it’s done (again, this is only really used by the Integration Developers).
-brady
OpenEMR
bradymiller wrote on Saturday, April 06, 2013:
Ok,
The upgrade has happened and here is the message I got via email regarding the sourceforge repo, which - pasted below. Again, this will only effect the integration developers that are committing code to sourceforge; I have turned off the mirroring script for now until I fully understand the below message and incorporate it into the mirroring repo on my server
-brady
Your code repository in upgraded project openemr is now ready for use.
Old repository url: git://openemr.git.sourceforge.net/gitroot/openemr/openemr
New repository checkout command: git clone ssh://bradymiller@git.code.sf.net/p/openemr/code openemr-code
You should do a checkout using the new repository location. The old repository is read-only now.
For more detailed instructions on migrating to your new repo, please see https://sourceforge.net/p/forge/community-docs/Repository%20Upgrade%20FAQ/
arnabnaha wrote on Saturday, April 06, 2013:
Good Work done…Atleast we can now edit and delete the posts…
arnabnaha wrote on Saturday, April 06, 2013:
Testing
Arnab Naha
On Apr 7, 2013 1:21 AM, “Arnab Naha” arnabnaha@users.sf.net wrote:
Good Work done…Atleast we can now edit and delete the posts…
Upgrade of SF Projecthttps://sourceforge.net/p/openemr/discussion/202506/thread/9a9af0b4/?limit=25#1fb4
Sent from sourceforge.net because you indicated interest in
OpenEMR / Discussion / DevelopersTo unsubscribe from further messages, please visit
SourceForge.net: Log In to SourceForge.net
yehster wrote on Sunday, April 07, 2013:
I had to re-subscribe to the forums by hitting the envelope in the upper right corner for each of the three forums.
sunsetsystems wrote on Sunday, April 07, 2013:
So for the repository change I just did this:
git remote rm origin
git remote add origin ssh://sunsetsystems@git.code.sf.net/p/openemr/code
git fetch origin
Then it looks like I’m back in business. Seems right?
bradymiller wrote on Sunday, April 07, 2013:
Hi,
Got the repo and mirroring script working. As Rod did above, this worked for setting my write to sourceforge:
ssh://bradymiller@git.code.sf.net/p/openemr/code
And this is what I used in the mirroring script to read from sourceforge repo:
git://git.code.sf.net/p/openemr/code
I just changed these within the .git/config files in the local repos.
Again, this stuff is only pertinent for the Integration Developers. I have created a test commit to ensure everything is working which it is.
-brady
OpenEMR
bradymiller wrote on Sunday, April 07, 2013:
yehster,
Can you try to push a testing commit through sourceforge (just place a new line at the end of the README file or something like that). The permissions engine has completely changed and trying to set it up so you and Tony have the permissions to commit to the git repo.
thanks,
-brady
OpenEMR
yehster wrote on Sunday, April 07, 2013:
Insufficient permission pushing to sourceforge using the new URI
ssh://yehster@git.code.sf.net/p/openemr/code
As reported by git on my system below:
Counting objects: 9, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 544 bytes, done.
Total 5 (delta 4), reused 0 (delta 0)
error: insufficient permission for adding an object to repository database ./objects
fatal: failed to write object
error: unpack failed: unpack-objects abnormal exit
To ssh://yehster@git.code.sf.net/p/openemr/code
! [remote rejected] master -> master (n/a (unpacker error))
error: failed to push some refs to 'ssh://yehster@git.code.sf.net/p/openemr/code
’
yehster wrote on Sunday, April 07, 2013:
Testing email subscriptions. Not sure how to subscriber to all new posts. I just flagged this one thread for myself.
bradymiller wrote on Sunday, April 07, 2013:
Hi Kevin,
Try the commit now. Let me know if it is working.
thanks,
-brady
OpenEMR
yehster wrote on Sunday, April 07, 2013:
Push worked.
yehster wrote on Sunday, April 07, 2013:
Anybody else successfully getting email notifications? I thought maybe it was because it didn’t send updates posted by the subscriber, but I didn’t get an email from Brady’s post even though on the “discussions list” screen there’s a check mark for this discussion in the “mail icon column.”