[Bug 433915] Review Request: unison2.13 - File synchronization tool (compatibility package)

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: unison2.13 - File synchronization tool (compatibility package)


https://bugzilla.redhat.com/show_bug.cgi?id=433915





------- Additional Comments From s-t-rhbugzilla at wwwdotorg.org  2008-03-16 02:35 EST -------
Kevin Fenzi wrote:
> 1. Current installs that have 'unison' installed. 
> 
> I would guess we would make the newest version in each dist
> "Provides: unison = %{version}-%{release}"
> This would upgrade current installs to the newest version for that dist. 

Yes, that's already in the specs. The new packages obsolete the existing
"unversioned" unison package in order to get it off the system so that the
alternatives links set up by the new packages will work.

> 2. Dist upgrades (ie, from f8 to f9 or f9 to f10)
> 
> The above would mean that if you had the newest unison package installed, 
> you could be upgraded to an incompatible version on dist upgrade. 
> Of course users could then simply install the 'unisonXYZ' to maintain
> compatibility.

Really? If I "yum install unison", I'll get "unison227-XXX" with these new
packages. Given this, won't unison227 be the thing yum looks for on
update/upgrade, and hence will stay installed. Does a package that provides
something really get removed and replaced with a different package just because
something different provides that?

New spec/SRPM coming up soon, once mock has finished updating my build root.
Sorry to take so long - had company visiting and a needy baby...

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.