Bug 1343578 - package NetworkManager-l2tp-gnome-1.0.2-1.fc23.x86_64 requires NetworkManager-l2tp = 1.0.2-1.fc23, but none of the providers can be installed
Summary: package NetworkManager-l2tp-gnome-1.0.2-1.fc23.x86_64 requires NetworkManager...
Keywords:
Status: CLOSED DUPLICATE of bug 1342335
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager-l2tp
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ivan Romanov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-07 13:40 UTC by Basic Six
Modified: 2016-06-08 19:49 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-06-08 19:49:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Basic Six 2016-06-07 13:40:40 UTC
Description of problem:

There seems to be a dependency issue with NetworkManager-l2tp-gnome/NetworkManager-l2tp.


Version-Release number of selected component (if applicable):

Fedora 23.



How reproducible:

When running "dnf update". System can't be updated:

# dnf update --best --allowerasing
Last metadata expiration check: 0:45:22 ago on Tue Jun  7 14:47:34 2016.
Error: package NetworkManager-l2tp-gnome-1.0.2-1.fc23.x86_64 requires NetworkManager-l2tp = 1.0.2-1.fc23, but none of the providers can be installed

NetworkManager-l2tp had to be uninstalled (dnf erase NetworkManager-l2tp) to be able to update the system.



Steps to Reproduce:
1. dnf update



Actual results:

package NetworkManager-l2tp-gnome-1.0.2-1.fc23.x86_64 requires NetworkManager-l2tp = 1.0.2-1.fc23, but none of the providers can be installed



Expected results:

System update.



Additional info:

System update worked after uninstalling NetworkManager-l2tp.

Comment 1 Veteran 2016-06-07 16:16:11 UTC
This bug is a duplicate of #1342335

Comment 2 J. Randall Owens 2016-06-08 19:49:10 UTC

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


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