Bug 43976

Summary: Binary upgrade to 4.7R fails if package 'freetype2' or 'imake' is already installed
Product: Base System Reporter: Brian Candler <B.Candler>
Component: miscAssignee: Bruce A. Mah <bmah>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.7-RELEASE   
Hardware: Any   
OS: Any   

Description Brian Candler 2002-10-12 16:00:03 UTC 
I just tried to upgrade a 4.4 system to 4.7, and it failed because I had package freetype2-2.0.4 installed. In fact, after informing me of this fact, it then told me that "we couldn't even extract the bin distribution. This upgrade should be considered a failure and started from the beginning, sorry! The system will reboot now". That probably makes it seem more catastrophic than it actually was :-) After rebooting, removing that package, and reinstalling, I got the same thing again, but this time because of package "imake". After removing
that it was OK.

It seems that somewhere between 4.4 and 4.7, X moved into the package system (ah yes, I just found it in the release notes for 4.6). However it's maybe worth keeping a note in the errata or upgrade instructions, since normally I wouldn't expect the existence of any package in /usr/local to break a system upgrade.

Fix: 

Perhaps worth adding a note to the 4.7R errata

For future, change sysinstall to be able to replace a previously installed but older version of the same package?
Comment 1 Kris Kennaway freebsd_committer freebsd_triage 2003-07-13 01:37:49 UTC 
Responsible Changed
From-To: freebsd-bugs->bmah

Over to the errata maintainer to decide if this should still be added.
Comment 2 Bruce A. Mah freebsd_committer freebsd_triage 2003-08-15 16:08:15 UTC 
State Changed
From-To: open->closed

I've been thinking for awhile about how to document this.  It's not 
really an errata item for any release currently supported by the 
errata documents, so I'm going to (reluctantly) close this with a 
vague sense of guilt at not being able to do anything.