Ticket #348 (closed defect: worksforme)

Opened 2 years ago

Last modified 1 year ago

packaging upgrades, 0.6 -> 0.7

Reported by: jsuttor Assigned to: ebrown
Priority: high Milestone:
Component: ambra Version: 0.7
Keywords: configuration, plosone Cc:
Blocking: Blocked By:

Description

per Russ:

When upgrading from 0.6 to 0.7 on a single box, topaz needs to be uninstalled before plosone can be upgraded, as /etc/topaz/topaz.xml causes a conflict. Conveniently, uninstalling topaz creates /etc/topaz/topaz.xml.rpmsave, and seems to preserve the lucene folder.

In /etc/topaz/topaz.xml, you have left the <server><http-port> element set to 8008 (the old topaz port), and hardcoded 8080 as the port in the <fedoragsearch> block. It strikes me that you might want to update <server><http-port> instead.

Also, is it possible that this could be the release where /etc/topaz/plosOne.xml has <app-context> left empty by default so that we don't have to keep removing this deprecated setting on each upgrade? CAS's global_config.ftl made this change awhile ago...

Dependency Graph

Change History

05/29/07 15:53:22 changed by jsuttor

  • owner changed from ebrown to jsuttor.
  • status changed from new to assigned.

05/29/07 15:53:40 changed by jsuttor

  • owner changed from jsuttor to ebrown.
  • status changed from assigned to new.

05/29/07 17:04:04 changed by amit

  • component changed from plos-one-testing to plos-one.
  • milestone changed from TBD to 0.7.

06/01/07 11:01:38 changed by ebrown

  • status changed from new to closed.
  • resolution set to worksforme.

This bug is no longer relevant with the new /etc/topaz/plosone.xml.

10/29/07 21:13:36 changed by

  • milestone deleted.

Milestone 0.7 deleted