# Software Updates - communication, frequency, contents etc **URL:** \ **Category:** Rocky Linux Help & Support\ **Created:** [April 19, 2023, 11:29pm UTC](https://forums.rockylinux.org/t/software-updates-communication-frequency-contents-etc/9636 "2023-04-19T23:29:15Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![LinuxFTW](https://avatars.discourse-cdn.com/v4/letter/l/0ea827/32.png) [@LinuxFTW](https://forums.rockylinux.org/u/LinuxFTW)\ **Post date:** [April 19, 2023, 11:29pm UTC](https://forums.rockylinux.org/t/software-updates-communication-frequency-contents-etc/9636/1 "2023-04-19T23:29:16Z")
I have said multiple times now in the last three weeks “wow, that’s a lot of updating of the OS!” So, just thought I’d ask a couple questions. (Ihave Rocky 9.1 Onyx installed) 1. Where do I go to see what is included in the OS update? 2. Why are there so many OS updates - i.e. frequency is weekly / biweekly? I find the frequency to be inconvenient if these are not emergency patches or updates Thanks in advance for any answer to these questions. ---
**Author:** ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)\ **Post date:** [April 20, 2023, 12:07am UTC](https://forums.rockylinux.org/t/software-updates-communication-frequency-contents-etc/9636/2 "2023-04-20T00:07:02Z")
1. You can view the change logs of the packages by issuing `rpm -i --changelog` - More details of the sources are in our [git](https://git.rockylinux.org/staging/rpms). 2. We issue updates typically as Red Hat issues them. This can happen any day of the week (normally not on the weekends). We strive to have updates out within 24-48 hours. See our [wiki](https://wiki.rockylinux.org/rocky/version/#general-update-timeline) for more information. ---
**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\ **Post date:** [April 20, 2023, 5:56am UTC](https://forums.rockylinux.org/t/software-updates-communication-frequency-contents-etc/9636/3 "2023-04-20T05:56:22Z")
Since most updates are due to what Red Hat issues, you can also browse their erratas: [Red Hat Customer Portal - Access to 24x7 support and knowledge](https://access.redhat.com/errata-search/#/?q=&p=1&sort=portal_publication_date%20desc&rows=10&portal_product=Red%20Hat%20Enterprise%20Linux&portal_product_version=9&portal_architecture=x86_64) ---
**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:** [April 20, 2023, 6:49pm UTC](https://forums.rockylinux.org/t/software-updates-communication-frequency-contents-etc/9636/4 "2023-04-20T18:49:58Z")
You can also find our errata at [https://errata.rockylinux.org](https://errata.rockylinux.org) ---
**Author:** ![Ritov](https://avatars.discourse-cdn.com/v4/letter/r/3ec8ea/32.png) [@Ritov](https://forums.rockylinux.org/u/Ritov)\ **Post date:** [April 20, 2023, 7:45pm UTC](https://forums.rockylinux.org/t/software-updates-communication-frequency-contents-etc/9636/5 "2023-04-20T19:45:08Z")
Not criticizing just an observation - the errata are quite late updated. Speak, updates already available/installed, then days later the errata? Is this known? ---
**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:** [April 20, 2023, 9:19pm UTC](https://forums.rockylinux.org/t/software-updates-communication-frequency-contents-etc/9636/6 "2023-04-20T21:19:33Z")
You’re 100% right. It’s something we’re working to close the gap on. The short explanation is that there have been a lot of issues with the RH errata api in recent months and we’ve had to go back and fetch them. Along with this, we’re under way on some revisions to our build system in order to fully integrate the errata subsystem with the rest of the build and compose functions in order to make sure we keep the errata and packages in lock step. I apologize for the recent delay, as it’s been mostly due to my being spread a bit thin. I’m posting discussions on our github repo this weekend for Peridot related to these sorts of features, and we’d love feedback about what the users want, especially w.r.t. errata. I’ll comment back here with a link to the relevant discussion(s) when they’re posted. ---
**Author:** ![illuminatus](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/illuminatus/32/716_2.png) [@illuminatus](https://forums.rockylinux.org/u/illuminatus)\ **Post date:** [April 20, 2023, 10:02pm UTC](https://forums.rockylinux.org/t/software-updates-communication-frequency-contents-etc/9636/7 "2023-04-20T22:02:53Z")
In addition to checking [https://errata.rockylinux.org](https://errata.rockylinux.org) you can do some minor investigation on the command line to determine which of all the available packages are enhancements, bugfixes or security issues as well as severity can also be investigated more closely. 1. Check which packages are enhancements `dnf check-update --enhancement` 2. Check which packages fix bugs with `dnf check-update --bugfix`. 3. Check which packages fix security issues with `dnf check-update --security` 4. Check the specific severity level of fixes by using **one** of the following severity levels `dnf check-update --sec-severity [Critical|Important|Moderate|Low]` ---
**Author:** ![illuminatus](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/illuminatus/32/716_2.png) [@illuminatus](https://forums.rockylinux.org/u/illuminatus)\ **Post date:** [April 20, 2023, 10:07pm UTC](https://forums.rockylinux.org/t/software-updates-communication-frequency-contents-etc/9636/8 "2023-04-20T22:07:41Z")
For feedback: I noticed that the `--advisory` and `--cve` flags didnt seem to be working w/ `dnf update` even when listed on [https://errata.rockylinux.org](https://errata.rockylinux.org). Not sure if it also related to the RH errata api changes, but I’ll go ahead and mention I would love to have both flags working for patching all packages applicable to the specific errata and cve id. Once the discussion link is posted I’ll add comments there and any additional requests/findings. Thanks ---
**Author:** ![label](https://avatars.discourse-cdn.com/v4/letter/l/c5a1d2/32.png) [@label](https://forums.rockylinux.org/u/label)\ **Post date:** [April 21, 2023, 12:26am UTC](https://forums.rockylinux.org/t/software-updates-communication-frequency-contents-etc/9636/9 "2023-04-21T00:26:05Z")
```auto [root@xmpp01 ~]# dnf update --advisory RLSA-2023:1368 Last metadata expiration check: 0:41:55 ago on Thu 20 Apr 2023 04:34:44 PM MST. Dependencies resolved. ================================================================================================================================================================ Package Architecture Version Repository Size ================================================================================================================================================================ Upgrading: nspr x86_64 4.34.0-18.el9_1 appstream 135 k nss x86_64 3.79.0-18.el9_1 appstream 703 k nss-softokn x86_64 3.79.0-18.el9_1 appstream 379 k nss-softokn-freebl x86_64 3.79.0-18.el9_1 appstream 330 k nss-sysinit x86_64 3.79.0-18.el9_1 appstream 20 k nss-tools x86_64 3.79.0-18.el9_1 appstream 428 k nss-util x86_64 3.79.0-18.el9_1 appstream 88 k Transaction Summary ================================================================================================================================================================ Upgrade 7 Packages Total download size: 2.0 M Is this ok [y/N]: n [root@xmpp01 ~]# dnf update --cve CVE-2023-0767 Last metadata expiration check: 0:01:25 ago on Thu 20 Apr 2023 05:19:24 PM MST. Dependencies resolved. ================================================================================================================================================================ Package Architecture Version Repository Size ================================================================================================================================================================ Upgrading: nspr x86_64 4.34.0-18.el9_1 appstream 135 k nss x86_64 3.79.0-18.el9_1 appstream 703 k nss-softokn x86_64 3.79.0-18.el9_1 appstream 379 k nss-softokn-freebl x86_64 3.79.0-18.el9_1 appstream 330 k nss-sysinit x86_64 3.79.0-18.el9_1 appstream 20 k nss-tools x86_64 3.79.0-18.el9_1 appstream 428 k nss-util x86_64 3.79.0-18.el9_1 appstream 88 k Transaction Summary ================================================================================================================================================================ Upgrade 7 Packages Total download size: 2.0 M Is this ok [y/N]: ``` Do you mean like this? There are cases where the errata is not being applied (or available immediately upstream) which causes some information to be missing/latent in our own repos. This is part of the gaps we’re trying to close by trying to update our metadata as soon as its available within a reasonable time frame. ---
**Author:** ![LinuxFTW](https://avatars.discourse-cdn.com/v4/letter/l/0ea827/32.png) [@LinuxFTW](https://forums.rockylinux.org/u/LinuxFTW)\ **Post date:** [June 16, 2023, 1:40pm UTC](https://forums.rockylinux.org/t/software-updates-communication-frequency-contents-etc/9636/10 "2023-06-16T13:40:53Z")
Thanks for the reply. I appreciate the answer of 'reflecting the frequency of RH releases." Makes sense! ---
**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:00am UTC](https://forums.rockylinux.org/t/software-updates-communication-frequency-contents-etc/9636/11 "2023-08-25T03:00:04Z")