Hide Forgot
Description of problem: dnf remove BackupPC erases libidn Version-Release number of selected component (if applicable): BackupPC-3.3.1-2.fc23.x86_64 How reproducible: dnf remove BackupPC Steps to Reproduce: 1. fresh fedora 23 setup 2. dnf remove BackupPC 3. services failed to start/etc Actual results: libidn erased with cold blood Expected results: Additional info: Last metadata expiration check performed 0:42:08 ago on Tue Mar 8 22:31:33 2016. Transaction ID : 33 Begin time : Tue Mar 8 22:35:25 2016 Begin rpmdb : 1857:d1549b5a5a165ac71ae967717e86dcea67e93a58 End time : 22:35:45 2016 (20 seconds) End rpmdb : 1831:ea67ac765119a373a43d9f25c91f6ab55fba6772 User : Anton Barsukov <iscsi> Return-Code : Success Command Line : remove BackupPC Transaction performed with: Installed dnf-1.1.6-2.fc23.noarch @updates Installed rpm-4.13.0-0.rc1.12.fc23.x86_64 @updates Packages Altered: Erase BackupPC-3.3.1-2.fc23.x86_64 @fedora Erase libidn-1.32-1.fc23.x86_64 @fedora Erase perl-Class-Singleton-1.5-3.fc23.noarch @fedora Erase perl-Date-ISO8601-0.004-12.fc23.noarch @fedora Erase perl-DateTime-Format-W3CDTF-0.06-11.fc23.noarch @fedora Erase perl-DateTime-Locale-0.46-3.fc23.noarch @fedora Erase perl-DateTime-TimeZone-1.95-1.fc23.noarch @updates Erase perl-DateTime-TimeZone-SystemV-0.009-5.fc23.noarch @fedora Erase perl-DateTime-TimeZone-Tzfile-0.010-3.fc23.noarch @fedora Erase perl-Dist-CheckConflicts-0.11-5.fc23.noarch @fedora Erase perl-Exporter-Tiny-0.042-4.fc23.noarch @fedora Erase perl-File-RsyncP-0.74-3.fc23.x86_64 @fedora Erase perl-List-MoreUtils-0.413-2.fc23.x86_64 @fedora Erase perl-Module-Implementation-0.09-5.fc23.noarch @fedora Erase perl-Module-Runtime-0.014-6.fc23.noarch @fedora Erase perl-Net-FTP-AutoReconnect-0.3-15.fc23.noarch @fedora Erase perl-Net-FTP-RetrHandle-0.2-14.fc23.noarch @fedora Erase perl-Params-Classify-0.013-14.fc23.x86_64 @fedora Erase perl-Params-Validate-1.22-1.fc23.x86_64 @updates Erase perl-Sub-Name-0.14-3.fc23.x86_64 @fedora Erase perl-Time-ParseDate-2015.103-1.fc23.noarch @updates Erase perl-Try-Tiny-0.22-6.fc23.noarch @fedora Erase perl-XML-Parser-2.44-3.fc23.x86_64 @fedora Erase perl-XML-RSS-1.56-3.fc23.noarch @fedora Erase perl-DateTime-Format-Mail-1:0.402.0-1.fc23.noarch @fedora Erase perl-DateTime-2:1.18-3.fc23.x86_64 @fedora
I think this is solver issue but don't sure.
This is a duplicate of #1222812
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.