On 12/15/22 9:09 AM, Robert McBroom via users wrote:
On 12/14/22 22:45, home user wrote:
[... snip ...]
set /etc/dnf.conf to retain the kernels of several updates to give
rpmfusion time to catch up to new kernels in a new major grouping. Can
take a couple of weeks.
[main]
gpgcheck=1
installonly_limit=5
max_parallel_downloads=10
fastestmirror=True
clean_requirements_on_remove=true
keepcache=0
----
No such file...
------
-bash.9[~]: cat /etc/dnf.conf
cat: /etc/dnf.conf: No such file or directory
-bash.10[~]:
------
Do you mean /etc/dnf/dnf.conf?...
------
-bash.10[~]: cat /etc/dnf/dnf.conf
# see `man dnf.conf` for defaults and possible options
[main]
gpgcheck=True
installonly_limit=3
clean_requirements_on_remove=True
best=False
skip_if_unavailable=True
-bash.11[~]:
------
Is your suggestion to edit the "installonly_limit" value? If yes, is my
current setting (3) of that value sufficient?
I am not clear on what you mean by "in a new major grouping". Has RPM
Fusion already caught up to the current f36 kernel (6.0.5-200.fc36 or
whatever is now current) in a way that fixes the problems I encountered
on Nov. 03?
I have a system with a gtx 610 which uses the even older 390xx drivers.
Another uses the gt 710 with the 470xx drivers, both have been updated
on rpmfusion for weeks. Upgrades to f37 went smoothly
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
