Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=800526 --- Comment #13 from Kalev Lember <[email protected]> 2012-04-01 13:59:25 EDT --- (In reply to comment #12) > From what I understand, if I have the old seahorse, and if I install the new > seahorse-sharing , it will remove the old seahorse, that's all. Exactly, and this will also happen on package update: seahorse gets removed and replaced with seahorse-sharing. Yum has a nice wiki page that describes behaviour with Obsoletes: http://yum.baseurl.org/wiki/YumPackageUpdates If we consider a system with seahorse-3.0.0-1.fc15 installed and a repo with seahorse-3.4.0-1.fc17 and seahorse-sharing-3.4.0-1.fc17 available, there are 3 different ways to do the upgrade: a) Installed: seahorse-3.0.0-1.fc15 After distro update: seahorse-3.4.0-1.fc17 b) Installed: seahorse-3.0.0-1.fc15 After distro update: seahorse-3.4.0-1.fc17 seahorse-sharing-3.4.0-1.fc17 c) Installed: seahorse-3.0.0-1.fc15 After distro update: seahorse-sharing-3.4.0-1.fc17 Which one of these is desired here? What currently happens with the way Obsoletes are used in this package is option (c). -- 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. _______________________________________________ package-review mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/package-review
