Dear all,
SourceForge is pushing out emails concerning the new SVN repository for
qooxdoo-contrib. Mind that in each mail they are using *my* user id for
the checkout (!), which is certainly not the way it should work. (Why
they are doing this is beyond me, but probably because I triggered the
update).
If you want to do a fresh checkout, try this command instead:
svn svn checkout --username=<your SF uid> \
svn+ssh://<your SF
uid>@svn.code.sf.net/p/qooxdoo-contrib/code/trunk
I was succesful doing this using my SF user id.
Changing an existing checkout also seems to work. Change to the
checkout's root directory and issue the command:
svn switch --relocate \
https://qooxdoo-contrib.svn.sourceforge.net/svnroot/qooxdoo-contrib/trunk/qooxdoo-contrib
\
https://svn.code.sf.net/p/qooxdoo-contrib/code/trunk/qooxdoo-contrib
(The first URL should match the "URL:" entry when you type 'svn info' in
the root directory). [1]
Commits should also be possible again. The new code browsing site [2]
seems to be broken. We'll keep you updated on any progress.
Please report any issues you come across.
Thanks,
T.
[1]
https://sourceforge.net/p/forge/community-docs/Repository%20Upgrade%20FAQ/#how-do-i-change-svn-to-point-to-the-new-repo
[2] https://sourceforge.net/p/qooxdoo-contrib/code/
On 02/13/2013 04:18 PM, thron7 wrote:
Reminder: Upgrade of qooxdoo-contrib to Allura is in progress.
SVN reads from the old repo still work. I've also made a small commit
which went through, but wouldn't bet that it'll make it through to the
new repo. So better hold back commits until the upgrade is finalized.
The new code browser still shows "Repo status: importing..." [1].
T.
[1] https://sourceforge.net/p/qooxdoo-contrib/code/?source=navbar
On 02/06/2013 06:14 PM, thron7 wrote:
Concerns: qooxdoo-contrib commiters and users of contributions
Hi all,
SourceForge is pushing out its new "Allura" hosting platform, so we
need to migrate our existing SF projects. We will start migrating the
*qooxdoo-contrib* project coming
Wednesday, Feb. 13, 2013, 15.00 CET
I hope this gives everybody enough time to prepare. Mind that SF
queues upgrade requests so that the actual changes might commence at
some later point in time. I don't know if and how project members
would be able to tell if the upgrade is going on. During the process
the project might be inaccessible. Please try to avoid any
modifications during that time.
Here is a list of how the various aspects of the project are affected
(according to SF docs).
Will be affected by the upgrade:
Meta-data (name, description, ...)
SVN repository
qooxdoo-contrib-commit mailing list (supposedly only web interface,
not functionality)
Will work unchanged:
Project summary page
File releases and download stats
IMPORTANT: SVN Repository URL
With the upgrade the URL to the SVN repository (currently
https://qooxdoo-contrib.svn.sourceforge.net/svnroot/qooxdoo-contrib)
WILL CHANGE, and all developers (i.e. people that can commit to
qooxdoo-contrib) will receive an email notification with the new URL
after the upgrade has finished. You will need to change the
corresponding setting in your local SVN checkout [1], or create a new
checkout.
IMPORTANT-2: This will also affect using contrib:// libraries in
qooxdoo projects
Accessing contributions in a project (with a "contrib://..." config
key) WILL STOP WORKING as the repository URL needs to be adapted in
the Generator as well. We'll be providing a patch for that, but need
to test that ourselves after the upgrade, so there might be some delay.
For *existing* projects a workaround for the latter issue is to
change the "contrib://..." URL in your config.json into a regular
file path pointing to a local copy of the contribution. You can use
the copy that has been downloaded automatically with earlier builds
of your project, but move it away from the cache directory so it
doesn't get deleted with a 'generate.py distclean' (Use a
'generate.py info' to find the download directory on your system).
There is also the "Download GNU tarball" facility of the old ViewVC
interface for each contribution (e.g.
http://qooxdoo-contrib.svn.sourceforge.net/viewvc/qooxdoo-contrib/trunk/qooxdoo-contrib/UploadMgr/trunk/
and look for "Download GNU tarball") to obtain a local copy of a
contribution.
Adding a *new* contrib to your project after the SF upgrade will only
work after applying the Generator patch.
Once this upgrade is accomplished we'll be addressing the migration
of the SF 'qooxdoo' project.
Cheers,
Thomas
[1] In the root of your working copy, 'svn switch --relocate <old
URL> <new URL>' should do the trick.
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
