We are encountering disk space issues so I've decided it might be time to clean up the expired updates in our update packages :)
What's the simplest way of accomplishing this? I was thinking I go into each package, find the expired updates, edit their membership to remove them from the SUGs and then delete them. There should be no risk in doing this because expired updates cannot be deployed correct? Should I also consider removing superseded updates or is there more of a risk with those? Eg. unlike expired updates they're still deployable so I risk deleting a superseded update in which its successor might not have been deployed! Daniel. ********************************************************************* This email, including any attachment, is confidential to the intended recipient. It may also be privileged and may be subject to copyright. If you have received this email in error, please notify the sender immediately and delete all copies of the email. Any confidentiality or privilege is not waived. Neither the Council nor the sender warrant that this email does not contain any viruses or other unsolicited items. This email is an informal Council communication. The Council only accepts responsibility for information sent under official letterhead and duly signed by, or on behalf of, the Chief Executive Officer. Privacy Collection Notice Logan City Council may collect your personal information, e.g. name, residential address, phone number etc, in order to conduct its business and/or meet its statutory obligations. The information will only be accessed by employees and/or Councillors of Logan City Council for Council business related activities only. If your personal information will be passed onto a third party, Council will advise you of this disclosure, the purpose of the disclosure and reason why. Your information will not be given to any other person or agency unless you have given us permission or we are required by law.
