-
Notifications
You must be signed in to change notification settings - Fork 134
Open
Description
I was trying to figure out why byobu is reporting updates available on CachyOS, which is basically Arch.
Here is what I could find:
❯ env |grep BYOBU
BYOBU_WINDOW_NAME=-
BYOBU_RUN_DIR=/dev/shm/byobu-valankar-Yr5oyLER
❯ ls -l /dev/shm/byobu-valankar-Yr5oyLER/cache.tmux
.rw-r--r-- 2 valankar 27 Apr 15:20 updates-available
.rw-r--r-- 0 valankar 27 Apr 12:54 updates-available.lock
❯ cat /dev/shm/byobu-valankar-Yr5oyLER/cache.tmux/updates-available
1
❯ ls -l /var/lib/pacman/sync/*.db
.rw-r--r-- 508k root 27 Apr 15:00 /var/lib/pacman/sync/cachyos.db
.rw-r--r-- 120k root 27 Apr 02:13 /var/lib/pacman/sync/core.db
.rw-r--r-- 8.0M root 27 Apr 15:14 /var/lib/pacman/sync/extra.db
.rw-r--r-- 139k root 24 Apr 20:14 /var/lib/pacman/sync/multilib.db
❯ pacman -Sup | grep -vc "^\(::\| \)"
0
❯ sudo pacman -Syu
[sudo] password for valankar:
:: Synchronizing package databases...
cachyos is up to date
core is up to date
extra is up to date
multilib is up to date
:: Starting full system upgrade...
there is nothing to do
It still reports 1! in the status bar despite no packages available.
I see the cache is only updated when the DB is newer:
byobu/usr/lib/byobu/updates_available
Line 120 in 34ca6fe
| [ "$db" -nt "$mycache" ] && return 0 |
But it seems the cache is never updated if that is not the case? That seems like it would stay like this forever.
Metadata
Metadata
Assignees
Labels
No labels