# Older packages missing in repositories

**URL:** <https://forums.rockylinux.org/t/older-packages-missing-in-repositories/12267>\
**Category:** Rocky Linux Help & Support\
**Tags:** rocky-linux-9\
**Created:** [December 22, 2023, 1:20pm UTC](https://forums.rockylinux.org/t/older-packages-missing-in-repositories/12267 "2023-12-22T13:20:38Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![cloos](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/cloos/32/2896_2.png) [@cloos](https://forums.rockylinux.org/u/cloos)\
**Post date:** [December 22, 2023, 1:20pm UTC](https://forums.rockylinux.org/t/older-packages-missing-in-repositories/12267/1 "2023-12-22T13:20:38Z")

</div>

Why are packages removed from the repositories?

For example in [Index of /pub/rocky/9.3/BaseOS/x86\_64/os/Packages/k/](http://dl.rockylinux.org/pub/rocky/9.3/BaseOS/x86_64/os/Packages/k/) there was once the `kernel-5.14.0-362.8.1.el9_3.x86_64.rpm` package, but now there is only the latest kernel package `kernel-5.14.0-362.13.1.el9_3.x86_64.rpm`.

---

<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:** [December 22, 2023, 1:34pm UTC](https://forums.rockylinux.org/t/older-packages-missing-in-repositories/12267/2 "2023-12-22T13:34:01Z")

</div>

That is the Rocky way; only keep the latest rather than adding more.

The 362.8.1 was the first kernel of 9.3 and the first versions do remain in [Index of /pub/rocky/9.3/BaseOS/x86\_64/kickstart/Packages/k/](http://dl.rockylinux.org/pub/rocky/9.3/BaseOS/x86_64/kickstart/Packages/k/)

---

<div class="post-metadata">

**Author:** ![cloos](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/cloos/32/2896_2.png) [@cloos](https://forums.rockylinux.org/u/cloos)\
**Post date:** [December 22, 2023, 1:38pm UTC](https://forums.rockylinux.org/t/older-packages-missing-in-repositories/12267/3 "2023-12-22T13:38:01Z")

</div>

But how can I then downgrade to a older version of a package?

---

<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:** [December 22, 2023, 2:35pm UTC](https://forums.rockylinux.org/t/older-packages-missing-in-repositories/12267/4 "2023-12-22T14:35:10Z")

</div>

> [@jlehtone](#):
>
> That is the Rocky way; only keep the latest rather than adding more.

This is not a useful response and does not help nor explain to the original poster why Rocky Linux 9 does not have the older packages.

> [@cloos](#):
>
> Why are packages removed from the repositories?

> [@cloos](#):
>
> But how can I then downgrade to a older version of a package?

This is unfortunately a quirk of the current build system we use for 9. See our wiki page here: [Rocky Linux Repositories - Rocky Linux Wiki](https://wiki.rockylinux.org/rocky/repo/#version-policy)

To downgrade you can try to use the kickstart repositories as they are a snapshot. Alternatively, we keep older packages in koji. [kernel | Package Info | Rocky Linux Build Service](https://kojidev.rockylinux.org/koji/packageinfo?packageID=202)

---

<div class="post-metadata">

**Author:** ![cloos](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/cloos/32/2896_2.png) [@cloos](https://forums.rockylinux.org/u/cloos)\
**Post date:** [December 22, 2023, 2:50pm UTC](https://forums.rockylinux.org/t/older-packages-missing-in-repositories/12267/5 "2023-12-22T14:50:53Z")

</div>

Thanks for the explanation and links.

---

<div class="post-metadata">

**Author:** ![neil](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/neil/32/34_2.png) [@neil](https://forums.rockylinux.org/u/neil)\
**Post date:** [December 22, 2023, 4:37pm UTC](https://forums.rockylinux.org/t/older-packages-missing-in-repositories/12267/6 "2023-12-22T16:37:18Z")

</div>

we’re working to address, specifically, the ‘keep old versions around’ thing with a rewrite of the underlying storage for the build system which will be started on in earnest in 2024 (January 🙂 )

The other idea I have been thinking about is to add a search functionality to our build system for 9 (Peridot) which will allow folks to find specific builds they are looking for, in the meantime.

I definitely understand this pain point, and we’re working to try and alleviate it and fix it for good, in time.

---

<div class="post-metadata">

**Author:** ![Ritov](https://avatars.discourse-cdn.com/v4/letter/r/3ec8ea/32.png) [@Ritov](https://forums.rockylinux.org/u/Ritov)\
**Post date:** [December 23, 2023, 12:48pm UTC](https://forums.rockylinux.org/t/older-packages-missing-in-repositories/12267/7 "2023-12-23T12:48:12Z")

</div>

> [@label](#):
>
> To downgrade you can try to use the kickstart repositories as they are a snapshot. Alternatively, we keep older packages in koji. [kernel | Package Info | Rocky Linux Build Service](https://kojidev.rockylinux.org/koji/packageinfo?packageID=202)

I assumed that RL9 packages are build in Peridot. Now, I see this koji instance. Just out of interest; do you use both tools to generate packages/composes/repos for RL9?

---

<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:** [December 23, 2023, 1:57pm UTC](https://forums.rockylinux.org/t/older-packages-missing-in-repositories/12267/8 "2023-12-23T13:57:14Z")

</div>

Koji is used to build and compose for 8. Peridot is used to build and compose for 9. Koji is only used as a secondary storage/backup for 9, meaning no builds happen for 9 in koji.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\
**Post date:** [February 21, 2024, 1:57pm UTC](https://forums.rockylinux.org/t/older-packages-missing-in-repositories/12267/9 "2024-02-21T13:57:45Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
