deb-get: Can't update/upgrade - /var/cache/deb-get/deb-get.json empty
Can’t update/upgrade - /var/cache/deb-get/deb-get.json empty
can’t install with one line install : curl -sL https://raw.githubusercontent.com/wimpysworld/deb-get/main/deb-get | sudo -E bash -s install deb-get
I’s not the first time. Sometimes work, sometimes not. Today, i’m blocked. Yesterday everything good. I’ts not the first time it happens to me. Seems like a down server (?)
Expected behavior
Download new content of deb-get.json
Actual behavior
Error - can’t use deb-get.
Steps to reproduce
deb-get update deb-get upgrade
System information
Run the following a paste the output below:
/etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
deb-get version
0.3.8
deb-get update
[+] Updating /etc/deb-get/01-main
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 108k 0 108k 0 0 175k 0 --:--:-- --:--:-- --:--:-- 351k
[+] Updating cache of supported apps in the background
[+] Updating /var/cache/deb-get/deb-get.json
[*] WARNING! Updating /var/cache/deb-get/deb-get.json failed.
[*] WARNING! Cached file /var/cache/deb-get/deb-get.json is empty or missing.
Thank you for this must have tool. Sorry for reporting a trouble.
About this issue
- Original URL
- State: open
- Created a year ago
- Comments: 17 (9 by maintainers)
I get it consistently too. initial setup is impossible without the DEBGET_TOKEN set either, it just sits there stuck. may be worth adding a warning that failing to set it will slow things down considerably or fail gracefully.
also, I have an extra error there:
seems $ETC_DIR and $ELEVATE need to be exported before used in the subshell around lines 710-720. I’ll make a PR.
Thanks for the feedback.
It may be that you haven’t set up an API key for github - this is effectively required now that so many repos are supported unless you set a much longer cache retention time (e.g.
export DEBGET_CACHE_RTN=240- minutes, defaults to 60 ) and then repeat theupdatewhen you have refreshed the rate-limit allowance. (See https://github.com/wimpysworld/deb-get#github-api-rate-limits ) Another possibility is some temporary outage at github (I’ve seen a few of those either with github timing out or occasionally with a particular app being mid-workflow of a release and being temporarily “broken” until the release .deb asset is built) . In those cases a little patience and retry later is all I can suggest.