Closed bcook128 closed 1 year ago
Hello there π Thanks for submitting your first issue to the deb-get project π We'll try and take a look at your issue soon β²
In the meantime you might want to join the Wimpys World Discord π£ where we have a large community of Linux π§ enthusiasts and passionate open source developers π§βπ»
You might also be interested in following Wimpys World Twitch π‘ channel where Wimpy streams let's code video, including this project, several times a week. A back catalog of past live stream and other Linux related content is available on Wimpys World YouTube πΊ channel.
It is possible github has been having issues today. I just checked on jammy with the 0.3.7 release and got a clean update (although one package got an error on the first fetch, but since it is installed a second fetch (which normally would not happen because it would be cached and fresh) succeeded fine. However you shouldn't see those errors in the list
Can you please check if you have /var/cache/deb-get/updating_supported.lock
(and if you do, sudo rm /var/cache/deb-get/updating_supported.lock
)
and retry a deb-get update
?
Also, might you be hitting the problem fixed in #774 ?
Errors when running deb-get list after 0.3.7 update
Since 0.3.7 update, cannot produce a list of installed/available packages. Env DEBGET_TOKEN is set to valid github token.
Tried running:
Problem continues.
Expected behavior
Output list of available packages
Actual behavior
Steps to reproduce
Run command: deb-get list
System information
/etc/os-release
/etc/lsb-release
deb-get version
deb-get update