Removing a corrupt patch

From: Iain Barker (ibarker_at_aastra.com)
Date: 06/15/04

  • Next message: Siebert, Aaron: "Failed udp response" 
    Date: Tue, 15 Jun 2004 10:40:30 -0400
To: tru64-unix-managers@ornl.gov

    I've got a system on which the ssh patch partially applied, and now ssh doesn't work.

    (T64KIT0020964-V51BB24-ES-20031204.tar, patch OSFPATC0040901540 number C409.01 on Tru64_UNIX_V5.1B)

    Using setld I can see the patch is present, but is not in the correct "installed" state:

    > setld -i | grep OSFPATC0040901540
    OSFPATC0040901540 load completed Patch: Fix for SSRT3629B, ssh (Security Related Patches)

    I booted single user to use dupatch to delete the patch, but now dupatch doesn't think it's installed:

    # dupatch -delete -name x -note x -patch C409.01
     Patch "C409.01" for Tru64_UNIX_V5.1B is not installed on your system.
     There are no deletable patches as specified on the command line.

    Also, if I do a "dupatch -track -type patch" it doesn't show this patch in the installed list.

    Somehow dupatch and setld seem to have a different list of patches that are applied.

    Any ideas?

  • Next message: Siebert, Aaron: "Failed udp response"

    Relevant Pages

    • SUMMARY: Removing a corrupt patch
      ... No idea why the two tools see different patch databases, ... and finbally reinstall the patch using dupatch. ... Now both setld and dupatch can see the patch and ssh is operating correctly. ... First, have a good backup and second, do this with caution! ...
      (Tru64-UNIX-Managers)
    • SUMMARY: More 4.0F PK8 patchkit installation woes
      ... Thanks to those who replied - Iain Barker, Pat O'Brien, and especially John ... It seems the problem (i.e. that of long list of complaints from dupatch ... override in baselining makes patch backout complicated. ... Lindsay ...
      (Tru64-UNIX-Managers)
    • P.K.#2 for v.5.1b automated instl. failed leaving machine unpatchable.
      ... I have tried to install the whole patch kit #2 to a freshly-installed ... "dupatch" looped more tan 14 hours and created some 60000 ... Obvious solution is to re-install the painfully customized O.S., ... [Some of the other machines went through automated patch installation ...
      (comp.unix.tru64)