https://bugzilla.redhat.com/show_bug.cgi?id=1143773 Michal Jaegermann <michal@xxxxxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |ASSIGNED Resolution|NOTABUG |--- Keywords| |Reopened --- Comment #2 from Michal Jaegermann <michal@xxxxxxxxxxxx> --- (In reply to Jitka Plesnikova from comment #1) > perl-PlRPC was not provided or required by perl rpm And that is here relevant how? A dependency was pulled out by an update of a perl package without making a dependant "obsolete". > It will be also removed, if somebody > installs perl-PlRPC, which works with the latest Perl, from third-party > repository. If you will look more carefully then this report is really about that perl-PlRPC was NOT removed and this is causing serious update problems. The package itself was pulled in by some dependencies in the past, now I cannot tell really why, and surely not installed on its own merits. If an update would really removed it you would not see any bug report about it. > Removing of the package was reported at > https://lists.fedoraproject.org/pipermail/devel/2014-June/199572.html So you propose that in case of update troubles an end user should wade through old archives of some mailing list on an off-chance that s/he will find there something which will shed some ligth? You cannot be serious. As you can find out from the report I managed to go around that obstacle; thank you very much. The worry is how a regular "Joe User" is supposed to do such thing. -- You are receiving this mail because: You are on the CC list for the bug. Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=nCaNLOi3yW&a=cc_unsubscribe -- Fedora Extras Perl SIG http://www.fedoraproject.org/wiki/Extras/SIGs/Perl perl-devel mailing list perl-devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/perl-devel
