Showing 1-1 of 1 unresolved posts
1
Can we please have all Trac installs updated from 1.0 to 1.0.1? In r4654-deploy, I’ve updated the wporg-svn 0005 tag and migration script.
(In particular, http://trac.edgewall.org/changeset/11319 is needed to fix the rendering of attachments ending in *.diff.)
This Trac ticket is not loading: http://core.trac.wordpress.org/ticket/15058. Unicode error.
Looks to be some Genshi 0.7 weirdness. I downgraded to 0.6.1 and it’s working now.
We need a new VM on xen1.lax for archive.wordpress.org, which should have nginx-base but not PHP. A new wporg-archive role should have the bare minimum – just an nginx config that listens on archive.wordpress.org (SSL not needed) and serves up static files in /home/archive/public_html.
The SSH keys for coffee2code, otto42, and myself should be installed for the archive user. Ideally the user should have the ability do to the following:
(This has been discussed with and signed off by @barry)
To move this along I started the role, see r4661-deploy.
Can I have a new repository created, meta.svn.wordpress.org?
This will serve as a fresh, public repo for dotorg.svn. WP.org would eventually begin to leverage externals of meta, until eventually meta is the main checkout and dotorg is the extra stuff (like config, hyperdb, security, etc.). Its directory structure will ideally mimic dotorg.
Do you need a trac set up as well?
Nope. It will be added to core.trac for the time being.
Thus, it’s post-commit hook should be:
/usr/local/bin/trac-admin /home/trac/trac-environs/wp-core/ changeset added “meta” $2
No svnnotify at this time.
Sorry for the delay. https://meta.svn.wordpress.org/ is ready now.
Can the Trac Duplicates plugin running on core.trac please be activated for the GlotPress Trac?
After it is added, nothing will change. This is expected. I will then need to make some trac.ini changes before it actually works.
(I plan to have it activated on other Tracs soon as well, but there is a bug I need to fix first.)
enabled the trac duplicate plugin on glotpress.trac.wordpress.org
Can I please have the following SQL commands run against the Codex Mediawiki database?
stankea is discussing.
INSERT INTO interwiki (iw_prefix, iw_url, iw_local, iw_trans) VALUES ('wporgmake', 'http://make.wordpress.org/$1', 1, 0);
INSERT INTO interwiki (iw_prefix, iw_url, iw_local, iw_trans) VALUES ('wporglearn', 'http://learn.wordpress.org/$1', 1, 0);
This is designed to allow us to create external links and redirects to handbooks, which (will) live in WordPress on make.wordpress.org and learn.wordpress.org.
Implemented by @stankea. Confirmed as working: http://codex.wordpress.org/Automated_Testing?redirect=no.
Can I have a deploy on deploy repo r3965?
deployed, sorry for the delay
Can @markjaquith and I please have git installed on our sandboxes? We need it for some mirroring scripts, and I can benefit when working with some of our external libraries.
Howdy and happy new year! Santa has installed git on your sandboxes, and sorry for the delay 
In preparation for porting Trac from sqlite to MySQL, I would like a dump of the current DB for core.trac.wordpress.org. I will then run through the full conversion locally, document it, and script it for the eventual live transition. We’ll probably want to move a smaller Trac first to work out any kinks, so a dump of either code.trac or unit-tests.trac would also be good.
Dumped core (sounds funny) and wp-unit-tests. You can find them in /home/wporgdev/trac on your sandbox
We’re merging design.trac and unit-tests.trac into core.trac (but keeping separate SVN repos), taking advantage of Trac 0.12′s multi-repository support.
Everything is set up on Trac’s end, I just need two commands run:
trac-admin $ENV repository resync "tests" trac-admin $ENV repository resync "design"
… where $ENV would be the path to trac-environs/wp-core.
I then need two post-commit hooks, one on the unit-tests.svn repo, and the other on design.svn, both pointing to the wp-core environment:
trac-admin $ENV changeset added "design" $REV trac-admin $ENV changeset added "tests" $REV
design.trac (which has no tickets, etc.) can be killed off with this. unit-tests.trac should remain operational, as it has existing tickets. I’ll make it read-only like what we did with WordPress MU’s Trac once this is done.
I don’t *think* anything needs to change with core.svn’s post-commit hook.
Also, I am pretty sure that “design” and “tests” for the post-commit hooks can likely be their full SVN paths instead, so the same as core.svn’s post-commit hook.
I can set up svnnotify after.
Done by @stankea! Including svn notify for both. (Design is now also piped to wp-svn, like tests.)
Awesome.
Barry 4:00 am on May 20, 2013 Permalink | Log in to Reply
Done.