Use non-redirecting link for archive.org

source/posts/2014-02-24-deploy-package-not-just-tag-branch-or-binary.html.markdown.erb

@@ -21,7 +21,7 @@ We concur. This is a good example of cross-pollination of good ideas between dev
 2.   Dependency management.
 3.   Distribution via standardized repository layouts, metadata and protocol.
 4.   Transactional install/upgrade/uninstall via package managers.
-5.   Managing configuration files: OS packages know how to manage files that are expected to change after installation so you don't lose your changes when you uninstall or override when you upgrade. e.g. rpm's [%config macro](https://web.archive.org/web/https://www-uxsup.csx.cam.ac.uk/~jw35/docs/rpm_config.html).
+5.   Managing configuration files: OS packages know how to manage files that are expected to change after installation so you don't lose your changes when you uninstall or override when you upgrade. e.g. rpm's [%config macro](https://web.archive.org/web/20230926132600/http://www.cl.cam.ac.uk/~jw35/docs/rpm_config.html).
 6.   File verification: Packages have built-in checksums, which can be used for verification before a package is extracted and installed.
 7.   Signature verification (e.g. [rpm](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/deployment_guide/s1-check-rpm-sig)).
 8.   Idempotence - Issuing the same package install/upgrade/uninstall multiple times leaves the system in the same state as issuing it once.