Kernel Module: Be smarter when the pacman database is missing or outdated #35
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
applications/manjaro-settings-manager#35
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Created by: ghost
hi , i see pamac of what ever messed a bit with the DB pacman, i dont know what it was
but then i get 👍
http://i.imgur.com/5YvqHa4.png
its because DB is bit messed i notice, pacman -Syy fixed the thing i notice. but on translation
for Not supported is bit messed up.. i think i hear further those confusion like not supported..
but its likely more that the database not synced properly
after pacman -Syy
i get this 👍
http://i.imgur.com/dUur2cz.png
thats better, i know is something on pamac , have to see further on that before i fill :)
on matter, i see its status of te repo, the middle line.. but some users seems also read different..
I would say, Auto-sync option if the kernel module not see not more then 3 kernels. i mean online...
To suppose to act bit smarter... not supported some people read different.. but the middle line is not what they mean.. but i would say atmeast auto-sync feature to the database because if database bit messed up or what ever happend kernels dont show up as it should..
Then it said not supported. but is a minor not direct a issue only i see some here and there people talk about that. but issuie is more the mirror sync.
Created by: Kirek
Yes, I suppose msm should be a little smarter when the databases are missing or outdated, and prompt the user to update them.
Created by: Kirek
Fixed
github.com/manjaro/manjaro-settings-manager@c3be96d661