Bug 433742 - Unison incorrectly updated to incompatible version
Unison incorrectly updated to incompatible version
Status: CLOSED DUPLICATE of bug 433915
Product: Fedora
Classification: Fedora
Component: unison (Show other bugs)
8
All Linux
urgent Severity urgent
: ---
: ---
Assigned To: Gérard Milmeister
Fedora Extras Quality Assurance
: Reopened
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-02-20 23:37 EST by Stephen Warren
Modified: 2008-02-21 23:35 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-02-21 23:35:37 EST
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 Stephen Warren 2008-02-20 23:37:29 EST
Fedora 8 used to include Unison 2.13.

However, a recent update bumped the version to 2.27.57.

This new version is incompatible with the old version, and consequently this
update completely breaks all existing users of Unison.

Incompatible updates like this are only allowed in new releases of Fedora; they
should not be randomly incorporated into updates of existing Fedora versions.

Therefore, please urgently roll back the F8 (and earlier) packages to the old
version. F9 (devel) can happily updata.
Comment 1 Gérard Milmeister 2008-02-21 06:24:47 EST
Im am aware of that. However, this update has been requested by several people,
exactly because on other platforms the newer version is generally used. Two
Fedora boxes seem to synchronize as well after the update as before, so I
consider this not a bug.
Comment 2 Stephen Warren 2008-02-21 10:29:16 EST
No way, this is definitely a bug!

Your argument (That F8 doesn't need to inter-operate with anything other than
F8) is basically the same as Microsoft saying "hey, Windows inter-operates with
Windows, so who cares about standards?".

The correct way to handle this is to do as Cygwin did; have a different Unison
package for each incompatible version. Then, things don't break for existing
users, but users wanting the updated version can simply install the other package.

For example, have packages unison_2_13-$release and unison_2_27-$other_release.
Comment 3 Jonathan Underwood 2008-02-21 11:52:34 EST
Welcome to bleeding edge. NOTABUG.
Comment 4 Michael J. Chudobiak 2008-02-21 11:58:10 EST
I ran into this problem between F6 and F8 systems. However, the F8 rpm installs
just fine on F6. So, yes, NOTABUG...

- Mike
Comment 5 Yanko Kaneti 2008-02-21 12:15:58 EST
Bleeding egde??? Thats why you have the six months release cycle and rawhide. 
Major break of compatibility with an update to a stable release is insane.
Comment 6 Jonathan Underwood 2008-02-21 12:51:28 EST
Well, what does it break compatibility with ? Not F-7 as updates have been
pushed for that. F-6 is EOL. Fedora can't possibly keep compatibility with RHEL,
otherwise it wouldn't evolve. I'm not sure I see the problem here - please be
specific about what platforms it has broken compatibility with.
Comment 7 Les Mikesell 2008-02-21 14:31:00 EST
The more generic bug here is that yum won't re-install the working version when
a packager ships a newer update that turns out to be broken in real-world
situations.
Comment 8 Stephen Warren 2008-02-21 14:44:45 EST
You can do this to get the old version back:

wget
http://download.fedora.redhat.com/pub/fedora/linux/releases/8/Everything/i386/os/Packages/unison-2.13.16-3.fc6.i386.rpm

rpm --oldpackage -UvH unison-2.13.16-3.fc6.i386.rpm

You'll probably also want to edit /etc/yum.conf to add:

exclude=unison

so that "yum update" (or whatever mechanism you use) won't simply install the
new version again.
Comment 9 Andrew McNabb 2008-02-21 17:09:50 EST
I had the same problem.  This is definitely a bug.  Unison shouldn't get
upgraded until Fedora 9.
Comment 10 Andrew McNabb 2008-02-21 17:16:16 EST
By the way, since Unison requires matching versions, the RPM should allow
several versions to be installed at the same time.  You should be able to run
unison-2.13 or unison-2.27 to get either version.  It should be possible to have
both versions installed at the same time.  In any case, backwards incompatible
changes should only happen in the development repo.
Comment 11 Stephen Warren 2008-02-21 22:40:03 EST
I have created a compatibility package. See bug 433915 for the review request.

I intend to package this for FC-7, F-8, EPEL 4, EPEL 5, and devel.

Gérard, can you review this new package? Thanks.
Comment 12 Kevin Kofler 2008-02-21 23:35:37 EST

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

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