[darcs-users] darcs.net upgrade status

[Eric Kow]

Hi everybody,

Here's the status on the darcs.net upgrade.

We have to the latest version of Debian stable (i.e. from etch to
lenny).  There was a bit of trouble at first because of an out of memory
error (probably related to darcsit), but that was resolved with a
reboot.  Since the reboot, I have successfully installed the packages
from lenny and rebooted again.

So we're making progress!  Unfortunately, not everything is working
out smoothly...

Overview
--------
- :-)  web site (and darcs repos)
- :-)  wiki

- :-/  build system
- :-/  buildbot integration

- :-(  bug tracker
- :-(  upgrading from PostgreSQL 8.1 to 8.3

:-) Web site and wiki
---------------------
Meanwhile, the website seems to be running and fetching stuff over darcs
works.  I've also restarted gitit and it seems to be fine.

Note that the old Moin site broke, perhaps due to some kind of mismatch
between the old config file and the new Moin.  I opted not to deal with
this, and to disable test.darcs.net instead as well as remove the Debian
packages for Moin.  The old wiki is now gone completely.

:-/ Build system and buildbot integration
-----------------------------------------
We've gone from GHC 6.6 to GHC 6.8.2.  I'll need to install new
libraries and get darcs building again (not to mention the darcs
website).  I'll probably get to this last.

There's also a little hook that we use to tell the buildmaster
to start a new build.  I suspect that's gone and that we'll need
to do something to reinstate it.

:-( Roundup issues
-------------------
It looks like going from Etch to Lenny brought us from roundup 1.2.1
to 1.4.4.  I was pleased at first because the bug browser appeared to be
working, but poking a bit more at it reveals some errors

1. Bug tracker does not seem to accept updates via email or the web
   interface.  I attach a log.

2. Search is broken.

3. roundup-admin migrate (which I only thought to run late in the
   process

I've taken the web interface down for now and will bring it back up on
request.

Simon and Trent: any chance you could help with this?  I'll try to be
around tomorrow so that we can talk about this.

:-( Upgrading from PostgreSQL 8.1 to 8.3
----------------------------------------
One of the dpkg user friendly dialog boxes told me that I should install
the latest PostgreSQL and do

  pg_dropcluster --stop 8.3 main
  pg_upgradecluster 8.1 main

But this fails with "could not bind IPv4 socket: Cannot assign requested
address".

I got the friendly log message "Is another postmaster already running on
port 5433?" (5432 is being used for 8.1) but did not find anything that
seemed to be using that port.

I suppose this is not particularly urgent, but it would be nice to get
it done and over with.

One step at a time...

-- 
Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow>
PGP Key ID: 08AC04F9
-------------- next part --------------
$ roundup-admin migrate
Enter tracker home: /var/lib/roundup/trackers/darcs/
Traceback (most recent call last):
  File "/usr/bin/roundup-admin", line 3, in <module>
    run()
  File "/usr/lib/python2.5/site-packages/roundup/scripts/roundup_admin.py", line 38, in run
    sys.exit(tool.main())
  File "/usr/lib/python2.5/site-packages/roundup/admin.py", line 1529, in main
    ret = self.run_command(args)
  File "/usr/lib/python2.5/site-packages/roundup/admin.py", line 1428, in run_command
    self.db = tracker.open('admin')
  File "/usr/lib/python2.5/site-packages/roundup/instance.py", line 130, in open
    db.post_init()
  File "/usr/lib/python2.5/site-packages/roundup/backends/rdbms_common.py", line 234, in post_init
    save = save | self.upgrade_db()
  File "/usr/lib/python2.5/site-packages/roundup/backends/rdbms_common.py", line 284, in upgrade_db
    self.fix_version_4_tables()
  File "/usr/lib/python2.5/site-packages/roundup/backends/rdbms_common.py", line 311, in fix_version_4_tables
    self.add_class_key_required_unique_constraint(cn, klass.key)
  File "/usr/lib/python2.5/site-packages/roundup/backends/rdbms_common.py", line 567, in add_class_key_required_unique_constraint
    self.sql(sql)
  File "/usr/lib/python2.5/site-packages/roundup/backends/rdbms_common.py", line 165, in sql
    self.cursor.execute(sql)
psycopg.ProgrammingError: ERROR:  relation "_status_key_retired_idx" already exists

create unique index _status_key_retired_idx
            on _status(__retired__, _name)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osuosl.org/pipermail/darcs-users/attachments/20090713/7401a156/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://lists.osuosl.org/pipermail/darcs-users/attachments/20090713/7401a156/attachment-0001.pgp>