Bug 999397 - Broken upgrade from F19 -> F20
Summary: Broken upgrade from F19 -> F20
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager-pptp
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-21 09:18 UTC by Miroslav Suchý
Modified: 2016-04-21 10:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-21 10:18:49 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Miroslav Suchý 2013-08-21 09:18:54 UTC 
Description of problem:
In Fedora 19 is newer package than in Fedora 20. Which results in problems during upgrade:
Error: Package: 1:NetworkManager-pptp-gnome-0.9.8.2-3.fc19.x86_64 (@updates/19)
           Requires: NetworkManager-pptp = 1:0.9.8.2-3.fc19
           Removing: 1:NetworkManager-pptp-0.9.8.2-3.fc19.x86_64 (@updates/19)
               NetworkManager-pptp = 1:0.9.8.2-3.fc19
           Downgraded By: 1:NetworkManager-pptp-0.9.3.997-3.fc18.x86_64 (fedora)
               NetworkManager-pptp = 1:0.9.3.997-3.fc18


Version-Release number of selected component (if applicable):
Fedora 19: NetworkManager-pptp-gnome-0.9.8.2-3.fc19.x86_64
Fedora 20: NetworkManager-pptp-0.9.3.997-3.fc18.x86_64

How reproducible:
deterministic

Steps to Reproduce:
1. yum --releasever=rawhide distro-sync
Comment 1 Jaroslav Reznik 2015-03-03 14:59:31 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 2 Fedora Admin XMLRPC Client 2015-10-14 14:48:18 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 3 Lubomir Rintel 2016-04-21 10:18:49 UTC 
Fixed already.
Note You need to log in before you can comment on or make changes to this bug.