For those of us who aren't git wizards, this can be accomplished via:

git remote –v       <---- Shows the current repository URL – should be the one 
below

git remote set-url origin git://git.code.sf.net/p/pyxb/code

In the pyxb root directory…


From: Peter Bigot <big...@acm.org<mailto:big...@acm.org>>
Date: Wednesday, March 6, 2013 9:19 AM
To: "pyxb-users@lists.sourceforge.net<mailto:pyxb-users@lists.sourceforge.net>" 
<pyxb-users@lists.sourceforge.net<mailto:pyxb-users@lists.sourceforge.net>>
Subject: Re: [pyxb-users] SF project update scheduled for 2013-03-06

The project update has been completed.  Please follow-up here or by creating a 
trac ticket if you encounter problems.

git remote urls must be updated:

Old repository url: 
git://pyxb.git.sourceforge.net/gitroot/pyxb/pyxb<http://pyxb.git.sourceforge.net/gitroot/pyxb/pyxb>

New repository url: 
git://git.code.sf.net/p/pyxb/code<http://git.code.sf.net/p/pyxb/code>

Peter

On Mon, Mar 4, 2013 at 7:14 AM, Peter Bigot 
<big...@acm.org<mailto:big...@acm.org>> wrote:
SourceForge keeps badgering me to move the PyXB project to their new Allura 
platform, and if I don't do it manually some day it'll be done automatically, 
probably at a time that's extremely inconvenient.  Below is the text they 
provide as a description of what will happen.  As far as I can tell the primary 
effect will be a change to the git repository links, and the look-and-feel of 
the pages.

This update is supposed to be unrelated to the eventual need to move hosted 
applications like Trac from the SourceForge hosted environment into the project 
itself.  SourceForge has not yet finished the work that enables this move.

I plan to update the project platform on Wednesday.  I'll send a second message 
when that's done that will provide the new repo URLs.


Peter

Upgrading your project to the Allura platform gives you access to some great 
new features<https://sourceforge.net/p/allura/wiki/Features/>, including custom 
tracker fields, integrated wiki, blog and code browsing tools, threaded 
discussions, and more! Here are changes you can expect to see when you upgrade 
your project:

Will be upgraded
At this time, we are able to update the following aspects of your project:

  *   Meta-data (name, description, trove categories, etc)
  *   Members and permissions
  *   Project News
  *   Forums
  *   Hosted Applications and Project Web
  *   Virtual Host configuration and MySQL databases
  *   Git, Subversion, Mercurial, Bazaar and CVS repositories
  *   Mailing Lists
  *   Tracker data
  *   Project Donations*

Will not be upgraded
These items will not be moved to your upgraded project:

  *   Project Help Wanted<https://sourceforge.net/p/allura/tickets/4218/>
  *   SCM stats<https://sourceforge.net/p/allura/tickets/4618/>, Forum 
stats<https://sourceforge.net/p/allura/tickets/4906/>, Ticket 
stats<https://sourceforge.net/p/allura/tickets/4907/> & Traffic 
stats<https://sourceforge.net/p/allura/tickets/4908/>
  *   Trac will no longer integrate with SVN

Waiting for one of these features?
The links above will take you to our engineering ticket for that feature. On 
the ticket, click the "+" icon to vote for it, so we know it's important to 
your project.

Will work exactly the same
These items will continue to function they way they currently do:

  *   Project summary page
  *   File releases and download stats
  *   Project Reviews

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.

Once you click Upgrade, the upgrade will be scheduled and will begin shortly. 
Any changes made to your project while the upgrade is in progress may not be 
reflected in the upgraded project.

*If you have donations enabled, there will be a Donate link that will allow 
donations. However, it will be a direct link to the PayPal donation page, and 
individual donors will no longer be tracked or displayed.

Prior to upgrading, you can obtain a copy of your project's data as an XML file 
by clicking on the project name, selecting Project Admin » Features, then 
selecting XML Export.



------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
pyxb-users mailing list
pyxb-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pyxb-users

Reply via email to