Bug 195818 - wine-docs: broken FC3 -> FC4 upgrade path
wine-docs: broken FC3 -> FC4 upgrade path
Status: CLOSED NEXTRELEASE
Product: Fedora
Classification: Fedora
Component: wine-docs (Show other bugs)
4
All Linux
low Severity low
: ---
: ---
Assigned To: Andreas Bierfert
Fedora Extras Quality Assurance
:
Depends On: 179852
Blocks:
  Show dependency treegraph
 
Reported: 2006-06-18 03:41 EDT by Ville Skyttä
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-08-22 04:30:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ville Skyttä 2006-06-18 03:41:56 EDT
From https://www.redhat.com/archives/fedora-extras-list/2006-June/msg00749.html

wine-docs:
  3: 0:0.9.15-1.fc3 (FE3)
  4: 0:0.9.15-0.1.fc4 (FE4)
  5: 0:0.9.15-1.fc5 (FE5)
  6: 0:0.9.15-1.fc6 (FE6)

This is probably not at all critical since it's a doc package after all, but
should be fixed even if only to keep it off the broken upgrade paths report.
Comment 1 Ville Skyttä 2006-06-26 18:00:42 EDT
I see this was updated to 0.9.16, why not fix the upgrade path while at it?  I
don't see why bug 179852 should block such a simple fix.
Comment 2 Andreas Bierfert 2006-06-27 05:07:43 EDT
because ;)
The version number reflects that the FE4 build is just a ugly workaround nothing
more and nothing less and that other stuff needs to be fixed in order to get
this working. So actually I would rather stick with the FE3 version on an
FE3->FE4 upgrade then install the FE4 version (if you take a closer look
FE{3,5,6} specs are identical. So this is ok, at least from my pov. I would
rather want to know what is blocking the fix so we can get this build in a sane
fashion.
Comment 3 Andreas Bierfert 2006-08-22 04:30:21 EDT
K you won ;) 

Note You need to log in before you can comment on or make changes to this bug.