# Unable to Downgrade Packages, only Newest Kernel Available?

**URL:** <https://forums.rockylinux.org/t/unable-to-downgrade-packages-only-newest-kernel-available/7979>\
**Category:** Rocky Linux Help & Support\
**Created:** [November 23, 2022, 2:38am UTC](https://forums.rockylinux.org/t/unable-to-downgrade-packages-only-newest-kernel-available/7979 "2022-11-23T02:38:31Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![benjoshyo](https://avatars.discourse-cdn.com/v4/letter/b/9f8e36/32.png) [@benjoshyo](https://forums.rockylinux.org/u/benjoshyo)\
**Post date:** [November 23, 2022, 2:38am UTC](https://forums.rockylinux.org/t/unable-to-downgrade-packages-only-newest-kernel-available/7979/1 "2022-11-23T02:38:31Z")

</div>

I just spun up an instance of Rocky 9 in AWS. I was super excited to give it a try. Our policy dictates that we install CrowdStrike Falcon on our instances. For this, I need to make sure that we keep to specific kernel versions. After spinning it up, I’m only seeing an update to the most recent kernel version available (5.14.0-70.30.1.el9\_0.x86\_64).

I thought this was a little weird, as there are multiple versions in between the image and 70.30.1.

I put in some test configurations for some basic things, updated, and my nginx configuration stopped working. I attempted to downgrade nginx, and received the message:

> Package nginx of lowest version already installed, cannot downgrade it.

A quick search of the forums returned this [post](https://forums.rockylinux.org/t/old-package-archive-planned/7491/2).

Am I to understand that older packages are not kept in the repos? If something breaks or I need to install an intermediate version, is my only option to build the lower package from source? Or is there a better way?

---

<div class="post-metadata">

**Author:** ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)\
**Post date:** [November 23, 2022, 2:44am UTC](https://forums.rockylinux.org/t/unable-to-downgrade-packages-only-newest-kernel-available/7979/2 "2022-11-23T02:44:10Z")

</div>

Older packages are not kept in the repositories for Rocky Linux 9 at this time. There is a way to pull older artifacts from the build system, but unfortunately it is complex to do so.

[Rocky Linux Version Policy](https://wiki.rockylinux.org/rocky/repo/#version-policy)  
[Peridot Issue 18](https://github.com/rocky-linux/peridot/issues/18)

@mustafa would have a better answer for you.

---

<div class="post-metadata">

**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\
**Post date:** [November 23, 2022, 7:50am UTC](https://forums.rockylinux.org/t/unable-to-downgrade-packages-only-newest-kernel-available/7979/3 "2022-11-23T07:50:11Z")

</div>

The dnf seeks `BaseOS/$basearch/os` that has the _latest_ version,  
but there is `BaseOS/$basearch/kickstart` that has the _first_ version of the point update.

Is there a way to redirect dnf other than edit of \*.repo -files?

Obviously, if one needs some interim version, then that does not help. Nor if security is important.

@benjoshyo Can you spun up clones of instance that has the “correct version”?

---

<div class="post-metadata">

**Author:** ![brian](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/brian/32/5777_2.png) [@brian](https://forums.rockylinux.org/u/brian)\
**Post date:** [August 25, 2023, 3:33am UTC](https://forums.rockylinux.org/t/unable-to-downgrade-packages-only-newest-kernel-available/7979/4 "2023-08-25T03:33:34Z")

</div>