Bug 618039

Summary:	Upgrade script broken
Product:	[Fedora] Fedora	Reporter:	Nick Bebout <nb>
Component:	horde	Assignee:	Nick Bebout <nb>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	j, nathanael, nb
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-07-25 19:42:15 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nick Bebout 2010-07-25 19:39:52 UTC

Adding this to bugzilla so I don't forget.

Nick

----

I'm not sure if this meets what you are looking for, but I just found
that updating Horde in EPEL (and Fedora) from version 3.2.x to 3.3.x is
broken.  The UPGRADING file says that you have to run

scripts/upgrades/2008-08-29_fix_mdb2_sequences.php

but it requires PEAR MDB2_Schema package installed.  That isn't even
packaged for Fedora (and then of course EPEL).

There isn't really a way to test for this, but it probably should be
noted that software upgrade instructions should at least be read, and
hopefully tested.  There are a number of things that I can think of that
this applies to, such as Horde (and other Horde pieces like IMP), RT,
and Mediawiki (there are often manual upgrade steps required for these
packages).

-- 
Chris Adams <cmadams>
Systems and Network Administrator - HiWAAY Internet Services
I don't speak for anybody but myself - that's enough trouble.

Comment 1 Nick Bebout 2010-07-25 19:41:14 UTC

I'll look at this when I get back from vacation a week from tomorrow.

Comment 2 Nick Bebout 2010-07-25 19:42:15 UTC

Oh there was already a bug.

*** This bug has been marked as a duplicate of bug 617894 ***