DP4 Command Line Tools Update

Discussion in 'OS X Yosemite (10.10)' started by d21mike, Jul 21, 2014.

  1. d21mike macrumors 68040

    d21mike

    Joined:
    Jul 11, 2007
    Location:
    Torrance, CA
    #1
    DP4 Command Line Tools Update keeps coming up after I apply the update. I have done it 3 times now. Under Updates Installed in the Last 30 Days it is there 3 times. Seems to me I have seen this kind of problem before and after reboot it goes away but not this time.

    Anybody else see this and is there a way to stop it?
     
  2. grahamperrin, Jul 21, 2014
    Last edited: Jul 21, 2014

    grahamperrin macrumors 601

    grahamperrin

    Joined:
    Jun 8, 2007
    #3
    Please use Feedback Assistant at the time of the problem, i.e. when there next appears an invitation to install what you believe is already installed.

    You might experiment with the --forget command of pkgutil(1) but please refrain from that, or any other attempted workaround, until after feedback is sent.

    Be certain that when the update is re-offered – specifically, when there's the offer on screen and before you proceed – that the update is truly already installed. Look beyond the App Store interface, and so on.

    If you find that an apparently successful installation was not truly successful: I have a good idea of at least one situation where that behaviour can occur, but it can't be discussed here.
     
  3. tworkemon macrumors newbie

    Joined:
    Jul 15, 2011
    #4
    I had similar issues. To resolve you need to look to see if you have any existing/previous; CLTools,DeveloperToolsCLI,clang,llvm-gcc4,DevSKD_* "bom" files in /var/db/receipts. From there use "lsbom -fls" to read those files and remove the file outputs. This will remove any version of CLT you had prior. Then "rm" those "bom" files along with their corresponding "plist" file. Install latest CLT and that should fix your issue. If none of this makes sense to you, you probably shouldn't be using 10.10.

    **DO THIS AT YOUR OWN RISK**
     
  4. Tigrao macrumors member

    Joined:
    Jun 1, 2012
    #5
    This solution actually worked great for me. I removed the files referenced in the bom files, then removed the bom and plist files, and then manually downloaded and installed the latest command line tools package and installed it. The App Store no longer reports that an update is available.
     
  5. d21mike thread starter macrumors 68040

    d21mike

    Joined:
    Jul 11, 2007
    Location:
    Torrance, CA
    #6
    Thanks for your feedback. I do have those files but at this point I think I will wait to remove them. Since I am able to compile my code without any problems it is not worth the risk to create a problem for myself.
     

Share This Page