# How to deal with waiting for the channel in production environments?

**URL:** https://discourse.nixos.org/t/how-to-deal-with-waiting-for-the-channel-in-production-environments/33378
**Category:** Development
**Created:** [September 23, 2023, 12:48pm UTC](https://discourse.nixos.org/t/how-to-deal-with-waiting-for-the-channel-in-production-environments/33378 "2023-09-23T12:48:20Z")
**Posts on this page:** 1
**Showing post:** 16

<div class="post-metadata">

### Author: ![wamserma](https://discourse.nixos.org/user_avatar/discourse.nixos.org/wamserma/32/5353_2.png) [@wamserma](https://discourse.nixos.org/u/wamserma)
#### Post date: [September 24, 2023, 7:18pm UTC](https://discourse.nixos.org/t/how-to-deal-with-waiting-for-the-channel-in-production-environments/33378/16 "2023-09-24T19:18:01Z")

</div>

> [@SynQ](#):
>
> My question remains: what would be the best way to deal with packages lagging in the build process that cannot wait because of security updates?

If there is a reason you can not wait for the channel to update and you know that the update of package XY will not break any downstream packages you rely on, you can  
use `system.replaceRuntimeDependencies` as detailed here with a security-hotfix for OpenSSL: [OpenSSL 3.0.7 update (2022-11-01) FAQ](https://discourse.nixos.org/t/openssl-3-0-7-update-2022-11-01-faq/22875/1)

---

_[View the full topic](https://discourse.nixos.org/t/how-to-deal-with-waiting-for-the-channel-in-production-environments/33378)._