On 01/10/2014 02:16, Richard Shaw wrote:

Hi Richard,

On Tue, Sep 30, 2014 at 8:10 PM, Bill Somerville <g4...@classdesign.com <mailto:g4...@classdesign.com>> wrote:

    On 01/10/2014 02:00, Richard Shaw wrote:
    In the yum-utils package there is a helper script called
    "package-cleanup" which can be used to find orphans (or other
    issues).

    $ package-cleanup --leaves

    But the list needs to be reviewed line by line because not all
    packages that lack dependencies should be removed, such as the
    kernel, which is not depended upon by another package :)
    Hmmm, tried that but it didn't pick up many of the packages that I
    thought it would. There were a bunch that I believe were orphaned
    when I upgraded with fedup from 18 to 20 but the Qt packages that
    were pulled in by the wsjtx install and all the 32-bit
    compatibility packages were not listed.


Well, sometimes it's just nomenclature :) With yum/rpm orphans are packages that no longer reside in an available repository so ALL locally installed packages will be in that list.
Yes sorry about that, I realized as soon as I clicked send that I should have said leaves rather than orphans.

After an upgrade you want to use the --problems and --dupes options to do some housekeeping.
OK, they list nothing.


    Sometimes yum remove seems to know what were installed as
    dependants other time it seems to forget and leave the leaves
    installed.


Well, it's basically that it works in one direction only. If you install a -devel package it will install all the required base packages, if you try to remove the -devel package it doesn't know you don't need the base packages anymore, but if you try to remove any of the base packages, it MUST remove the -devel package or there will be dependency issues.
OK, but what about chains of base packages. The Qt5 multimedia package requires several other packages and it was pulled in by installing wsjtx as "Dep-Install" yet none of them come up with 'package-cleanup --leaves' after I 'yum remove wsjtx'. So what is causing the Qt packages to hang around?

I've just run 'yum autoremove' and that has dropped the Qt 5 chain. Maybe I should have just run 'sudo yum autoremove wsjtx' in the first place.

It seems that the 32-bit compat libs are not handled properly by these tools as they never seem to get auto removed. I suppose they must be protected in some way.

Thanks,
Richard
73
Bill
G4WJS.
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to