Skip Menu | Logged in as guest | Logout
 
Ticket metadata
The Basics
Id: 2960
Status: resolved
Priority: 4/0
Queue: vdt-internal
Custom Fields
Fixed in: 1.8.1
Fix scheduled: (no value)
People
Owner: Tim Cartwright
Requestors: Tim Cartwright
Cc:
AdminCc:
Reminders
New reminder:
Dates
Created: Mon Sep 10 15:21:05 2007
Starts: Not set
Started: Wed Sep 19 08:26:48 2007
Last Contact: Not set
Due: Not set
Closed: Wed Sep 19 08:26:48 2007
Updated: Wed Sep 19 08:27:09 2007 by cat
Links
Depends on: (Create)
Depended on by: (Create)
Parents: (Create)
Children: (Create)
Refers to: (Create)
Referred to by: (Create)

History Brief headers — Full headers
# Mon Sep 10 15:21:06 2007 cat - Ticket created [Reply] 
Subject: Make configure_voms look for existing VOs
Download (untitled) / with headers
text/plain 494b
When we update VOMS and VOMRS (using pacman), a bad thing happens. After the
old VOMS or VOMRS is uninstalled, and we have untarred the new one, we call the
configuration script. However, it configures only the VDT VO, regardless of the
VOs that actually existed before the update. We should modify the configuration
scripts to look for existing VOs (with data preserved in vdt-app-data) and, if
found, reconfigure them.

In each case, the magic function to modify is called build_vo_list().
# Mon Sep 10 15:24:14 2007 cat - Subject changed from 'Make configure_voms look for existing VOs' to 'Make configure_voms & _vomrs look for existing VOs'
# Wed Sep 19 08:26:48 2007 cat - Status changed from 'new' to 'resolved'
# Wed Sep 19 08:27:09 2007 cat - Fixed in 1.8.1 added